- db-wg - mailman.ripe.net

Re: [db-wg] IRR and Hurricane Electric and RIPE
by Peter Courtney 13 Nov '18

13 Nov '18

thank you for the advice, much appreciated but all sorted now by Net Solutions Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

Re: [db-wg] IRR and Hurricane Electric and RIPE
by Peter Courtney 13 Nov '18

13 Nov '18

thank you Christoffer, I am now well on my way to sorting this out with Net Solutions Europe, we will see what tomorrow brings, thank you for the advice Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

IRR and Hurricane Electric and RIPE
by Peter Courtney 13 Nov '18

13 Nov '18

First Message on here, please go easy as I am learning every day, just recently a number of our customers have been complaining that they cannot get on to various web sites, so I sent an email to HE, and got this reply back Hello Teledesign AS41614 and your BGP Query Looks like you do not have valid IRR entries for some entries. http://irrexplorer.nlnog.net/search/91.204.244.0/24 says "Prefix is in DFZ, but NOT registered in any IRR You are NOT getting routed to the whole Internet. From BGP.HE.NET https://bgp.he.net/AS41614#_prefixes You should have GREEN check mark next to the prefixes. From route-views.oregon-ix.net: route-views>sh ip b 91.204.244.0/24 l | i 1299 route-views> Please ensure all of your prefixes have valid IRR entries. It seems these may be getting filtered by remote networks. Documentation is available here, but you essentially need to create a route object with your ASN as the origin http://fcix.net/whitepaper/2018/07/14/intro-to-irr-rpsl.html =================================================== could anyone help me find a simple "How To Document" that I can follow and do what HE are asking me to do, or is it something I can ask RIPE to do on my behalf thanks in advance to all Peter ( newbie sysadmin ) Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 2

Re: [db-wg] [Ext] [address-policy-wg] Policies and Guidelines for Assignments for Network Infrastructure and End User Networks
by Töma Gavrichenkov 05 Nov '18

05 Nov '18

Hi Leo, Just to make it 100% clear for me: do you mean to say that you support my proposal No. 2? пн, 5 нояб. 2018 г., 23:12 Leo Vegoda <leo.vegoda(a)icann.org>: > Hi, > > Töma Gavrichenkov wrote: > > [...] > > > > 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. > > [...] > > > All in all, RIPE-708 6.2 is a perfect example of an imperfect > > policy, too strict and too vague at the same time. Which is bad, > > because a) some ISPs would just prefer to ignore it, no matter > > the "must", and would be paying less attention to other "musts" > > they would encounter in other policy documents, b) those ISPs > > who would choose to be responsible about RIPE DB usage risk > > losing customers and wouldn't be able to defend their attitude > > against the customers, let alone courts, based on the RIPE DB > > policy. > > Over 20 years ago, the ISP at which I worked had a number of customers > with home networks using public IP address space. The ISP placed its own > contact information in the RIPE Whois Database with a comment that the > address space was assigned to an individual customer. > > If I remember correctly this was done for two key reasons: > > 1. RIPE policy does not override the law of the land. > 2. There was very little value in placing those customers' contact details > in the RIPE Whois Database because they were network users and not network > administrators. The ISP's NOC staff had skills, tools, processes, and > training and were in a much stronger position to provide meaningful > assistance to anyone with a genuine reason to make contact about the > administration of one of those customer networks. > > As I remember, the RIPE NCC was happy with the rationale back then. While > the specific wording of RIPE policy might have changed somewhat in the last > 20 years, I don't think the intent has. > > The contact details of the End User do not have to mean their personal > phone number or e-mail address. And if they do not have the skills, tools, > processes, and training to provide meaningful assistance to anyone with a > genuine reason to make contact about a specific network, providing a > personal phone number or e-mail address is arguably unhelpful. > > Kind regards, > > Leo Vegoda >

2 1

Re: [db-wg] Proposal for restricting authentication concerning use of revoked and expired GPG ID's in key-cert objects
by Christoffer Hansen 05 Nov '18

05 Nov '18

On Mon, 5 Nov 2018 at 15:33, Gunnar Guðvarðarson <gunnar.gudvardarson(a)advania.is> wrote: > That's amazing(ly bad), thank you! True.

1 0

