DNSMON policy proposal change
Hello, I would like this WG to discuss following proposal to change DNSMON policy. I am also attaching new document (ripe-342-1.txt), and diff between this and current policy (ripe-342.diff). Number: TBD Policy Proposal Name: Allow DNSMON services to monitor ENUM domains Author: a. name: Ondrej Sury b. e-mail: ondrej.sury@nic.cz c. organisation: CZ.NIC, z.s.p.o. Proposal Version: 1.0 Submission Date: 2007-08-01 Suggested RIPE Working Group for discussion and publication: ncc-services Proposal type: modify Policy term: permanent Summary of proposal: Policy text: a. Current: see ripe-342.txt b. New: see ripe-342-1.txt Rationale: a. Arguments supporting the proposal ENUM domains are already monitored by DNSMON on request when country ENUM administrator is also ccTLD registry. This proposal formalized this and also allows country ENUM administrators to request such service in case they are not ccTLD registry. b. Arguments opposing the proposal Only one argument was raised during discussion from Jim Reid which oppose idea of NCC doing non-core services for their members. -- Ondřej Surý technický ředitel/Chief Technical Officer ----------------------------------------- CZ.NIC, z.s.p.o. -- .cz domain registry Americká 23,120 00 Praha 2,Czech Republic mailto:ondrej.sury@nic.cz http://nic.cz/ sip:ondrej.sury@nic.cz tel:+420.222745110 mob:+420.739013699 fax:+420.222745112 -----------------------------------------
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.
Peter, others,
-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.
Unrelated to the proposed change: how can a TB be "located inside a TLD"?
What we meant was, even though the wording is perhaps a bit unlucky, that the hosts of TB inside country XX may ask DNSMON to monitor the .XX domain. Henk -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Is one of the choices leaving the office open? Alan Greenspan on the next elections
Henk,
What we meant was, even though the wording is perhaps a bit unlucky, that the hosts of TB inside country XX may ask DNSMON to monitor the .XX domain.
now that you say it! Apologies for the misreading. -Peter
Peter Koch píše v Čt 04. 10. 2007 v 15:04 +0200:
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).
I tried to change as few words as possible. We could change b) and c) to: a. TLD: A Top Level Domain, as recorded by the IANA. b. ENUM Tier-1 domain: A delegated domain corresponding to E.164 country code, as delegated by RIPE NCC. c. Administrator: The organisation(s) responsible for the registry of a TLD or ENUM Tier-1 domain.
* 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 operators of the root servers, TLD and ENUM Tier-1 domain servers,
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.
Maybe we could replace TLD with something like "Monitored Domain"? Again I tried to change as few words as possible. Replacing all "TLD" with "TLD and ENUM Tier-1 domain" doesn't improve readability of the document (and the contract) at all. Ondrej. -- Ondřej Surý technický ředitel/Chief Technical Officer ----------------------------------------- CZ.NIC, z.s.p.o. -- .cz domain registry Americká 23,120 00 Praha 2,Czech Republic mailto:ondrej.sury@nic.cz http://nic.cz/ sip:ondrej.sury@nic.cz tel:+420.222745110 mob:+420.739013699 fax:+420.222745112 -----------------------------------------
participants (3)
-
Henk Uijterwaal -
Ondřej Surý -
Peter Koch