- db-wg - mailman.ripe.net

Update RIPE MNT records
by Mohamed Eldemiri 22 Feb '20

22 Feb '20

Hello RIPE support , In the past few years, our organization has gone through a privatization program by the government of Kuwait. Kuwait Stock Exchange has been changed now to Boursa Kuwait our old domain was kuwaitse.com is now boursakuwait.com.kw. The MNT ID and email is still pointing to old inaccessible domain ID, Anyway, the phone number & address are still the same, and the contact person still with Boursakuwait looped in this mail with his new email id 'ybaniyan(a)boursakuwait.com.kw'. Do you have any idea how to change these records? I have contacted the local registrar LR: Fast Telco and they said this must be done through the RIPE and they are not authorized to change these registration parameters. We will adhere to provide all the supporting official documents and memos that RIPE might asking for this change. LIR : Fast Telecommunications Company W.L.L. P.O.Box 287 15453 Dasman KUWAIT phone: +96522256666 fax: +96522401925 e-mail: ripeadmin (at) fasttelco (dot) net Areas serviced: KW 195.137.174.0/24 AS# 49104 Domain : BoursaKuwait.com.kw<https://dnslytics.com/bgp/as49104> % Abuse contact for '195.137.174.0 - 195.137.174.255' is 'abuse(a)fasttelco.net' inetnum: 195.137.174.0 - 195.137.174.255 netname: Kuwait-Stock-Exchange country: KW org: ORG-KSE1-RIPE admin-c: YA443-RIPE tech-c: YA443-RIPE status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-by: MNT-Kuwait-Stock-Exchange mnt-routes: MNT-Kuwait-Stock-Exchange mnt-domains: MNT-Kuwait-Stock-Exchange created: 2005-09-20T07:36:57Z last-modified: 2016-04-14T08:28:19Z source: RIPE # Filtered sponsoring-org: ORG-FTC1-RIPE organisation: ORG-KSE1-RIPE org-name: Kuwait Stock Exchange org-type: OTHER address: P.O. Box 22235 - Safat - Kuwait abuse-c: AR25180-RIPE mnt-ref: MNT-Kuwait-Stock-Exchange mnt-by: MNT-Kuwait-Stock-Exchange created: 2005-09-19T11:59:15Z last-modified: 2014-11-17T21:01:58Z source: RIPE # Filtered person: Yousef Abbas address: Kuwait City phone: +965 22992576 nic-hdl: YA443-RIPE created: 2009-07-27T06:57:06Z last-modified: 2016-04-06T19:52:01Z mnt-by: RIPE-NCC-LOCKED-MNT source: RIPE % Information related to '195.137.174.0/24AS49104' route: 195.137.174.0/24 descr: Kuwait Stock Exchange origin: AS49104 mnt-by: MNT-Kuwait-Stock-Exchange created: 2009-04-16T10:13:58Z last-modified: 2009-04-16T10:13:58Z source: RIPE Regards, Mohamed Eldemiri Network Administrator [cid:image001.png@01D5E970.A74CE0E0] Address: Mubarak Al Kabeer Street, Kuwait City, Kuwait P.O.Box: 22235, Safat, 13083 Kuwait Telephone: +(965) 2299-2595 Mobile: +(965) 55266079 Fax: +(965) 2244-0476 www.boursakuwait.com.kw Disclaimer: This e-mail message and any files attached to it are intended only for the recipients named above. The information in this e-mail is confidential and may be legally privileged. If you are not the intended recipient or have received this e-mail by error, you must not use or disseminate the information and must promptly notify the sender and delete this e-mail immediately. Unless otherwise explicitly provided in the body of this e-mail, neither this e-mail nor any attachment hereto is intended to operate as a commitment of whatever type or to include an electronic signature of whatever form under any applicable law. Opinions, conclusions and other information in this email that do not relate to the official business of Boursa Kuwait. Shall be understood as neither given nor endorsed by Boursa Kuwait. Although this email and any attachments are believed to be free of any virus or other defect, it is the responsibility of the recipient to ensure that it is virus free. Boursa Kuwait accepts no responsibility for any loss or damage arising in any way from the use of this email.