Re: [db-wg] Proposal for restricting authentication concerning use of revoked and expired GPG ID's in key-cert objects
by Christoffer Hansen (Lists) 05 Nov '18

05 Nov '18

Hi Gunnar, On Thu, 1 Nov 2018 at 15:51, Gunnar Guðvarðarson <gunnar.gudvardarson(a)advania.is> wrote: > What happens if you send signed update A, then signed update B, and then re-send signed update A. > > Does the re-sent signed update overwrite the object? Yes! If you re-send an older (signed) version (A) of an object in the RIPE database. A newer update (B) can be overwritten with the older one (A). The current implementation in the DB does not validate anything apart if the key as allowed or not. Expiration date or if an object has been update since an incoming update message is not taken into account. If the update message is signed with a valid key. It is accepted. (Currently I have only tested this with my own objects in the DB) Christoffer

1 0

Policies and Guidelines for Assignments for Network Infrastructure and End User Networks
by Töma Gavrichenkov 05 Nov '18

05 Nov '18

Hello WG (both, actually), A recent case of a Russian broadband ISP, roughly 6th in size in the country, exposing the personal data of their individual VIP customers by posting said data to RIPE DB(*) highlighted an important issue in RIPE-708, 6.2 "[policies and guidelines for assignments for] Network Infrastructure and End User Networks"(**). To quote: > 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. (note the "must", we'll soon get back to it) While it's out of question that posting individual users' personal data to RIPE DB is insane, what's interesting is that small business owners(***), when aware of the leak, seem to also be concerned that their B2B broadband data contract apparently included a clause they've missed, and their mobile telephone number is now published to a public database on the Internet, and, you know, one cannot simply remove an information from the Internet which is already there. But when we try to rely on 6.2 for a definitive advice, we don't get any: - There's no definition of what is exactly meant under "point-to-point links" (PTPL). Some speculate it's a historical term from the times of PPP/SLIP, meaning just "end-user access links", and, as such, includes individual and SMB customer links. Other read it as those IPv4 /30s ASes waste all the time for BGP session establishment, and argue that what's really meant by PTPL is just the IP addresses never ever communicating with the world outside of their own local net (BGP sessions included, SMB access obviously not included). (Personally, the second opinion looks more convincing for me, because this way only those IP addresses which never send or receive packets from the Internet may lack a proper abuse-c, which makes sense, and I like when things make sense, so. But at the same time the first opinion is backed by people I respect.) Anyway, RIPE-708 fails to provide an answer. - Another scary term is "a network using public address space" (NUPAS). Is IPv4 /32 a network? What about /31? What's "using public address space" after all, there's no doubt we won't report our usage of 192.168.0.0/16 to RIPE DB. This sentence was meant to clear our concerns but it just adds up to them. What is also meant to help us but adds to the mess is the RIPE NCC Local Internet Registry Training Course(****), slides 94-95: - Somehow, training material includes more specific definitions and corner cases (e.g. "points of presence") than the policy does. Is it only me, or such a thing should never ever happen? A policy training course must not be different from the policy itself, no matter if the difference is in being either more strict of more relaxed. If an NCC trainer just knows more about the subject than is stated in a policy, they'd better report to the WG first that the policy lacks an important consideration. - However, those definitions don't really clarify what's PTPL and NUPAS are, too. - Slide 95 is even better: it says there's a grey area around. Well, it might be again only me, but personally I feel very uncomfortable seeing "must" and "grey area" in the same sentence. If there's a grey area in an area, it must be "should" there, not "must". - There's apparently a border line between "when the End User has a few addresses out of a larger address block" and "If the End User has a separate subnet". Now again, (an occasional?) /31 is a subnet or just a few addresses? Who's going to check ISPs against this strict ("must") requirement, and how? - What if there's a customer with an pizza store (so, an office within their location) and their own equipment (Mikrotik) connected to a broadband pool? - What if a broadband customer sets up an HTTP server on their point-to-point link's public v4 address and starts serving whatever children drug suicide abuse torrents they have. All in all, RIPE-708 6.2 is a perfect example of an imperfect policy, too strict and too vague at the same time. Which is bad, because a) some ISPs would just prefer to ignore it, no matter the "must", and would be paying less attention to other "musts" they would encounter in other policy documents, b) those ISPs who would choose to be responsible about RIPE DB usage risk losing customers and wouldn't be able to defend their attitude against the customers, let alone courts, based on the RIPE DB policy. So here are two separate things I propose, and I'd prefer them to be discussed and evaluated separately: 1) Ask the author of LIR training material to provide the WG (both) with the historical insight on what was meant in 6.2, and how's that supposed to work. Afterwards, after a heated discussion on the mailing list (both), make a decision and amend a policy towards either a more relaxed, or a more constraining fashion, but do either of things anyway, as there's no SLIP anymore, and such an irresponsible wording of a policy as it stands today undermines the trust in policy process, especially in some Eastern European and Northeast countries where there's hardly any trust even now. My personal suggestion is that the only border line that should be there is between businesses/organizations with public IP addresses, on one side, and individual users/NAT pools, on the other. If a company is using a public IP address space for any purpose at all, it must publish at least an abuse-c contact to a public IP database. Fair enough IMO. 2) Change 6.2 to reflect the fact that the contact information of End Users who are individuals not MAY, but rather MUST be substituted with the contact data of the service provider. This perfectly reflects currently ongoing legislation trends as well as a concern in the society at large, and also would be seen as a responsible attitude of an ISP community towards the personal data safety — an attitude the ISP community hardly used to show before. (*) — https://www.bbc.com/russian/news-46083410. Here's a Google Translate link for your convenience: https://translate.google.com/translate?sl=ru&tl=en&js=n&u=https%3A%2F%2Fwww… (**) — https://www.ripe.net/publications/docs/ripe-708#62 (***) — My definition of a "small business" here might seem too broad, but if's fully grounded: e.g. Main Directorate for Drugs Control of the Ministry of Internal Affairs of Russia, as a business, is definitely not so big; Alfa Bank is a large bank in Russia but Russian banking system is comparatively small when compared to the rest of the world; etc. (****) — https://www.ripe.net/support/training/material/lir-training-course/lir-slid… | Töma Gavrichenkov | gpg: 2deb 97b1 0a3c 151d b67f 1ee5 00e7 94bc 4d08 9191 | mailto: ximaera(a)gmail.com | fb: ximaera | telegram: xima_era | skype: xima_era | tel. no: +7 916 515 49 58

