- tld-wg - mailman.ripe.net

Some ideas on the future direction of the RIPE TLD-WG
by schneider＠switch.ch 13 Sep '99

13 Sep '99

On Monday, 13 Sep 1999, "Kurt Jaeger" writes: Hello Kurt ... > Well, then ask yourself: how much different is your workflow, e.g. > from the one from .at 8-) ? What exactly is your point ? > -- > MfG/Best regards, Kurt Jaeger 21 years to go ! > LF.net GmbH pi at LF.net Oberon.net GmbH pi at oberon.net > Vor dem Lauch 23 fon +49 711 90074-23 Friedrich-Ebert-Str.1 > D-70567 Stuttgart fax +49 711 7289041 40210 Duesseldorf fon +49 211 179253-11 > For Redmond: "nuke the site from orbit -- it's the only way to be sure." Marcel -------- Logged at Mon Sep 13 14:12:34 CEST 1999 ---------

2 1

Some ideas on the future direction of the RIPE TLD-WG
by schneider＠switch.ch 13 Sep '99

13 Sep '99

On Sunday, 12 Sep 1999, "Kurt Jaeger" writes: Hello >> It may indeed be that only registries (only registries are >> members of CENTR) need to be involved in TLD issues. >> >> Is there another view ? > Basically, if they come to common standards, then there's no > need to intervene 8-) > As we currently delegate domains from more than one country, > some, ahem, standardisation might be useful. Currently, it's a mess > with different rules, templates etc for each country with respect to almost > everything. Hope you are aware that the registrars under COM/NET /ORG are allowed to have different policies as well. Check out e.g. NSI's that from register.com and the one from Namesecure at http://www.namesecure.com/services/dispute_policy.cfm. You will find many differences. I'm not against harmonization but you may also be aware the most commonly used policy, the one from NSI, is considered a debacle, at least with respect to marks. Would it help if anybody would adopt something that is considered a flop ? > I'm not sure whether this deviation from common ground is obvious > to the TLDs themselves, as they normally only deal with their > own TLD 8-) We know quite well what's happening outside our territory, don't be afraid ;-). > -- > MfG/Best regards, Kurt Jaeger 21 years to go ! > LF.net GmbH pi at LF.net Oberon.net GmbH pi at oberon.net > Vor dem Lauch 23 fon +49 711 90074-23 Friedrich-Ebert-Str.1 > D-70567 Stuttgart fax +49 711 7289041 40210 Duesseldorf fon +49 211 179253-11 > For Redmond: "nuke the site from orbit -- it's the only way to be sure." Marcel Schneider at SWITCH -------- Logged at Mon Sep 13 10:13:29 CEST 1999 ---------

2 1

Some ideas on the future direction of the RIPE TLD-WG
by Niall.oReilly＠ucd.ie 13 Sep '99

13 Sep '99

On Mon, 13 Sep 1999 09:44:32 +0200, Marcel Schneider wrote: > On Sunday, 12 Sep 1999, "Kurt Jaeger" writes: > > Hello > [ ... ] > > Basically, if they come to common standards, then there's no > > need to intervene 8-) > > > As we currently delegate domains from more than one country, > > some, ahem, standardisation might be useful. Currently, it's a mess > > with different rules, templates etc for each country with respect to almost > > everything. > [ ... ] > > > I'm not sure whether this deviation from common ground is obvious > > to the TLDs themselves, as they normally only deal with their > > own TLD 8-) > > We know quite well what's happening outside our territory, don't > be afraid ;-). > Marcel, "outside our territory" indicates a perspective which is quite natural for a registry. Kurt's perspective is different, and one which I believe we registry people (although we understand it in principle) may not be sufficiently aware of. He is a customer of (or has to deal with) several registries. Maybe we can learn something useful from listening to how others see us. Kurt, would you like to say more ... ? Niall O'Reilly -------- Logged at Mon Sep 13 11:09:06 CEST 1999 ---------

2 1

Some ideas on the future direction of the RIPE TLD-WG
by Niall.oReilly＠ucd.ie 12 Sep '99

12 Sep '99

On Tue, 07 Sep 1999 14:02:04 +0200, Marcel Schneider wrote: > It still could be a forum for technical matters regarding > DNS, e.g. secure DNS, WHOIS servers and clients, security, > BIND stuff etc. but there is overlap with other WG's and > CENTR as you notice. Therefore it might be that no specific > TLD issues are left (well, maybe except technical management > of a TLD name registry). The suggestions I've seen for the technical workshop which CENTR is organising in conjunction with RIPE 34 seem to indicated that CENTR is trying to develop a set of technical activities. It may indeed be that only registries (only registries are members of CENTR) need to be involved in TLD issues. Is there another view ? Niall -------- Logged at Fri Sep 10 10:06:08 CEST 1999 ---------