1 0

NWI-1 overview of abuse contacts for resources
by ripedenis＠yahoo.co.uk 21 Feb '20

21 Feb '20

Colleagues I said at Ripe 79 that I would review the open NWIs. So lets start with NWI-1. This has been open and virtually static since 2016. The original summary is here:https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005234.html The situation has changed since then with the "abuse-c:" attribute now allowed in resource objects. The main point I was making (as one of the authors of this NWI) is that there is no easy way for a resource holder to view all the abuse contact details for any of their resources. Hierarchical queries for abuse contacts only search 'up' the hierarchy. There is no easy way for the resource holder to search 'down' through the hierarchies to find all/any abuse contact details. These can now be added at any point in a hierarchy and forgotten about. But they are still active and may present the wrong information when people query for these details. The question now is "Do we need a search/query option or RIPEstat widget that will present an overview of all abuse contacts from a resource allocation down the hierarchy, or even for all of an organisation's resources?" cheers denis co-chair DB-WG

1 0

2018-06 Proposal Implemented (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
by Edward Shryane 31 Jan '20

31 Jan '20

Dear Working Group, The RIPE NCC Database team have now implemented the 2018-06 proposal (now ripe-731), "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". We plan to deploy this to production on Wednesday 15th January. A nightly job will run from that evening onwards. We expect approximately 965 route objects will be initially marked for cleanup (which will happen 2 weeks after that). Regards Ed Shryane RIPE NCC > > From: Petrit Hasani <phasani(a)ripe.net> > Subject: [policy-announce] 2018-06 Proposal Accepted (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up) > Date: 6 November 2019 at 16:03:18 GMT+1 > To: policy-announce(a)ripe.net > > Dear colleagues, > > Consensus has been reached on 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". > > This proposal aimed at creating a process to delete a non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. > > You can find the full proposal at: > https://www.ripe.net/participate/policies/proposals/2018-06 > > The new RIPE Document is called ripe-731 and is available at: > https://www.ripe.net/publications/docs/ripe-731 > > We estimate that this proposal will take around two to three months to fully implement. > > We will send another announcement once the implementation is complete and the new procedures are in place. > > Thank you to everyone who provided us with your input. > > Kind regards, > > -- > Petrit Hasani > Policy Officer > RIPE NCC > > > > >

4 4

NWI-10 country attribute
by ripedenis＠yahoo.co.uk 27 Jan '20

27 Jan '20

Colleagues The chairs of the DB-WG declared a consensus on NWI-10 at RIPE 79. This is to add a "country:" attribute to the ORGANISATION object which will be managed by the RIPE NCC in ORGANISATION objects for resource holders. This email is to document that consensus and ask the RIPE NCC to implement this change. cheers denis co-chair DB-WG

2 1

RIPE Database Usage Survey - Database Requirements Task Force
by Boris Duval 20 Jan '20

20 Jan '20

Dear Colleagues, The RIPE Database Requirements Task Force (DBTF) needs your feedback! The DBTF has just launched a survey to know more about how the RIPE Community uses the RIPE databases. The results will provide feedback to the RIPE Database Task Force to help understand the relevance of the database to the RIPE Community and to help shape future RIPE Database policy. You can take the survey at: https://www.surveymonkey.com/r/PC9HTYP <https://www.surveymonkey.com/r/PC9HTYP> The deadline to answer the survey is 31 January. Feel free to share it with your network. Many thanks! Best, Boris Communications Officer RIPE NCC

1 0

NWI-9: Making the Whois NRTM Service Public
by Edward Shryane 16 Jan '20

16 Jan '20

Dear colleagues, Last month, as part of the DB-WG NWI-9 proposal, the RIPE NCC Executive Board resolved to make the Whois NRTM Service public. The full minutes of the Board meeting are on our website: https://www.ripe.net/about-us/executive-board/minutes/2019/minutes-130th-ri… We will now start working on all aspects related to implementing this decision and will have more details for you soon. Regards Ed Shryane RIPE NCC

2 1

database support for ed25519 PGP keys
by Marco d'Itri 19 Dec '19

19 Dec '19

Can RIPE staff clarify if there are plans to support PGP authentication of database updates using ed25519 keys? This should require not much more that upgrading gnupg to a modern release. -- ciao, Marco

2 1

converting a C class from PI to PA
by Franco Tauceri 19 Dec '19

19 Dec '19

Hello. What's the right how-to convert an existing C class from PI to PA? According to this: https://www.ripe.net/manage-ips-and-asns/ipv4/converting-pi-to-pa "Members can request this update via the LIR Portal." ... but I was not able to find HOW this may be done (If I try to edit the object, the field "status" is locked, and I can't edit it anyway... while I can edit other fields as usual) Regards -- Franco Tauceri DomainRegister m: 39.3483064202 w: https://DomainRegister.international e: franco.tauceri(a)domainregister.it

