- db-wg - mailman.ripe.net

Idea: magic mntner for all LIR contacts
by Tore Anderson 03 Dec '18

03 Dec '18

Hi, I'm starting to lose count of how many times I've made changes to the User Accounts list on the LIR Portal, but forgot to update our mntner object to add/remove the corresponding «auth: SSO foo@bar»-attributes. So I was thinking: is this mandatory and error-prone duplication of work really necessary? Wouldn't it be possible to instead have some kind of magic mntner object that is is kept automatically up to date with «auth: SSO»-attributes for all the LIR user accounts? Tore

1 0

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