2 1

HarmoNIC : progress report
by renaut＠nic.fr 10 Sep '99

10 Sep '99

Hi all, following Neil's mail on HarmoNIC, the NIC-FR's directory system, I can make a short progress report on it. This directory is currently operationnal in France in two languages at the following URL http://harmonic.nic.fr The news are : - it is being presented to a European Commission's call for proposal which should enable us to jump to 8 languages instead of two. - DENIC is in this project and will be using HarmoNIC directory too. These two news may help you to feel that this project is evolving nicely. A bi-country first phase of development can help getting rid of technical issues. It is still perfect momentum to try to create a harmonized European tool to offer to users a nice way of searching domains. So everyone which could be interested is welcome. Please let me know ! Philippe RENAUT AFNIC -------- Logged at Mon Sep 13 09:29:01 CEST 1999 ---------

1 0

Some ideas on the future direction of the RIPE TLD-WG
by Niall.oReilly＠ucd.ie 10 Sep '99

10 Sep '99

On Tue, 07 Sep 1999 14:02:04 +0200, Marcel Schneider wrote: > On Tuesday, 7 Sep 1999, Jaap Akkerhuis writes: > > Hi Jaap > > > I do agree with you that there is quite some overlap with work > > being carried out with by CENTRE and other groups make one wonder > > about the raison d'etre of the TLD-WG. > > The TLD-WG was created before CENTR. May 1997 seems such a long time ago! The raison-d'etre for a TLD WG was so much clearer then. > ... > > CENTR is a club concerned with policies and politics. Having > a technical group in addition _could_ be advantageous. This > probably is what Niall would like to have discussed and an > agenda if the RIPE TLD-WG stays alive. I think we should > support him with these tasks. > CENTR is starting to develop its own line of technical activities. I expect that some of the policy recommendations it develops will relate to the technical work of the registries. It would probably be useful to try to identify areas to which CENTR is unlikely to give early attention (for reasons of resources, priority), but which are nevertheless of concern to the RIPE community. Thanks, Marcel, for your kind expression of support. Niall O'Reilly -------- Logged at Fri Sep 10 10:47:45 CEST 1999 ---------

1 0

(Fwd) Top 100 Maintainers List
by k13＠nikhef.nl 10 Sep '99

10 Sep '99

Folks, +--- Start of included message from: Jaap Akkerhuis ----- | | Hi Niall, | | Let me make some remarks about this. We probably should this dicuss | in details this later at the meeting. | | This message from the RIPE-NCC Database Group shows that a | number of domain registries appear among the top-scoring | maintainers of inconsistent objects in the RIPE Database. | | Yeah, and we're the winner! And we could have done better :-). I'll | discuss the situation further on. | | Irrespective of the future of the TLD-WG, we need to identify | how best to address these concerns and, in particular, this | problem of inconsistent objects. | | Let me start to raise some questions. Citating (probably incorrectly) | Daniel Karrenberg, ``Ripe is in the IP-number business, not in the | naming business''. Given that, one wonders whether domein name | objects should be part of the Ripe database at all. Since Centr is | now in de name business, I wonder whether control of this part of | the database should not be adressed bij Centr. This has been brought to the attention of CENTR some time ago already. There are a few possibilities: + CENTR takes over this activity + RIPE NCC keeps on doing it, covered by an agreement with CENTR + forget about the whole thing It is one of the issues that CENTR should (and will) be discussing amongst themselves. Rob -------- Logged at Fri Sep 10 17:03:10 CEST 1999 ---------

1 0

Some ideas on the future direction of the RIPE TLD-WG
by Niall.oReilly＠ucd.ie 10 Sep '99

10 Sep '99

Thanks for your comments, Jaap. I would like to identify issues for which the TLD-WG could become a useful focus. Registry interests are well covered by CENTR. Perhaps registrars, ISP's, others involved in naming, but not represented in CENTR, have concerns for which this RIPE WG would be the place for discussion. Given such a new role for the WG, it would be appropriate to consider a new Workplan, changes in the Terms of Reference, (maybe even a new Chairman !). Niall On Tue, 07 Sep 1999 13:41:58, Jaap Akkerhuis <jaap at nic.nl> wrote: > Niall, > > Thanks for bringing me up to date with the tld-wg and preparing > the discussion document. > > I do agree with you that there is quite some overlap with work > being carried out with by CENTRE and other groups make one wonder > about the raison d'etre of the TLD-WG. > > jaap > -------- Logged at Fri Sep 10 09:52:07 CEST 1999 ---------

