<html><head></head><body><div><span><div>Colleagues,</div><div><br></div><div>Elvis, James and myself have started talking about personal data in the RIPE Database. I said we would bring sub issues to the community when we need direction or clarification. We looked at three policy documents maintained by AP-WG and have a few questions.</div><div><br></div><div>Before we look at WHERE and HOW the data is stored, we would like to get community feedback on exactly WHAT contact details should be published as per current policies?</div><div><br></div><div>Below are the quotes and links to the 3 policy documents we looked at.</div><div><br></div><div>cheers</div><div>denis</div><div>co-chair DB-WG</div><div><br></div><div><br></div><div>In the "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" (ripe-708) [1] first mention about contact data is 4.0:</div><div><br></div><div>"4.0 Registration Requirements</div><div><br></div><div>All assignments and allocations must be registered in the RIPE Database. This is necessary to ensure uniqueness and to support network operations. </div><div><br></div><div>Only allocations and assignments registered in the RIPE Database are considered valid. Registration of objects in the database is the final step in making an allocation or assignment. Registration data (range, contact information, status etc.) must be correct at all times (i.e. they have to be maintained)."</div><div><br></div><div>and then in 6.2:</div><div><br></div><div>"6.2 Network Infrastructure and End User Networks</div><div><br></div><div>IP addresses used solely for the connection of an End User to a service provider (e.g. point-to-point links) are considered part of the service provider's infrastructure. These addresses do not have to be registered with the End User's contact details but can be registered as part of the service provider's internal infrastructure. 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>[...]"</div><div><br></div><div>In the "IPv6 Address Allocation and Assignment Policy" (ripe-707) [2] the requirement is even more vague in 3.3:</div><div><br></div><div>"3.3. Registration</div><div><br></div><div>Internet address space must be registered in a registry database accessible to appropriate members of the Internet community. This is necessary to ensure the uniqueness of each Internet address and to provide reference information for Internet troubleshooting at all levels, ranging from all RIRs and IRs to End Users.</div><div><br></div><div>The goal of registration should be applied within the context of reasonable privacy considerations and applicable laws."</div><div><br></div><div>The "Autonomous System (AS) Number Assignment Policies" [3] does not mention anything about contact data requirements.</div><div><br></div><div>[1] https://www.ripe.net/publications/docs/ripe-708</div><div>[2] https://www.ripe.net/publications/docs/ripe-707</div><div>[3] https://www.ripe.net/publications/docs/ripe-679</div><div><br></div></span><br></div><div class="ydp6a53d6e7yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"></div></body></html>