2 2

RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
by Marco Schmidt 16 Oct '18

16 Oct '18

Dear colleagues, We just published the RIPE Policy proposal, 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", to the Routing Working Group mailing list. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. As the RIPE IRR is part of the RIPE Database, we want to notify the Database Working Group. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-06 We encourage you to review this proposal and send your comments to <routing-wg(a)ripe.net> before 9 November 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

8 16

Re: [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
by Alexander Azimov 16 Oct '18

16 Oct '18

2Robert How does it help to get rid of commercial IRRs? It's only RIPE policy, it doesn't work like GPDR. :) 2Job There is only one good thing about mistakes - if you can fix it. Here if one fails to properly configure ROAs it may lead to ongoing operational problems, that can't be fixed even after fixing ROAs, since RIPE-NONAUTH database is locked. I think, that it's ok to delete route objects that conflict with ROAs only if you are able to create new. Otherwise, the only winning party will be commercial IRRs. пн, 15 окт. 2018 г. в 17:29, Alexander Azimov <aa(a)qrator.net>: > 2Robert > How does it help to get rid of commercial IRRs? It's only RIPE policy, it > doesn't work like GPDR. :) > > 2Job > There is only one good thing about mistakes - you can fix it. > Here if one fails to properly configure ROAs it may lead to ongoing > operational problems, that can't be fixed even after fixing ROAs, since > RIPE-NONAUTH database is locked. > I think, that it's ok to delete route objects that conflict with ROAs only > if you are able to create new. Otherwise, the only winning party will be > commercial IRRs. > > пн, 15 окт. 2018 г. в 17:06, Robert Heuvel via db-wg <db-wg(a)ripe.net>: > >> Hi, >> >> Where can we express our support for this RIPE Policy proposal? >> We think it is a great idea and gets rid of commercial IIRs where you can >> register just about anything which is or is not yours... >> >> Robert Heuvel >> atom86 (AS8455) >> >> Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum >> >> > > -- > | Alexander Azimov | HLL l QRATOR > | tel.: +7 499 241 81 92 > | mob.: +7 915 360 08 86 > | skype: mitradir > | visit: radar.qrator.net > -- | Alexander Azimov | HLL l QRATOR | tel.: +7 499 241 81 92 | mob.: +7 915 360 08 86 | skype: mitradir | visit: radar.qrator.net