3 2

Whois Release 1.96
by Edward Shryane 04 Dec '19

04 Dec '19

Dear Working Group, RIPE Database release 1.96 has been deployed to the Release Candidate environment. We plan to deploy to production on Wednesday 4th December. This release contains the following main changes since 1.95.1: * Added "country:" attribute to organisation object type * Deprecated "mnt-lower:" attribute in autnum object type * Abuse-c validation comment must refer to the LIR organisation * Limit number of results in full-text search queries * Apply query limit to version queries For a full list of changes, refer to the release notes: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rel… More information on the Release Candidate environment can be found on our website: https://www.ripe.net/manage-ips-and-asns/db/release-notes/rc-release-candid… Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

1 1

Removing the "mnt-lower" attribute from aut-num objects
by Edward Shryane 03 Dec '19

03 Dec '19

Dear Colleagues, as presented during the DB-WG session at RIPE 79, we plan to remove the "mnt-lower" attribute from the aut-num object type. From the RIPE database documentation [0]: “mnt-lower: This attribute has no meaning in the aut-num object. In the RIPE NCC service region, we do not allocate blocks of AS numbers for users to assign from. All AS numbers are assigned by the RIPE NCC therefore there is no hierarchy to ‘maintain’ or authorise against. This attribute should be deprecated.”  We plan to implement this change in the next Whois release (we will announce this separately). We do not expect any operational impact. It is currently an optional attribute. This attribute will be removed (with a warning) from any aut-num updates. At the same time, we plan to remove this attribute from approximately 948 of 35,144 aut-num objects. We will announce separately to the db-wg and affected maintainers, before and after removal. Please let me know of any feedback or questions you may have. Regards Ed Shryane RIPE NCC [0] https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-data…

1 1

Removing the Legacy Status "remarks" attribute
by Edward Shryane 03 Dec '19

03 Dec '19

Dear Colleagues, As presented during the DB-WG session at RIPE 79, we plan to remove the legacy status "remarks" attribute from inetnum and aut-num objects in the RIPE database. This remark was added to LEGACY resources in 2015, when implementing the policy 2012-07 "RIPE NCC Services to Legacy Internet Resource Holders” [0]. The remark states: "For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources” We now consider this remark to be obsolete, and have already performed a similar cleanup on (most) aut-num objects in August 2017. We plan to shortly remove this remark from approximately 19,059 inetnum and 15 aut-num objects, and will email affected maintainers before and after the change. Please let me know of any feedback or questions you may have. Regards Ed Shryane RIPE NCC [0] https://www.ripe.net/participate/policies/proposals/2012-07

1 1

Internationalized domain names in the data abase?
by Ronald F. Guilmette 08 Nov '19

08 Nov '19

Sorry if I am interrupting any ongoing discussion, but I just have a quick and simple question... Is it permitted to have internationalized domain names appear within the database? By that I really mean to ask if it is permissible to have there appear in the data base IDNs which are written in their UTF-8 encoded forms, rather than, say, in punycode? I have found at least one specific case where an IDN does appear in the data base as a UTF-8 encoded string, but since I had never seen that before, I just wanted to know if that was an anomalous mistake or if it was consider normal, acceptable, and routine.

4 15

Re: [db-wg] NWI-10 Definition of Country
by Arash Naderpour 08 Nov '19

