Wat we doen

“Hosting-instellingen zijn gebaat bij periodieke aandacht.”
“Lastige meldingen kunnen verder komen dan support als zandbak.”
“Kennis van IT-standaarden is over te dragen met trainingsmateriaal.”
“Web-ID’s zijn in voorbereiding. ‘Peter Jansen’ kan geen identificatie zijn.”

Veranderend systeembeheer

“De rol van de systeembeheerder verdwijnt niet maar wordt wezenlijk anders. Hij/zij zit niet meer aan de oplos-knoppen (dat doet de leverancier voortaan) maar de systeembeheerder zal veel meer de regie moeten gaan voeren over de leverancier voor het domein waarvoor hij/zij verantwoordelijk wordt.”
Bron: https://www.dirkzwager.nl/kennis/artikelen/help-ik-word-ontzorgd-en-nu/

Towards control over web hosting

Regarding security: ncsc.nl/onderwerpen/basismaatregelen
Reaching the Hall of Fame: nl.internet.nl/halloffame/
Purchasing: janwillemstegink.nl/webhosting-kiezen/
Using my specialist tool: www.hostingtool.nl/server_headers/

Towards control over web domains

What can authorities implement regarding web domains and/or NIS2?

Related to Ministry of Economic Affairs:

  • Include automated task costs in just one annual web domain fee;
  • Include a change in a registrar’s own data in its period costs;
  • Eliminate all registry discounts. A volume discount causes unfair competition;
  • Have SIDN B.V. correct ‘deleted’ to the globally understood ‘expired’, in Dutch ‘verlopen’.

Related to Ministry of the Interior and Ministry of Justice:

  • List all areas of expertise in the NIS2 (/NIS3) IT security optimization;
  • Engage specialists and make decisions. Professionals need dynamic interaction;
  • Set up an EU desk to work towards generic application software related to DNS and registries;
  • Develop well-considered proposals, RFC and non-RFC, for the IANA organization.

EU / US and including generic top-level domain zones:

  • Discuss global design and programming of Registration Data Access Protocol software;
  • Complete Whois with the missing ‘deletion_date’ field. This could ease the transition to RDAP;
  • Introduce in RDAP an emergency entity in order to formally organize backup to get access;
  • Generate web IDs that start with the ISO2 country code, for business entities and natural persons;
  • Plan verification of web domain users indexed by web ID, starting with modeling in RDAP like mine;
  • Build Domain Control Registers, country-specific DCRs, based on the real web domain user;
  • Report regarding expired HTTPS, security.txt or DANE via email. Perhaps a DCR revenue model;
  • Agree on an authority plus input platform, for the DNS and for a dynamic next RDAP protocol;
  • A dynamic RDAP protocol may mean that custom fields get an approved and listed syntax.