3 6

Re: [db-wg] Agenda RIPE77 - Database Working Group
by William Sylvester 13 Oct '18

13 Oct '18

Dear Working Group Members, Below is the agenda for the Database Working Group for RIPE77. If you have any questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 5 min * Welcome * Scribe * Jabber * Agenda B. Operational Update RIPE Database – 20 mins Edward Shryane, RIPE NCC C. RIPE-NONAUTH Cleanup – 20mins Job Snijders, NTT D. Country Code Use in RIPE DB and Extended Delegated Statistics – 20 mins Ingrid Wijte, RIPE NCC E. Discussion: PERSON objects in the RIPE Database – 15 mins Denis Walker F. NWI - Open Proposals – 5 mins Z. AOB (open discussion)

1 0

Re: [db-wg] PERSON objects in the RIPE Database
by Maria Stafyla 12 Oct '18

12 Oct '18

Hi Denis, all According to Article 3 of the RIPE Database Terms and Conditions, one of the defined purposes for the use of the RIPE Database is "Facilitating coordination between network operators". A PERSON object is meant to contain the (business) contact information of people who are responsible for the networks the Internet number resources correspond to and/or for maintaining the related information in the RIPE Database and the DNS zone contacts. If someone creates a PERSON object that is not meant for one of the defined purposes, this would constitute a violation of the RIPE Database Terms and Conditions (See Article 4.1.). It's also worth noting that PERSON objects that are not referenced in any other object (and thus do not serve any operational purpose) are automatically deleted after 90 days. In general, personal data may only be processed in accordance with the relevant principles. If personal data is no longer required in relation to the defined purpose it was supplied/collected for, then its processing will not be justified any more. However, depending on the information that is inserted when a ROLE object is created, it might contain personal data - this is something the RIPE NCC has no control over. Kind regards, Maria Stafyla Legal Counsel RIPE NCC > Hi Nick, Athina > > Perhaps the RIPE NCC legal team can give us some advice on this issue. > In your presentation at RIPE 76 you said the justification for > personal data in the RIPE Database was for contacting people about > operational issues. If many of these 2 million people whose personal > data is held in the RIPE Database are not contacts, is there any legal > justification for having this amount of personal data in the database? > > Also if 'contacts' can be roles rather than identifiable people, can > we justify holding this personal data simply because, historically, > PERSON objects were used instead of ROLE objects? > > cheers > denis > co-chair DB-WG > > > ------------------------------------------------------------------------ > *From:* Nick Hilliard <nick(a)foobar.org> > *To:* denis walker <ripedenis(a)yahoo.co.uk> > *Cc:* DB-WG <db-wg(a)ripe.net> > *Sent:* Sunday, 7 October 2018, 14:56 > *Subject:* Re: [db-wg] PERSON objects in the RIPE Database > > denis walker wrote on 25/09/2018 23:55: > > So really the only question that must be answered is "Can we justify > > holding this amount of personal data on the basis of contacts for > > administrative and technical issues relating to internet resources and > > network operations?" If the answer is 'no' then change MUST happen, > long > > before the universe dies. > > I.e. "is what we have [...] legal"? > > DBWG probably needs to get a legal opinion on this. > > > Nick > > > >

1 0

remove bogon prefixes in the RIPE IRR NON-AUTH DB?
by Job Snijders 09 Oct '18

09 Oct '18

