<html><head></head><body><div class="ydp89e6b83byahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Colleagues</div><div><br></div><div>Someone has kindly referred me to the conversation you had last November on this same paragraph 6.2. It's not surprising that there is some reluctance to discuss it again. BUT this is a different discussion. Last time you focussed on defining what type of network needs to be separately registered in the RIPE Database. I want to discuss the next step from that. Once you have decided a type of network needs to be separately registered then what information about that network needs to be entered into the RIPE Database?</div><div><br></div><div><br></div><div>I will come straight to the point, which should be controversial enough to start a discussion :) MY interpretation of the wording in 6.2 is that the policy, as written, requires an ORGANISATION object to be created for these End Users if you register their network in the RIPE Database.</div><div><br></div><div><br></div><div>Let me explain my reasoning for this interpretation. The policy refers to the End User as either an individual or an organisation. In other words the End User is the '(legal) entity' that operates the network. Just as the LIR is the (legal) entity that holds the allocation resource. So when the policy requires the contact details of the End User, it is requiring the contact details of this operating entity. That is not the "xxx-c" attributes in the INETNUM object, it is an ORGANISATION object details.</div><div><br></div><div><br></div><div>This takes us back to the long running discussion we had with "abuse-c:" where many members refused to create separate ORGANISATION objects for End Users just to add an "abuse-c:" for them. But as it is currently written, this is exactly what this policy requires. Perhaps the wording of this paragraph 6.2 doesn't reflect the original intent. So what we must now do is look again at this situation and answer 3 basic questions about these End Users:</div><div><br></div><div><br></div><div>1/ What information do we need/want to store about the End User?</div><div><br></div><div>2/ What is the reason for storing this information?</div><div><br></div><div>3/ Who needs this information?</div><div><br></div><div>If we can answer these basic questions then perhaps the policy needs to be updated.</div><div><br></div><div>cheers</div><div>denis</div><div><br></div><div>co-chair DB-WG</div><div><br></div><div><br></div>
</div><div id="ydp14f710b0yahoo_quoted_5647475549" class="ydp14f710b0yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, 15 April 2019, 16:18:33 CEST, ripedenis--- via address-policy-wg <address-policy-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp14f710b0yiv8926883586"><div><div class="ydp14f710b0yiv8926883586yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><span><div><br></div><div><br></div><div>6.2 Network Infrastructure and End User Networks</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></span></div></div></div></div></div>
</div>
</div></body></html>