08 Nov '19

Hi Denis, What you name it as "meaningless values" are not meaningless to the organizations that they are using it. When you request a new allocation from NCC you will be asked to *"specify the country which the allocation will be announced"*, and based on your selection the country code will be set for both the inet(6)numns and allocation entry in the delegation file. This is the way that the country code is added in first place in delegation file. A member may decides to use the allocation later in a different country, and they can update the country code for inet(6)numns in ripe db, so I think the best practice is to sync the delegation file with the database and let the members decide what value should be set. Regards, Arash Naderpour On Fri, Nov 1, 2019 at 11:50 PM denis walker <dw100uk(a)yahoo.co.uk> wrote: > Hi Arash > > If many organisations are using these values then, unfortunately, you are > basing decisions on meaningless values. > > The country attribute in resource objects is undefined. Users can set this > to any country they wish with no meaning to anyone reading the value from > the database. > > From the description of the extended delegated stats file > ftp://ftp.ripe.net/ripe/stats/RIR-Statistics-Exchange-Format.txt > > it says this about the country code: > > Format: > > registry|cc|type|start|value|date|status[|extensions...] > > registry = One value from the set of defined strings: > > {apnic,arin,iana,lacnic,ripencc}; > > cc = ISO 3166 2-letter country code, and the enumerated > variances of > > {AP,EU,UK} > > These values are not defined in ISO 3166 but are widely used. > > The cc value identifies the country. However, it is not specified > if this is the country where the addresses are used. > There are no rules defined for this value. > It therefore cannot be used in any reliable way to map IP addresses > to countries > > If you were to sync the stats file with resource object data you are in > effect setting an undefined field in the stats to an undefined value from > the database. > > The purpose of NWI-10 is to create a well defined country value in both > the stats file and the ORGANISATION object. The legal location of an > organisation is currently the only well defined country information > available. There is no information available anywhere in the database or > stats file telling you where a network is being used. > > cheers > denis > > co-chair DB-WG > > On Friday, 1 November 2019, 05:37:28 CET, Arash Naderpour via db-wg < > db-wg(a)ripe.net> wrote: > > > Hi, > > I'm new to DB-WG, but want to express my opinion in this regard, > from problem definition: > "Historically the country code was used to refer to the location of the > network" > > There are plenty of organization out there that are already set their > network and firewalls rules to use country code value in delegation file as > reference to the location of the network. > > Changing the rule to to something new, will cause problem for clients and > providers, so I don't think it is a good idea, > country code in delegation file can be synced with the country code for > resource object in RIPE DB. > A new attribute in organization object refers to where the resource holder > is legally based is totally fine, but having the same value in delegation > file can break networks and services. > > Regards, > > Arash Naderpour > Parsun Network Solutions >

4 6

Re: [db-wg] [Ext] Re: NWI-10 Definition of Country
by Leo Vegoda 01 Nov '19

01 Nov '19

Sanjaya wrote: > Just a thought, maybe we could redefine the RIR extended delegated > file format to incorporate both cc values of inet(6)num|autnum and > organisation Whois objects like this: > > registry|xx|type|start|value|date|status|yy-custodianid > Where: > xx = country code of inet(6)num|autnum > yy = country code of organisation > > This will require agreement among the RIRs and some adjustments > by the relying parties, but provides a clearer mapping between > Whois objects and the stats file records. My 2 cents. The stats file could have its structure adjusted but remember that "country:" is a multiple attribute, so there could technically be as many countries listed as there are valid ISO 3166 codes. Also, aligning the stats file and inet(6)numns doesn't solve the fundamental issue, which is that the "country:" attribute in inet(6)nums has never had a clearly defined meaning. Readers and writers of the data almost certainly mean and understand different things. As there is already a lack of shared understanding and a very large deployed base, which includes lots of legacy software, managing a change that leaves the structure intact while potentially changing how that data should be used sounds dangerous to me. That's the sort of change that leads to subtle, quiet errors that are hard to debug. I think it is safer to break things in a way that is very obvious, so that they get noticed and fixed. Kind regards, Leo Vegoda

1 0

