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/ncc-services-wg@ripe.net/
[ncc-services-wg] querying national infrastructure
- Previous message (by thread): [ncc-services-wg] querying national infrastructure
- Next message (by thread): [ncc-services-wg] RIPE55 Draft Agenda for NCC Service WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carsten Schiefner
ripe-wgs.cs at schiefner.de
Thu Oct 18 13:53:45 CEST 2007
Hi Jim, Jim Reid wrote: > [...] Some clarity is needed here so that everyone knows > what the operating conditions are: ie a statement which makes it clear > that there are no grounds for these sorts of complaints. I guess such constrains could very well go into the DNSMON policy (RIPE-342). I further believe it is defacto handled already this way for the monitored TLDs. > Er, it was me who was recommending that any monitoring would only be > done at the request of the Administration concerned. For some vague > definition of "Administration" which could include the Tier1 registry. I would only see the Tier 1 registry as the requesting entity as it is supposed to act with the consent of the "Administration" anyways. Best, Carsten
- Previous message (by thread): [ncc-services-wg] querying national infrastructure
- Next message (by thread): [ncc-services-wg] RIPE55 Draft Agenda for NCC Service WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]