<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Jan!</p>
<p>You and Denis are arguing that registration/user data needs to
include certain (sometimes sensitive details (ie: PII)) that need
to be put in the database. Your Argument is that this is a policy
requirement.</p>
<p>When I tried to get both of you to spell out what this "user
data"/"contact information" is exactly and where that is defined -
We do not get a clear answer.</p>
<p>I have read every single of denis replies/comments.</p>
<p></p>
<p>When asked, neither of you cannot reference a policy section that
actually spells out what is considered "contact details".</p>
<p>According to your own e-mail - your opinion is based on a
software interface/implementation (ripe-db). This interface itself
is an interpretation of what the policy could mean.<br>
The Interface of the DB also does not specify what kind of
Information (regular address, proxy address,...) needs to be
inserted. Just that some fields need to be filled out (and its
open to interpret what goes into them to a certain extent - wich
is the point of this discussion).<br>
</p>
<p>The relationship is policy -to- database. Not Database -to-
Policy. <br>
</p>
<p>And yet, we have no document or reference that defines what kind
of contact information (direct only, or indirect via
proxy/masking/....) is permissable.<br>
Just that it needs to be maintained (meaning "if it works" ->
OK). <br>
In my previous e-mail i did argue that in some scenarios working
witout"proxy" data is impossible (think: Role/NOC Contacts).</p>
<p>I have also read your reference
<a class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-705">https://www.ripe.net/publications/docs/ripe-705</a> . It defines an
abuse inbox is mandatory for certain objects. And that it has to
be an email address. - Nothing else.</p>
<p>Regards</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/12/24 09:40, Jan Ingvoldstad
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEffzkxyzi3Foe9pEVz9weCSzzMh68jCV1adpctmDPZfQ1rgmw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div id="gmail-:2yi" style="user-select: none;"
class="gmail-ajR" role="button" tabindex="-1"
aria-label="Show trimmed content">
<div id="gmail-:2pc" class="gmail-uC"><img class="gmail-ajT"
src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"
moz-do-not-send="true">On Fri, Jan 12, 2024 at 9:28 AM
Sebastian Graf <<a
href="mailto:ripe-lists@sebastian-graf.at"
moz-do-not-send="true" class="moz-txt-link-freetext">ripe-lists@sebastian-graf.at</a>>
wrote:<br>
</div>
</div>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Dear Jan!<br>
</p>
</div>
</blockquote>
<div><br>
</div>
<div>Dear Sebastian, <br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p> </p>
<p>Thank you for your reply. But you have not answerred my
question.<br>
</p>
</div>
</blockquote>
<div>I answered your question, but I did not understand that
you intended your ancillary comment as an additional
question. Sorry about that.<br>
</div>
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p> </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><br>
</p>
</div>
</blockquote>
<div>As I understand it, this comes from how contact objects
are defined in the database, and this is what RIPE-804
references.</div>
<div><br>
</div>
<div>Denis has provided more detailed context.</div>
<div><br>
</div>
<div>RIPE-705 sets specific requirements regarding abuse
contact details.<br>
</div>
</div>
<br>
<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>