Publication of Sponsoring LIR for Independent Number Resources

Slides:

Advertisements

Similar presentations

Axel Pawlik. LACNIC IV, 25 April 2003, Santiago. 1 Update from the RIPE NCC.

Advertisements

Kuala Lumpur February 2004 APNIC 17 Kuala Lumpur February 2004 APNIC 17 IPv4 /8 Address Space Status.

Erik Bais, May 15 th 2013 PP Resource Certification for non-RIPE NCC Members Presenter : Erik Bais –

Registration Services Feedback Andrea Cima RIPE NCC RIPE 66 - Dublin.

Operational Policies for NIRs in the APNIC Region NIR Meeting APNIC14, Kitakyushu, Japan 4 Sept 2002.

Protecting Resource Records in APNIC Whois Database Database SIG APNIC-16, Seoul August 2003 Sanjaya

AfriNIC Anti-Abuse Group S. Moonesamy AfriNIC 11 November

Role and responsibility of internet intermediaries in the field of trademarks Federation of Swiss Watch Industry FH Geneva, 17th September 2012.

1IPv6 Day in Armenia, Yerevan, June 6, IPv6 Day in Armenia I.Mkrtumyan ISOC AM.

APNIC Internet Routing Registry Routing SIG APNIC-15, Taipei 26 February 2003.

Nigel Titley. RIPE 54, 9 May 2007, Tallinn, Estonia. 1 RIPE NCC Certification Task Force Update Presented by Nigel Titley RIPE NCC.

NCC Services to PI Resource Holders RIPE / Dublin Axel Pawlik Randy Bush Services to PI 1.

Publication of Sponsoring Organisationfor Direct Assignments 2012-XX Nick Hilliard David Freedman.

Update about the “SHOULDs Analysing Project” in RIPE Policy Documents “Should” we use the RFC 2119 Defined Language in RIPE Policy Documents? Jan Žorž,

Проект IPv6 сети RUNNet Владимир, апреля 2006 г. Гугель Юрий, ФГУ ГНИИ ИТТ «Информика»________________ Не говорю о: О протоколе IPv6 О том, как это.

December 2013 Internet Number Resource Report. December 2013 Internet Number Resource Report INTERNET NUMBER RESOURCE STATUS REPORT As of 31 December.

March 2014 Internet Number Resource Report. March 2014 Internet Number Resource Report INTERNET NUMBER RESOURCE STATUS REPORT As of 31 March 2014 Prepared.

Database Update Kaveh Ranjbar Database Department Manager, RIPE NCC.

1 Axel Pawlik APNIC 22, 8 September 2006, Kaohsiung RIPE NCC Update APNIC 22.

RIPE Network Coordination Centre ISOC 2007/IPv6 Forum, Tel Aviv, Feb Arno Meulenkamp IP Resource Statistics & IPv6 Policy Update.

Update on RIPE NCC Inter- RIR Transfer proposal Adam Gosling APNIC 38 Policy SIG Meeting 18 September 2014.

A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E Database SIG APNIC Database Privacy Issues 1 March 2001 APRICOT, Malaysia Fabrina.

Database Update Paul Palse Database Manager, RIPE NCC.

IP address Allocation & and Requests AfNOG Workshop, May 2004 Dakar, Senegal.

Mirjam Kühne 1 RIPE 33, May 1999 Introduction to the RIPE NCC presented by Mirjam Kühne.

NATO Advanced Networking Workshop. Ljubljana, 19 September RIPE whois Database RIPE Network Coordination Centre.

Erik Bais, May 13 th 2015 PP – unassigned yet General Transfer Policy Presenter : Erik Bais –

1 To Insert AS Origin field into APNIC IP address database Xing Li Shuang Zhu CERNET

Abuse-c Update Denis Walker Database Department, RIPE NCC.

Rough Edges of Current Policies Alex Le Heux RIPE NCC Rome.

Contractual Relationship Requirements for End Users Implementation Update:

Leo vegoda. APNIC 14, 3–6 Sept. 2002, Kitakyushu, Japan. 1 RIPE NCC Status Report at APNIC 14 Looking forward to winter…

Horses for courses- like IPv6 profiles for german administration Constanze Bürger Bundesministerium des Innern.

Update of WHOIS Data Privacy in JP Izumi Okutani Japan Network Information Center (JPNIC) DB SIG APNIC Indonesia.

Erik Bais, May 5 th 2011 PP Removal of multihomed requirement for IPv6 Presenter : Erik Bais –

