From bortzmeyer at nic.fr Mon Aug 4 13:46:15 2003 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 4 Aug 2003 13:46:15 +0200 Subject: [dns-wg] Looking for a tool to find the fastest DNS server Message-ID: <20030804114615.GA24969@nic.fr> I'm looking for a small tool (running on Unix) that can take a list of DNS servers, a query to ask (such as "A ns1.nic.fr.") and which can print the fastest server to reply. Something like "netselect" which only exercices the kernel, not the actual servers, unfortunately (and which can be blocked by filters): ~ % netselect {a,b,c,d,e,f,g,h,i,j,k,l,m}.root-servers.net 123 i.root-servers.net BIND9's lib/dns/resolver.c has code to do so and I wonder if someone extracted it in a simple tool? From daniel.karrenberg at ripe.net Mon Aug 4 14:04:27 2003 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 4 Aug 2003 14:04:27 +0200 Subject: [dns-wg] Looking for a tool to find the fastest DNS server In-Reply-To: <20030804114615.GA24969@nic.fr> References: <20030804114615.GA24969@nic.fr> Message-ID: <20030804120426.GG6903@reifa-wave.karrenberg.net> I am sure Eric Wassenaar's host (ftp://ftp.ripe.net/tools/dns/host.tar.Z) can be easily adapted to that if it does not do it alreeady. daniel On 04.08 13:46, Stephane Bortzmeyer wrote: > I'm looking for a small tool (running on Unix) that can take a list of > DNS servers, a query to ask (such as "A ns1.nic.fr.") and which can > print the fastest server to reply. > > Something like "netselect" which only exercices the kernel, not the > actual servers, unfortunately (and which can be blocked by filters): > > ~ % netselect {a,b,c,d,e,f,g,h,i,j,k,l,m}.root-servers.net > 123 i.root-servers.net > > BIND9's lib/dns/resolver.c has code to do so and I wonder if someone > extracted it in a simple tool? > > From bortzmeyer at nic.fr Mon Aug 4 14:15:22 2003 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 4 Aug 2003 14:15:22 +0200 Subject: [dns-wg] Looking for a tool to find the fastest DNS server In-Reply-To: <20030804120426.GG6903@reifa-wave.karrenberg.net> References: <20030804114615.GA24969@nic.fr> <20030804120426.GG6903@reifa-wave.karrenberg.net> Message-ID: <20030804121522.GA25192@nic.fr> On Mon, Aug 04, 2003 at 02:04:27PM +0200, Daniel Karrenberg wrote a message of 20 lines which said: > if it does not do it alreeady. No, it does not. From jabley at isc.org Mon Aug 4 14:17:34 2003 From: jabley at isc.org (Joe Abley) Date: Mon, 4 Aug 2003 08:17:34 -0400 Subject: [dns-wg] Looking for a tool to find the fastest DNS server In-Reply-To: <20030804114615.GA24969@nic.fr> References: <20030804114615.GA24969@nic.fr> Message-ID: On Monday, 4 August 2003, at 07:46AM, Stephane Bortzmeyer wrote: > I'm looking for a small tool (running on Unix) that can take a list of > DNS servers, a query to ask (such as "A ns1.nic.fr.") and which can > print the fastest server to reply. > > Something like "netselect" which only exercices the kernel, not the > actual servers, unfortunately (and which can be blocked by filters): > > ~ % netselect {a,b,c,d,e,f,g,h,i,j,k,l,m}.root-servers.net > 123 i.root-servers.net > > BIND9's lib/dns/resolver.c has code to do so and I wonder if someone > extracted it in a simple tool? #!/bin/sh # q=$1; shift # [ -z "$*" ] && echo "Syntax: $0 query server..." && exit 1 # for m in 0 1 2 3; do for n in $*; do dig @${n} ${q}; done done | \ awk '/^;; Query time:/ { qt = $4; } \ /^;; SERVER: / { sum[$3] += qt; n[$3]++; } \ END { for (s in sum) { print int(sum[s]/n[s]), s; } }' | \ sort -n | head -1 [jabley at snowfall]% ./qtest.sh ". NS" a.root-servers.net b.root-servers.net c.root-servers.net d.root-servers.net e.root-servers.net f.root-servers.net g.root-servers.net h.root-servers.net i.root-servers.net j.root-servers.net k.root-servers.net l.root-servers.net m.root-servers.net 40 192.58.128.30#53(j.root-servers.net) [jabley at snowfall]% From bortzmeyer at nic.fr Mon Aug 4 14:37:28 2003 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 4 Aug 2003 14:37:28 +0200 Subject: [dns-wg] Looking for a tool to find the fastest DNS server In-Reply-To: References: <20030804114615.GA24969@nic.fr> Message-ID: <20030804123728.GA26504@nic.fr> On Mon, Aug 04, 2003 at 08:17:34AM -0400, Joe Abley wrote a message of 39 lines which said: > #!/bin/sh Works fine. Thanks for the fast coding. Suggestions if someone wants to improve it: 1) Parallelize requests (the tool can take a long time if some servers are slow). 2) Better handling of errors instead of printing: dig: Couldn't find server 'Truncated,': Name or service not known dig: Couldn't find server 'retrying': Name or service not known dig: Couldn't find server 'TCP': Name or service not known dig: Couldn't find server 'mode.': Name or service not known dig: Couldn't find server ';;': Name or service not known From brad.knowles at skynet.be Mon Aug 4 14:48:54 2003 From: brad.knowles at skynet.be (Brad Knowles) Date: Mon, 4 Aug 2003 14:48:54 +0200 Subject: [dns-wg] Looking for a tool to find the fastest DNS server In-Reply-To: <20030804123728.GA26504@nic.fr> References: <20030804114615.GA24969@nic.fr> <20030804123728.GA26504@nic.fr> Message-ID: At 2:37 PM +0200 2003/08/04, Stephane Bortzmeyer wrote: > Suggestions if someone wants to improve it: > > 1) Parallelize requests (the tool can take a long time if some servers > are slow). Speaking as the current maintainer of `doc`, parallelizing shell code is a bitch. Moreover, if you were going to do that, you should really do a statistically useful number of queries for each target, so that you have a more reasonable conclusion -- As of time T, server X is Y% faster than the second-fastest server Z, with a minimum response time of M1, an average response time of A, a maximum response time of M2, and a sample standard deviation of S. This is the sort of thing I tried to do in my root/gTLD/ccTLD survey for my presentation at RIPE44. I still need to make all those tools publicly available, as promised. If you want them, periodically bug me about it and I'll try to remember to put them up. > 2) Better handling of errors instead of printing: > > dig: Couldn't find server 'Truncated,': Name or service not known > dig: Couldn't find server 'retrying': Name or service not known > dig: Couldn't find server 'TCP': Name or service not known > dig: Couldn't find server 'mode.': Name or service not known > dig: Couldn't find server ';;': Name or service not known Yup. I have that problem with `doc`, too. I keep saying that I'm going to import all this functionality into `dnswalk` and get rid of `doc`, but I still haven't found time to do it. Maybe one of these days. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From bortzmeyer at nic.fr Mon Aug 4 15:04:48 2003 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 4 Aug 2003 15:04:48 +0200 Subject: [dns-wg] Looking for a tool to find the fastest DNS server In-Reply-To: References: <20030804114615.GA24969@nic.fr> <20030804123728.GA26504@nic.fr> Message-ID: <20030804130448.GA27150@nic.fr> On Mon, Aug 04, 2003 at 02:48:54PM +0200, Brad Knowles wrote a message of 43 lines which said: > Speaking as the current maintainer of `doc`, parallelizing shell > code is a bitch. Yes, I was not seriously suggesting that. > Moreover, if you were going to do that, you should > really do a statistically useful number of queries for each target, Right, that's the difference between Joe Abley's tool (simple, effective, delivered on time) and a proper and professionnal tool, which only has the problem of not existing yet. From paf at cisco.com Wed Aug 13 15:27:44 2003 From: paf at cisco.com (=?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=) Date: Wed, 13 Aug 2003 15:27:44 +0200 Subject: [dns-wg] Proposal: Charter for DN* wg at RIPE Message-ID: Note: I want _LOTS_ of comments on the following. You will see after this a message about the agenda of the meeting at RIPE 46. Idea: Create a list of "topics" which are divided in two groups: [1] Topics which are larger discussion items. Each one will have one or more deliverables. There is a small group of people responsible for deliverables and they report back every DN* meeting. [2] Organisations and groups (inside and outside of RIPE and RIPE NCC) which report to the DNS wg what is happening, what is currently discussed etc. This is summarized at every RIPE meeting as a compiled report to the RIPE DNS wg participants so they know what is happening in the world The agenda at the RIPE meeting then consists of these two PLUS two other categories: [3] Invited longer talks [4] Short reports from groups which do not come back every meeting The result from [3] and [4] is only included in the minutes of the RIPE meeting. Nothing more, nothing less. Is that ok? Given this is ok, the question is then what to include under each one of the bullets. This is (as you will see on the proposed agenda) what I want to have discussed at the RIPE meeting. Below you can see _MY_PERSONAL_ idea. Probably many things forgotten, possibly many things wrong. Please correct. Let me know you are interested in spending some CPU cycles. Small things which will make the future more organized is that my goal is to keep exactly the same "item numbers" for every item, and never changing them over the years. That means the only topic I have got suggestions on (see below) is 1.1. Next will be 1.2. Etc. paf Charter for the DN* wg at RIPE (to be updated at each RIPE meeting) ------------------------------------------------------------------- [1] Topics with deliverables 1.1 Quality of the DNS We have a few contributors here: + domainSentinel tool for lame checking Chagres Role Account + RIPE NCC DNS Monitoring Daniel Karrenberg + DNSCHECK for verification of delegations Patrik F?ltstr?m Deliverables: 1.1.1 Recommendations for measures DNS serv*ice* quality 1.1.2 Recommendations how to summarise the results for consumption by the non-technical public 1.1.3 What is an "error"? 1.1.3.1 "Lame" 1.1.3.2 "Wrong glue" 1.1.3.3 "Non-authoritative response" 1.1.3.4 "Transport over TCP" 1.1.3.5 ... 1.1.4 What is good practice regarding measurement? 1.1.5 ... [2] Reports / status items 2.1 Monitoring 2.1.1 RIPE NCC DNS Monitoring Daniel Karrenberg 2.2 DNS in the IETF 2.2.1 DNSEXT 2.2.2 DNSOP 2.2.3 Other wg's which touch DNS 2.3 EPP deployment / experience / status Edward Lewis 2.4 Root servers 2.5 IDN deployment / experience 2.6 DNSSEC deployment / experience 2.7 Anycast deployment / experience 2.7.1 Dave Knight 2.7.2 I-Root (Lars-Johan Liman) 2.7 CENTR Technical committee 2.8 DNS Software 2.8.1 Bind 2.8.2 OpenReg 2.8.3 ... 2.9 IPv6 deployment / experience Unknown From paf at cisco.com Wed Aug 13 15:37:19 2003 From: paf at cisco.com (=?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=) Date: Wed, 13 Aug 2003 15:37:19 +0200 Subject: [dns-wg] Agenda DNS wg at RIPE 46 Message-ID: <42CBAE4C-CD93-11D7-A046-000A959CF516@cisco.com> This is the first suggested agenda. Note that this include: - A skeleton built from the proposed charter of the wg, which you might not agree with. If the charter change, of course also the agenda is to be changed. - Bullets which doesn't have any speakers (yet). I want *YOU* to agree on saying something. Or, even better, nominate your friend/enemy instead of taking up the glove yourself!!! :-) - No time for each agenda item yet. It is unclear how to divide the three 90 minute slots we have between all DN* groups which we might merge Agenda at RIPE 46 ----------------- [0] Charter / Agenda Bashing / Goals etc Leader of the discussion: Patrik F?ltstr?m Help from co-chairs: Jim Reid, Peter Koch and Jaap Akkerhuis. 0.1 Agenda 0.2 Charter 0.3 What are we doing here anyway? [1] Topics with deliverables 1.1 Quality of the DNS Leader of the discussion: Unknown [2] Reports / status items (same bullets every meeting) (max 5 min each) 2.1 Monitoring 2.1.1 RIPE NCC DNS Monitoring Daniel Karrenberg 2.2 DNS in the IETF 2.2.1 DNSEXT Unknown 2.2.2 DNSOP Unknown 2.2.3 Other wg's which touch DNS Unknown 2.3 EPP deployment / experience / status Edward Lewis Suggested reading: http://www.read of ipe.net/ripe/mail-archives/dns-wg/2003/msg00122.html 2.4 Root servers Unknown 2.5 IDN deployment / experience Unknown 2.6 DNSSEC deployment / experience Unknown 2.7 Anycast deployment / experience 2.7.1 Dave Knight 2.7 CENTR Technical committee Unknown 2.8 DNS Software 2.8.1 Bind Unknown 2.8.2 OpenReg Unknown 2.9 IPv6 deployment / experience Unknown [3] Special invited (longer) presentation (30 min) 3.1 RIPE NCC DNS Monitoring Daniel Karrenberg [4] Temporary items (15 min each) 4.1 Use of DNS for SPAM prevention Note: This is not to be a spam discussion, but more a heads-up on the various mechanisms which exists and are discussed for example in the anti-spam research group in the IETF. Anne P. Mitchell, Esq. From paf at cisco.com Wed Aug 13 17:07:12 2003 From: paf at cisco.com (=?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=) Date: Wed, 13 Aug 2003 17:07:12 +0200 Subject: [dns-wg] Proposal: Charter for DN* wg at RIPE In-Reply-To: Message-ID: On onsdag, aug 13, 2003, at 16:52 Europe/Stockholm, Joao Damas wrote: > So what you are suggesting is that the agenda is the charter (or > viceversa) therefore provide a more or less stable framework for the > agenda and ask people to step forward and help the chairs and the wg > by taking responsibility for certain specific items on an ongoing > basis? Yes. I want the agenda to be "automatically created" from the current state of the charter. This so we get a path forward. This first time of course the agenda and charter go more hand in hand than next time. Hopefully the charter will be good enough so it will be easy to create the agenda in the future. paf > Just making sure I understand your intentions as this is a "different" > way of putting down a charter. I like it. > > Joao > > > On Wednesday, August 13, 2003, at 03:27 PM, Patrik F?ltstr?m wrote: > >> Note: I want _LOTS_ of comments on the following. You will see after >> this a message about the agenda of the meeting at RIPE 46. >> >> Idea: Create a list of "topics" which are divided in two groups: >> >> [1] Topics which are larger discussion items. Each one >> will have one or more deliverables. There is a small >> group of people responsible for deliverables and they >> report back every DN* meeting. >> >> [2] Organisations and groups (inside and outside of RIPE >> and RIPE NCC) which report to the DNS wg what is happening, >> what is currently discussed etc. This is summarized at >> every RIPE meeting as a compiled report to the RIPE DNS >> wg participants so they know what is happening in the world >> >> The agenda at the RIPE meeting then consists of these two PLUS two >> other categories: >> >> [3] Invited longer talks >> >> [4] Short reports from groups which do not come back every meeting >> >> The result from [3] and [4] is only included in the minutes of the >> RIPE meeting. Nothing more, nothing less. >> >> Is that ok? >> >> >> Given this is ok, the question is then what to include under each one >> of the bullets. This is (as you will see on the proposed agenda) what >> I want to have discussed at the RIPE meeting. >> >> Below you can see _MY_PERSONAL_ idea. Probably many things forgotten, >> possibly many things wrong. >> >> Please correct. Let me know you are interested in spending some CPU >> cycles. >> >> Small things which will make the future more organized is that my >> goal is to keep exactly the same "item numbers" for every item, and >> never changing them over the years. That means the only topic I have >> got suggestions on (see below) is 1.1. Next will be 1.2. Etc. >> >> paf >> >> >> Charter for the DN* wg at RIPE (to be updated at each RIPE meeting) >> ------------------------------------------------------------------- >> >> [1] Topics with deliverables >> >> 1.1 Quality of the DNS >> >> We have a few contributors here: >> >> + domainSentinel tool for lame checking >> Chagres Role Account >> >> + RIPE NCC DNS Monitoring >> Daniel Karrenberg >> >> + DNSCHECK for verification of delegations >> Patrik F?ltstr?m >> >> Deliverables: >> >> 1.1.1 Recommendations for measures DNS serv*ice* quality >> >> 1.1.2 Recommendations how to summarise the results for consumption by >> the non-technical public >> >> 1.1.3 What is an "error"? >> >> 1.1.3.1 "Lame" >> 1.1.3.2 "Wrong glue" >> 1.1.3.3 "Non-authoritative response" >> 1.1.3.4 "Transport over TCP" >> 1.1.3.5 ... >> >> 1.1.4 What is good practice regarding measurement? >> >> 1.1.5 ... >> >> >> [2] Reports / status items >> >> 2.1 Monitoring >> 2.1.1 RIPE NCC DNS Monitoring >> Daniel Karrenberg >> >> 2.2 DNS in the IETF >> 2.2.1 DNSEXT >> 2.2.2 DNSOP >> 2.2.3 Other wg's which touch DNS >> >> 2.3 EPP deployment / experience / status >> Edward Lewis >> >> 2.4 Root servers >> >> 2.5 IDN deployment / experience >> >> 2.6 DNSSEC deployment / experience >> >> 2.7 Anycast deployment / experience >> 2.7.1 Dave Knight >> 2.7.2 I-Root (Lars-Johan Liman) >> >> 2.7 CENTR Technical committee >> >> 2.8 DNS Software >> 2.8.1 Bind >> 2.8.2 OpenReg >> 2.8.3 ... >> >> 2.9 IPv6 deployment / experience >> Unknown >> >> > From joao at isc.org Wed Aug 13 16:52:14 2003 From: joao at isc.org (Joao Damas) Date: Wed, 13 Aug 2003 16:52:14 +0200 Subject: [dns-wg] Proposal: Charter for DN* wg at RIPE In-Reply-To: Message-ID: So what you are suggesting is that the agenda is the charter (or viceversa) therefore provide a more or less stable framework for the agenda and ask people to step forward and help the chairs and the wg by taking responsibility for certain specific items on an ongoing basis? Just making sure I understand your intentions as this is a "different" way of putting down a charter. I like it. Joao On Wednesday, August 13, 2003, at 03:27 PM, Patrik F?ltstr?m wrote: > Note: I want _LOTS_ of comments on the following. You will see after > this a message about the agenda of the meeting at RIPE 46. > > Idea: Create a list of "topics" which are divided in two groups: > > [1] Topics which are larger discussion items. Each one > will have one or more deliverables. There is a small > group of people responsible for deliverables and they > report back every DN* meeting. > > [2] Organisations and groups (inside and outside of RIPE > and RIPE NCC) which report to the DNS wg what is happening, > what is currently discussed etc. This is summarized at > every RIPE meeting as a compiled report to the RIPE DNS > wg participants so they know what is happening in the world > > The agenda at the RIPE meeting then consists of these two PLUS two > other categories: > > [3] Invited longer talks > > [4] Short reports from groups which do not come back every meeting > > The result from [3] and [4] is only included in the minutes of the > RIPE meeting. Nothing more, nothing less. > > Is that ok? > > > Given this is ok, the question is then what to include under each one > of the bullets. This is (as you will see on the proposed agenda) what > I want to have discussed at the RIPE meeting. > > Below you can see _MY_PERSONAL_ idea. Probably many things forgotten, > possibly many things wrong. > > Please correct. Let me know you are interested in spending some CPU > cycles. > > Small things which will make the future more organized is that my goal > is to keep exactly the same "item numbers" for every item, and never > changing them over the years. That means the only topic I have got > suggestions on (see below) is 1.1. Next will be 1.2. Etc. > > paf > > > Charter for the DN* wg at RIPE (to be updated at each RIPE meeting) > ------------------------------------------------------------------- > > [1] Topics with deliverables > > 1.1 Quality of the DNS > > We have a few contributors here: > > + domainSentinel tool for lame checking > Chagres Role Account > > + RIPE NCC DNS Monitoring > Daniel Karrenberg > > + DNSCHECK for verification of delegations > Patrik F?ltstr?m > > Deliverables: > > 1.1.1 Recommendations for measures DNS serv*ice* quality > > 1.1.2 Recommendations how to summarise the results for consumption by > the non-technical public > > 1.1.3 What is an "error"? > > 1.1.3.1 "Lame" > 1.1.3.2 "Wrong glue" > 1.1.3.3 "Non-authoritative response" > 1.1.3.4 "Transport over TCP" > 1.1.3.5 ... > > 1.1.4 What is good practice regarding measurement? > > 1.1.5 ... > > > [2] Reports / status items > > 2.1 Monitoring > 2.1.1 RIPE NCC DNS Monitoring > Daniel Karrenberg > > 2.2 DNS in the IETF > 2.2.1 DNSEXT > 2.2.2 DNSOP > 2.2.3 Other wg's which touch DNS > > 2.3 EPP deployment / experience / status > Edward Lewis > > 2.4 Root servers > > 2.5 IDN deployment / experience > > 2.6 DNSSEC deployment / experience > > 2.7 Anycast deployment / experience > 2.7.1 Dave Knight > 2.7.2 I-Root (Lars-Johan Liman) > > 2.7 CENTR Technical committee > > 2.8 DNS Software > 2.8.1 Bind > 2.8.2 OpenReg > 2.8.3 ... > > 2.9 IPv6 deployment / experience > Unknown > > From alberto.jimenezdeleon at telefonica.es Fri Aug 15 01:00:33 2003 From: alberto.jimenezdeleon at telefonica.es (alberto.jimenezdeleon at telefonica.es) Date: Fri, 15 Aug 2003 01:00:33 +0200 Subject: [dns-wg] Alberto Jimenez De Leon/INFR/TESA =?iso-8859-1?Q?est=E1_ausente_de_la_oficina=2E?= Message-ID: Estar? ausente de la oficina desde el 07/08/2003 y no volver? hasta el 01/09/2003. Responder? a su mensaje cuando regrese. ___________________________________________________________________________ Este mensaje se dirige exclusivamente a su destinatario y puede contener informaci?n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci?n, divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. This message is intended exclusively for its addressee and may contain information that is CONFIDENTIAL and protected by professional privilege. If you are not the intended recipient you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please immediately notify us via e-mail and delete it. ___________________________________________________________________________ From paf at cisco.com Thu Aug 21 11:42:44 2003 From: paf at cisco.com (=?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=) Date: Thu, 21 Aug 2003 11:42:44 +0200 Subject: [dns-wg] Agenda DNS wg at RIPE 46, take two In-Reply-To: <42CBAE4C-CD93-11D7-A046-000A959CF516@cisco.com> Message-ID: Second version of the agenda. Things which very late in the process still have "unknown" on them will be removed. I have the last three days (suddenly) got volunteers for slots. Maybe because people are back from vacation. But, we still need more people. Keep on sending me requests! regards, paf Agenda at RIPE 46 ----------------- [0] Charter / Agenda Bashing / Goals etc Leader of the discussion: Patrik F?ltstr?m Help from co-chairs: Jim Reid, Peter Koch and Jaap Akkerhuis. 0.1 Agenda 0.2 Charter 0.3 What are we doing here anyway? [1] Topics with deliverables 1.1 Quality of the DNS Topic-Leader: Unknown 1.1.1 Background, deliverables, participants etc 1.1.1.1 Who will lead this topic? 1.1.1.2 Deliverables 1.2.1 Tools 1.2.1.1 DomainSentinel John Brown [2] Reports / status items (same bullets every meeting) (approx 5 min each) 2.1 Monitoring 2.1.1 RIPE NCC DNS Monitoring Daniel Karrenberg 2.2 DNS in the IETF 2.2.1 DNSEXT Lars-Johan Liman 2.2.2 DNSOP Lars-Johan Liman 2.2.3 Other wg's which touch DNS 2.2.3.1 IPSECKEY Unknown 2.2.3.2 SSHFP Unknown 2.2.3.3 ENUM Patrik Faltstrom 2.2.3.4 PROVREG Jaap Akkerhuis 2.3 EPP deployment / experience / status Unknown 2.4 Root servers 2.4.1 F-Root Joao Damas 2.4.2 I-Root Lars-Johan Liman 2.5 IDN deployment / experience 2.5.1 Experience in Poland (15-30 minutes) Andrzej Bartosiewicz 2.6 DNSSEC deployment / experience 2.6.1 DNSSEC status Sam Weiler 2.7 Anycast deployment / experience 2.7.1 Dave Knight 2.7 CENTR Technical committee Unknown 2.8 DNS Software (I accept info from _anyone_ here, not only ISC things) 2.8.1 Bind (maybe) Joao Damas 2.8.2 OpenReg (maybe) Joao Damas 2.9 IPv6 deployment / experience 2.9.1 Adding IPv6 glue to the root zone Ronald van der Pol [3] Special invited (longer) presentation (30 min) 3.1 RIPE NCC DNS Monitoring Daniel Karrenberg [4] Temporary items (15 min each) 4.1 Use of DNS for SPAM prevention Note: This is not to be a spam discussion, but more a heads-up on the various mechanisms which exists and are discussed for example in the anti-spam research group in the IETF. Anne P. Mitchell, Esq. From paf at cisco.com Wed Aug 27 07:36:06 2003 From: paf at cisco.com (=?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=) Date: Wed, 27 Aug 2003 07:36:06 +0200 Subject: [dns-wg] Agenda for DNS-wg at RIPE 46, version 3 Message-ID: <5B2E7C54-D850-11D7-837E-000A959CF516@cisco.com> Third version of the agenda. The reason why it has not ended up on the RIPE website is that I have all the time bcc:ed the correct address at RIPE NCC secretariat when I post this agenda to this address, and that doesn't work apparently. Mea culpa. Sorry. Exact division of agenda items on the different slots will happen shortly. Things which very late in the process still have "unknown" on them will be removed. Keep on sending me requests! FYI: I will not arrive to Amsterdam before late Wed evening, so my dear co-chairs will take care of sessions before that point in time. regards, paf Agenda at RIPE 46 ----------------- [0] Charter / Agenda Bashing / Goals etc Leader of the discussion: Jim Reid Help from co-chairs: Peter Koch and Jaap Akkerhuis. 0.1 Agenda 0.2 Charter 0.3 What are we doing here anyway? [1] Topics with deliverables 1.1 Quality of the DNS Topic-Leader: Unknown 1.1.1 Background, deliverables, participants etc 1.1.1.1 Who will lead this topic? 1.1.1.2 Deliverables 1.2.1 Tools 1.2.1.1 DomainSentinel John Brown [2] Reports / status items (same bullets every meeting) (approx 5 min each) 2.1 Monitoring 2.1.1 RIPE NCC DNS Monitoring Daniel Karrenberg 2.2 DNS in the IETF 2.2.1 DNSEXT Lars-Johan Liman 2.2.2 DNSOP Lars-Johan Liman 2.2.3 Other wg's which touch DNS 2.2.3.1 IPSECKEY Unknown 2.2.3.2 SSHFP Jakob Schlyter 2.2.3.3 ENUM Patrik Faltstrom (depending on what day it will be) 2.2.3.4 PROVREG Jaap Akkerhuis 2.3 EPP deployment / experience / status Unknown 2.4 Root servers 2.4.2 B-Root Bill Manning 2.4.2 F-Root Joao Damas 2.4.3 I-Root Lars-Johan Liman 2.5 IDN deployment / experience 2.5.1 Experience in Poland (15-30 minutes) Andrzej Bartosiewicz 2.6 DNSSEC deployment / experience 2.6.1 DNSSEC status Sam Weiler 2.7 Anycast deployment / experience 2.7.1 Dave Knight 2.7 CENTR Technical committee Unknown 2.8 DNS Software (I accept info from _anyone_ here, not only ISC things) 2.8.1 Bind (maybe) Joao Damas 2.8.2 OpenReg (maybe) Joao Damas 2.8.3 NSD (they are asked, but have not said "ok" yet) Erik Rozendaal Alexis Yushin 2.9 IPv6 deployment / experience 2.9.1 Adding IPv6 glue to the root zone Ronald van der Pol [3] Special invited (longer) presentation (30 min) 3.1 RIPE NCC DNS Monitoring Daniel Karrenberg [4] Temporary items (approximately 15 min each) 4.1 Use of DNS for SPAM prevention Note: This is not to be a spam discussion, but more a heads-up on the various mechanisms which exists and are discussed for example in the anti-spam research group in the IETF. Anne P. Mitchell, Esq. 4.2 The status of the rs.net testbed: CN & JP tlds registered punycode entries KeyMgmt issues w/ persistant DNSSEC testbeds Precursors for IPv6 tlds & glue in the root zone