Dear WG, I'd like to raise the issue of bogon prefixes in the RIPE IRR, and ask RIPE NCC to remove all "bogon" route object registrations from the "RIPE-NONAUTH" IRR database. Today I was made aware of this example: $ whois -h whois.ripe.net -- "-Troute6 2001:db8::/32" | egrep -v "%|^$" route6: 2001:db8::/32 origin: AS25375 descr: AS25375 mnt-by: ch-stafag-1-mnt mnt-by: LEUNET-SECURITY-MNT created: 2018-08-25T15:27:50Z last-modified: 2018-08-25T15:27:50Z source: RIPE I'd consider the following prefixes, and any more-specifics of these to be bogons prefixes: 0.0.0.0/8 # RFC 1122 'this' network 10.0.0.0/8 # RFC 1918 private space 100.64.0.0/10 # RFC 6598 Carrier grade nat space 127.0.0.0/8 # RFC 1122 localhost 169.254.0.0/16 # RFC 3927 link local 172.16.0.0/12 # RFC 1918 private space 192.0.2.0/24 # RFC 5737 TEST-NET-1 192.168.0.0/16 # RFC 1918 private space 198.18.0.0/15 # RFC 2544 benchmarking 198.51.100.0/24 # RFC 5737 TEST-NET-2 203.0.113.0/24 # RFC 5737 TEST-NET-3 224.0.0.0/4 # Multicast 240.0.0.0/4 # Reserved ::/8 # RFC 4291 IPv4-compatible, loopback, et al 0100::/64 # RFC 6666 Discard-Only 2001:2::/48 # RFC 5180 BMWG 2001:10::/28 # RFC 4843 ORCHID 2001:db8::/32 # RFC 3849 documentation 3ffe::/16 # RFC 3701 old 6bone fc00::/7 # RFC 4193 unique local unicast fe80::/10 # RFC 4291 link local unicast fec0::/10 # RFC 3879 old site local unicast ff00::/8 # RFC 4291 multicast Any route/route6 objects covered by the above prefixes should be deleted from the database, and the software should be extended in such a way that nobody can register new route/route6 objects covered by the above list. Kind regards, Job

8 10

PERSON objects in the RIPE Database
by denis walker 07 Oct '18

07 Oct '18

Colleagues, I will start with a blunt question, then give some arguments for my concern. In May the RIPE NCC told me there are more than 2 million PERSON objects in the RIPE Database. That is almost 25% of the objects in the database. Who are these people and why do we hold so much personal data? At RIPE 76 the RIPE NCC legal team gave a presentation on GDPR and the RIPE Database. The basis of that presentation seemed to be that Article 3 of the RIPE Database Terms and Conditions defined one of the purposes of the database as: Facilitating coordination between network operators (network problem resolution, outage notification etc.) It was argued that this justifies the inclusion of personal data in the RIPE Database so that these people can be contacted in the event of network operational issues, even by people who have no business relationship with these contacts. But this Article makes no mention of 'personal' contact information. It was also mentioned that some personal data is included for policy reasons. The IPv4 Address Allocation and Assignment Policy makes a couple of references to contact data. In 4.0 Registration Requirements it says: All assignments and allocations must be registered in the RIPE Database....Registration data (range, contact information, status etc.) must be correct at all times This clearly associates contact information with the necessary registration. But this does not specify that it has to be 'personal' contact information. In 6.2 Network Infrastructure and End User Networks it says: 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. This clearly has the intent of avoiding the need to enter 'personal' data as contact information. In the IPv6 Address Allocation and Assignment Policy it is even more vague saying in 3.3 Registration: 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. The goal of registration should be applied within the context of reasonable privacy considerations and applicable laws. 'Reference' information and concerns about privacy again clearly indicate that the intent is to avoid using 'personal' data for the contacts. This does raise a number of questions: -Should I believe that we really do have more than 2 million individual people in this region who can seriously address technical or administrative questions on Internet resources or network operational issues? -Why is it considered necessary for contacts to be identifiable people rather than roles? -Abuse-c was intentionally designed to reference a ROLE object, which no longer needs to have any referenced PERSON objects, to avoid the need to enter personal data, why can't technical matters be addressed in the same way? The purpose in the Terms and Conditions may define a reason for holding contact information, but it doesn't justify this level of personal data being held in the database. Perhaps it's time to review what is meant by 'contact information'. What is really needed to satisfy this purpose? For example, why do we need an address for a technical contact who may need to be contacted in the event of an operational issue? No one is going to go to that address or post a letter. As always your thoughts and opinions are welcome... cheers denis co-chair DB WG

4 7

Re: [db-wg] WG Chair Selection - Call for Discussion
by William Sylvester 05 Oct '18

05 Oct '18