Current Policy Topics Emilio Madaio RIPE NCC RIPE November 2010, Rome.

Contractual Relationship Requirement for End Users Implementation update policy proposal

Registration Services Feedback Andrea Cima RIPE NCC RIPE 67 - Athens.

1 The Internet Registry System Mirjam Kühne RIPE NCC EC-POP Brussels 5 July 1999.

17 th APNIC Open Policy Meeting APNIC IPv6 Address Guidelines Akira Nakagawa )/ POWEREDCOM Billy MH Cheon / KRNIC Toshiyuki.

Abuse-c update Denis Walker Business Analyst RIPE NCC Database Team.

Contractual Relationship Requirements for End Users Implementation Update: Policy Proposal

Update from the RIPE NCC Axel Pawlik Managing Director.

Whois & Data Accuracy Across the RIRs. Terms ISP – An Internet Service Provider is allocated address space by an RIR for the purpose of providing connectivity.

Veronika McKillop, UK IPv6 Council

November 2006 Geoff Huston APNIC

IPv6 address deployment status Paul Wilson, APNIC

Legacy Resources in the Research & Education Community

Addressing 2016 Geoff Huston APNIC.

IPv6 address deployment status Paul Wilson, APNIC

AFRINIC Services Update

Project Management Processes for a Project

ارگونومی کار با کامپیوتر

RIPE Whois Database Software Recent Changes

A Proposal for IPv4 Essential Infrastructure

Internet Routing Registry daemon version 4

Progress Report on Resource Certification

IPv6 Policy and Allocation Update

A view from ARIN, LACNIC & RIPE Communities Laura Cobley

PERSON objects in the RIPE Database

Publication of Legal Address of Internet Number Resource Holders

A Proposal to Protect Historical Records in APNIC Whois Database

Status Update Presented By Ray Plzak On Behalf Of AfriNIC.

IPv6 distribution and policy update

1 Not a question, just a remark

Private Information Handling at APNIC Database

© 2018 The Hartford. Classification: Internally Controlled

Whois Database Upgrade

PP Allow AS Number Transfers

By Keessun Fokeerah Member Services(MS) Team

Presentation transcript:

Publication of Sponsoring LIR for Independent Number Resources 2012-08 Nick Hilliard

RIPE 452 + RIPE 556 +

Pay no attention…. The object still exists (452) inetnum: 91.198.120.0 - 91.198.120.255 netname: YTTI-NET-FI descr: T:mi Ytti remarks: Hosting country: FI org: ORG-YA14-RIPE admin-c: YTTI-RIPE tech-c: YTTI-RIPE status: ASSIGNED PI notify: saku@ytti.fi mnt-by: RIPE-NCC-END-MNT mnt-by: YTTI-RIPE-MNT mnt-lower: RIPE-NCC-END-MNT mnt-routes: YTTI-RIPE-MNT mnt-domains: YTTI-RIPE-MNT changed: hostmaster@ripe.net 20070918 changed: hostmaster@ripe.net 20121022 source: RIPE organisation: ORG-YA14-RIPE org-name: T:mi Ytti org-type: OTHER The object still exists (452) The EU has been verified (556) THEN WHO WAS SPONSOR? showcased by kind permission, T:mi Ytti

Why do you care? Isn’t this supposed to be some kind of… registry? Why have a process if you won’t document the outcome? Without knowing the outcome, how do you help resource holders (who may be current or potential customers) without directing them to the NCC? Why isn’t this published? Surely there is nothing to hide? Why should this create any support/privacy exception?

Sponsorship reflected as ORG inetnum: 91.198.120.0 - 91.198.120.255 netname: YTTI-NET-FI descr: T:mi Ytti remarks: Hosting country: FI org: ORG-YA14-RIPE sponsoring-org: ORG-SNO1-RIPE admin-c: YTTI-RIPE tech-c: YTTI-RIPE status: ASSIGNED PI notify: saku@ytti.fi mnt-by: RIPE-NCC-END-MNT mnt-by: YTTI-RIPE-MNT mnt-lower: RIPE-NCC-END-MNT mnt-routes: YTTI-RIPE-MNT mnt-domains: YTTI-RIPE-MNT changed: hostmaster@ripe.net 20070918 changed: hostmaster@ripe.net 20121022 source: RIPE organisation: ORG-YA14-RIPE org-name: T:mi Ytti org-type: OTHER organisation: ORG-SNO1-RIPE org-name: TDC Oy Finland org-type: LIR 2012-08 in review phase. Impact analysis complete! Updates to database needed. Updates to RIPE-559 needed.