- db-wg - mailman.ripe.net

Whois Release 1.112.1
by Edward Shryane 24 Jun '24

24 Jun '24

Dear colleagues, RIPE Database release 1.112.1 has been deployed to the PRODUCTION environment just now. This is a bugfix release to help mitigate the ongoing production issue caused by many updates containing objects with an unusual amount of references. This is the only change from release 1.112. We will also apply this change to the upcoming 1.113 release (due next Monday, 1st July). We will continue to monitor for any more incidents, and will publish a full post-mortem later. Regards Ed Shryane RIPE NCC

1 0

RPSL for for foreigh IPv6 space
by Randy Bush 23 Jun '24

23 Jun '24

hi, All of RGnet's address space, mostly legacy, is in the RIPE whois, with RPKI etc. Except ... RGnet has three IPv6 /48s from NTT. Cogent filters BGP based on RPSL, and wants the RPSL for our ASs to be in the appropriate RPSL route6: objects, each with the appropriate AS. This is pretty old-fashioned and reasonable. Do we figure out how to register the route6: objects in NTT and presume Cogent will pick them up across IRR instances? Do we try some hack to violate the RIPE database's pristine authority model? Do we give up on this silly IPv6 stuff? [ just kidding, gert :) ] Surely other have been here before us. randy

3 2

RIPE Policy document updated “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” (ripe-826)
by Angela Dall'Ara 20 Jun '24

20 Jun '24

Dear Colleagues, The RIPE policy “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” has been updated to align with the implementation of NWI4, done in Whois release 1.112, which added the option to change the status of an IPv4 allocation object in the RIPE Database from “ALLOCATED PA” to “ALLOCATED-ASSIGNED PA” when the whole address space is assigned to the LIR infrastructure or for use by an End User with services provided by the issuing LIR. The new document is called ripe-826 and is available at: https://www.ripe.net/publications/docs/ripe-826/ Please note that also the following has been updated: 1) In the Abstract: The link to the webpage where to find information on the Address Policy WG from https://www.ripe.net/participate/ripe/wg/ap to https://www.ripe.net/community/wg/active-wg/ap/ 2) In 1.1 Scope: The link to the webpage listing the RIPE community’s policies: from https://www.ripe.net/ripe-policies to https://www.ripe.net/publications/docs/ripe-policies/ 3) In 5.3 Sub-Allocations The option to ask for a conversion of PI to PA via LIR Portal has been added. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 0

So what happened last night to the DB?
by Hank Nussbacher 17 Jun '24

17 Jun '24

3 2

Re: [db-wg] So what happened last night to the DB?
by Lutz Donnerhacke 17 Jun '24

17 Jun '24

> I have thought about doing it so, as I was also included as the > maintainers of the object. The real question is: why did blake66 made > such an object ? And how could we prevent something alike to happen > again (not an easy question -- maybe limiting the amount of mnt-by ?) Especially the DB should not process backscatter messages from MAILER-DAEMON.

1 0

Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes
by Edward Shryane 28 May '24

28 May '24

