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] DNSMON policy proposal change
- Previous message (by thread): [ncc-services-wg] DNSMON policy proposal change
- Next message (by thread): [ncc-services-wg] DNSMON policy proposal change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Thu Oct 4 15:04:32 CEST 2007
On Thu, Oct 04, 2007 at 01:00:07PM +0200, OndÅ?ej SurÃœ wrote: > policy. I am also attaching new document (ripe-342-1.txt), and diff > between this and current policy (ripe-342.diff). judging from previous discussion I do not expect much controversy on the overall direction, so hopefully touching upon wording isn't premature: > +0. Definitions > + > + a. TLD: Top Level Domain, as recorded by the IANA. > + > + b. ENUM domain: Delegated domain corresponding to E.164 country codes, > + as delegated by RIPE NCC. > + > + b. TLD Administrator: The organisation(s) responsible for the registry > + of a TLD or ENUM domain. I'm not too comfortable seeing the term "TLD" extended into ENUM land. Also, even if "Tier 0/1/2" usually denotes the registry instead of the domain or zone, we should speak of ENUM Tier 1 domains, just as we - on purpose - say "TLD" instead of "Domain". The term "delegated" in (b), while technically perfectly OK, might undergo the same polishing applied to (a). > * the Test Box Hosts, > - * the operators of the root servers and TLD servers, > + * the operators of the root servers, TLD and ENUM domain servers, > * the Internet community in general. ENUM Tier1 Domain name servers, similar below ... > -The RIPE NCC will include the servers of a TLD in the service if that > -TLD Administrator asks for it. Servers of a TLD may be included even > -if the TLD Administrator does not ask for it. The hosts of the TBs > -located inside a TLD may also ask for the TLD servers to be > -monitored. A TLD Administrator that did not ask for its servers to be > -monitored will not have access to the services listed above. > +The RIPE NCC will include the servers of a TLD or ENUM domain in the > +service if that TLD Administrator asks for it. Servers of a TLD or ENUM > +domain may be included even if the TLD Administrator does not ask for > +it. The hosts of the TBs located inside a TLD may also ask for the TLD or > +ENUM domain servers to be monitored. A TLD Administrator that did not ask > +for its servers to be monitored will not have access to the services listed > +above. Unrelated to the proposed change: how can a TB be "located inside a TLD"? > 3.1. Definitions > > - a. TLD Administrator: The organisation(s) responsible for the > - registry of a Top Level Domain, as recorded by the IANA. > + a. TLD: Top Level Domain, as recorded by the IANA, or delegated domain > + corresponding to E.164 country code, as delegated by RIPE NCC. This definition collides with the one provided 0.a. As stated above, we should keep the distinction of TLD and ENUM Tier 1. -Peter PS: Thinking of implementation, the domain overview page is sorted alphabetically, giving preference to the e164.arpa domains right now. Maybe some grouping of ccTLD and e164.arpa (where appropriate) could increase legibility.
- Previous message (by thread): [ncc-services-wg] DNSMON policy proposal change
- Next message (by thread): [ncc-services-wg] DNSMON policy proposal change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]