1 / 3

Enhancing Sponsor-End User Relationship Transparency in RIPE Database

Learn about the publication of Sponsor Organisation for Direct Assignments in the RIPE database. Understand the requirements, tracking changes, and the proposal to publish linkage to the Sponsor. Explore the benefits and concerns related to this transparency.

nura
Download Presentation

Enhancing Sponsor-End User Relationship Transparency in RIPE Database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Publication of Sponsoring OrganisationforDirect Assignments 2012-XX Nick Hilliard David Freedman

  2. RIPE-452, 556, 559 • RIPE 452 introduces requirement for direct assignment “End User” to have contractual relationship with a “Sponsor” Organisation, this can be either an LIR or the RIPE NCC. • RIPE 556 and RIPE 559 define how the NCC identify and track changes to the particulars of the End User, through the Sponsor. • These details are published as an ORG object, thus the resources are linked to the ORG object of the End User. • No publishing of the linkage to the Sponsor currently exists, this proposal is to enable such publishing. • Proposal supporting arguments are use cases relating to alignment of registry goals, sponsorship confirmation / verification and abuse handling benefits. • Only opposing argument is that it reveals relationships that would otherwise have been kept private.

  3. Questions?

More Related