Re: [db-wg] NWI-10 Definition of Country
by ripedenis＠yahoo.co.uk 01 Nov '19

01 Nov '19

Hi Arash If many organisations are using these values then, unfortunately, you are basing decisions on meaningless values. The country attribute in resource objects is undefined. Users can set this to any country they wish with no meaning to anyone reading the value from the database. >From the description of the extended delegated stats fileftp://ftp.ripe.net/ripe/stats/RIR-Statistics-Exchange-Format.txt it says this about the country code:Format: registry|cc|type|start|value|date|status[|extensions...] registry = One value from the set of defined strings: {apnic,arin,iana,lacnic,ripencc}; cc = ISO 3166 2-letter country code, and the enumerated variances of {AP,EU,UK} These values are not defined in ISO 3166 but are widely used. The cc value identifies the country. However, it is not specified if this is the country where the addresses are used. There are no rules defined for this value. It therefore cannot be used in any reliable way to map IP addresses to countriesIf you were to sync the stats file with resource object data you are in effect setting an undefined field in the stats to an undefined value from the database. The purpose of NWI-10 is to create a well defined country value in both the stats file and the ORGANISATION object. The legal location of an organisation is currently the only well defined country information available. There is no information available anywhere in the database or stats file telling you where a network is being used. cheersdenis co-chair DB-WG On Friday, 1 November 2019, 05:37:28 CET, Arash Naderpour via db-wg <db-wg(a)ripe.net> wrote: Hi, I'm new to DB-WG, but want to express my opinion in this regard, from problem definition:"Historically the country code was used to refer to the location of the network" There are plenty of organization out there that are already set their network and firewalls rules to use country code value in delegation file as reference to the location of the network. Changing the rule to to something new, will cause problem for clients and providers, so I don't think it is a good idea, country code in delegation file can be synced with the country code for resource object in RIPE DB.A new attribute in organization object refers to where the resource holder is legally based is totally fine, but having the same value in delegation file can break networks and services. Regards, Arash NaderpourParsun Network Solutions

2 1

Re: [db-wg] NWI-10 Definition of Country
by Arash Naderpour 01 Nov '19

01 Nov '19

Hi, I'm new to DB-WG, but want to express my opinion in this regard, from problem definition: "Historically the country code was used to refer to the location of the network" There are plenty of organization out there that are already set their network and firewalls rules to use country code value in delegation file as reference to the location of the network. Changing the rule to to something new, will cause problem for clients and providers, so I don't think it is a good idea, country code in delegation file can be synced with the country code for resource object in RIPE DB. A new attribute in organization object refers to where the resource holder is legally based is totally fine, but having the same value in delegation file can break networks and services. Regards, Arash Naderpour Parsun Network Solutions

1 0

country attribute in aut-num
by Cynthia Revström 23 Oct '19

23 Oct '19

Hello, I ran into an issue today that was the inability to have a country attribute in the aut-num object, despite having a country code in the delegated file. I would like to see it added to WHOIS. - Cynthia

4 5

Apologies for the accidental email
by Fallon Albrecht 23 Oct '19

23 Oct '19

Dear working group, I apologise for the accidental email that was sent out, it was meant to be an internal feature request. Sorry for spamming you. Fallon

1 0

Re: [db-wg] [swe-database] Implementation -K Flag Request
by Fallon Albrecht 23 Oct '19

23 Oct '19