WG Members, Congratulations to everyone on the success of NWI-5! With the deployment behind us and everyone back from holiday in August we are moving to the next step in our chair selection process. This email opens the two (2) weeks of chair selection discussion. All members of the community are encourage to make a discussion and express their approval or otherwise of the presented candidates. The candidates are as follows and have either made their interest known on this mailing list, or directly to the chair(s). I encourage each candidate to reiterate their qualifications to the mailing list. Piotr Strzyzewski Sean Stuart As members of this working group please discuss your approval or otherwise of each candidate. Best regards, Denis & William DB-WG Chairs

4 3

"key-cert" objects - emails listed as "owner" even thou id has been revoked
by netravnen＠gmail.com 03 Oct '18

03 Oct '18

Hi db-wg, Was updating my key-cert object in the database. And was wondering if it is by design revoked key id's is listed as owner of the key? (I would normally expect revoked id's not being listed inside key-cert objects.) The Explanation =============== I have several gpg id's as part of the key. Half is active. Half is revoked id's. All id's; even the revoked ones; is being listed as "owner:" when viewing the key-cert object in the database. -Netravnen

2 1

alloclist.txt
by nusenu 01 Oct '18

01 Oct '18

Hi, before I start parsing the alloclist.txt [1] file (with multiline context) I was wondering if there is a more parse-friendly version of that? (one record per line?) thanks, nusenu [1] https://ftp.ripe.net/pub/stats/ripencc/membership/alloclist.txt -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

2 2

RIPE Policy Proposal 2018-05 Aims to Publish Legal Address Information
by Marco Schmidt 27 Sep '18

27 Sep '18

Dear colleagues, We just published the RIPE Policy proposal, 2018-05, "Publication of Legal Address of Internet Number Resource Holder", to the RIPE NCC Services Group mailing list. The goal of the proposal is for the RIPE NCC to publish the validated legal address information of holders of Internet number resources. As the publishing of such data likely will happen in the RIPE Database, we want to notify the Database Working Group. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-05 We encourage you to review this proposal and send your comments to <ncc-services-wg(a)ripe.net> before 26 October 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

Re: [db-wg] Draft Agenda RIPE77 - Database Working Group
by William Sylvester 25 Sep '18

25 Sep '18

Dear Working Group Members, Below is the DRAFT agenda for the Database Working Group for RIPE77. If you would like to present please submit your content as soon as possible to the chairs. If you have any questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 5 min * Welcome * Scribe * Jabber * Agenda B. Operational Update RIPE Database – 45 mins Edward Shryane, RIPE NCC C. Discussion: PERSON objects in the RIPE Database – 15 mins Denis Walker D. NWI - Open Proposals – 15 mins Z. AOB (open discussion)

1 0

PERSON objects in the RIPE Database
by Alexander Stranzky 21 Sep '18

21 Sep '18