Dear colleagues, Currently the RIPE database only allows a subset of ASCII characters in the "org-name:", "person:" and "role:" attributes, for a few reasons including: * These attributes are also a look-up key and the Whois protocol does not allow specifying character sets in queries. * RPSL names are ASCII according to RFC2622 * Using a normalised name makes the object easier to query * Reading a normalised name is easier to interpret However there are some drawbacks to forcing names to only use a subset of ASCII characters: * Organisations, roles and persons cannot use their actual name if it includes characters outside this subset. * Normalisation is not standard, but is an interpretation done by each maintainer, e.g. characters could be excluded or converted in different ways. Since we support the Latin-1 character set in the RIPE database, I propose we also allow non-ASCII Latin-1 characters in these attributes. Querying for a name can be done either using the latin-1 characters (proposed) or a normalised, ASCII representation (currently). The normalised version will be generated by Whois and stored in a database index for querying. The primary key will also be generated from the normalised version. Please let me know your feedback. Regards Ed Shryane RIPE NCC --- Whois attribute verbose description (copied from the help text). org-name -------- Specifies the name of the organisation that this organisation object represents in the RIPE Database. This is an ASCII-only text attribute. The restriction is because this attribute is a look-up key and the whois protocol does not allow specifying character sets in queries. The user can put the name of the organisation in non-ASCII character sets in the "descr:" attribute if required. A list of 1 to 30 words separated by white space. A word is made up of ASCII alphanumeric characters and additionally: ][)(._"*@,&:!'`+/- A word may have up to 64 characters and is not case sensitive. Each word can have any combination of the above characters with no restriction on the start or end of a word. person ------ Specifies the full name of an administrative, technical or zone contact person for other objects in the database. It should contain 2 to 10 words. A word is made up of ASCII alphanumeric characters and additionally: .`'_- The first word should begin with a letter. At least one other word should also begin with a letter. Max 64 characters can be used in each word. role ---- Specifies the full name of a role entity, e.g. RIPE DBM. A list of 1 to 30 words separated by white space. A word is made up of ASCII alphanumeric characters and additionally: ][)(._"*@,&:!'`+/- A word may have up to 64 characters and is not case sensitive. Each word can have any combination of the above characters with no restriction on the start or end of a word.

9 17

Historical data on deleted objects
by Yang Yu 27 May '24

27 May '24

Hi, According to https://apps.db.ripe.net/docs/Types-of-Queries/Historical-Queries/ , historical query doesn't return data on deleted objects. This behavior makes it difficult to distinguish whether a resource was squatted on / analyze history associated with abuse on the resource. And it is not consistent with other RIR's whowas behavior. Currently on RIPE whowas UI unallocated and deleted objects look exactly the same. https://stat.ripe.net/widget/historical-whois#w.resource=as199256 Last time the discussion came up appears to be https://www.ripe.net/ripe/mail/archives/db-wg/2013-November/004195.html Can history support for deleted objects get implemented? Thanks. Yang

3 5

Preferred names in the database
by Harry Cross 22 May '24

22 May '24

Dear all (copying this to both the Diversity list and the Database list), I hope you’re having a wonderful weekend and recovering from Rome. I’d like to begin thinking about a proposal for preferred names in the database/on resources. Some may have noticed this week (and for a bit prior), I have begun going by Harri instead of Harry. At the moment there is no correct way for me to represent this in the database, as an LIR the details have to match my legal name. I may think about going through the legal processes to change this soon (albeit in the UK this is easier than a lot of places). I know a few people hold their resources under a shell company for this purpose, (e.g I could incorporate Harri Cross Limited to hold the resources and be in the database). This applies to end users who hold PI or ASNs alongside LIRs. It would be good for us to think about a way for these preferred names (and pronouns?) to be shown in the database alongside the process for changing the name of an end user. I know the preferred way a lot of people in this situation would like this to be handled is to totally mask the legal name in the database. The NCC could still validate legal names to know who they are working with - and we will need some compromise here I suspect. A complete lack of verification is of course a bad thing. I have experienced talking to the NCC when handling end users in these situations who have legally name changed and the process seems to be incredibly hard with the lack of understanding on documentation for name changes. Responses from the Registry have included “How can we be sure that <oldName> and <newName> are not identical twins?” (Which in my mind, is rather disrespectful). I also have another name change in process that is being stonewalled by a lack of understanding of documents in different jurisdictions for this. Kind Regards, Harri Sent from Outlook for iOS<https://aka.ms/o0ukef>

3 2

RIPE 88 chair selection
by David Tatlisu 21 May '24

21 May '24

Dear colleagues, This is a brief reminder that the DB WG co-chair selection will happen at the Database Working Group session on Thursday. Please have your personal Meetecho link ready. We planned a time slot to discuss the recent changes in the chair selection process, as there has been a lot of discussion between the chairs. Kind regards, David RIPE DB WG co-chair

1 0

Whois Release 1.112
by Edward Shryane 21 May '24

21 May '24

Dear colleagues, RIPE Database release 1.112 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Thursday 16th May. The 1.112 release has the following main changes: * NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432) * Set Charset Flag (#1450) * Don't allow "mnt-lower" on assignments (#1452) * Fixed Syncupdates HELP Bug (#1453) * RDAP Link Title is a String not List (#1445) * Route ROA checker (#1416) * Allow inverse query for sponsoring-org from all addresses (#1431) * Return 404 on invalid NRTMv4 notification file path (#1422) The release notes are on the website: https://rc.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-112 More information on the Release Candidate environment can be found on our website: https://apps.db.ripe.net/docs/Release-Notes/ The data in the RC environment is a dummified copy of production from 30th April. Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

2 5

Agenda RIPE88 - Database Working Group [REVISED]
by William Sylvester 17 May '24

17 May '24

All, Here is the revised agenda for the Database Working Group for RIPE88. If you would like to present, have questions, comments, or requested changes please let the chairs know. Best regards, William, Denis, & David DB-WG Chairs A. Introduction - 15 min * Welcome * Scribe * Agenda B. Operational Update– 20 mins Edward Shryane, RIPE NCC C. Adding Contact Methods in Whois & RDAP – 15 mins, Cynthia Revström, Dmitry Kohmanyuk, Leo Vegoda C. NWI Review – 15 mins, WG Chairs D. WG Discussion – 25 mins, WG Chairs Z. AOB (open discussion)

1 0

Update to RIPE Database Terms & Conditions
by denis walker 17 May '24

17 May '24

Colleagues In the Impact Analysis (IA) for 2023-04, the RIPE NCC legal team expressed rules for entering personal data into the RIPE Database that are quite different to our previous understanding. This legal IA was relied on heavily by the proposers of 2023-04 and constantly referred to by them during the policy discussions. Based on the discussions and the IA, the chairs of the AP-WG have now approved the proposal 2023-04. We MUST now update the RIPE Database Terms and Conditions to reflect this new understanding on personal data. In the IA the legal team said this: "Inserting any personal data in the RIPE Database must be in compliance with the RIPE Database Terms and Conditions, even when it relates to the contact details of the member’s own contact person(s). In particular, before anyone updates the RIPE Database with personal data, they must obtain the contact person’s informed and expressed consent and ensure this data is kept accurate and up-to-date." Article 6.3 of the RIPE Database Terms and Conditions currently says: "The Maintainer who enters personal data into the RIPE Database has a responsibility to inform the individual to whom the data pertains and to obtain their explicit consent for the entry in the public RIPE Database if required by law." This article does not accurately reflect the statement in the IA by the legal team. The text "if required by law." must be removed. This suggests that some personal data may not need the 'contact person’s informed and expressed consent'. The IA makes it clear that all personal data entered into the RIPE Database must have the 'contact person’s informed and expressed consent'. There are no exceptions or caveats to this consent. Also the responsibility must not be restricted to the 'Maintainer'. ANYONE has the capability to enter personal data into the RIPE Database. This personal data can then be referenced by a Maintainer of resource data. I would suggest Article 6.3 says something like this: "Anyone who updates the RIPE Database with personal data must obtain the contact person’s informed and expressed consent to enter their personal details into a global, freely accessible, public database. This consent cannot be subject to any conditions. If the consent is withdrawn, the personal data must be removed from the RIPE Database in a reasonable time frame. The personal data must be kept accurate and up-to-date. The right to use some Internet resources requires a consenting contact. If no such contact person is available, the right to use some Internet resources may be revoked." This is a clear and honest statement that fully reflects the IA understanding of the use of personal data in the RIPE Database. I would like to ask the RIPE NCC legal team to make arrangements for this update to the Terms and Conditions. cheers denis co-chair DB-WG ======================================================== DISCLAIMER Everything I said above is my personal, professional opinion. It is what I believe to be honest and true to the best of my knowledge. No one in this industry pays me anything. I have nothing to gain or lose by any decision. I push for what I believe is for the good of the Internet, in some small way. Nothing I say is ever intended to be offensive or a personal attack. Even if I strongly disagree with you or question your motives. Politicians question each other's motives all the time. RIPE discussion is often as much about politics and self interest as it is technical. I have a style of writing that some may not be familiar with, others sometimes use it against me. I also have OCD. It makes me see the world slightly differently to others. It drives my mind's obsessive need for detail. I can not change the way I express my detailed opinions. People may choose how to interpret them. ========================================================

2 5

Unintended consequences of 2023-04
by denis walker 15 May '24

15 May '24

Colleagues The proposers of 2023-04 assured the community that their motivation was purely to provide aggregation, an optional, minor, inconsequential feature that did not change anything else. So if their minds were focused purely on aggregation, as they have told us and we must accept that without question, then it is reasonable to expect that they put a lot of effort into getting all the details and implications of aggregation correct. Unfortunately they seem to have missed quite a lot of details and consequences. Nothing much was said throughout the whole discussion, nor in the policy proposal itself, about where AGGREGATED-BY-LIR fits in relation to other status values. Nothing was said about the semantics of the RIPE Database. So, as it has not been explicitly stated what types of address space can be created more specific to an aggregation, we can have partitions, sub-allocations and assignments. The assignments can either be directly under the aggregation or from any of the multiple, same level or hierarchical levels of sub-allocations. There can be quite a complex structure of address space more specific to an aggregation, but you may never know because none of it needs to be documented in the RIPE Database. The boundaries of aggregations have not been defined. So they can overlap the boundaries of assignments that do not have objects in the database. If objects are created in the database, the software will not allow any overlapping objects to be created. Objects must be fully contained within the boundaries of a less specific object. But now that objects do not need to be created and they are not of a fixed size, you can do whatever you want. This can be by mistake or intentional. So resource holders can now delete all assignments from an allocation and create two equal sized aggregation objects. If the boundaries of the aggregations overlap the existing assignments it doesn't matter as long as you delete the assignment objects first. Nothing prohibits the creation of sub-allocations within an aggregation. The definition simply says "This address space has been assigned...". It does not state that the assignment must be only one level more specific to the aggregation. So you can create as complex a structure as you wish with multiple sub-allocations in a hierarchy and multiple sub-allocations on the same level within the hierarchy, as long as it ends with an assignment. Then you have satisfied the condition that "This address space has been assigned". You think that is bad...it gets worse... Previously it was not permitted to sub-assign. So you could not create an assignment more specific to an existing assignment. Now this is permitted. The policy says: "The creation of an inetnum object with a status of "ASSIGNED PA" or "ASSIGNED PI" is only possible if there is no less specific or more specific inetnum object with an "ASSIGNED" status." How many times have I said "words matter"!!! And still no one listens. This rule relates to 'objects' in the RIPE Database. It does NOT refer to 'assignments'. Previously it meant the same as an assignment could only exist if there was an assignment 'object' in the database. Now we do not need to create assignment objects in the database. Now you can create hierarchies of multiple assignments as deep as you like, provided no more than one of those assignments is represented in the database by an assignment object. Now some will say that we all 'know what it means' and people will respect the 'spirit' of the policy. IPv4 runout proved that 'spirit' and 'intent' are meaningless. All that matters is what is actually written in the policy and how those words can be literally interpreted. Before runout, the 'intent' was to keep the last bits of IPv4 for new entrants into the industry who intended to provide LIR services and needed that little bit of IPv4 for their infrastructure. That intent was never written into the policy, so it was heavily ignored by everyone. Existing members, financial investors and the RIPE NCC. It turned into a land grab for free address space for profit. So the only thing that matters is the actual words in the policy. Sub-assignment to any level is now permitted. You think that is bad...it gets even worse... We can now have duplicate and overlapping assignments to multiple End Users. There is no requirement for resource holders to have state of the art IPAM systems. A notebook on an office desk is perfectly valid. The same address block could be assigned to multiple End Users. Or two address blocks with an overlap. This could be accidental or intentional. Previously, you had to create the assignment objects in the database for an assignment to be valid. The database software prevented duplicate or overlapping assignments. Now you don't need to create these objects so there is no final check to prevent mistakes or deliberate intent. I don't know much about how internet technical operations work, so I am just going to put some thoughts here. People with more knowledge than I have can consider these scenarios to see if it is a problem. Suppose overlapping assignments are given to two End Users. Suppose they each only use the first few addresses of their respective assignments. Then only one is using the overlapping addresses. Can the LIR know for sure which End User is actually using those overlapping addresses? If not, then if some criminal activity occurs with those addresses, who committed the crime? We have also created a situation now where people with criminal intent can construct hierarchies of data that would hide the End User for a long period of time. Based on a comment by Europol that a court order can take months to get the information, we are looking at possibly delaying the identification of an End User by a couple of years. I won't describe how this can be done here. I don't want to give an instruction manual to criminals. I will explain it to Europol when I see them at RIPE 88. Looking at different parts of the address policy, there are other concerns now. (Yes I know this is the DB-WG and some people will use this to deflect attention away from the message by attacking the messenger. A frequently used tactic. But as I said over there, on the other list, not everything fits perfectly within the bounds of one WG. There is considerable overlap between Database and Address Policy.) 3.0 Goals of the Internet Registry System Because of the issue of duplicate and overlapping assignments mentioned above, two of the 4 goals of the Internet Registry System can no longer be guaranteed. 3.1 Uniqueness: this can no longer be maintained if it is possible to assign the same addresses to multiple End Users. 3.4 Registration: the public registry no longer contains sufficient detail to ensure uniqueness. 4.0 Registration Requirements The level of detail in the RIPE Database is no longer sufficient to ensure uniqueness. "Only allocations and assignments registered in the RIPE Database are considered valid." It is no longer possible to validate assignments that are aggregated. So this requirement no longer has any meaning. 6.3 Validity of an Assignment "An assignment is valid as long as the original criteria on which it was based remain valid and it is properly registered in the RIPE Database." Again because of the lack of detail about assignments within an aggregation is is not possible to determine if an assignment is valid. Although with or without aggregation, I am not sure what this 'validity' means in the real world. Was it to show if an IP address is actually assigned to an End User or maybe it is unused address space that has been hijacked? I have no idea how the 'original criteria' for an assignment is documented in the RIPE Database registry or any changes to that original criteria. Is this another example or registration rules that we have lost the meaning of? You can fix all this wording if you want, but in the end it makes no difference. Previously the policy said all resource holders MUST document assignments in the database. Some chose not to do that, even though it was mandatory. It seems the community has accepted that some resource holders refused to comply with mandatory policy. The RIPE NCC had no power to enforce the policy, other than the nuclear option of closure. One of the arguments for 2023-04 was that if we dilute the registration requirements, maybe a few more resource holders will choose to comply with the policy. If you make new rules about aggregation, some will choose to ignore them. Before we could see who chose to ignore the registration of assignments. Now we will have no idea who is ignoring any new rules. It's all hidden inside the aggregations. The proposers frequently referred to IPv6 and kept telling us how wonderful everything was 'over there'. So I had a look and not everything is rosy in the IPv6 garden. Let's look at some numbers. There are 16,144 /29 allocation objects. 11,246 of them have no more specific objects (i.e. nothing underneath the /29). That is about 70% of all the allocated IPv6 is either not in use or nothing has been registered about usage. If it is not in use, that is a huge stockpile of unused IPv6 address space. Why is it out there at all if no one is using it? If a lot of it is in use, even if it is only one assignment for the LIRs infrastructure, then it is a huge rejection of the registration policy to register nothing in the RIPE Database. So which one is it? A massive stockpile of unused address space or large scale refusal to register anything? There are only 4,898 /29 allocations that have any more specifics. Of these, 370 of them have 2 /30's with status (ALLOCATED-BY-LIR or AGGREGATED-BY-LIR) with *nothing* more specific below the /30's. That is about 7.6% of the registered in use IPv6 that tells us nothing about End Users. Of the 370 objects, 88 of them have two sub-allocations (ALLOCATED-BY-LIR) with no more specifics. So they don't even register any aggregations. I checked a number of these sub-allocation objects randomly and not one of them even had a mnt-lower. So the sub-allocation holder can't even create any aggregations or assignments. I also found a batch of them allocated to the same resource holder where both the /30 objects have been deleted in the last couple of weeks since these numbers were generated. The proposers of 2023-04 claimed IPv6 to be a beacon of perfection and used that to argue that nothing will go wrong with adding aggregation to IPv4. From my brief look at IPv6 all I see is a lot of very dodgy looking data with little information. I suspect that will become the reality for IPv4... So this optional, minor, inconsequential feature seems to have changed quite a lot. Is it worth all this for aggregation? I suspect many people will consider it worth it to make assignments optional. cheers denis co-chair DB-WG ======================================================== DISCLAIMER Everything I said above is my personal, professional opinion. It is what I believe to be honest and true to the best of my knowledge. No one in this industry pays me anything. I have nothing to gain or lose by any decision. I push for what I believe is for the good of the Internet, in some small way. Nothing I say is ever intended to be offensive or a personal attack. Even if I strongly disagree with you or question your motives. Politicians question each other's motives all the time. RIPE discussion is often as much about politics and self interest as it is technical. I have a style of writing that some may not be familiar with, others sometimes use it against me. I also have OCD. It makes me see the world slightly differently to others. It drives my mind's obsessive need for detail. I can not change the way I express my detailed opinions. People may choose how to interpret them. ========================================================

2 1

Agenda RIPE88 - Database Working Group
by William Sylvester 15 May '24

15 May '24

All, Here is the proposed agenda for the Database Working Group for RIPE88. If you would like to present, have questions, comments, or requested changes please let the chairs know. Best regards, William, Denis, & David DB-WG Chairs A. Introduction - 15 min * Welcome * Scribe * Agenda B. Operational Update– 25 mins Edward Shryane, RIPE NCC C. NWI Review – 15 mins, WG Chairs D. WG Discussion – 25 mins, WG Chairs Z. AOB (open discussion)

1 0

Re: [db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois
by Lutz Donnerhacke 13 May '24

13 May '24

* Denis Walker wrote: > But looking through lots of email notifications about changes that you > already know about, because you did them, and maybe in the middle is a > notification of an attempted security breach that failed on > authentication (that you may miss), doesn't that also eat up brain > cycles? Please do not assume that LIR activities are single handed everywhere. Several LIRs do have an automation (i.e. netbox) to update the RIPE DB. Others might have multiple independent people working with RIPE on their own behalf. So notifications, especially the notify: attribute are currently in use. > So how about a compromise. A full audit trail of all details of all > changes to all your data available by default to designated people > through your portal account. Plus a daily email summarising all the > changes also sent to people whose email addresses are set up in the > portal account. So still no notif email addresses needed all across > the database. This could even be done per maintainer. How about using the notify: attribute for notifications?

7 8

Re: [db-wg] Call for Volunteers for RIPE Database Working Group Co-Chair
by Randy Bush 07 May '24

07 May '24

> Peter Hessler volunteered for the working group co-chair position. cool beans! thanks peter. randy

1 0

Proceeding with NWI-4
by David Tatlisu 02 May '24

02 May '24

Hi everyone, Following recent discussions the working group chairs have determined the new "status" option for NWI-4 garnered the most support. The working group chairs would like to ask the NCC to proceed with the implementation. Your feedback and engagement have been invaluable throughout this process, and we appreciate your continued involvement as we move forward with NWI-4. Kind regards, Denis, William, and David

2 1

Overly specific inet6num objects by Hetzner
by Semisol 27 Apr '24

27 Apr '24

Hetzner apparently creates an `inet6num` object per dedicated server allocation (enough to get my IP blocked for 1 day trying to query them all), and it took several seconds to execute the query. > whois -r -- "-i mnt-by HOS-GUN -T inet6num" (warning: this will get your IP blocked) Some questions: 1. Is there any policy about "too specific" objects? 2. Is there any plans to restrict how many objects a single query can get at once?

2 1

Re: [db-wg] Call for Volunteers for RIPE Database Working Group Co-Chair
by David Tatlisu 24 Apr '24

24 Apr '24

Dear colleagues, Peter Hessler volunteered for the working group co-chair position. He wrote: I've been active for the last few years as a member, and I would like to contribute more by helping to guide the working group. I did not receive any other emails from volunteers. Please keep in mind that the official selection will take place during the DB WG session at RIPE 88. Furthermore, I would like to thank Peter in my personal capacity for volunteering and for his many contributions to the working group. Kind regards, David RIPE DB WG co-chair

2 1

creating a second route object
by Aleksi Suhonen 16 Apr '24

16 Apr '24

Hi, When migrating a route from one ASN to another, the best practice is to create a second route(6) object for it with the new origin. The creation of the new object is dependent on the "mnt-routes:" field of the enclosing inetnum(6) object. Am I correct thus far? Because I'm running into an issue. When trying to create a new route object using the LIR portal, I'm getting an error that the route is not authenticated by the maintainer of _the other_ route object. Am I missing something obvious, or have I found a bug/regression? BR, -- Aleksi Suhonen () ascii ribbon campaign /\ support plain text e-mail

6 7

Whois Inverse Query by "sponsoring-org:" Attribute
by Edward Shryane 08 Apr '24

08 Apr '24

Dear colleagues, Currently, Whois query does not support the "sponsoring-org:" attribute in an inverse query, i.e. to find all resources sponsored by an organisation. The "sponsoring-org:' attribute was added to the RIPE database in these policies, but there's no mention of support for inverse queries: 2012-08: https://www.ripe.net/membership/policies/proposals/2012-08/ 2014-06: https://www.ripe.net/membership/policies/proposals/2014-06/ If there is no objection, I propose for consistency to also add "sponsoring-org:" to the list of inverse query attributes. Regards Ed Shryane RIPE NCC

18 19

email's disappeared from RDAP output
by Ben Cartwright-Cox 05 Apr '24

05 Apr '24

Hi everybody, I was just re-running some tests internally within bgp.tools and I've noticed that the RDAP responses from RIPE no longer include the email address of the person object. For example I used to (and expected) to get the email address in the object for https://rdap.db.ripe.net/entity/BC6775-RIPE, but it seems to have been removed from the output at some point. That does not appear to be a way to log in to authenticate trustworthiness of RDAP responses, is there any other way to get this information? I can see this information on the RIPE website ( https://apps.db.ripe.net/db-web-ui/lookup?source=ripe&key=BC6775-RIPE&type=… ) but I do not want to scrape that, and this information is incredibly useful for helping users onboard ( with a trustworthy email address ) to services like bgp.tools. Is this an intended change? Have I done something silly? All of the above ;) ? By looking at the release info I can see it was added in November (#1333) Thanks Ben

7 18

Call for Volunteers for RIPE Database Working Group Co-Chair
by David Tatlisu 29 Mar '24

29 Mar '24

********************************************************************************** Please DO NOT reply to this message if you wish to propose a volunteer. ********************************************************************************** Dear colleagues, We would like to invite you to volunteer for the role of the co-chair of the RIPE Database working group. We will have two seats to fill at RIPE 88. Anyone can volunteer for this role. You can also nominate others. Please send a mail to db-wg-volunteers(a)tatlisu.eu before 22 April. Please DO NOT send your name directly to the DB WG mailing list. Please include your motivation and any ideas you might have for the future of the RIPE Database WG. I will then publish the list of volunteers to this mailing list no later than 24 April. Any statements of support on the mailing list are welcome. However, the selection will take place during the DB WG session at RIPE 88. You can find a job description for RIPE WG Chairs here: https://www.ripe.net/publications/docs/wgchair-job-description You can find an e-learning course about the role and responsibilities of RIPE Working Chairs here: https://academy.ripe.net/enrol/index.php?id=16 Please feel free to contact me directly if you have any questions about the role or the process. Kind regards, David RIPE DB WG co-chair

4 5

Whois Release 1.111
by Edward Shryane 28 Mar '24

28 Mar '24

Dear colleagues, RIPE Database release 1.111 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Thursday 28th March. The 1.111 release has the following main changes: * Don't send email to undeliverable addresses (#1404) * Add email unsubscribe support This release is *combined* with the 1.110 release, which we had planned to deploy in March. However as we have an upcoming deadline in April to comply with email anti-spam requirements, we decided to combine the releases. We will explain those changes separately. The 1.110 release has the following main changes: * Implemented RDAP Extension for Geofeed Data (draft-ietf-regext-rdap-geofeed-01) (#1366) * Improve RDAP documentation (#1373, #1388) * Implement RDAP RIR Search - Basic Search Features (#1379) * Enable e-mail in RDAP entity responses (in top level vcard) (#1384) * Add geofeed as a link to conform with v1 draft (#1374) * Separate secure connector for Client Certificate authentication (#1390) * Use clientip flag as remote address from trusted source (#1391) * Redirect HTTP(S) requests to whois.ripe.net to the DB web application query page (#1396) * Elasticsearch refreshed after update/create (#1367) * Document inet6num assignment-size maximum prefix (#1375) * Daily limit is configurable (#1401) The release notes are on the website: https://rc.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-111 More information on the Release Candidate environment can be found on our website: https://apps.db.ripe.net/docs/Release-Notes/ The data in the RC environment is a dummified copy of production from 19th February. Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

1 1

Complying with Mail Provider Requirements When Sending Mail from Whois
by Edward Shryane 19 Mar '24

19 Mar '24

Dear colleagues, As part of the Whois 1.111 release planned for 28th March, we will make changes to comply with new requirements for bulk email senders from two of the large email providers, namely Google [1][2] and Yahoo [3][4]. The RIPE NCC are reviewing these requirements across all our services. Please refer to the RIPE Labs article published today [5]. We send a lot of mail from Whois, on average 30,000 messages a day (comprised mostly of update acknowledgements and notifications) which qualifies us as a bulk sender. We want to comply with these requirements as we depend on email for notifications but also to listen to our users wishes. There are nearly 900,000 email addresses in the RIPE Database. 65,000 are hosted by Google and 5,000 by Yahoo, so these addresses are directly affected by these requirements. In this release, we will implement mail bounce detection (i.e. an outgoing message has permanently failed delivery) and also unsubscription (i.e. one-click unsubscribe from a mail client). Once an address is undeliverable or unsubscribed, we will not send further Whois update acknowledgements or notifications to that address. However we will continue to send targeted notifications where required by RIPE policy (e.g. abuse-c validation, RIPE-NONAUTH route object cleanup etc.). Notification attributes in the RIPE Database (i.e. irt-nfy, mnt-nfy, notify, ref-nfy, upd-to) will be affected, as we will no longer send update notifications to an unsubscribed or undeliverable address. In update acknowledgements we will warn if any address is undeliverable or unsubscribed. Once unsubscribed, if you want to re-subscribe, for now you will need to contact RIPE NCC support [6]. The changes can already be tested in our Release Candidate environment [7]. We welcome feedback from the community. Regards Ed Shryane RIPE NCC --- References 1. Google announcement: https://blog.google/products/gmail/gmail-security-authentication-spam-prote… 2. Google email sender guidelines: https://support.google.com/a/answer/81126?hl=en 3. Yahoo announcement: https://blog.postmaster.yahooinc.com/post/730172167494483968/more-secure-le… 4. Yahoo sender best practices: https://senders.yahooinc.com/best-practices/ 5. Enhancing Email Delivery at the RIPE NCC: https://labs.ripe.net/author/fergalc/enhancing-email-delivery-at-the-ripe-n… 6. Contacting the RIPE NCC https://www.ripe.net/support/contact/ 7. Release candidate environment https://apps.db.ripe.net/docs/Release-Notes/#release-candidate-environment

3 4