Hi Ed, I have some feature requests: 1. To have a perma link option for full text search. 2. If a SSO account is associated with the mnt-by of the inetnum and they query the allocation that they also can see all the more specific objects. 3. If the SSO account is a Ripe NCC email address and you login that the functionality “do not retrieve related objects” is disabled. That is’t for now. Thank you! Fallon > On 23 Oct 2019, at 11:20, Valentino Dijkstra <vdijkstra(a)ripe.net> wrote: > > Hi Ed, > > Thank you for the reply. > > That is ok for us, in case we are receiving any other future request I will let you know. > > Cheers, > > Valentino > > >> On 22 Oct 2019, at 17:21, Edward Shryane <eshryane(a)ripe.net> wrote: >> >> Thanks Valentino, >> >> I added a story to the DB team's backlog for this feature request: "db-web-ui: Support the --primary-keys/-K flag on the Query Page" (https://jira.ripe.net/browse/DB-2659) >> >> We are busy with other work, but we'll review when we're next working on new website functionality. >> >> The DB team doesn't need a "feature request" tag in Zendesk (unless CS needs it), as we're tracking everything in one place (Jira) already. >> >> Just send us the request and I'll add it to our backlog. You can then close the Zendesk ticket. >> >> We add a ticket # to the story (or bug) in Jira, so we remember to contact the user again once it's done. >> >> Regards >> Ed >> >> >> >> >>> On 22 Oct 2019, at 16:40, Valentino Dijkstra <vdijkstra(a)ripe.net> wrote: >>> >>> Dear Team, >>> >>> >>> In the last couple of weeks we did not receive any particular future request. >>> >>> The only request came from ticket 219462 requesting to have the -K flag implemented in order to >>> retrieve all the route objects related to a certain range. >>> >>> Also I will make sure that we will have a “future request” tag in the DB queue so it will be easy to retrieve the tickets in the future. >>> >>> Let me know if this can be done in a short period of time. For further questions feel free to contact me. >>> >>> Cheers, >>> >>> Valentino >>> CS_______________________________________________ >>> swe-database mailing list >>> swe-database(a)ripe.net >>> https://intlists.ripe.net/mailman/listinfo/swe-database >> >

1 0

Set Default Maintainer on all Top-level Resources
by Edward Shryane 22 Oct '19

22 Oct '19

Dear Colleagues, as presented during the DB-WG session at RIPE 79, we wish to extend the "Default Maintainer" functionality for LIR organisations. Firstly, to set the Default Maintainer (with an mnt-by: attribute) on *all* top-level resources (where the org: reference is the LIR itself): - IPv4 and IPv6 allocations (the current behaviour) - ASNs - IPv4 and IPv6 assignments - IPv4 LEGACY resources Secondly, to automatically (re-)set the Default Maintainer on a nightly basis, on *all* top-level resources: - Fix inconsistencies due to manual updates - Add the default maintainer (with an mnt-by: attribute), and remove other user maintainer(s) Please let me know of any feedback or questions you may have. Regards Ed Shryane RIPE NCC

3 4

Cleanup Locked Person Objects - Implementation Plan
by Edward Shryane 21 Oct '19

21 Oct '19

Dear Colleagues, As presented during the DB-WG session at RIPE 79, we will shortly begin to cleanup locked person objects in the RIPE database. We will select person objects maintained by RIPE-NCC-LOCKED-MNT, which are referenced by inetnum allocations or assignments, and re-assign them to the resource maintainer. The goals of this cleanup are: - Align with RIPE-730 Policy - “Registration data (range, contact information, status etc.) must be correct at all times (i.e. they have to be maintained).” - Align with GDPR - assign responsibility for contact details to the correct maintainer - Cleanup 90% of locked person objects in the RIPE database (the remainder will be cleaned up separately) We will implement this cleanup as follows: - Announce to ncc-announce, ncc-services-wg and db-wg beforehand - Perform the cleanup one LIR at a time - Email the affected LIR and assignment maintainers beforehand to explain the change, including a list of planned updates - Set the locked persons mnt-by to the assignment maintainer, where we are sure of a link between them (e.g., if the objects were originally created together, and if the assignment maintainer has not changed since (this applies to two thirds of all locked persons)). - Otherwise, set the locked persons mnt-by to the LIR maintainer (for one third of all locked persons). - Email the LIR and assignment maintainers afterwards, and ask them to validate the contact details on their resources. Please let me know of any feedback or questions you may have. Regards Ed Shryane RIPE NCC

1 0

Agenda RIPE79 - Database Working Group
by William Sylvester 10 Oct '19

10 Oct '19