On 20/09/2018 15:04, denis walker via db-wg wrote: > Colleagues, > > I will start with a blunt question, then give some arguments for my > concern. In May the RIPE NCC told me there are?more than 2 million > PERSON objects in the RIPE Database. That is almost 25% of the objects > in the database. Who are these people and why do we hold so much > personal data? Hello, I suspect that many of these objects are old (pre-API) and/or duplicates. Before RIPE had a REST API (and I can't tell how many ISPs still use emails to create their resources) automatically fetching, linking, and updating a RIPE object was a pain (as is the current situation with APNIC) and likely involved someone to create the email personally. Hence going the easy route--making new entries every time. Regards, Alexander Stranzky -- velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * 63452 Hanau Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588 Tel: +49 6181 1898119 * http://www.velia.net

5 7

Re: [db-wg] PERSON objects in the RIPE Database
by Cynthia Revström 20 Sep '18

20 Sep '18

Hi, I am not sure how the best way to do this but maybe check the database for person handles with identical name, address, phone number and such things. Also maybe if we could take a look at the amount of person handles that are not used at all in any other object, and potentially delete them. Kind regards, Cynthia Revström On 2018-09-20 14:57, Alexander Stranzky via db-wg wrote: > On 20/09/2018 15:04, denis walker via db-wg wrote: >> Colleagues, >> >> I will start with a blunt question, then give some arguments for my >> concern. In May the RIPE NCC told me there are?more than 2 million >> PERSON objects in the RIPE Database. That is almost 25% of the objects >> in the database. Who are these people and why do we hold so much >> personal data? > Hello, > > I suspect that many of these objects are old (pre-API) and/or > duplicates. Before RIPE had a REST API (and I can't tell how many ISPs > still use emails to create their resources) automatically fetching, > linking, and updating a RIPE object was a pain (as is the current > situation with APNIC) and likely involved someone to create the email > personally. Hence going the easy route--making new entries every time. > > Regards, > Alexander Stranzky >

2 1

Whois release 1.92.6 deployed to Production
by Edward Shryane 20 Sep '18

20 Sep '18

Dear Working Group, we have deployed a bug-fix release 1.92.6 to production that fixes a bug when updating an object with a lowercase source value (e.g. "source: ripe"). The release notes have been updated: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rel… Regards Ed Shryane RIPE NCC

1 0

avoiding RIPE IRR vs. RPKI ROA mismatches/inconsistencies
by nusenu 13 Sep '18

13 Sep '18

Dear DB Working Group, when looking into RPKI and RIPE IRR coverage I stumbled on prefixes that are covered by a RIPE route object and a RPKI ROA, which is great, but there are cases where these records make conflicting statements about the origin of a prefix. example: 185.46.20.0/22 origin according to ROA: AS199785 origin according to route object: AS61952 origin according to RIS: AS61952 (matches route object) Note: this is just an example to better illustrate the issue. (I didn't do a comprehensive analysis to be able to tell how often this is the case but for a sample of ~1900 prefixes I found 3 such occurrences.) Since route objects and ROAs are created by the prefix holders this is possible (human mistake). Are there any measures in place to prevent or at least warn about the inconsistency when the IP holder creates/updates route objects and ROAs that would result in inconsistencies? What do you think about an UI feature that says something like: "You are about to change/create the route object for prefix ... would you also like to update the existing ROA to match the route object and help avoid inconsistencies?" [ ] yes [ ] no, I know what I'm doing, I'll fix the mismatch manually similarly for updating/creating ROAs. Should there even be a 'No' option? Should the question even be exposed to the user or should records simply be synced automatically once one of either is changed by the IP holder? and simply showing an info like: "We took care of updating your ROA/route object to keep in sync." In case there are well established best practices for an ASN change of a prefix these best practices should be incorporated (i.e. delete the route object and ROA, change the actual announcement in BGP, create new route and ROAs that match the announcement) kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

2 3

Whois release 1.92.5 deployed to Production
by Edward Shryane 11 Sep '18

11 Sep '18

Dear Working Group, after deploying the NWI-5 changes last week, we found an issue preventing out of region transfers (the top-level placeholder template still referenced the RPSL maintainer). We have now deployed a bug-fix release 1.92.5 to production that fixes this issue. Regards Ed Shryane RIPE NCC

1 0

Re: [db-wg] WG Chair Selection - Call for Discussion
by Erik Bais 10 Sep '18

10 Sep '18

In case of 1 chair this time, my vote would be for Sean Stuart. Piotr already got selected for the RIPE exec board last meeting, I’m sure he has enough to deal with on that ‘WG’ 😉 Sean has been looking for a way to volunteer for a while in the community and his background could provide a good fit for the role imho. Regards, Erik Bais From: db-wg <db-wg-bounces(a)ripe.net> on behalf of William Sylvester via db-wg <db-wg(a)ripe.net> Reply-To: William Sylvester <william.sylvester(a)addrex.net> Date: Wednesday 5 September 2018 at 22:32 To: "db-wg(a)ripe.net" <db-wg(a)ripe.net> Subject: Re: [db-wg] WG Chair Selection - Call for Discussion WG Members, Congratulations to everyone on the success of NWI-5! With the deployment behind us and everyone back from holiday in August we are moving to the next step in our chair selection process. This email opens the two (2) weeks of chair selection discussion. All members of the community are encourage to make a discussion and express their approval or otherwise of the presented candidates. The candidates are as follows and have either made their interest known on this mailing list, or directly to the chair(s). I encourage each candidate to reiterate their qualifications to the mailing list. Piotr Strzyzewski Sean Stuart As members of this working group please discuss your approval or otherwise of each candidate. Best regards, Denis & William DB-WG Chairs

2 1

Re: [db-wg] WG Chair Selection - Call for Discussion
by Andy Davidson 06 Sep '18

06 Sep '18

Hi, William Thank you kindly for working on this process. Please could you confirm how many seats are open for selection this time? Are we selecting for one seat or two from this list of people? Andy

2 1