This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
- Previous message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
- Next message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carsten Schiefner
ripe-wgs.cs at schiefner.de
Tue Oct 18 12:04:05 CEST 2016
Hi Jim, On 18.10.2016 11:36, Jim Reid wrote: > The contractual terms are implementation detail and therefore out of > scope for the WG. This also applies to the RFP and NCC’s selection > procedure. what other forum you would see fit then for such kind of Q&A? > The WG should only intervene here -- ie by asking the NCC board to > investigate -- if we have reason to believe the RFP and/or contract > was unfair or defective in some way. For the record: I am not even only remotely insinuating this by any means at all - I am just a curious Internet Citizen in this regard. But as a side note: how would you come to believe that the RfP and/or contract is unfair or defective in some way, if neither one is disclosed? > The WG must not and can’t (try to) micromanage the NCC’s DNS team. Not that I have attempted this by any means, I think. Best, -C.
- Previous message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
- Next message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]