DB-WG Members, Here is our agenda for the RIPE meeting next week. Best regards, DB-WG Chairs A. Introduction - 5 min * Welcome * Scribe * Jabber * Agenda B. Operational Update RIPE Database – 20 mins Edward Shryane, RIPE NCC C. DB Requirements Tast Force Update – 5 mins D. NWI-8 LIR’s SSO Authentication Groups Demonstration – 5 mins Mahesh Aggrwal, RIPE NCC E. NWI-3 RIPE-NONAUTH perspective, still needed? – 15 mins Job Snijders, NTT F. NWI-9 In-Band Notification Mechanism – 15 mins TBD G. NWI - Open Proposals – 15 mins Z. AOB (open discussion)

1 0

GDPR and the RIPE Database
by Edward Shryane 08 Oct '19

08 Oct '19

Dear Working Group, as mentioned in last week's DB-WG meeting, we will shortly be implementing the following changes: - Do not include personal data in historical queries (notify, e-mail, address attributes). - Do not include person/role references in historical queries (admin-c, tech-c, ping-hdl, zone-c). A legal review found we should not return historical contact details, as they may contain personal data, which is not in line with the purpose of the RIPE database or data protection legislation. For background, Maria Stafyla from RIPE NCC Legal presented on this topic at RIPE 76: https://ripe76.ripe.net/presentations/101-GDPR-Database-WG-RIPE-76.pdf Regards Ed Shryane RIPE NCC

4 8

NWI-10 Definition of Country
by ripedenis＠yahoo.co.uk 08 Oct '19

08 Oct '19

Colleagues The DB-WG chairs have agreed to create "NWI-10 Definition of Country". This is an issue that has been debated many times over many years and needs a solution. The Solution Definition below is based on a presentation made at RIPE 78 by the RIPE NCC. There has been very little discussion on this since RIPE 78 so perhaps we can have a final round of pros and cons over this next week and then see if we have a consensus. cheersdenis co-chair DB-WG NWI-10 Definition of Country Problem DefinitionThere is no clarity for the meaning of the country code attribute in the RIPE Database and the Extended Delegated statistics. This creates confusion and inconsistencies. Historically the country code was used to refer to the location of the network. Until recently this location was, in most cases, identical to the legal presence of the resource holder. However, in recent years there has been a growing number of resource holders that have, for various reasons, their legal presence in one country, but the network located in another country. There is also a growing number of out-of-region members resulting in an increase in requests to update the country code in the Extended Delegated Statistics for different purposes (e.g. commercial). While the country code attribute in the RIPE Database can be updated directly by the resource holder, the Extended Delegated Statistics are maintained by the RIPE NCC and they were created as part of a joint effort from the RIRs with a specific purpose. Solution Definition1. The country code for resource objects in the RIPE Database should remain as it is currently, ie the resource holder remains responsible for maintaining this attribute and deciding what the country code should be, according to whatever criteria best suits their needs. 2. A new attribute should be added to the ORGANISATION object, which contains a country code that refers to where the resource holder is legally based. The RIPE NCC would be responsible for this field and would only make updates to this field after being provided with documentation that proves the resources holder is legally-based in another country. This would essentially be the same process for updating an organisation's legal name currently. 3. The new country code value in the ORGANISATION object would then be reflected in the Extended Delegated Statistics – so that this file will show where the holder of a resource is legally based and will not make any claims about where the resources are being used. This will ensure the Extended Delegated Statistics file is consistent with those published by the other RIRs. This may mean there is a greater divergence between the country code contained in resource objects in the RIPE Database and those listed in the statistics file. As the country code in the resource objects only has meaning to the resource holder, which should be made clear, this should not be a problem.

9 13

Synchronising Users from the LIR Portal to the Default Maintainer in the RIPE Database
by Edward Shryane 23 Sep '19

23 Sep '19

Dear colleagues, Following a request by the Database Working Group earlier this year, we have implemented a new feature to synchronise users from the LIR Portal to the Default Maintainer in the RIPE Database. More information can be found in the Labs article: https://labs.ripe.net/Members/ed_shryane/synchronising-users-from-the-lir-p… The discussion by the DB-WG was defined as the Numbered Work Item NWI-8 : https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items We plan to deploy this new feature to production next Monday, 23rd September. Regards, Ed Shryane RIPE NCC

1 1