Re: [db-wg] Agenda RIPE85 - Database Working Group
Hi William and Denis, Is Denis talking about the proposal as co-chair or as proposal author? If it is the latter then I think it would be good to clarify that. -Cynthia On Mon, Oct 10, 2022 at 7:23 PM William Sylvester via db-wg wrote: > > Below is the agenda for the Database Working Group for RIPE85. If you would > like to present, have questions, comments, or requested changes please let > the chairs know. > > > > Best regards, > > > > William & Denis > > DB-WG Chairs > > > > A. Introduction - 10 min > > Welcome > Scribe > Jabber > Chairs & Succession Planning > Agenda > > > > B. NWI Update – 20 mins Denis Walker, Co-Chair DB-WG > > > > C. Operational Update– 20 mins Edward Shryane, RIPE NCC > > > > D. Geofeed Discussion – 10 mins Denis Walker, Co-Chair DB-WG > > > > E. Proposal 2022-01 – 10 mins Denis Walker, Co-Chair DB-WG > > > > Z. AOB (open discussion) > > > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/db-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
Re: [db-wg] 2022-01 Review Phase (Personal Data in the RIPE Database)
Hi Sander Thanks for the comments and kicking off the new discussion. I have to admit I was a bit confused by some of the comments in the impact analysis, including these. On Sun, 9 Oct 2022 at 13:33, Sander Steffann via db-wg wrote: > > Hi, > > > The RIPE NCC has prepared an impact analysis on this latest proposal > > version to support the community’s discussion. > > > > You can find the proposal and impact analysis at: > > https://www.ripe.net/participate/policies/proposals/2022-01 > > https://www.ripe.net/participate/policies/proposals/2022-01#impact-analysis > > The executive board feedback corresponds to my opinion on this policy, > especially these points: > - It significantly reduces the usability for one of its core purpose - being > able to contact resource holders about their number resources. In what way does my proposal reduce contact with resource holders, never mind significantly? Currently you can contact a resource holder via the ORGANISATION object that may contain: Postal address Phone number Fax number Several email addresses Several contact references If this proposal is accepted it may still contain all of the above. The only changes are that I am saying the phone and email should be business and not their personal details and postal address is optional. A resource holder who wants to add their postal address will still do so. Those who don't may currently add a false address. So there is really no difference in the way you can contact a resource holder. Note that the Database Task Force also recommended making postal address optional and went further to suggest it should then be deprecated. > - It puts at risk the public chain of custody of Internet number resources. I don't see how this proposal in any way impacts the public chain of custody of internet number resources. On the other hand the recent proposal, 2022-02, would completely destroy this chain. > - We would welcome a discussion that focuses more on which parts of the data > are publicly available, rather than a sweeping removal. This is an interesting comment. My first version of this proposal did suggest making some of the data private. There was strong opposition to that idea. But again this proposal is not suggesting any sweeping removal of data (unlike 2022-02). I suggest changing the data from personal based to business role based, not removal. Yes, the PERSON object will be removed. But the contact data will remain as business ROLE data. cheers denis proposal author > > I think a new and more detailed discussion is indeed necessary for this > proposal to go anywhere. The current proposal is not acceptable to me. > > Cheers, > Sander > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/db-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
[db-wg] Agenda RIPE85 - Database Working Group
Below is the agenda for the Database Working Group for RIPE85. If you would like to present, have questions, comments, or requested changes please let the chairs know. Best regards, William & Denis DB-WG Chairs A. Introduction - 10 min * Welcome * Scribe * Jabber * Chairs & Succession Planning * Agenda B. NWI Update – 20 mins Denis Walker, Co-Chair DB-WG C. Operational Update– 20 mins Edward Shryane, RIPE NCC D. Geofeed Discussion – 10 mins Denis Walker, Co-Chair DB-WG E. Proposal 2022-01 – 10 mins Denis Walker, Co-Chair DB-WG Z. AOB (open discussion) -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
Re: [db-wg] Fwd: RIPE Database Service Criticality Questionnaire
> Since we sent out the form below, not one person has responded :( i do not believe that statement to be correct randy -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
[db-wg] Fwd: RIPE Database Service Criticality Questionnaire
Colleagues Since we sent out the form below, not one person has responded :( Vacation time is over, you are no longer sitting on the beach with that glass of wine (not that that should stop you thinking about the RIPE Database)...so can we please have some form filling time to help out the RIPE NCC..and ultimately yourselves. cheers denis co-chair DB-WG -- Forwarded message - From: denis walker Date: Mon, 11 Jul 2022 at 14:50 Subject: RIPE Database Service Criticality Questionnaire To: Database WG Colleagues [Apologies to Job for copying your email from the Routing WG but you explained it well :) ] The RIPE NCC has asked the Database WG Chairs to facilitate a working group conversation on framing the RIPE Database service subcomponents in terms of criticality. At the bottom of this email is a form that focuses on three components: confidentiality, integrity and availability. Each component is split into three questions (a, b, and c), a total of 9 questions are being put forward to the working group. We envisage this process to be a public consultation: WG participants can submit (free-form) responses, and also chime in by replying to each other's responses; hopefully bringing us to a degree of consensus in the coming weeks. We believe this is a unique opportunity to help the RIPE NCC! The goal is to help the RIPE NCC develop a deeper understanding of how the moving parts fit together, which in turn helps decide where and how to invest resources. >>> Your feedback is much appreciated! <<< cheers, denis, William DB WG co-chairs --- FORM STARTS HERE --- Service Criticality Form - RIPE Database Introduction This form is used to gather input from the community on the service criticality of the RIPE database. The framework is detailed in https://labs.ripe.net/author/razvano/service-criticality-framework/ The service criticality has three components: * Confidentiality What is the highest possible impact of a data confidentiality -related incident (data leak)? * Integrity What is the highest possible impact of a data integrity -related incident (hacking)? * Availability What is the highest possible impact of a service availability -related incident (outage)? All our services are designed with at least 99% availability, so please consider outages of up to 22 hours. Service Purpose --- The RIPE Database is the public internet registry for the RIPE NCC region, comprised of: * Internet Number Registry * Internet Routing Registry * Reverse Delegations The critical parts of the service are: * Query (Port 43, REST API, NRTM, Web Application) * FTP dumps (whole database and split files) The non-critical part of the service is: * Update (REST API, Mailupdates, Syncupdates) Service Criticality --- Please review the following three areas. (1) Global Routing Incident Severity * Low (No / negligible impact) * Medium (One or a few ASes are unavailable) * High (Many ASes in a region are unavailable) * Very High (Global Internet routing disruptions) Please rate the incident severity (Low to Very High) in the following three areas. Please explain why. (a) Confidentiality (Impact level of incidents such as data leaks) (b) Integrity (Impact level of incidents such as hack attempts) (c) Availability (Impact level of service outage incidents, up to 22 hours per quarter) (2) IP addresses and AS Numbers Incident Severity * Low (No / negligible impact) * Medium (Local disruptions (registration information not being available for some entities)) * High (Regional disruptions (registration information not being available for the RIPE NCC region)) * Very High (Global disruptions (lack of registration information for all AS Numbers and IP addresses)) Please rate the incident severity (Low to Very High) in the following three areas. Please explain why. (a) Confidentiality (Impact level of incidents such as data leaks) (b) Integrity (Impact level of incidents such as hack attempts) (c) Availability (Impact level of service outage incidents, up to 22 hours per quarter) (3) Global DNS Incident Severity * Low (No / negligible impact) * Medium (Local disruptions) * High (Regional disruptions) * Very High (Global disruptions) Please rate the incident severity (Low to Very High) in the following three areas. Please explain why. (a) Confidentiality (Impact level of incidents such as data leaks) (b) Integrity (Impact level of incidents such as hack attempts) (c) Availability (Impact level of service outage incidents, up to 22 hours per quarter) -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
Re: [db-wg] Whois Release 1.104
Dear Colleagues, We have now deployed Whois 1.104 to production. Regards Ed Shryane RIPE NCC > On 26 Sep 2022, at 18:11, Edward Shryane via db-wg wrote: > > Dear Colleagues, > > RIPE Database release 1.104 has been deployed to the Release Candidate > environment. We plan to deploy to production on Monday 10th October. > > This release includes the following main changes: > > * Allow Grouping (-G) flag in Whois Search API (#1077) > * cidr0 notation for rdap response (#1068) > * Remove whois tags (#1059) > * Added text/plain to Search and REST APIs (#1054) > * Add comment not NOOP (#1052) > * Do not allow comments in managed attributes (#1045) > * Use documentation prefix 192.0.2.0/24 (#1044) > * Organisation country: is modifiable for end-user orgs without RIPE NCC > resources (#1041) > * Do not return deleted versions (#1015) > * Redirect empty requests to syncupdates help (#1011) > > The release notes are on the website: > https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-release-1.104 > > 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-candidate-environment > > Please let us know if you find any issues with this release in the RC > environment. > > Regards > Ed Shryane > RIPE NCC > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/db-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