1 0

Action TLD-33.3 (HARMONIC and other registries)
by Niall.oReilly＠ucd.ie 10 Sep '99

10 Sep '99

TLD-33.3 [Chair] Request information from registries on whether they are prepared to make their data available for pilot project using HARMONIC interface. Philippe Renaud gave an excellent presentation at RIPE 33 on NIC-FR's directory system, HARMONIC. This allows registry data to be searched by geographical area, market (product or service) segment or company name, using natural language and is suggested as a means to 'take the heat out of naming'. HARMONIC is designed to integrate data from multiple registries in a single coherent query system. I understand that at least one other registry is interested in exploring use of this system, and that NIC-FR is eager to involve other registries. To explore, you can visit <http://harmonic.nic.fr/> If your registry is interested in co-operating in this project, please let Philippe know, either directly or via the tld-wg list. Niall O'Reilly -------- Logged at Fri Sep 10 09:50:28 CEST 1999 ---------

1 0

(Fwd) Top 100 Maintainers List
by Niall.oReilly＠ucd.ie 09 Sep '99

09 Sep '99

This message from the RIPE-NCC Database Group shows that a number of domain registries appear among the top-scoring maintainers of inconsistent objects in the RIPE Database. This is one aspect of the concerns which have been expressed regarding domain objects in the RIPE DB. Irrespective of the future of the TLD-WG, we need to identify how best to address these concerns and, in particular, this problem of inconsistent objects. Niall O'Reilly ------- Forwarded Message Follows ------- Date sent: Mon, 06 Sep 1999 17:45:54 +0200 From: RIPE Database Administration <ripe-dbm at ripe.net> Subject: Top 100 Maintainers List To: db-wg at ripe.net, lir-wg at ripe.net, routing-wg at ripe.net Dear list members, This is biweekly report on inconsistent objects in the RIPE whois database. The first 100 maintainers are listed as a table below sorted according to number of their inconsistent objects in the database. The rest of the maintainers which have inconsistent objects can be found at http://www.ripe.net/db/state/mntnerreport1.html You can find further information about the Consistency Project at http://www.ripe.net/db/state/ Regards, RIPE NCC Database Group =============================================================== Maintainer no of name inconsistent objects 1 NL-DOMREG 51932 http://www.ripe.net/db/state/maintainers/NL-DOMREG.html 2 DENIC-P 34021 http://www.ripe.net/db/state/maintainers/DENIC-P.html 3 XLINK-MNT 30463 http://www.ripe.net/db/state/maintainers/XLINK-MNT.html 4 DK-DOMREG 23138 http://www.ripe.net/db/state/maintainers/DK-DOMREG.html 5 AS1849-MNT 6033 http://www.ripe.net/db/state/maintainers/AS1849-MNT.html 6 FR-NIC-MNT 2818 http://www.ripe.net/db/state/maintainers/FR-NIC-MNT.html 7 ROKA-P 2446 http://www.ripe.net/db/state/maintainers/ROKA-P.html 8 DTAG-NIC 1966 http://www.ripe.net/db/state/maintainers/DTAG-NIC.html 9 SCHLUND-P 1524 http://www.ripe.net/db/state/maintainers/SCHLUND-P.html 10 BO-DOMREG 1320 http://www.ripe.net/db/state/maintainers/BO-DOMREG.html 11 NACAMAR-NOC 1303 http://www.ripe.net/db/state/maintainers/NACAMAR-NOC.html 12 ECORE-NET 1287 http://www.ripe.net/db/state/maintainers/ECORE-NET.html 13 AS1717-MNT 1114 http://www.ripe.net/db/state/maintainers/AS1717-MNT.html 14 DENIC-N 1070 http://www.ripe.net/db/state/maintainers/DENIC-N.html 15 WWW-MNT 1009 http://www.ripe.net/db/state/maintainers/WWW-MNT.html 16 DKNET-MNT 651 http://www.ripe.net/db/state/maintainers/DKNET-MNT.html 17 SEKTORNET-MNT 539 http://www.ripe.net/db/state/maintainers/SEKTORNET-MNT.html 18 INTERNET-NOC 534 http://www.ripe.net/db/state/maintainers/INTERNET-NOC.html 19 NETTUNO 499 http://www.ripe.net/db/state/maintainers/NETTUNO.html 20 CSL-MNT 494 http://www.ripe.net/db/state/maintainers/CSL-MNT.html 21 DK-NIC 494 http://www.ripe.net/db/state/maintainers/DK-NIC.html 22 DFN-NTFY 474 http://www.ripe.net/db/state/maintainers/DFN-NTFY.html 23 PSINET-UK-SYSADMIN 435 http://www.ripe.net/db/state/maintainers/PSINET-UK-SYSADMIN.h 24 RAIN-TRANSPAC 385 http://www.ripe.net/db/state/maintainers/RAIN-TRANSPAC.html 25 DIGITALWEB-MNT 375 http://www.ripe.net/db/state/maintainers/DIGITALWEB-MNT.html 26 NACAMAR-RES 372 http://www.ripe.net/db/state/maintainers/NACAMAR-RES.html 27 HIGHSPEED-DOM 367 http://www.ripe.net/db/state/maintainers/HIGHSPEED-DOM.html 28 EU-IBM-NIC-MNT 360 http://www.ripe.net/db/state/maintainers/EU-IBM-NIC-MNT.html 29 SDT-NOC 354 http://www.ripe.net/db/state/maintainers/SDT-NOC.html 30 AS1267-MNT 352 http://www.ripe.net/db/state/maintainers/AS1267-MNT.html 31 AS5378-MNT 345 http://www.ripe.net/db/state/maintainers/AS5378-MNT.html 32 GLOBAL-MNT 343 http://www.ripe.net/db/state/maintainers/GLOBAL-MNT.html 33 AS6678-MNT 339 http://www.ripe.net/db/state/maintainers/AS6678-MNT.html 34 ITNET-MNT 334 http://www.ripe.net/db/state/maintainers/ITNET-MNT.html 35 NACAMAR-POP 324 http://www.ripe.net/db/state/maintainers/NACAMAR-POP.html 36 TDK-MNT 299 http://www.ripe.net/db/state/maintainers/TDK-MNT.html 37 DE-VOSS 298 http://www.ripe.net/db/state/maintainers/DE-VOSS.html 38 IDNET-MNT 298 http://www.ripe.net/db/state/maintainers/IDNET-MNT.html 39 AT-DOM-MNT 288 http://www.ripe.net/db/state/maintainers/AT-DOM-MNT.html 40 KNIPP-NOC-MNT 259 http://www.ripe.net/db/state/maintainers/KNIPP-NOC-MNT.html 41 IL-P 254 http://www.ripe.net/db/state/maintainers/IL-P.html 42 FR-EASYNET 248 http://www.ripe.net/db/state/maintainers/FR-EASYNET.html 43 RAK-NET 246 http://www.ripe.net/db/state/maintainers/RAK-NET.html 44 INX-MNT 233 http://www.ripe.net/db/state/maintainers/INX-MNT.html 45 MARIDAN-P 229 http://www.ripe.net/db/state/maintainers/MARIDAN-P.html 46 GIGABELL-MNT 223 http://www.ripe.net/db/state/maintainers/GIGABELL-MNT.html 47 EUROCONNECT 222 http://www.ripe.net/db/state/maintainers/EUROCONNECT.html 48 AS2120-MNT 211 http://www.ripe.net/db/state/maintainers/AS2120-MNT.html 49 AS1899-MNT 207 http://www.ripe.net/db/state/maintainers/AS1899-MNT.html 50 IWAY-NOC 205 http://www.ripe.net/db/state/maintainers/IWAY-NOC.html 51 AS5617-MNT 197 http://www.ripe.net/db/state/maintainers/AS5617-MNT.html 52 AS3233-MNT 195 http://www.ripe.net/db/state/maintainers/AS3233-MNT.html 53 IT-NIC 192 http://www.ripe.net/db/state/maintainers/IT-NIC.html 54 AS2529-MNT 189 http://www.ripe.net/db/state/maintainers/AS2529-MNT.html 55 NDH-P 187 http://www.ripe.net/db/state/maintainers/NDH-P.html 56 NLNET-MNT 183 http://www.ripe.net/db/state/maintainers/NLNET-MNT.html 57 EU-IBM-NIC-MNT2 181 http://www.ripe.net/db/state/maintainers/EU-IBM-NIC-MNT2.html 58 FREENAME-NOC 179 http://www.ripe.net/db/state/maintainers/FREENAME-NOC.html 59 IBGNET 179 http://www.ripe.net/db/state/maintainers/IBGNET.html 60 OLEANE-NOC 175 http://www.ripe.net/db/state/maintainers/OLEANE-NOC.html 61 ROM-MIKNET 158 http://www.ripe.net/db/state/maintainers/ROM-MIKNET.html 62 AS5427-MNT 156 http://www.ripe.net/db/state/maintainers/AS5427-MNT.html 63 TRMD-MNT 154 http://www.ripe.net/db/state/maintainers/TRMD-MNT.html 64 SL-CUS-MNT 153 http://www.ripe.net/db/state/maintainers/SL-CUS-MNT.html 65 EVOSYS-MNT 151 http://www.ripe.net/db/state/maintainers/EVOSYS-MNT.html 66 MBT-MNT 150 http://www.ripe.net/db/state/maintainers/MBT-MNT.html 67 AS1241-MNT 149 http://www.ripe.net/db/state/maintainers/AS1241-MNT.html 68 AS5551-MNT 135 http://www.ripe.net/db/state/maintainers/AS5551-MNT.html 69 AS2871-MNT 134 http://www.ripe.net/db/state/maintainers/AS2871-MNT.html 70 NNCC 125 http://www.ripe.net/db/state/maintainers/NNCC.html 71 NETCOLOGNE-MNT 124 http://www.ripe.net/db/state/maintainers/NETCOLOGNE-MNT.html 72 OMNILINK-MNT 124 http://www.ripe.net/db/state/maintainers/OMNILINK-MNT.html 73 ONE2ONE-MNT 121 http://www.ripe.net/db/state/maintainers/ONE2ONE-MNT.html 74 WESPE-MNT 117 http://www.ripe.net/db/state/maintainers/WESPE-MNT.html 75 IMAGINET-NOC-MNT 115 http://www.ripe.net/db/state/maintainers/IMAGINET-NOC-MNT.htm 76 AS3292-MNT 112 http://www.ripe.net/db/state/maintainers/AS3292-MNT.html 77 ROSNIIROS-MNT 108 http://www.ripe.net/db/state/maintainers/ROSNIIROS-MNT.html 78 ISB-MNT 107 http://www.ripe.net/db/state/maintainers/ISB-MNT.html 79 ECRC-MNT 103 http://www.ripe.net/db/state/maintainers/ECRC-MNT.html 80 FO-DOMREG 100 http://www.ripe.net/db/state/maintainers/FO-DOMREG.html 81 TELIANET-LIR 100 http://www.ripe.net/db/state/maintainers/TELIANET-LIR.html 82 ISMA-MNT 98 http://www.ripe.net/db/state/maintainers/ISMA-MNT.html 83 GARR-LIR 95 http://www.ripe.net/db/state/maintainers/GARR-LIR.html 84 SEICOM-MNT 93 http://www.ripe.net/db/state/maintainers/SEICOM-MNT.html 85 PROFI-MNT 92 http://www.ripe.net/db/state/maintainers/PROFI-MNT.html 86 AS6721-MNT 87 http://www.ripe.net/db/state/maintainers/AS6721-MNT.html 87 TINET-NOC 85 http://www.ripe.net/db/state/maintainers/TINET-NOC.html 88 XNC-MNT 84 http://www.ripe.net/db/state/maintainers/XNC-MNT.html 89 AS8875-MNT 82 http://www.ripe.net/db/state/maintainers/AS8875-MNT.html 90 ISTLD-MNT 82 http://www.ripe.net/db/state/maintainers/ISTLD-MNT.html 91 TPNET 80 http://www.ripe.net/db/state/maintainers/TPNET.html 92 JIPS-NOSC 78 http://www.ripe.net/db/state/maintainers/JIPS-NOSC.html 93 MDA-Z 78 http://www.ripe.net/db/state/maintainers/MDA-Z.html 94 PRHO-GUARDIAN 78 http://www.ripe.net/db/state/maintainers/PRHO-GUARDIAN.html 95 ISAR-NIC 77 http://www.ripe.net/db/state/maintainers/ISAR-NIC.html 96 INETWIRE-MNT 76 http://www.ripe.net/db/state/maintainers/INETWIRE-MNT.html 97 GLOBAL-ONE 74 http://www.ripe.net/db/state/maintainers/GLOBAL-ONE.html 98 MAINT-AS3352 70 http://www.ripe.net/db/state/maintainers/MAINT-AS3352.html 99 JO-YN14 67 http://www.ripe.net/db/state/maintainers/JO-YN14.html 100 WEB4YOU-MNT 66 http://www.ripe.net/db/state/maintainers/WEB4YOU-MNT.html -------- Logged at Thu Sep 9 17:03:07 CEST 1999 ---------

2 1