From owner-dnsop@lists.uoregon.edu  Sun Aug  1 00:28:10 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06598
	for <dnsop-archive@lists.ietf.org>; Sun, 1 Aug 2004 00:28:09 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i713FwAb006899;
	Sat, 31 Jul 2004 20:15:59 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i713FwfZ006898;
	Sat, 31 Jul 2004 20:15:58 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i713FuCx006852
	for <dnsop@lists.uoregon.edu>; Sat, 31 Jul 2004 20:15:57 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i713FUu21780;
	Sun, 1 Aug 2004 06:15:33 +0300
Date: Sun, 1 Aug 2004 06:15:29 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
cc: Erik.Nordmark@sun.com, <miekg@atoom.net>, <namedroppers@ops.ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
In-Reply-To: <20040801001419.2854D1C0C4@coconut.itojun.org>
Message-ID: <Pine.LNX.4.44.0408010614440.21586-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

On Sun, 1 Aug 2004, Jun-ichiro itojun Hagino wrote:
> 	getaddrinfo() is not a DNS-only function; it can lookup hostname-to
> 	address using /etc/hosts, NIS, LDAP, whatever you have.  what value
> 	would you put in to ai_ttl when the lookup is done by non-DNS method?

-1, unless something else is provided?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Sun Aug  1 11:57:04 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07776
	for <dnsop-archive@lists.ietf.org>; Sun, 1 Aug 2004 11:57:03 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i71ElB6k019494;
	Sun, 1 Aug 2004 07:47:11 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i71ElBO8019493;
	Sun, 1 Aug 2004 07:47:11 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i71El99q019462
	for <dnsop@lists.uoregon.edu>; Sun, 1 Aug 2004 07:47:09 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i71El3531454
	for <dnsop@lists.uoregon.edu>; Sun, 1 Aug 2004 17:47:03 +0300
Date: Sun, 1 Aug 2004 17:47:03 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@lists.uoregon.edu
Subject: [dnsop] ipv6-dns-configuration-02 comments
Message-ID: <Pine.LNX.4.44.0408011745410.31045-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

A look how the draft was changed in response to LC comments..

substantial
-----------

 1) this revision has added a lot of text that the ND approach is unfit to
WLAN, and performs poorly.  However, the document never explains the
background or assumptions to such claims.  I guess this is mased on
Masataka's point that multicast on WLAN actually results in a lot of
point-to-point communication.  But this needs to be spelled out, keeping in
mind three things: 1) in some environments, this may not be a problem; 2) this
is no worse than WLAN today; 3) if folks thought multicast on WLAN had such
big problems, they might have devised a different mechanism for it -- for
example, if pure broadcast does not suffer from this issue, certain
multicast addresses, which are expected to have a larger number of
recipients, could be mapped to the broadcast address instead.

 2) A major (IMHO) advantage of RA option hasn't been mentioned -- that it
leverages SEND security out of the box, with zero new specification
(if you assume that if someone is authorized as a router, it is authorized
to send you any kind of RDNSS option).  This is potentially a really big
benefit.

 3) The anycast approach should maybe instead use the term "shared-unicast",
as coined by draft-ietf-ipngwg-anycast-analysis-02.txt.  That makes it
clearer which anycast it's referring to.

 4) 3GPP still needs to explain whether RA's are being used at all at the
moment -- that is, some have at least stated that e.g., addresses/prefixes
are configured as part of PDP context activation, which would seem to hint
at the fact that even if RA's would be possible, they might not be used that
much..

semi-editorial
--------------

   The RA approach is useful in some non-WLAN mobile environments
   where the addresses of the RDNSSes are changing because the RA
   option includes a lifetime field.  This can be configured to a
   value that will require the client to time out the entry and switch
   over to another RDNSS address [8].

==> I fail to see a strong justification for lifetime option in the first
place -- and it complicates the matters.  If your network connectivity
breaks, you'll lose DNS lookups no matter what.  If it doesn't break, but a
server gets renumbered, the advertising router's DNS information has to be
updated, no matter the lifetime in any case -- and if there is no lifetime,
a new advertisement without the removed server could simply overwrite the
old.  In summary, I can't figure a really convincing usage case for lifetime
in the first place.

RFC2461 [3] states, however,
   that there may be some link type on which ND is not possible; on
   such a link, some other mechanism will be needed for DNS 
   configuration. 

==> do such media exist?  If not, maybe it's worth stating the case; if yes,
noting that they aren't commonplace.

   1) ND is mostly implemented in kernel part of operating system.
   Therefore, if ND supports the configuration of some additional
   services, such as DNS, NTP and SIP servers, ND should be extended
   in kernel part.

==> , and completed by an user-land process.

   The DHCPv6 option for RDNSS has a few disadvantages.  These
   include: 
    
   1) Update currently requires message from server (however, see     
   [10]). 

==> I don't understand 1).  Doesn't update always require some kind of
message?  Please elaborate.

3.3.2 Disadvantages

   Well-known anycast addresses approach requires that DNS servers (or
   routers near it as a proxy) act as routers to advertise their
   anycast addresses to the routing system, which requires some
   configuration (see the last paragraph of the previous section on
   the scalability of the effort).

==> I think this requires a bit more beef.  In particular, one should
describe the model for failure recovery.  For example,
if a site or ISP doesn't have a route to the well-known service,
for example, but has a default discard route which blackholes the packets --
then what?  You're down to the timeouts.

I think the biggest issue with (inter-domain) anycast is that the service
which relies on it might not function properly in the case that the address
is blackholed due to whatever reasons, or if anyone close by isn't offering
service, you could end up travelling to the ends of the earth to get DNS
service...

  Regarding DNS configuration on the IPv6 host, several mechanisms
   have being considered at the DNSOP Working Group such as RA option,

==> s/have being/are being/ (or "have been") ?


-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Sun Aug  1 19:15:17 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01276
	for <dnsop-archive@lists.ietf.org>; Sun, 1 Aug 2004 19:15:15 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i71M9Lot029322;
	Sun, 1 Aug 2004 15:09:21 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i71M9LTZ029321;
	Sun, 1 Aug 2004 15:09:21 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [221.249.121.227])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i71M9Jlx029302
	for <dnsop@lists.uoregon.edu>; Sun, 1 Aug 2004 15:09:20 -0700 (PDT)
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id 255251C0BF;
	Mon,  2 Aug 2004 07:03:01 +0900 (JST)
To: Pekka Savola <pekkas@netcore.fi>
Cc: Erik.Nordmark@sun.com, miekg@atoom.net, namedroppers@ops.ietf.org,
        dnsop@lists.uoregon.edu
In-reply-to: pekkas's message of Sun, 01 Aug 2004 06:15:29 +0300.  <Pine.LNX.4.44.0408010614440.21586-100000@netcore.fi> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface 
From: itojun@iijlab.net
Date: Mon, 02 Aug 2004 07:03:01 +0900
Message-Id: <20040801220301.255251C0BF@coconut.itojun.org>
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: itojun@iijlab.net

>On Sun, 1 Aug 2004, Jun-ichiro itojun Hagino wrote:
>> 	getaddrinfo() is not a DNS-only function; it can lookup hostname-to
>> 	address using /etc/hosts, NIS, LDAP, whatever you have.  what value
>> 	would you put in to ai_ttl when the lookup is done by non-DNS method?
>
>-1, unless something else is provided?

	then what do you expect application to do with the data?  when does
	it expire?  any fabricated value (-1, 0, whatever) in ai_ttl is
	problematical to TTL-aware application, IMHO.  what i'm suggesting
	is to use DNS-only API like getrrrsetbyname() if you want TTL.

itojun
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Sun Aug  1 20:03:33 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03594
	for <dnsop-archive@lists.ietf.org>; Sun, 1 Aug 2004 20:03:32 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i71Mn8Ud018274;
	Sun, 1 Aug 2004 15:49:08 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i71Mn8EE018273;
	Sun, 1 Aug 2004 15:49:08 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i71Mn6J8018217
	for <dnsop@lists.uoregon.edu>; Sun, 1 Aug 2004 15:49:07 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i71MmrP07622;
	Mon, 2 Aug 2004 01:48:53 +0300
Date: Mon, 2 Aug 2004 01:48:53 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: itojun@iijlab.net
cc: Erik.Nordmark@sun.com, <miekg@atoom.net>, <namedroppers@ops.ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
In-Reply-To: <20040801220301.255251C0BF@coconut.itojun.org>
Message-ID: <Pine.LNX.4.44.0408020143180.7497-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

On Mon, 2 Aug 2004 itojun@iijlab.net wrote:
> >On Sun, 1 Aug 2004, Jun-ichiro itojun Hagino wrote:
> >> 	getaddrinfo() is not a DNS-only function; it can lookup hostname-to
> >> 	address using /etc/hosts, NIS, LDAP, whatever you have.  what value
> >> 	would you put in to ai_ttl when the lookup is done by non-DNS method?
> >
> >-1, unless something else is provided?
> 
> 	then what do you expect application to do with the data?  when does
> 	it expire?  any fabricated value (-1, 0, whatever) in ai_ttl is
> 	problematical to TTL-aware application, IMHO.  what i'm suggesting
> 	is to use DNS-only API like getrrrsetbyname() if you want TTL.

Let's assume that currently apps keep records forever, i.e., "-1" 
(infinite).

If apps would use TTL info to requery the addresses now and then, 
telling them that a particular record has infinite lifetime (because 
lifetime information wasn't provided) seems like pretty much equal to 
the situation now -- i.e., it doesn't make situations worse. (And 
infinite would actually probably be rather accurate esp. with 
/etc/hosts).

getrrsetbyname has the generic problem that the applications don't
want to care about the lookup mechanism used.  /etc/hosts or whatever
is just as fine as DNS.  Thus I think only apps which specifically
know that they definitely want their answers to come from DNS (and not
from hosts file or whateveR) can use getrrsetname.  But I don't think
the majority cares, or should need to care.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Sun Aug  1 23:26:31 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25337
	for <dnsop-archive@lists.ietf.org>; Sun, 1 Aug 2004 23:26:29 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i721q13s011419;
	Sun, 1 Aug 2004 18:52:01 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i721q1ns011411;
	Sun, 1 Aug 2004 18:52:01 -0700 (PDT)
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i721pxj7011222
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Sun, 1 Aug 2004 18:52:00 -0700 (PDT)
Received: from [192.168.0.5] (cable0-stm-219.gmpexpress.net [63.147.50.219])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by goose.ehsco.com (Postfix ) with ESMTP id AA55338F23;
	Sun,  1 Aug 2004 20:51:57 -0500 (CDT)
Message-ID: <410D9E24.6000206@ehsco.com>
Date: Sun, 01 Aug 2004 21:51:32 -0400
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
Cc: Jun-ichiro itojun Hagino <itojun@itojun.org>, Erik.Nordmark@sun.com,
        miekg@atoom.net, pekkas@netcore.fi, namedroppers@ops.ietf.org,
        dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
References: <20040801003710.4D95513DE9@sa.vix.com>
In-Reply-To: <20040801003710.4D95513DE9@sa.vix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Eric A. Hall" <ehall@ehsco.com>
Content-Transfer-Encoding: 7bit


On 7/31/2004 8:37 PM, Paul Vixie wrote:

> i don't think expansing getaddrinfo/getnameinfo to return ttl is the
> right approach.  we need a "getrrsetbyname" for dns-aware applications
> that returns ttl, security status, and so on.

"rrset" is the right target, too.

apps that try to do their own load-balancing and whatnot need to be given
the original unordered set, not a random member of the set




.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Mon Aug  2 12:50:32 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18160
	for <dnsop-archive@lists.ietf.org>; Mon, 2 Aug 2004 12:50:31 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i72FMMuG015584;
	Mon, 2 Aug 2004 08:22:22 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i72FMMOF015575;
	Mon, 2 Aug 2004 08:22:22 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i72FMLbP015251
	for <dnsop@lists.uoregon.edu>; Mon, 2 Aug 2004 08:22:22 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i72FMFv06376;
	Mon, 2 Aug 2004 08:22:15 -0700
X-mProtect: <200408021522> Nokia Silicon Valley Messaging Protection
Received: from danira-pool05174.americas.nokia.com (10.241.51.74, claiming to be "l5131412.nokia.com")
	by darkstar.iprg.nokia.com smtpddEP2Ij; Mon, 02 Aug 2004 08:22:13 PDT
Message-Id: <4.3.2.7.2.20040802081842.034b91c8@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 02 Aug 2004 08:21:48 -0700
To: dnsop@lists.uoregon.edu
From: Bob Hinden <bob.hinden@nokia.com>
Subject: Re: [dnsop] ipv6-dns-configuration-02 comments
Cc: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0408011745410.31045-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Bob Hinden <bob.hinden@nokia.com>

Hi,

At 07:47 AM 08/01/2004, Pekka Savola wrote:
>A look how the draft was changed in response to LC comments..
>
>substantial
>-----------
>
>  1) this revision has added a lot of text that the ND approach is unfit to
>WLAN, and performs poorly.  However, the document never explains the
>background or assumptions to such claims.  I guess this is mased on
>Masataka's point that multicast on WLAN actually results in a lot of
>point-to-point communication.  But this needs to be spelled out, keeping in
>mind three things: 1) in some environments, this may not be a problem; 2) this
>is no worse than WLAN today; 3) if folks thought multicast on WLAN had such
>big problems, they might have devised a different mechanism for it -- for
>example, if pure broadcast does not suffer from this issue, certain
>multicast addresses, which are expected to have a larger number of
>recipients, could be mapped to the broadcast address instead.
>
>  2) A major (IMHO) advantage of RA option hasn't been mentioned -- that it
>leverages SEND security out of the box, with zero new specification
>(if you assume that if someone is authorized as a router, it is authorized
>to send you any kind of RDNSS option).  This is potentially a really big
>benefit.
>
>  3) The anycast approach should maybe instead use the term "shared-unicast",
>as coined by draft-ietf-ipngwg-anycast-analysis-02.txt.  That makes it
>clearer which anycast it's referring to.
>
>  4) 3GPP still needs to explain whether RA's are being used at all at the
>moment -- that is, some have at least stated that e.g., addresses/prefixes
>are configured as part of PDP context activation, which would seem to hint
>at the fact that even if RA's would be possible, they might not be used that
>much..

I agree with all of Pekka's substantial comments and think the document 
needs to be updated.

Bob


>semi-editorial
>--------------
>
>    The RA approach is useful in some non-WLAN mobile environments
>    where the addresses of the RDNSSes are changing because the RA
>    option includes a lifetime field.  This can be configured to a
>    value that will require the client to time out the entry and switch
>    over to another RDNSS address [8].
>
>==> I fail to see a strong justification for lifetime option in the first
>place -- and it complicates the matters.  If your network connectivity
>breaks, you'll lose DNS lookups no matter what.  If it doesn't break, but a
>server gets renumbered, the advertising router's DNS information has to be
>updated, no matter the lifetime in any case -- and if there is no lifetime,
>a new advertisement without the removed server could simply overwrite the
>old.  In summary, I can't figure a really convincing usage case for lifetime
>in the first place.
>
>RFC2461 [3] states, however,
>    that there may be some link type on which ND is not possible; on
>    such a link, some other mechanism will be needed for DNS
>    configuration.
>
>==> do such media exist?  If not, maybe it's worth stating the case; if yes,
>noting that they aren't commonplace.
>
>    1) ND is mostly implemented in kernel part of operating system.
>    Therefore, if ND supports the configuration of some additional
>    services, such as DNS, NTP and SIP servers, ND should be extended
>    in kernel part.
>
>==> , and completed by an user-land process.
>
>    The DHCPv6 option for RDNSS has a few disadvantages.  These
>    include:
>
>    1) Update currently requires message from server (however, see
>    [10]).
>
>==> I don't understand 1).  Doesn't update always require some kind of
>message?  Please elaborate.
>
>3.3.2 Disadvantages
>
>    Well-known anycast addresses approach requires that DNS servers (or
>    routers near it as a proxy) act as routers to advertise their
>    anycast addresses to the routing system, which requires some
>    configuration (see the last paragraph of the previous section on
>    the scalability of the effort).
>
>==> I think this requires a bit more beef.  In particular, one should
>describe the model for failure recovery.  For example,
>if a site or ISP doesn't have a route to the well-known service,
>for example, but has a default discard route which blackholes the packets --
>then what?  You're down to the timeouts.
>
>I think the biggest issue with (inter-domain) anycast is that the service
>which relies on it might not function properly in the case that the address
>is blackholed due to whatever reasons, or if anyone close by isn't offering
>service, you could end up travelling to the ends of the earth to get DNS
>service...
>
>   Regarding DNS configuration on the IPv6 host, several mechanisms
>    have being considered at the DNSOP Working Group such as RA option,
>
>==> s/have being/are being/ (or "have been") ?
>
>
>--
>Pekka Savola                 "You each name yourselves king, yet the
>Netcore Oy                    kingdom bleeds."
>Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug  3 03:16:56 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21328
	for <dnsop-archive@lists.ietf.org>; Tue, 3 Aug 2004 03:16:55 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7369TpU022612;
	Mon, 2 Aug 2004 23:09:29 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7369TsZ022603;
	Mon, 2 Aug 2004 23:09:29 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7369S7J022226
	for <dnsop@lists.uoregon.edu>; Mon, 2 Aug 2004 23:09:28 -0700 (PDT)
Received: from rtp-core-1.cisco.com (64.102.124.12)
  by rtp-iport-1.cisco.com with ESMTP; 03 Aug 2004 02:16:39 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i7369KRW004646
	for <dnsop@lists.uoregon.edu>; Tue, 3 Aug 2004 02:09:21 -0400 (EDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-15.cisco.com [10.86.242.15])
	by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AKO32454;
	Tue, 3 Aug 2004 02:09:19 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040802182850.02b0e200@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 02 Aug 2004 18:30:14 -0400
To: dnsop@lists.uoregon.edu
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] ipv6-dns-configuration-02 comments
In-Reply-To: <4.3.2.7.2.20040802081842.034b91c8@mailhost.iprg.nokia.com>
References: <Pine.LNX.4.44.0408011745410.31045-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Ralph Droms <rdroms@cisco.com>

At 08:21 AM 8/2/2004 -0700, Bob Hinden wrote:
>Hi,
>
>At 07:47 AM 08/01/2004, Pekka Savola wrote:
>>A look how the draft was changed in response to LC comments..
>>
>>substantial
>>-----------
>>
>>  2) A major (IMHO) advantage of RA option hasn't been mentioned -- that it
>>leverages SEND security out of the box, with zero new specification
>>(if you assume that if someone is authorized as a router, it is authorized
>>to send you any kind of RDNSS option).  This is potentially a really big
>>benefit.

If and when SEND is done.  DHCPv6 has security built in today.

>>  4) 3GPP still needs to explain whether RA's are being used at all at the
>>moment -- that is, some have at least stated that e.g., addresses/prefixes
>>are configured as part of PDP context activation, which would seem to hint
>>at the fact that even if RA's would be possible, they might not be used that
>>much..

Agreed...

- Ralph

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug  3 21:15:14 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28693
	for <dnsop-archive@lists.ietf.org>; Tue, 3 Aug 2004 21:15:13 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i73Nl6vg013923;
	Tue, 3 Aug 2004 16:47:06 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i73Nl6S2013920;
	Tue, 3 Aug 2004 16:47:06 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [192.149.252.32])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i73Nl4Q4013903
	for <dnsop@lists.uoregon.edu>; Tue, 3 Aug 2004 16:47:04 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id E126B19B8F3; Tue,  3 Aug 2004 19:37:12 -0400 (EDT)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id 5BEAA19B8F3;
	Tue,  3 Aug 2004 19:37:12 -0400 (EDT)
Received: from [10.0.2.5] (mercury.arin.net [127.0.0.1])
	by mercury.arin.net (Postfix) with ESMTP id BD686CF394;
	Tue,  3 Aug 2004 19:47:02 -0400 (EDT)
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a0602041abd35d2b19e8f@[10.0.2.5]>
In-Reply-To: <Roam.SIMC.2.0.6.1091369126.19351.nordmark@bebop.france>
References: <Roam.SIMC.2.0.6.1091369126.19351.nordmark@bebop.france>
Date: Tue, 3 Aug 2004 16:47:03 -0700
To: Erik Nordmark <Erik.Nordmark@sun.com>
From: Edward Lewis <edlewis@arin.net>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
Cc: Edward Lewis <edlewis@arin.net>,
        Jun-ichiro itojun Hagino <itojun@itojun.org>, miekg@atoom.net,
        pekkas@netcore.fi, namedroppers@ops.ietf.org, dnsop@lists.uoregon.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.63-arin1 (2004-01-11) on smtp2.arin.net
X-Spam-Status: No, hits=-5.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63-arin1
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Edward Lewis <edlewis@arin.net>

At 7:05 -0700 8/1/04, Erik Nordmark wrote:
>Hence I think we could collectively be more effective in fixing this
>if we could present an API mechanism by which the application/middleware
>could find out an upper limit on how long time it should retain
>the information in its own cache.

I've thought about replying to this for some time.

I can see that the DNS TTL would be an appropriate measure of time 
that an application can "refer to" an answer it got from a DNS lookup 
- in essence the application is acting like a DNS cache and the TTL 
applies.

But, that's the limit of how an application ought to make use of the 
TTL.  The TTL isn't a necessarily a measure of the volatility of the 
data - e.g., it's not an indication of the "mean time to next 
change," say before the next dynamic update.  Another example, the 
TTL isn't a measure of the useful life of the data - just the amount 
of time that a cache holding of it is "wise."

DNS can offer up the following times - TTL, end of the signature 
validity (under DNSSEC), zone expiration.  Signature validity can be 
a measure of the validity of the data's signature or the measure of 
the validity of the union of the entire chain.  (I.e., just the RRSIG 
for the A record you want, or the "sum" of the times for the root's 
KEY, TLD's DS and KEY, ..., and the A's validity.)

DNS does not have a "next scheduled change" (like there is in things 
like X.509 CRLs), which would probably far more interesting to an 
application.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

"I can't go to Miami.  I'm expecting calls from telemarketers." -
Grandpa Simpson.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug  3 21:43:41 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00391
	for <dnsop-archive@lists.ietf.org>; Tue, 3 Aug 2004 21:43:41 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i740h36j005177;
	Tue, 3 Aug 2004 17:43:03 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i740h3AZ005176;
	Tue, 3 Aug 2004 17:43:03 -0700 (PDT)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i740gxlm005130
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Tue, 3 Aug 2004 17:43:02 -0700 (PDT)
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i740gvN11184;
	Wed, 4 Aug 2004 03:42:57 +0300 (EET DST)
X-Scanned: Wed, 4 Aug 2004 03:41:36 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i740far4003259;
	Wed, 4 Aug 2004 03:41:36 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 001HQ71s; Wed, 04 Aug 2004 03:41:22 EEST
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i740fLn00187;
	Wed, 4 Aug 2004 03:41:21 +0300 (EET DST)
Received: from esebe005.NOE.Nokia.com ([172.21.138.45]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Wed, 4 Aug 2004 03:41:21 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [dnsop] ipv6-dns-configuration-02 comments
Date: Wed, 4 Aug 2004 03:41:20 +0300
Message-ID: <245DBCAEEC4F074CB77B3F984FF9834F020CE476@esebe005.ntc.nokia.com>
Thread-Topic: [dnsop] ipv6-dns-configuration-02 comments
Thread-Index: AcR5IYH8UmWd2ThsT+WaBNu3Xmdk0wAmMUPg
From: <juha.wiljakka@nokia.com>
To: <pekkas@netcore.fi>, <dnsop@lists.uoregon.edu>
X-OriginalArrivalTime: 04 Aug 2004 00:41:21.0316 (UTC) FILETIME=[C326C640:01C479BB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by darkwing.uoregon.edu id i740h3ll005166
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: <juha.wiljakka@nokia.com>
Content-Transfer-Encoding: 8bit


Pekka and others,

-----Original Message-----

>>  4) 3GPP still needs to explain whether RA's are being used at all at the
>>moment -- that is, some have at least stated that e.g., addresses/prefixes
>>are configured as part of PDP context activation, which would seem to hint
>>at the fact that even if RA's would be possible, they might not be used that
>>much..

Usage of RA in 3GPP nw is no problem, i.e. it can be and is used. I can provide some clarifying text on that in the 3GPP section. RA is a part of the 3GPP UE IPv6 addressing:

From 3GPP TS 23.060, section 9.2.1.1:
----clip----
...
1)	The MS sends an Activate PDP Context Request message to the SGSN as defined in clause "PDP Context Activation Procedure". The MS shall leave PDP Address empty and set PDP Type to IPv6.

2)	Upon reception of the Create PDP Context Request, the GGSN creates an IPv6 address composed of the prefix allocated to the PDP context and an interface identifier generated by the GGSN. This address is then returned in the PDP Address information element in the Create PDP Context Response message. The processing of the Create PDP Context Request and Create PDP Context Response, in both the SGSN and the GGSN, is otherwise as specified in clause "PDP Context Activation Procedure".

NOTE: 	Since the MS is considered to be alone on its link towards the GGSN, the interface identifier does not need to be unique across all PDP contexts on any APN.

3)	The MS receives the IPv6 address produced by the GGSN in the Activate PDP Context Accept. The MS extracts the interface identifier from the address received and stores it. The MS shall use this interface identifier to build its link-local address and may also use it for building its full IPv6 address, as describe in step 5. The MS shall ignore the prefix contained in the address received in the Activate PDP Context Accept. The processing of the Activate PDP Context Accept is otherwise as specified in clause "PDP Context Activation Procedure".

4)	The MS may send a Router Solicitation message to the GGSN to activate the sending of the Router Advertisement message.

5)	The GGSN sends a Router Advertisement message. The Router Advertisement messages shall contain the same prefix as the one provided in step 2. A given prefix shall not be advertised on more than one PDP context on a given APN, or set of APNs, within the same addressing scope. The GGSN shall be configured to advertise only one prefix per PDP context.

	After the MS has received the Router Advertisement message, it constructs its full IPv6 address by concatenating the interface identifier received in step 3, or a locally generated interface identifier, and the prefix received in the Router Advertisement. If the Router Advertisement contains more than one prefix option, the MS shall only consider the first one and silently discard the others.
...
----clip----

Cheers,
	 -Juha-

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Wed Aug  4 13:34:36 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21672
	for <dnsop-archive@lists.ietf.org>; Wed, 4 Aug 2004 13:34:36 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i74G3Aok017557;
	Wed, 4 Aug 2004 09:03:10 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i74G3AGh017555;
	Wed, 4 Aug 2004 09:03:10 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [192.149.252.32])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i74G39ZX017531
	for <dnsop@lists.uoregon.edu>; Wed, 4 Aug 2004 09:03:09 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 4E5EE19B595; Wed,  4 Aug 2004 11:53:05 -0400 (EDT)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id DE7F619B332;
	Wed,  4 Aug 2004 11:53:04 -0400 (EDT)
Received: from [10.0.2.5] (mercury.arin.net [127.0.0.1])
	by mercury.arin.net (Postfix) with ESMTP id E1E66CF394;
	Wed,  4 Aug 2004 12:03:00 -0400 (EDT)
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a0602041ebd36b2ea2882@[10.0.2.5]>
In-Reply-To: <Roam.SIMC.2.0.6.1091578923.13038.nordmark@bebop.france>
References: <Roam.SIMC.2.0.6.1091578923.13038.nordmark@bebop.france>
Date: Wed, 4 Aug 2004 08:40:39 -0700
To: Erik Nordmark <Erik.Nordmark@sun.com>
From: Edward Lewis <edlewis@arin.net>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
Cc: Edward Lewis <edlewis@arin.net>, Erik Nordmark <Erik.Nordmark@sun.com>,
        Jun-ichiro itojun Hagino <itojun@itojun.org>, miekg@atoom.net,
        pekkas@netcore.fi, namedroppers@ops.ietf.org, dnsop@lists.uoregon.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.63-arin1 (2004-01-11) on smtp2.arin.net
X-Spam-Status: No, hits=-5.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63-arin1
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Edward Lewis <edlewis@arin.net>

At 17:22 -0700 8/3/04, Erik Nordmark wrote:

>Do you have example of where an application would actually believe that the
>data would change after the TTL expires?

No, I don't.  I was just imagining the worst-case scenario of an 
application developers "wild imagination." ;)  The last time I did 
any work myself in this area, it was the 80's and I didn't have a TTL 
but did have changing data.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

"I can't go to Miami.  I'm expecting calls from telemarketers." -
Grandpa Simpson.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Wed Aug  4 18:58:20 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17409
	for <dnsop-archive@lists.ietf.org>; Wed, 4 Aug 2004 18:58:19 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i74LtTg0014872;
	Wed, 4 Aug 2004 14:55:29 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i74LtTQM014869;
	Wed, 4 Aug 2004 14:55:29 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i74LtR69014715
	for <dnsop@lists.uoregon.edu>; Wed, 4 Aug 2004 14:55:28 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i74LtMr29277
	for <dnsop@lists.uoregon.edu>; Thu, 5 Aug 2004 00:55:22 +0300
Date: Thu, 5 Aug 2004 00:55:22 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@lists.uoregon.edu
Subject: [dnsop] dnsop-ipv6-dns-issues: references and doc organization (fwd)
Message-ID: <Pine.LNX.4.44.0408050047490.29115-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

FYI -- resend. (with a slight update below.)

1. do we want to split off some sections to separate document(s), for 
example Forward or Reverse DNS updating?  We'd still need to wait for 
such a draft to finish, though.

2. are there references which are not normative which we should wait 
for? (i.e., important references, which we should wait for if they 
aren't RFCs already)  Thomas asked us to sit down and think real hard 
about this.

Please provide feedback.  If you agree with the current approach, feel
free to send a note off-list if you don't want to spam the list.

---------- Forwarded message ----------
Date: Wed, 14 Jul 2004 13:04:44 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@lists.uoregon.edu
Cc: narten@us.ibm.com
Subject: [dnsop] dnsop-ipv6-dns-issues: references and doc organization

Hi,

Thomas Narten provided extensive feedbakc on 
draft-ietf-dnsop-ipv6-dns-issues at IESG evaluation, and I've tried to 
address his comments (see the I-D tracker) in:

[ http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-issues-08.txt ]

but there are still a few where it might be useful to get feedback 
from the WG.

The two relatively simpler issues were:

 1. Document organization.  The document is a bit long and a bit "raw"  
in some areas.  One way to try to fix that would be trying to separate
some subjects to new I-Ds, just summarize them here, and wait for
their completion.  Such possible subjects could be e.g., the issues
with DDNS (about 5-6 pages), or the TTL/additional data issues.  I'm a
bit hesitant to do that because the overall length would not 
decrease.. but if we want to split off something, DDNS would be IMHO 
the best candidate..

Thoughts?

 2. References.  Only few were normative (normative ones block the 
publication of the document until the normative ones are published), 
required for the understanding of the document.

I've increased the number of normative documents to a lot, with still 
Internet-drafts being:

   [I-D.ietf-dnsop-ipv6-dns-configuration]
   [I-D.ietf-dnsop-ipv6-transport-guidelines]
   [I-D.ietf-dnsop-misbehavior-against-aaaa]
   [I-D.ietf-ipv6-deprecate-site-local]
   [I-D.ietf-v6ops-application-transition]
   [I-D.ietf-v6ops-renumbering-procedure]

I've kept these as informative due to various reasons -- some of them 
are just providing additional information, and some have gotten stuck 
in the process and waiting doesn't seem justified.  I've marked with 
a star those I-D's which I think would be particularly useful to have 
as normative but might take too long to get complete:

   [I-D.durand-v6ops-natpt-dns-alg-issues]
   [I-D.huitema-v6ops-teredo]
   [I-D.huston-6to4-reverse-dns]  *
   [I-D.ietf-dhc-ddns-resolution]
   [I-D.ietf-dhc-fqdn-option]
   [I-D.ietf-dnsext-dhcid-rr]   
   [I-D.ietf-dnsop-bad-dns-res]   *
   [I-D.ietf-dnsop-dontpublish-unreachable]  *
   [I-D.ietf-dnsop-inaddr-required]  *
   [I-D.ietf-ipseckey-rr]
   [I-D.ietf-ipv6-unique-local-addr]
   [I-D.ietf-send-cga]
   [I-D.ietf-v6ops-3gpp-analysis]
   [I-D.ietf-v6ops-mech-v2]
   [I-D.ietf-v6ops-onlinkassumption]
   [I-D.ietf-v6ops-v6onbydefault]
   [I-D.jeong-dnsop-ipv6-dns-discovery]
   [I-D.moore-6to4-dns]
   [I-D.ohta-preconfigured-dns]
   [I-D.savola-v6ops-6bone-mess]
   [RFC2766] (NAT-PT)
   [RFC2826] (IAB comment on unique DNS root)
   [RFC3704] Ingress Filtering (update)

Thoughts?  Comments?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Wed Aug  4 21:35:41 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27310
	for <dnsop-archive@lists.ietf.org>; Wed, 4 Aug 2004 21:35:41 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i750OSBj015376;
	Wed, 4 Aug 2004 17:24:28 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i750OSI8015375;
	Wed, 4 Aug 2004 17:24:28 -0700 (PDT)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i750OSvd015349
	for <dnsop@lists.uoregon.edu>; Wed, 4 Aug 2004 17:24:28 -0700 (PDT)
Received: from esunmail ([129.147.156.34])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id i750M453026760
	for <dnsop@lists.uoregon.edu>; Wed, 4 Aug 2004 18:22:04 -0600 (MDT)
Received: from xpa-fe2 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTP id <0I1Y007ZG6GRCB@edgemail1.Central.Sun.COM> for
 dnsop@lists.uoregon.edu; Wed, 04 Aug 2004 18:24:27 -0600 (MDT)
Received: from [130.129.132.22] by mail.sun.net
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTPSA id <0I1Y003VX6GPL2@mail.sun.net> for dnsop@lists.uoregon.edu;
 Wed, 04 Aug 2004 18:24:27 -0600 (MDT)
Date: Wed, 04 Aug 2004 17:25:33 -0700
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: [dnsop] Comment on draft-ietf-dnsop-ipv6-dns-configuration-02.txt
To: dnsop@lists.uoregon.edu
Message-id: <41117E7D.3020105@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040601
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Alain Durand <Alain.Durand@Sun.COM>
Content-Transfer-Encoding: 7BIT

This draft is making an analysis of 3 possible suggestions on how to
do DNS server discovery.

This draft then fails to recognise that one solution (DHCPv6) is already 
standardize when the others are not and then weight the
advantages of standardizing a new mechanism versus the drawbacks
of having more than one solution to achieve the same thing
and all the cost behind it, like the added complexity of
choosing which mechanims to use (Section 4.0 does not provide enough 
help here) and the added support cost in implementations.

     - Alain.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Wed Aug  4 22:27:23 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00187
	for <dnsop-archive@lists.ietf.org>; Wed, 4 Aug 2004 22:27:22 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7515mTG021824;
	Wed, 4 Aug 2004 18:05:48 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7515msJ021820;
	Wed, 4 Aug 2004 18:05:48 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with SMTP id i7515l1r021736
	for <dnsop@lists.uoregon.edu>; Wed, 4 Aug 2004 18:05:47 -0700 (PDT)
Received: (qmail 56404 invoked from network); 5 Aug 2004 01:17:30 -0000
Received: from yahoobb219178198081.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.81)
  by necom830.hpcl.titech.ac.jp with SMTP; 5 Aug 2004 01:17:30 -0000
Message-ID: <41118952.6020308@necom830.hpcl.titech.ac.jp>
Date: Thu, 05 Aug 2004 10:11:46 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Alain Durand <Alain.Durand@Sun.COM>
CC: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Comment on draft-ietf-dnsop-ipv6-dns-configuration-02.txt
References: <41117E7D.3020105@sun.com>
In-Reply-To: <41117E7D.3020105@sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Content-Transfer-Encoding: 7bit

Alain Durand wrote:

> This draft is making an analysis of 3 possible suggestions on how to
> do DNS server discovery.

No.

						Masataka Ohta


.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Thu Aug  5 02:34:48 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27389
	for <dnsop-archive@lists.ietf.org>; Thu, 5 Aug 2004 02:34:48 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i755CCAL015112;
	Wed, 4 Aug 2004 22:12:12 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i755CCSA015108;
	Wed, 4 Aug 2004 22:12:12 -0700 (PDT)
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i755CBeH015013
	for <dnsop@lists.uoregon.edu>; Wed, 4 Aug 2004 22:12:11 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [2001:240:5bf:128:1184:ea5f:d2b:fc7c])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 62FF51525D; Thu,  5 Aug 2004 14:12:08 +0900 (JST)
Date: Thu, 05 Aug 2004 14:12:10 +0900
Message-ID: <y7vwu0ep3rp.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: Alain Durand <Alain.Durand@Sun.COM>
Cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Comment on draft-ietf-dnsop-ipv6-dns-configuration-02.txt
In-Reply-To: <41117E7D.3020105@sun.com>
References: <41117E7D.3020105@sun.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>

>>>>> On Wed, 04 Aug 2004 17:25:33 -0700, 
>>>>> Alain Durand <Alain.Durand@Sun.COM> said:

> This draft then fails to recognise that one solution (DHCPv6) is already 
> standardize when the others are not and then weight the
> advantages of standardizing a new mechanism versus the drawbacks
> of having more than one solution to achieve the same thing
> and all the cost behind it, like the added complexity of
> choosing which mechanims to use (Section 4.0 does not provide enough 
> help here) and the added support cost in implementations.

I understand your concern, particularly in that the current draft
could hide the cost of having more than one solution.  In fact, I
showed a similar concern for a prior version of the draft as a meta
comment, and I see the 02 revision is better than before on this
point.

Perhaps the current revision is still not perfect in this sense, but I
understand that the chairs are in a hurry to submit it to the IESG due
to the deadline and that the current goal of this document is to
provide food of thought in conjunction with the IESG in order to make
an appropriate next step quickly.  I trust the IESG to take into
account the standardization status of each approach correctly in the
evaluation procedure.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Thu Aug  5 15:09:49 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07684
	for <dnsop-archive@lists.ietf.org>; Thu, 5 Aug 2004 15:09:48 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i75HUip6024339;
	Thu, 5 Aug 2004 10:30:44 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i75HUie8024336;
	Thu, 5 Aug 2004 10:30:44 -0700 (PDT)
From: "Scott Hollenbeck" <sah@428cobrajet.net>
To: <dnsop@lists.uoregon.edu>
Subject: [dnsop] DNSSEC and EPP Review Request
Date: Thu, 5 Aug 2004 12:36:44 -0400
Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF02E0F7A5@vsvapostal8.vcorp.ad.vrsn.com>
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Scott Hollenbeck" <sah@428cobrajet.net>

[Sorry if this is a repeat.  I sent a similar message to the list yesterday,
but it doesn't appear to have been redistributed.  I may have sent it from
an unsubscribed address, dooming it to moderation purgatory.]

As a follow-up to my presentation at yesterday's dnsop working group
meeting, this is the document that I would like to have reviewed by people
with DNS operations and management experience:

http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-secdns-03.txt

There is also a question of whether or not this document should be a dnsop
work item.  I've been working it as an individual submission for the last
few years and I'm perfectly happy to continue doing so, but I'd also happily
submit to wg processes if that makes sense.  So, if I could please ask two
questions:

1. Would working group members please take a look at the document to ensure
that I got things right with the child-parent key information exchange?

2. Should this document become a dnsop work item?

There is some specific text in the document that describes some of the
issues with child-parent key management.  That text in particular could
stand some review.

Thanks,
-Scott-

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Sat Aug  7 08:27:48 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25314
	for <dnsop-archive@lists.ietf.org>; Sat, 7 Aug 2004 08:27:47 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i77AoNmV017327;
	Sat, 7 Aug 2004 03:50:23 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i77AoNb4017323;
	Sat, 7 Aug 2004 03:50:23 -0700 (PDT)
Received: from netmon.hz.zj.cn ([202.101.172.20])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with SMTP id i77AnrSf014425
	for <dnsop@lists.uoregon.edu>; Sat, 7 Aug 2004 03:50:17 -0700 (PDT)
Received: (qmail 17772 invoked from network); 7 Aug 2004 18:42:17 +0800
Received: from unknown (HELO topgun) (jshen@christmas.9966.org@202.96.96.35)
  by netmon.hz.zj.cn with SMTP; 7 Aug 2004 18:42:17 +0800
From: "Joe Shen" <jshen@christmas.9966.org>
To: <dnsop@lists.uoregon.edu>
Subject: [dnsop] Cache Server operation and  Performance Optimization
Date: Sat, 7 Aug 2004 18:51:29 +0800
Message-ID: <000301c47c6c$7f4691e0$6f02a8c0@topgun>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Joe Shen" <jshen@christmas.9966.org>
Content-Transfer-Encoding: 7bit

Hi,

I'm new to this list. If the question is out of topic forgive me please.

I noticed there is a lot of work on root server operation and authorized
DNS 
server management, but what about cache server? 
As I know  ISPs usually  use cache server to provide name resolution
service 
to their customers. This means cache server may be the bottleneck of
domain name 
resolution path  or may be the critical point of service failure.

Is there any statistics on Cache server load and performance
measurement?   

And,  is that any document on how root server is configured to support a
peak load around 
10k_req/sec? I means, does the root server use  load balancer before
multiple computers ?
 or  there is  just one computer optimized for DNS service?

thanks 

Joe 

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Sun Aug  8 16:33:03 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10865
	for <dnsop-archive@lists.ietf.org>; Sun, 8 Aug 2004 16:33:02 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i78HiLPR018626;
	Sun, 8 Aug 2004 10:44:21 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i78HiL49018624;
	Sun, 8 Aug 2004 10:44:21 -0700 (PDT)
Received: from mxr.enom.com (mxr.enom.com [63.251.174.172])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i78Hi8rp017571
	for <dnsop@lists.uoregon.edu>; Sun, 8 Aug 2004 10:44:19 -0700 (PDT)
Received: from mail pickup service by mxr.enom.com with Microsoft SMTPSVC;
	 Sun, 8 Aug 2004 10:43:55 -0700
Received: from mail pickup service by mxr.enom.com with Microsoft SMTPSVC;
	 Sat, 7 Aug 2004 22:39:41 -0700
Received: from darkwing.uoregon.edu ([128.223.142.13]) by mxr.enom.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Sat, 7 Aug 2004 11:10:17 -0700
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i77AoNmV017327;
	Sat, 7 Aug 2004 03:50:23 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i77AoNb4017323;
	Sat, 7 Aug 2004 03:50:23 -0700 (PDT)
Received: from netmon.hz.zj.cn ([202.101.172.20])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with SMTP id i77AnrSf014425
	for <dnsop@lists.uoregon.edu>; Sat, 7 Aug 2004 03:50:17 -0700 (PDT)
Received: (qmail 17772 invoked from network); 7 Aug 2004 18:42:17 +0800
Received: from unknown (HELO topgun) (jshen@christmas.9966.org@202.96.96.35)
  by netmon.hz.zj.cn with SMTP; 7 Aug 2004 18:42:17 +0800
From: "Joe Shen" <jshen@christmas.9966.org>
To: <dnsop@lists.uoregon.edu>
Subject: [dnsop] Cache Server operation and  Performance Optimization
Date: Sat, 7 Aug 2004 18:51:29 +0800
Message-ID: <000301c47c6c$7f4691e0$6f02a8c0@topgun>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-OriginalArrivalTime: 07 Aug 2004 18:10:29.0203 (UTC) FILETIME=[D2415230:01C47CA9]
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Joe Shen" <jshen@christmas.9966.org>
Content-Transfer-Encoding: 7bit

Hi,

I'm new to this list. If the question is out of topic forgive me please.

I noticed there is a lot of work on root server operation and authorized
DNS 
server management, but what about cache server? 
As I know  ISPs usually  use cache server to provide name resolution
service 
to their customers. This means cache server may be the bottleneck of
domain name 
resolution path  or may be the critical point of service failure.

Is there any statistics on Cache server load and performance
measurement?   

And,  is that any document on how root server is configured to support a
peak load around 
10k_req/sec? I means, does the root server use  load balancer before
multiple computers ?
 or  there is  just one computer optimized for DNS service?

thanks 

Joe 


dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Mon Aug  9 16:58:44 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16704
	for <dnsop-archive@lists.ietf.org>; Mon, 9 Aug 2004 16:58:44 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i79JPVIJ023912;
	Mon, 9 Aug 2004 12:25:31 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i79JPVQP023899;
	Mon, 9 Aug 2004 12:25:31 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i79JPT5m023805
	for <dnsop@lists.uoregon.edu>; Mon, 9 Aug 2004 12:25:30 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01576;
	Mon, 9 Aug 2004 15:25:26 -0400 (EDT)
Message-Id: <200408091925.PAA01576@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: dnsop@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Subject: [dnsop] I-D ACTION:draft-ietf-dnsop-ipv6-dns-issues-09.txt
Date: Mon, 09 Aug 2004 15:25:26 -0400
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations Working Group of the IETF.

	Title		: Operational Considerations and Issues with IPv6 DNS
	Author(s)	: A. Durand, et al. 
	Filename	: draft-ietf-dnsop-ipv6-dns-issues-09.txt
	Pages		: 30
	Date		: 2004-8-9
	
This memo presents operational considerations and issues with IPv6
Domain Name System (DNS), including a summary of special IPv6
addresses, documentation of known DNS implementation misbehaviour,
recommendations and considerations on how to perform DNS naming for
service provisioning and for DNS resolver IPv6 support,
considerations for DNS updates for both the forward and reverse
trees, and miscellaneous issues.  This memo is aimed to include a
summary of information about IPv6 DNS considerations for those who
have experience with IPv4 DNS.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-issues-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dnsop-ipv6-dns-issues-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dnsop-ipv6-dns-issues-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-8-9154717.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsop-ipv6-dns-issues-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsop-ipv6-dns-issues-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-8-9154717.I-D@ietf.org>

--OtherAccess--

--NextPart--


.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Mon Aug  9 17:03:34 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17220
	for <dnsop-archive@lists.ietf.org>; Mon, 9 Aug 2004 17:03:34 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i79JPZ98024188;
	Mon, 9 Aug 2004 12:25:35 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i79JPZHK024187;
	Mon, 9 Aug 2004 12:25:35 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i79JPXbO024089
	for <dnsop@lists.uoregon.edu>; Mon, 9 Aug 2004 12:25:34 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01600;
	Mon, 9 Aug 2004 15:25:31 -0400 (EDT)
Message-Id: <200408091925.PAA01600@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: dnsop@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Subject: [dnsop] I-D ACTION:draft-ietf-dnsop-key-rollover-requirements-01.txt
Date: Mon, 09 Aug 2004 15:25:31 -0400
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations Working Group of the IETF.

	Title		: Requirements for Automated Key Rollover in DNSsec
	Author(s)	: G. Guette, O. Courtay
	Filename	: draft-ietf-dnsop-key-rollover-requirements-01.txt
	Pages		: 7
	Date		: 2004-8-9
	
This document describes problems that appear during an automated
   rollover and gives the requirements for the design of communication
   between parent zone and child zone in an automated rollover process.
   This document is essentially about key rollover, the rollover of
   one other Resource Record present at delegation point (NS RR) is
   also discussed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-key-rollover-requirements-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dnsop-key-rollover-requirements-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dnsop-key-rollover-requirements-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-8-9154723.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsop-key-rollover-requirements-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsop-key-rollover-requirements-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-8-9154723.I-D@ietf.org>

--OtherAccess--

--NextPart--


.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug 10 20:39:26 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20070
	for <dnsop-archive@lists.ietf.org>; Tue, 10 Aug 2004 20:39:25 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7AN6e2m002011;
	Tue, 10 Aug 2004 16:06:40 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7AN6eEO002007;
	Tue, 10 Aug 2004 16:06:40 -0700 (PDT)
Received: from mailout3.samsung.com (mailout3.samsung.com [203.254.224.33])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7AN6cxx001833
	for <dnsop@lists.uoregon.edu>; Tue, 10 Aug 2004 16:06:39 -0700 (PDT)
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I29009016UWET@mailout3.samsung.com> for dnsop@lists.uoregon.edu; Wed,
 11 Aug 2004 08:06:32 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I29001UC6UWOZ@mailout3.samsung.com> for
 dnsop@lists.uoregon.edu; Wed, 11 Aug 2004 08:06:32 +0900 (KST)
Received: from LocalHost ([168.219.202.103])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I29005336UVHS@mmp1.samsung.com> for
 dnsop@lists.uoregon.edu; Wed, 11 Aug 2004 08:06:32 +0900 (KST)
Date: Wed, 11 Aug 2004 08:07:36 +0900
From: "S. Daniel Park" <soohong.park@samsung.com>
Subject: RE: [dnsop] ipv6-dns-configuration-02 comments
In-reply-to: <245DBCAEEC4F074CB77B3F984FF9834F020CE476@esebe005.ntc.nokia.com>
To: juha.wiljakka@nokia.com, pekkas@netcore.fi, dnsop@lists.uoregon.edu
Message-id: <EDELKJDGPGNIPOAOHMNPMEDJGBAA.soohong.park@samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "S. Daniel Park" <soohong.park@samsung.com>
Content-Transfer-Encoding: 7BIT

Good indication and thanks Juha.

As one of IPv6-enabled mobile device manufacturer, 
I strongly second the usage of RA option for configuring 
recursive DNS Server. It's one of our business aspect
toward IPv6...

Regards.

- Daniel (Soohong Daniel Park)
- Mobile Platform Lab. Samsung Electronics.

> -----Original Message-----
> From: owner-dnsop@lists.uoregon.edu 
> [mailto:owner-dnsop@lists.uoregon.edu]On Behalf Of juha.wiljakka@nokia.com
> Sent: Wednesday, August 04, 2004 9:41 AM
> To: pekkas@netcore.fi; dnsop@lists.uoregon.edu
> Subject: RE: [dnsop] ipv6-dns-configuration-02 comments
> 
> 
> 
> Pekka and others,
> 
> -----Original Message-----
> 
> >>  4) 3GPP still needs to explain whether RA's are being used at 
> all at the
> >>moment -- that is, some have at least stated that e.g., 
> addresses/prefixes
> >>are configured as part of PDP context activation, which would 
> seem to hint
> >>at the fact that even if RA's would be possible, they might not 
> be used that
> >>much..
> 
> Usage of RA in 3GPP nw is no problem, i.e. it can be and is used. 
> I can provide some clarifying text on that in the 3GPP section. 
> RA is a part of the 3GPP UE IPv6 addressing:
> 
> From 3GPP TS 23.060, section 9.2.1.1:
> ----clip----
> ...
> 1)	The MS sends an Activate PDP Context Request message to the 
> SGSN as defined in clause "PDP Context Activation Procedure". The 
> MS shall leave PDP Address empty and set PDP Type to IPv6.
> 
> 2)	Upon reception of the Create PDP Context Request, the GGSN 
> creates an IPv6 address composed of the prefix allocated to the 
> PDP context and an interface identifier generated by the GGSN. 
> This address is then returned in the PDP Address information 
> element in the Create PDP Context Response message. The 
> processing of the Create PDP Context Request and Create PDP 
> Context Response, in both the SGSN and the GGSN, is otherwise as 
> specified in clause "PDP Context Activation Procedure".
> 
> NOTE: 	Since the MS is considered to be alone on its link 
> towards the GGSN, the interface identifier does not need to be 
> unique across all PDP contexts on any APN.
> 
> 3)	The MS receives the IPv6 address produced by the GGSN in 
> the Activate PDP Context Accept. The MS extracts the interface 
> identifier from the address received and stores it. The MS shall 
> use this interface identifier to build its link-local address and 
> may also use it for building its full IPv6 address, as describe 
> in step 5. The MS shall ignore the prefix contained in the 
> address received in the Activate PDP Context Accept. The 
> processing of the Activate PDP Context Accept is otherwise as 
> specified in clause "PDP Context Activation Procedure".
> 
> 4)	The MS may send a Router Solicitation message to the GGSN 
> to activate the sending of the Router Advertisement message.
> 
> 5)	The GGSN sends a Router Advertisement message. The Router 
> Advertisement messages shall contain the same prefix as the one 
> provided in step 2. A given prefix shall not be advertised on 
> more than one PDP context on a given APN, or set of APNs, within 
> the same addressing scope. The GGSN shall be configured to 
> advertise only one prefix per PDP context.
> 
> 	After the MS has received the Router Advertisement message, 
> it constructs its full IPv6 address by concatenating the 
> interface identifier received in step 3, or a locally generated 
> interface identifier, and the prefix received in the Router 
> Advertisement. If the Router Advertisement contains more than one 
> prefix option, the MS shall only consider the first one and 
> silently discard the others.
> ...
> ----clip----
> 
> Cheers,
> 	 -Juha-
> 
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> 
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Thu Aug 12 02:23:03 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05968
	for <dnsop-archive@lists.ietf.org>; Thu, 12 Aug 2004 02:23:02 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7C3iKHZ022680;
	Wed, 11 Aug 2004 20:44:20 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7C3iKxQ022679;
	Wed, 11 Aug 2004 20:44:20 -0700 (PDT)
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7C3iItP022666
	for <dnsop@lists.uoregon.edu>; Wed, 11 Aug 2004 20:44:19 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [2001:200:0:4819:99b8:98fa:2262:6c66])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id D189A1525D; Thu, 12 Aug 2004 12:44:17 +0900 (JST)
Date: Thu, 12 Aug 2004 12:44:15 +0900
Message-ID: <y7vvffprpf4.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: david.kessens@nokia.com
Cc: dnsop@lists.uoregon.edu
Subject: [dnsop] next steps for draft-ietf-dnsop-misbehavior-against-aaaa-01.txt
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>

Hello,

I'm sending this to you as the shepherding AD of
draft-ietf-dnsop-misbehavior-against-aaaa-01.txt.

According to the I-D tracker page,
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11591&rfc_flag=0

the status draft is "AD Followup" where "the shepherding AD has the
action item to determine appropriate next steps".  So, I've been
waiting for a suggestion on the next steps.

However, Pekka Savola suggested me to revise the draft spontaneously,
addressing the comments shown in the tracker page.  (according to him)
the new revision would help/accelerate the decision of the next steps
for the shepherding AD.

Basically, I'm willing to do that (at least revising the draft in the
IESG evaluation doesn't harm much...), but if I heavily misunderstand
the process and should rather wait for the suggested next steps,
please let me know.

Thanks,

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug 17 01:47:17 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09039
	for <dnsop-archive@lists.ietf.org>; Tue, 17 Aug 2004 01:47:17 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7H4LWBe020847;
	Mon, 16 Aug 2004 21:21:32 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7H4LWJ1020840;
	Mon, 16 Aug 2004 21:21:32 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7H4LVTS020788
	for <dnsop@lists.uoregon.edu>; Mon, 16 Aug 2004 21:21:31 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i7H4Kwca017977;
	Mon, 16 Aug 2004 21:20:58 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i7H4KwfC017976;
	Mon, 16 Aug 2004 21:20:58 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Mon, 16 Aug 2004 21:20:58 -0700
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
Cc: minutes@ietf.org, sra@isc.org
Subject: [dnsop] draft DNSOP minutes (IETF 60)
Message-ID: <20040817042058.GA17957@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: David Meyer <dmm@1-4-5.net>


	Folks,

	Here are the draft minutes. Please send corrections to
	the list.

	Thanks,

	Dave & Rob

-------

Domain Name System Operations (dnsop)

WEDNESDAY, August 4, 2004 (1300-1500)
=====================================

CHAIR(s): David Meyer <dmm@1-4-5.net>
          Rob Austein <sra@isc.org>

MINUTES:  Ted Lemon   <mellon@fugue.com>

==========================================

David Meyer:    Suggests authors look at xml2rfc.
                Agenda bashing.

Olaf Kolkman:   dnssec-operational-practices
                Very few differences between the initial submissions,
                except we did a major language (style, spelling)
                review. Content-wise very little changed. A few recs
                from this group such as turning the recs we made 
                more into tradeoffs. 

                Since there is code around, we would appreciate it if
                people could test what we've described as operational
                practices and see if what we've said makes sense. We'd
                really like feedback. Now there is code and a stable
                spec so people can really give us feedback. 

David Meyer:    One other thing I'd like to ask authors, let us know
                what they would like WG to do with their document.
                Ready for WGLC or still outstanding issues. 

Rob Austein:    Right, and in this case we need more readers before we
                proceed. 

David Meyer:    inaddr-required draft, very little activity.

Rob Austein:    This one's come up before. One issue is that some
                people never get past draft filename. If you look at
                the title it doesn't match that. We have one extremely
                vocal opponent of this draft who tries very hard to
                trash the discussion of it - if he does that again we
                will kick him off the list. 

David Meyer:    (consensus call)

Rob Austein:    Looks like people want to go forward with this.

AD (Kessens):   Do you have a plan to make progress with it?

Rob Austein:    We're ready for WGLC unless someone has some other
                issue. 

David Meyer:    With the exception of the individual who's been
                resisting it, there has been no discussion. 

Someone(??):    Take out the normative language.

Suzanne Woolf:  draft-ietf-dnsop-serverid-02.txt 

                This draft was allowed to expire after going through
                most of the process, dunno if it went to IESG, but
                history is that this document is mechanism for finding
                out which server you're talking to, perhaps in a
                load-balancing or anycast cluster. 

                Hostname.bind appeared specifically to support
                anycast. The draft was to document the existing
                practice and suggest a different name. Specific
                mechanism was send query QTYPE CHAOS hostname.bind TXT
                and get server name. Proposal was to change bind to
                server. When documenting, people noticed problems.

                Some concern about namespace abuse as it's an entire
                TLD in class not used for a whole lot. Also
                implementation specific. Most serious drawback
                operationally, requires a separate query because it's
                not in-band with query that's being answered. Some
                consideration of DNSOP coming up with requirements so
                DNSEXT can go do something. Obvious requirement -
                needs to be in-band. Easy to configure, for dumb
                administrators. Interoperable. Not
                implementation-specific. Preferred if it doesn't
                commit namespace abuse. 02 submitted last week,
                documents this initial set of requirements. People
                have suggested, up to WG to decide, needs to be easily
                extensible. Able to support clients that might want
                to offer information. Should be difficult to disable,
                in interests of encouraging people to share info about
                their servers. Initial attempt at solution submitted
                as individual draft to dnsext, uses EDNS0/OPT
                pseudo-RR. There are some gaps, need to think about
                what we want to put in that field. Comments for this
                document, discuss here. Solution to be discussed in
                DNSEX. tomorrow. Anything on current requirements?
                If you have opinions, send them in.

Matt Larson:    draft-ietf-dnsop-bad-dns-res-02.txt 

                Let me say there's a problem with versioning.
                Submitted -03, came out as -02. No idea
                why. Submitting new version to address what comes out
                of this and subsequent ML discussion, so hopefully
                academic. 

                Can I ask who's read the draft. It's been out a
                couple of years. 

                Upshot: draft discusses 11 specific issues that cause
                varying amounts of problems with .com and .net. Not
                worth going over this in detail, but it all adds up to
                some number of extra useless queries that we see.
                What do we do next? 

                Should we modify protocol. A bunch of these have been
                fixed. There are some other things up here that I
                think are worth having. Some are crossing line from
                ops recommendation to something that should be
                codified in protocol. On authns side, if you leave
                off trailing '.' on NS record, authns server can
                figure it out, emit a warning. 0 TTL on NS records can
                have detrimental effect on your parent, so becomes
                philosophical question what an implementation should
                do. Anybody who operates name servers high up can
                feel pain of aggressive dynamic update clients. Ought
                to be two-step process, probe with NS-aware query and
                only then send update. One thing we see a lot of is
                queries for domain names that look a lot like IP
                addresses. 1.2.3.4 rather than ptr query. What do
                you do about that to remove that noise. One
                possibility: delegate all numeric TLDs to separate set
                of servers. That in a nutshell is the draft and its
                recommendations. Encourage folks to read it. Ask
                co-chairs for next steps.

Rob Austein:    Topical document, looking for WGLC soon. Suspect that
                the way to handle protocol changes are to write it as
                here are the operational problems we've seen, we think
                appropriate fix is this, but don't actually specify
                changes. We don't do that. 

Pekka Savola:   In a related similar subject when we forwarded
                something like this to IESG got feedback back that
                proposed fix, even though good idea, if it hadn't been
                taken up in protocol working group, there might be
                some pushback. 

Rob Austein:    We want to document the requirements. Don't care
                which working group. Ask the AD.

Matt Larson:    So take out recommendations?

Rob Austein:    Lots aren't protocol changes. Maybe one or two are. 

Olaf Kolkman:   If you have protocol recommendations put them in
                another I-D, submit to dnsext.

Matt Larson:    Appreciate comments from WG on things in the draft
                that rise to level of protocol changes.

Olaf Kolkman:   I don't see anything in there that goes beyond
                implementation guideline except for creation of new
                TLDs which is ICANN problem. So I don't think we are
                going to be upset if this goes forward. 

Rob Austein:    Path forward: a couple of people, I'll be one, should
                go through this, if we find stuff that's crossing
                line, discuss with chairs and AD. Don't want to lose
                any of these suggestions. 

Rob Austein:    Ready for WGLC. (lots of hands.)

Rob Austein:    Readers who think not ready for WGLC:

Jinmei Tatuya:  I basically have no objection to having WGLC, but want
                to make one comment, previously I made comment on the
                issuing of queries to name servers, got response from
                ???, have not responded to comment, (joseph?), because
                have not found enough time, but am willing to make
                response. Probably can just do that during WGLC. 

Rob Austein:    Yes, sounds fine.

Matt Larson:    Would like to push out quick revision, is that good?

Rob Austein:    Doesn't matter if it's before or after WGLC.

David Meyer:    On to key roll-over requirements.

Francis Guette: Please read -00 draft, we will be doing 01 soon.
                There is still something unclear needed about
                emergency rollover. In case key known by too many
                persons. Section about it, perhaps you can review it,
                don't know exactly what to do. We know we need to do
                something fast to keep the chain of keys. We received
                no comment. As soon as there is no more issues or
                details to explain, etc, perhaps we can do a WGLC.

                Please help with MIP6 WG, trying to explain what
                DNSSEC is doing, asks for help to rewrite the DNSSEC
                subsection which I called . piece of DNSSEC bashing.
                Route Optimization Security Design Background
                document. Contact me or Gabriel Montenegro. 

Olaf Kolkman:   Haven't read in very long time, most people who were
                involved with DNSSEC have not done so. This very
                topic has been getting a lot of attention recently.
                We have had a few discussions on automatic key
                rollovers recently in DNSEXT. I will do it soon, ask
                others to do it as well.

G. Montenegro:  We have this document, it's a back grounder for MIPv6,
                we have a section on DNSSEC, really need some help
                from this WG. Either email me or Francis. 

Johan Ihrens:   Once upon a time I thought that rollover stuff will 
                certainly not require protocol changes and therefore
                DNSOPS would be place for discussions. However, it
                may well be that we end up with protocol changes which
                is why those other drafts on rollover are being bashed
                out in DNSEXT. My brain isn't large enough to cover
                this topic in two different WGs. Keep it all here or
                push it all into DNSEXT. Can't have requirements doc
                in one group and proposed in another.

Rob Austein:    We usually do.

Francis Guette: For solutions, perhaps these are some already in
                DNSSEC. 

David Meyer:    So how many people have read this?

Rob Austein:    Not much of a showing. Of those who read it, how many 
                thing we need to work on this. Is this something WG
                don't want to work on, or something WG does want to
                work on? 

Russ Mundy:     Think that that's true. We need to read it, need to
                attack the operational requirements. Don't remember
                content anymore. 

Rob Austein:    We need to work on key rollover requirements. We
                don't know this is the right doc. First step is to
                read it. 

David Meyer:    Moving right along, increasing dns server.

Rob Austein:    Olaf just reminded me that we have another WG that
                could use some help. MARID. They're talking about
                using DNS to hold stuff dealing with whether or not to
                accept mail from SMTP senders. Very interesting and
                somewhat loud topic. Some have interesting ideas about
                DNS. They have another meeting. 

Schnitz:        In DNSOP, years ago, producing informational RFC
                addressing what the rest of IETF needs to know about
                the DNS. Abby offered copyright protection for using 
                parts of her book. Did anything come of that?

Olaf Kolkman:   Interesting. One issue I want you to address in
                testing - if there is any preference for any of the
                servers in the query pattern. Like, first one gets
                most. Biggest reason for deploying this not mentioned
                in draft. Glue for net zone requires thirteen
                signatures. We could shrink to five. Signatures are
                big. NS and A records are small. 

Yasuhiro Morishita: Is this a DNSSEC issue. I think that we need to
                testing in DNSSEC environment. 

Rob Austein:    Particular issue for signatures is whether this is a
                good idea or not. Number of RRsets matters.

Paul Vixie:     When we looked into doing this at the time that Bill
                Manning first proposed that we switch to
                root-servers.net, reason we did not go with smaller
                numbers of names has to do with the way the recursive
                and stub clients handle SRVFAIL. In event of SRVFAIL,
                no other address for that name server will be tried.
                Timeout will stimulate retry. We thought that it
                would be bad if there was no fallback in event that
                single server did not have zone loaded. So the two
                suggestions I have are first that some minimum number,
                like two or three names, be used, each with small
                number of records, and second that this be considered
                for TLDs but not roots at this time. 

Yasuhiro Morishita: Root and TLDs not be amended be applied.

Rob Austein:    Not done yet, right?

Yasuhiro Morishita: Right.

Rob Austein:    I assume folks think this is useful work, I certainly
                think so. Anyone else. That looks like good support.

David Meyer:    I looked at id-trackers, generated list of other
                drafts, this stuff is already at IESG. misbehavior
                and ipv6-dns-issues are at IESG but in ad followup.

Pekka Savola:   Been revised a couple of times since it went through
                IESG, some comments from Thomas Narten, would like to
                get feedback. Least important one is whether you
                believe there are some documents that should be
                normative references but are not. Second is whether
                we need to do extra. (loud feedback. So feedback
                would be appreciated. It has some connection to
                protocol work, so feedback. from there would be
                welcome. Last issue - split off some parts of
                document into separate documents. E.g. forward and
                reverse DNS updates. 

Rob Austein:    Have you sent list of questions. Might want to resend.

Jinmei Tatuya:  In my understanding authors can just wait for feedback
                from IESG. I would like to make sure that the authors
                there is nothing for them to do in ad-for-ops status.

David Meyer:    We have to look at if there are discuss comments
                against it, or you can look. We can show you how.

David Meyer:    ad-is-watching - second draft is expired. this is
                local-zones. So I'll talk to AD to see what gives. 

Rob Austein:    Paul, want to say anything about respsize doc?

Paul Vixie:     I know that one person actually read this and found
                clownish commentary I put in draft. Nobody flamed me.
                There is a very controversial comment in this draft. 

Peter Koch:     Have one question or remark. We had funny discussion
                about what is allowed length for domain name. 255,
                256, 253. It'. a bit late now to discuss this
                because this is very basic DNS stuff. Nothing to do
                with your draft, but obviously some basic questions
                yet unresolved. Anything we can do in this or another
                WG to resolve this? 

Paul Vixie:     It is certainly the case that in respsize draft I
                should not have mentioned any numbers because it's
                easy to look in other specs. Should just refer to
                standards. That's how I plan to fix the problem in mu
                small corner of ocean. In larger context, it would be
                interesting to see results of survey of what people
                think is max length of domain name on wire. but for
                myself would be more interested in seeing results than
                doing survey. 

Peter Koch:     So by deferring this somewhere else, I beg to differ
                you, you ignored the problem. So what can we do about
                that? Obviously there is one.

Paul Vixie:     I don't know that there really is one. May be sleeping
                dog. People don't design their businesses/projects
                around ability to use names > 250 chars. If you are
                interested in subject, you are speaking words that
                normally precede the statement "I volunteer." 

Peter Koch:     To volunteer is a transitive word in IETF. You are
                probably right, so may or may not be academic
                problem. In your draft, and in other docs, there are
                consequences out of max length. If there is corner
                case, the one single octet that is missing or not, I
                would like to have the discussion before hand, so we
                don't wind up where Mary did solving basic DNS
                problems in midst of IETF meeting. 

Paul Vixie:     Wasn't at Mary because of lack of strong wind. If
                someone is using query name that is really that long,
                difference will be there will be very few glue records
                in the delegation area. Seems unlikely that difference
                of opinion of one octet is going to change planning
                very much. The fact that someone can concoct an
                experiment where really long name breaks model,
                doesn't matter. When people are asking for names that
                really do exist, you care if they got enough glue. So
                for my part only thing that matters is that I take out
                the number and reference 1035. Until someone writes
                critique of 1035, that's good enough for me.

Olaf Kolkman:   Second argument for all you ever wanted to know about
                DNS but were afraid to ask, would be handy to have.

Paul Vixie:     In terms of process, I do not think this draft is
                ready to progress, because no-one complained. So until
                I have some feeling that someone other than me has
                seen this text, I will say it's not ready to go
                forward. 
 
Rob Austein:    So given that we had a number of people claiming this
                was important work, suggests that there is some work
                to be done in terms of reading doc that hasn't
                happened yet. You're all slackers. Go read the document!

David Meyer:    On to the Non-WG documents...

Pekka Savola:   There was one WG doc that has expired a long time ago
                which hasn't been discussed - don't publish
                unreachable draft. Should work on it or not?

Rob Austein:    The author has in fact said he has no time to work on
                it anymore. thought we had a volunteer, have to check
                notes, have not  made obvious progress on it. Do
                people still feel it's useful? Itojun wanted it. I
                dropped ball on this one, will consult notes. 

David Meyer:    So these were the other drafts that had expired. A
                couple of them have been updated since I made these
                slides. Not sure there's anything to say about them
                other than that they're expired, we've been through
                these a couple of times, wanted to know if anybody
                thought this was work that needs to be brought back or
                let it die (dynreverse, interim-signed) 

Tim Chown:      I think dynreverse is important.

Alain Durand:   Thank you for volunteering to work on it with me.

Rob Austein:    Protocol change?

Alain Durand:   Depends on what you call protocol.

Rob Austein:    Change to whole bunch of deployed code. Dubious about
                this one fitting here.

Alain Durand:   I don't care about this particular draft, way of
                solving problem, but do care to have one solution for
                what to do with reverse DNS. In v4 ISP used to do
                prepopulation, would like to see  solution. Don't care
                what it is. 

Tim Chown:      I'm not saying this document is the perfect way, but this
                is important topic.

Rob Austein:    You're volunteering.

David Meyer:    What I had on agenda next was IPv6 config opts. Would
                like to leave for last. Let's go on to Peter.

Peter Koch:     Would like to ask WG question regarding an idea. Using
                SRV records in DNS to do something that has nothing to
                do with DNS. At the moment we have four regional
                internet registries, you ask for IP addresses, receive
                some information, who to contact for that
                address. Which whois server do I query. Would like
                client to figure it out. 

                Suggestion on table - draft-sanz-whois-srv-01.txt.

Pekka Savola:   Can we assume that hte division between different
                registries will be forever on first byte boundary?

Audience:       no.

Pekka Savola:   Does it work if we can't assume that?

Peter Koch:     No we can't know forever, but where's the problem at
                the moment. Currently the RIRs receive more than /8
                worth of address space. If we have non-octet
                boundaries, could take it down the path, distributing
                it on the next level. 

Paul Vixie:     First, the SRV records in question would have to be at
                apexes of delegated part of tree, not in in-addr zone,
                because can't have anything at point above zone cut. A
                query for these would be referred to authority zone
                for these, which is actually a good thing. With regard
                to CIDR allocations, ipv6 tree, we really need to be
                looking at RFC 1101 as far as networking certainly the
                bind resolver has been able to look up RFC 1101 info -
                getnetbyaddr, this works even in case of RFC 2317 or
                other CIDR delegations. Unfortunate that it requires
                lookup of A record to find mask, but can be done. If
                you were to cast this in terms of additional data to
                go into RFC 1101 network naming schema, this would be a
                wonderful thing.

Peter Koch:     So you are saying that this is only useful in
                conjunction with RFC 1101?

Paul Vixie:     Yes. We have to be able to cover that whole area. This
                is an odd form of label stripping. May be a particular
                WHOIS server for 193.10. Start by looking at /32
                level, don't have to check every bit. RFC 1101 gives way
                to find netmask for closest enclosing network. This is
                a good idea, excellent convention, I know that it
                needs to be done in bottom up fashion rather than
                top-down fashion. This is a better solution, but
                requires RFC 1101. 

Peter Koch:     I again beg to differ. What I was afraid to suggest
                was as you suggested, there may be a more specific
                responsible whois server for /32. So sure you could do
                that, but don't see where RFC 1101 comes into the
				thing there. 

Paul Vixie:     RFC 1101 gives you way to discover that there is a /15
				or a /27 or something. 

Peter:          You still have the closest enclosing delegation on
                octet boundary.

Paul Vixie:     Most frequent use of this other than data mining and
                spamming is complaining about them, need to go to
                closest enclosing. 

Russ Mundy:     We're co-chairing a project that's been underway for
                short length of time that focuses on getting DNSSEC
                deployed. Trying to provide a structure/org that's a
                program office for facilitating things that need to
                happen for DNSSEC to get out there. Need to identify
                what needs to happen. Trying to collect peoples' views
                on what needs to happen. Steve has web site,
                dnssec-deployment.org. We look forward to having folks
                join in, provide criticism and information, working
                with everybody. 

Steve Crocker:  You covered it pretty well. I would emphasize is that
                focus is on post-ietf process. What do you do after
                specs are done. There's a host of little problems,
                chicken-and-egg. Who holds the root key. What if you
                ask for signed, get back unsigned. Verisign has
                created its own DNSSEC consortium. I imagine there
                will be  other specialized groups that focus on stuff.

David Meyer:    Pekka, come up please. We have three more agenda
                items. RIPE survey, DNSSEC, EPP if Scott is
                here. Brief review of DNS config options work.

Pekka Savola:   David Malone asked me to present this. IPv6
                lookups. This misbehavior towards certain kinds of
                queries, esp. IPv6 lookups. Took quite a bit of logs
                and found over 20k DNS servers, did a query looking up
                how many had AAAA records or how many had problems
                looking up them. Not sure if this shows, but the thing
                was that 0% have AAA records, 80% have misbehavior. 

                So there's a big problem for IPv6 hosts. Something
                needs to be done about it. What to do is good
                question. Should we set up  hall of shame?

Scott Hollenbeck: Author of EPP. Work of provreg WG. This doc is
                individual submission, tracking progress of EPP and 
                DNSSEC. (reads notes) 

Rob Austein:    The way Scott phrased it, I think interval is
                recommendation. 

Russ Mundy:     I'm not sure if it's a work item for this WG because
                it's part of a space that WG hasn't dealt with in the
                past. I think it's very important work that needs to
                be done whether part of this WG or not. 

Rob Austein:    I asked Scott to bring this here. This is not DNSEXT
                work because it's not DNS protocol. Not really EPP
                work. This is really about what does DNSSEC need. So
                this seems like the right place to come to get
                help. Don't care if WG adopts it. 

Ed Lewis:       Its a good thing to discuss here. One operator said
                would like to see registries (?) in  common. EPP is
                primarily used in one set of registries, but not all
                registries. Would be good forum for operators to say
                how all registries should treat ???

Scott Hollenbeck: Quick note to ML. Will do.

David Meyer:    DNS configuration options draft. Advisory doc to
                IESG. Wanted to see fi there were solid objections to
                what's in draft, if not, WGLC. Let me remind you of
                the three things. If you've been asleep for last
                couple of years, these are the three options. RA,
                DHCP, WKA. What we want is to move this doc through
                WGLC, get it to  informational, if you have any
                objections, sense that some issue that you have isn't
                covered, please speak up. 

Rob Austein:    Documenting state of inconclusive discussion we've had
                over and over again. If it covers all issues
                adequately, we are done. If there is something
                missing, tell us now.

David Meyer:    Should really get it to informational (after all, this
                is the third time draft has been written).

David Kessens:  Major issues only. No nit-picking please.

David Meyer:    Reminder: this is not a proposal - just documenting
                what has been proposed.

Erik Nordmark:  Seems to make some performance claims based on
                unstated assumptions. E.g. claims that RAs are
                better. Sending this stuff many times a day in case it
                changes. Seems like wasting bytes. Don't know what to
                do about performance claims. Seems to need a bit more
                rigor. 

Rob Austein:    Needs more eyes on that part of text. It's just bytes
                in a message that's going out anyway.

Erik Nordmark:  May be a lot more bytes.

Rob Austein:    Right, so we should back it up.

Jinmei Tatuya:  Not making objection, but my understanding there are
                several substantial comments on previous draft. There
                are significant  changes from previous version, should
                issue last call again. Make solid consensus. Not
                necessarily going to push this idea if you are
                particularly in hurry. 

Rob Austein:    We're in a hurry because in order to get this done we
                had a deadline. The AD can speak for self. AD will be
                cool with taking more time for WGLC if we're making
                serious progress by doing so. Don't want it to drag on
                forever. 

David Kessens:  I can go for it.

-----
AGENDA

 o Administriva                      2 minutes

   - Mailing list: majordomo@lists.uoregon.edu
     subscribe dnsop

   - Scribe?

   - Blue Sheets

 o Agenda Bashing                    5 minutes
   Meyer                                           

 o Review and status of work items           55 minutes

   Active Drafts
   -------------
   draft-ietf-dnsop-dnssec-operational-practices-01.txt   5 minutes
    Kolkman et al
   draft-ietf-dnsop-inaddr-required-05.txt                5 minutes
     Senie
   draft-ietf-dnsop-ipv6-dns-issues-07.txt                2 minutes
    Durand, et al 
    IESG Evaluation::Revised ID Needed (Informational)
   draft-ietf-dnsop-ipv6-transport-guidelines-02.txt      2 minutes
    Durand, et al 
    RFC Ed Queue (BCP)
   draft-ietf-dnsop-key-rollover-requirements-00.txt      5 minutes
    Guette, et al
   draft-ietf-dnsop-misbehavior-against-aaaa-01.txt       2 minutes
    Morishita, et al.
    IESG Evaluation::AD Followup (Informational)
   draft-ietf-dnsop-ohta-shared-root-server-03.txt        1 minute
    Ohta
   draft-ietf-dnsop-serverid-02.txt                       2 minutes
    Woolf
   draft-ietf-dnsop-bad-dns-res-02.txt                   15 minutes
    Larson/Barber

   Expired WG documents
   ---------------------
   draft-ietf-dnsop-resolver-rollover-01.txt              2 minutes
    expired (Kolkman)

   AD is watching
   ---------------------
   draft-ietf-dnsop-respsize-01.txt                       5 minutes
    expired (Vixie/Kato)
   draft-kato-dnsop-local-zones-01.txt                    5 minutes
    expired/no WG document

   Non-WG Documents
   ------------------------
   draft-durand-dnsop-dynreverse-01.txt                   2 minutes
    expired
   draft-ihren-dnsop-interim-signed-root-02.txt           2 minutes
    expired
   draft-yasuhiro-dnsop-increasing-dns-server-01.txt      5 minutes
    expired

 o DNSSEC Deployment Activity                 5 minutes
   Steve Crocker/Russ Mundy

 o IPv6 DNS Configuration Options                        15 minutes

   draft-ietf-dnsop-ipv6-dns-configuration-01.txt
    Jeong, et al

 o RIPE survey                       10 minutes
   draft-ietf-dnsop-misbehavior-against-aaaa-01.txt
   http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-dns-malone.pdf
   Savola, et al.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug 17 11:26:48 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23033
	for <dnsop-archive@lists.ietf.org>; Tue, 17 Aug 2004 11:26:47 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HEOOv6004358;
	Tue, 17 Aug 2004 07:24:25 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7HEOOs0004354;
	Tue, 17 Aug 2004 07:24:24 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HEOONH004337
	for <dnsop@lists.uoregon.edu>; Tue, 17 Aug 2004 07:24:24 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i7HEGskT023055
	for <dnsop@lists.uoregon.edu>; Tue, 17 Aug 2004 07:16:54 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i7HEGsLs023054
	for dnsop@lists.uoregon.edu; Tue, 17 Aug 2004 07:16:54 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 17 Aug 2004 07:16:54 -0700
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
Subject: [dnsop] FYI (xml2rfc update)
Message-ID: <20040817141654.GB23036@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: David Meyer <dmm@1-4-5.net>

>> From: Marshall Rose <mrose+internet.xml2rfc@dbc.mtview.ca.us>
>> To: xml2rfc mailing list <xml2rfc@lists.xml.resource.org>
>> Subject: [xml2rfc] two things
>> Date: Mon, 16 Aug 2004 14:16:44 -0700
>> 
>> 1. v1.25 was released yesterday. numerous bug fixes, no new 
>> functionality
>> 
>> 	http://xml.resource.org/
>> 
>> 2. inspired by http://interglacial.com/rss/ there are now 3 RSS feeds 
>> available:
>> 
>> 	http://xml.resource.org/public/rfc/bibxml/index.rdf    - rfcs
>> 	http://xml.resource.org/public/rfc/bibxml3/index.rdf   - 
>> internet-drafts
>> 	http://xml.resource.org/public/rfc/bibxml4/index.rdf   - w3c
>> 
>> these feeds are generated by the process that creates the biblio xml 
>> files, so when the feed reports something new you know that the 
>> bibliographic database has been updated.
>> 
>> /mtr
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug 17 12:04:18 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25410
	for <dnsop-archive@lists.ietf.org>; Tue, 17 Aug 2004 12:04:17 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HFE1E1013822;
	Tue, 17 Aug 2004 08:14:01 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7HFE1pm013821;
	Tue, 17 Aug 2004 08:14:01 -0700 (PDT)
Received: from laposte.rennes.enst-bretagne.fr (laposte.rennes.enst-bretagne.fr [192.44.77.17])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HFDxHC013685
	for <dnsop@lists.uoregon.edu>; Tue, 17 Aug 2004 08:14:00 -0700 (PDT)
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i7HFD6V21735;
	Tue, 17 Aug 2004 17:13:06 +0200
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id i7HFD6Sj088411;
	Tue, 17 Aug 2004 17:13:07 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200408171513.i7HFD6Sj088411@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: David Meyer <dmm@1-4-5.net>
cc: dnsop@lists.uoregon.edu, minutes@ietf.org, sra@isc.org
Subject: Re: [dnsop] draft DNSOP minutes (IETF 60) 
In-reply-to: Your message of Mon, 16 Aug 2004 21:20:58 PDT.
             <20040817042058.GA17957@1-4-5.net> 
Date: Tue, 17 Aug 2004 17:13:06 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   	Here are the draft minutes. Please send corrections to
   	the list.
   
   
   Francis Guette: Please read -00 draft, we will be doing 01 soon.
           ^^^^^^
=> my name is Francis Dupont, Gilles Guette is one of the authors
and I spoke on behalf of them. BTW the 01 is already available.

                   There is still something unclear needed about
                   emergency rollover. In case key known by too many
                   persons. Section about it, perhaps you can review it,
                   don't know exactly what to do. We know we need to do
                   something fast to keep the chain of keys. We received
                   no comment. As soon as there is no more issues or
                   details to explain, etc, perhaps we can do a WGLC.
   
                   Please help with MIP6 WG, trying to explain what
                   DNSSEC is doing, asks for help to rewrite the DNSSEC
                   subsection which I called . piece of DNSSEC bashing.
                   Route Optimization Security Design Background
                   document. Contact me or Gabriel Montenegro. 
   
   Francis Guette: For solutions, perhaps these are some already in
           ^^^^^^  DNSSEC. 

=> same problem.

Thanks

Francis.Dupont@enst-bretagne.fr
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug 17 12:44:08 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28283
	for <dnsop-archive@lists.ietf.org>; Tue, 17 Aug 2004 12:44:07 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HFhxZY017851;
	Tue, 17 Aug 2004 08:43:59 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7HFhxPe017843;
	Tue, 17 Aug 2004 08:43:59 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HFhwDh017779
	for <dnsop@lists.uoregon.edu>; Tue, 17 Aug 2004 08:43:58 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i7HFhD6N025116;
	Tue, 17 Aug 2004 08:43:13 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i7HFhDZ0025115;
	Tue, 17 Aug 2004 08:43:13 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 17 Aug 2004 08:43:13 -0700
From: David Meyer <dmm@1-4-5.net>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Cc: dnsop@lists.uoregon.edu, minutes@ietf.org, sra@isc.org
Subject: Re: [dnsop] draft DNSOP minutes (IETF 60)
Message-ID: <20040817154313.GA25109@1-4-5.net>
References: <20040817042058.GA17957@1-4-5.net> <200408171513.i7HFD6Sj088411@givry.rennes.enst-bretagne.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200408171513.i7HFD6Sj088411@givry.rennes.enst-bretagne.fr>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: David Meyer <dmm@1-4-5.net>

On Tue, Aug 17, 2004 at 05:13:06PM +0200, Francis Dupont wrote:
>>  In your previous mail you wrote:
>> 
>>    	Here are the draft minutes. Please send corrections to
>>    	the list.
>>    
>>    
>>    Francis Guette: Please read -00 draft, we will be doing 01 soon.
>>            ^^^^^^
>> => my name is Francis Dupont, Gilles Guette is one of the authors
>> and I spoke on behalf of them. BTW the 01 is already available.

Gotcha. Thanks.

>> 
>>                    There is still something unclear needed about
>>                    emergency rollover. In case key known by too many
>>                    persons. Section about it, perhaps you can review it,
>>                    don't know exactly what to do. We know we need to do
>>                    something fast to keep the chain of keys. We received
>>                    no comment. As soon as there is no more issues or
>>                    details to explain, etc, perhaps we can do a WGLC.
>>    
>>                    Please help with MIP6 WG, trying to explain what
>>                    DNSSEC is doing, asks for help to rewrite the DNSSEC
>>                    subsection which I called . piece of DNSSEC bashing.
>>                    Route Optimization Security Design Background
>>                    document. Contact me or Gabriel Montenegro. 
>>    
>>    Francis Guette: For solutions, perhaps these are some already in
>>            ^^^^^^  DNSSEC. 
>> 
>> => same problem.
>> 
>> Thanks

Will fix.

Dave


>> 
>> Francis.Dupont@enst-bretagne.fr
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug 17 12:53:15 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29051
	for <dnsop-archive@lists.ietf.org>; Tue, 17 Aug 2004 12:53:14 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HFjVhl019825;
	Tue, 17 Aug 2004 08:45:31 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7HFjVsQ019823;
	Tue, 17 Aug 2004 08:45:31 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HFjV8Y019803
	for <dnsop@lists.uoregon.edu>; Tue, 17 Aug 2004 08:45:31 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i7HFiw2E025160;
	Tue, 17 Aug 2004 08:44:58 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i7HFiwhF025157;
	Tue, 17 Aug 2004 08:44:58 -0700
Date: Tue, 17 Aug 2004 08:44:58 -0700
Message-Id: <200408171544.i7HFiwhF025157@m106.maoz.com>
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
cc: minutes@ietf.org
Subject: [dnsop] updated DNSOP minutes
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: David Meyer <dmm@1-4-5.net>




Domain Name System Operations (dnsop)

WEDNESDAY, August 4, 2004 (1300-1500)
=====================================

CHAIR(s): David Meyer <dmm@1-4-5.net>
          Rob Austein <sra@isc.org>

MINUTES:  Ted Lemon   <mellon@fugue.com>

==========================================

David Meyer:    Suggests authors look at xml2rfc.
                Agenda bashing.

Olaf Kolkman:   dnssec-operational-practices
                Very few differences between the initial submissions,
                except we did a major language (style, spelling)
                review. Content-wise very little changed. A few recs
                from this group such as turning the recs we made 
                more into tradeoffs. 

                Since there is code around, we would appreciate it if
                people could test what we've described as operational
                practices and see if what we've said makes sense. We'd
                really like feedback. Now there is code and a stable
                spec so people can really give us feedback. 

David Meyer:    One other thing I'd like to ask authors, let us know
                what they would like WG to do with their document.
                Ready for WGLC or still outstanding issues. 

Rob Austein:    Right, and in this case we need more readers before we
                proceed. 

David Meyer:    inaddr-required draft, very little activity.

Rob Austein:    This one's come up before. One issue is that some
                people never get past draft filename. If you look at
                the title it doesn't match that. We have one extremely
                vocal opponent of this draft who tries very hard to
                trash the discussion of it - if he does that again we
                will kick him off the list. 

David Meyer:    (consensus call)

Rob Austein:    Looks like people want to go forward with this.

AD (Kessens):   Do you have a plan to make progress with it?

Rob Austein:    We're ready for WGLC unless someone has some other
                issue. 

David Meyer:    With the exception of the individual who's been
                resisting it, there has been no discussion. 

Someone(??):    Take out the normative language.

Suzanne Woolf:  draft-ietf-dnsop-serverid-02.txt 

                This draft was allowed to expire after going through
                most of the process, dunno if it went to IESG, but
                history is that this document is mechanism for finding
                out which server you're talking to, perhaps in a
                load-balancing or anycast cluster. 

                Hostname.bind appeared specifically to support
                anycast. The draft was to document the existing
                practice and suggest a different name. Specific
                mechanism was send query QTYPE CHAOS hostname.bind TXT
                and get server name. Proposal was to change bind to
                server. When documenting, people noticed problems.

                Some concern about namespace abuse as it's an entire
                TLD in class not used for a whole lot. Also
                implementation specific. Most serious drawback
                operationally, requires a separate query because it's
                not in-band with query that's being answered. Some
                consideration of DNSOP coming up with requirements so
                DNSEXT can go do something. Obvious requirement -
                needs to be in-band. Easy to configure, for dumb
                administrators. Interoperable. Not
                implementation-specific. Preferred if it doesn't
                commit namespace abuse. 02 submitted last week,
                documents this initial set of requirements. People
                have suggested, up to WG to decide, needs to be easily
                extensible. Able to support clients that might want
                to offer information. Should be difficult to disable,
                in interests of encouraging people to share info about
                their servers. Initial attempt at solution submitted
                as individual draft to dnsext, uses EDNS0/OPT
                pseudo-RR. There are some gaps, need to think about
                what we want to put in that field. Comments for this
                document, discuss here. Solution to be discussed in
                DNSEX. tomorrow. Anything on current requirements?
                If you have opinions, send them in.

Matt Larson:    draft-ietf-dnsop-bad-dns-res-02.txt 

                Let me say there's a problem with versioning.
                Submitted -03, came out as -02. No idea
                why. Submitting new version to address what comes out
                of this and subsequent ML discussion, so hopefully
                academic. 

                Can I ask who's read the draft. It's been out a
                couple of years. 

                Upshot: draft discusses 11 specific issues that cause
                varying amounts of problems with .com and .net. Not
                worth going over this in detail, but it all adds up to
                some number of extra useless queries that we see.
                What do we do next? 

                Should we modify protocol. A bunch of these have been
                fixed. There are some other things up here that I
                think are worth having. Some are crossing line from
                ops recommendation to something that should be
                codified in protocol. On authns side, if you leave
                off trailing '.' on NS record, authns server can
                figure it out, emit a warning. 0 TTL on NS records can
                have detrimental effect on your parent, so becomes
                philosophical question what an implementation should
                do. Anybody who operates name servers high up can
                feel pain of aggressive dynamic update clients. Ought
                to be two-step process, probe with NS-aware query and
                only then send update. One thing we see a lot of is
                queries for domain names that look a lot like IP
                addresses. 1.2.3.4 rather than ptr query. What do
                you do about that to remove that noise. One
                possibility: delegate all numeric TLDs to separate set
                of servers. That in a nutshell is the draft and its
                recommendations. Encourage folks to read it. Ask
                co-chairs for next steps.

Rob Austein:    Topical document, looking for WGLC soon. Suspect that
                the way to handle protocol changes are to write it as
                here are the operational problems we've seen, we think
                appropriate fix is this, but don't actually specify
                changes. We don't do that. 

Pekka Savola:   In a related similar subject when we forwarded
                something like this to IESG got feedback back that
                proposed fix, even though good idea, if it hadn't been
                taken up in protocol working group, there might be
                some pushback. 

Rob Austein:    We want to document the requirements. Don't care
                which working group. Ask the AD.

Matt Larson:    So take out recommendations?

Rob Austein:    Lots aren't protocol changes. Maybe one or two are. 

Olaf Kolkman:   If you have protocol recommendations put them in
                another I-D, submit to dnsext.

Matt Larson:    Appreciate comments from WG on things in the draft
                that rise to level of protocol changes.

Olaf Kolkman:   I don't see anything in there that goes beyond
                implementation guideline except for creation of new
                TLDs which is ICANN problem. So I don't think we are
                going to be upset if this goes forward. 

Rob Austein:    Path forward: a couple of people, I'll be one, should
                go through this, if we find stuff that's crossing
                line, discuss with chairs and AD. Don't want to lose
                any of these suggestions. 

Rob Austein:    Ready for WGLC. (lots of hands.)

Rob Austein:    Readers who think not ready for WGLC:

Jinmei Tatuya:  I basically have no objection to having WGLC, but want
                to make one comment, previously I made comment on the
                issuing of queries to name servers, got response from
                ???, have not responded to comment, (joseph?), because
                have not found enough time, but am willing to make
                response. Probably can just do that during WGLC. 

Rob Austein:    Yes, sounds fine.

Matt Larson:    Would like to push out quick revision, is that good?

Rob Austein:    Doesn't matter if it's before or after WGLC.

David Meyer:    On to key roll-over requirements.

Francis Dupont: Please read -00 draft, we will be doing 01 soon.
                There is still something unclear needed about
                emergency rollover. In case key known by too many
                persons. Section about it, perhaps you can review it,
                don't know exactly what to do. We know we need to do
                something fast to keep the chain of keys. We received
                no comment. As soon as there is no more issues or
                details to explain, etc, perhaps we can do a WGLC.

                Please help with MIP6 WG, trying to explain what
                DNSSEC is doing, asks for help to rewrite the DNSSEC
                subsection which I called . piece of DNSSEC bashing.
                Route Optimization Security Design Background
                document. Contact me or Gabriel Montenegro. 

Olaf Kolkman:   Haven't read in very long time, most people who were
                involved with DNSSEC have not done so. This very
                topic has been getting a lot of attention recently.
                We have had a few discussions on automatic key
                rollovers recently in DNSEXT. I will do it soon, ask
                others to do it as well.

G. Montenegro:  We have this document, it's a back grounder for MIPv6,
                we have a section on DNSSEC, really need some help
                from this WG. Either email me or Francis. 

Johan Ihrens:   Once upon a time I thought that rollover stuff will 
                certainly not require protocol changes and therefore
                DNSOPS would be place for discussions. However, it
                may well be that we end up with protocol changes which
                is why those other drafts on rollover are being bashed
                out in DNSEXT. My brain isn't large enough to cover
                this topic in two different WGs. Keep it all here or
                push it all into DNSEXT. Can't have requirements doc
                in one group and proposed in another.

Rob Austein:    We usually do.

Francis Dupont: For solutions, perhaps these are some already in
                DNSSEC. 

David Meyer:    So how many people have read this?

Rob Austein:    Not much of a showing. Of those who read it, how many 
                thing we need to work on this. Is this something WG
                don't want to work on, or something WG does want to
                work on? 

Russ Mundy:     Think that that's true. We need to read it, need to
                attack the operational requirements. Don't remember
                content anymore. 

Rob Austein:    We need to work on key rollover requirements. We
                don't know this is the right doc. First step is to
                read it. 

David Meyer:    Moving right along, increasing dns server.

Rob Austein:    Olaf just reminded me that we have another WG that
                could use some help. MARID. They're talking about
                using DNS to hold stuff dealing with whether or not to
                accept mail from SMTP senders. Very interesting and
                somewhat loud topic. Some have interesting ideas about
                DNS. They have another meeting. 

Schnitz:        In DNSOP, years ago, producing informational RFC
                addressing what the rest of IETF needs to know about
                the DNS. Abby offered copyright protection for using 
                parts of her book. Did anything come of that?

Olaf Kolkman:   Interesting. One issue I want you to address in
                testing - if there is any preference for any of the
                servers in the query pattern. Like, first one gets
                most. Biggest reason for deploying this not mentioned
                in draft. Glue for net zone requires thirteen
                signatures. We could shrink to five. Signatures are
                big. NS and A records are small. 

Yasuhiro Morishita: Is this a DNSSEC issue. I think that we need to
                testing in DNSSEC environment. 

Rob Austein:    Particular issue for signatures is whether this is a
                good idea or not. Number of RRsets matters.

Paul Vixie:     When we looked into doing this at the time that Bill
                Manning first proposed that we switch to
                root-servers.net, reason we did not go with smaller
                numbers of names has to do with the way the recursive
                and stub clients handle SRVFAIL. In event of SRVFAIL,
                no other address for that name server will be tried.
                Timeout will stimulate retry. We thought that it
                would be bad if there was no fallback in event that
                single server did not have zone loaded. So the two
                suggestions I have are first that some minimum number,
                like two or three names, be used, each with small
                number of records, and second that this be considered
                for TLDs but not roots at this time. 

Yasuhiro Morishita: Root and TLDs not be amended be applied.

Rob Austein:    Not done yet, right?

Yasuhiro Morishita: Right.

Rob Austein:    I assume folks think this is useful work, I certainly
                think so. Anyone else. That looks like good support.

David Meyer:    I looked at id-trackers, generated list of other
                drafts, this stuff is already at IESG. misbehavior
                and ipv6-dns-issues are at IESG but in ad followup.

Pekka Savola:   Been revised a couple of times since it went through
                IESG, some comments from Thomas Narten, would like to
                get feedback. Least important one is whether you
                believe there are some documents that should be
                normative references but are not. Second is whether
                we need to do extra. (loud feedback. So feedback
                would be appreciated. It has some connection to
                protocol work, so feedback. from there would be
                welcome. Last issue - split off some parts of
                document into separate documents. E.g. forward and
                reverse DNS updates. 

Rob Austein:    Have you sent list of questions. Might want to resend.

Jinmei Tatuya:  In my understanding authors can just wait for feedback
                from IESG. I would like to make sure that the authors
                there is nothing for them to do in ad-for-ops status.

David Meyer:    We have to look at if there are discuss comments
                against it, or you can look. We can show you how.

David Meyer:    ad-is-watching - second draft is expired. this is
                local-zones. So I'll talk to AD to see what gives. 

Rob Austein:    Paul, want to say anything about respsize doc?

Paul Vixie:     I know that one person actually read this and found
                clownish commentary I put in draft. Nobody flamed me.
                There is a very controversial comment in this draft. 

Peter Koch:     Have one question or remark. We had funny discussion
                about what is allowed length for domain name. 255,
                256, 253. It'. a bit late now to discuss this
                because this is very basic DNS stuff. Nothing to do
                with your draft, but obviously some basic questions
                yet unresolved. Anything we can do in this or another
                WG to resolve this? 

Paul Vixie:     It is certainly the case that in respsize draft I
                should not have mentioned any numbers because it's
                easy to look in other specs. Should just refer to
                standards. That's how I plan to fix the problem in mu
                small corner of ocean. In larger context, it would be
                interesting to see results of survey of what people
                think is max length of domain name on wire. but for
                myself would be more interested in seeing results than
                doing survey. 

Peter Koch:     So by deferring this somewhere else, I beg to differ
                you, you ignored the problem. So what can we do about
                that? Obviously there is one.

Paul Vixie:     I don't know that there really is one. May be sleeping
                dog. People don't design their businesses/projects
                around ability to use names > 250 chars. If you are
                interested in subject, you are speaking words that
                normally precede the statement "I volunteer." 

Peter Koch:     To volunteer is a transitive word in IETF. You are
                probably right, so may or may not be academic
                problem. In your draft, and in other docs, there are
                consequences out of max length. If there is corner
                case, the one single octet that is missing or not, I
                would like to have the discussion before hand, so we
                don't wind up where Mary did solving basic DNS
                problems in midst of IETF meeting. 

Paul Vixie:     Wasn't at Mary because of lack of strong wind. If
                someone is using query name that is really that long,
                difference will be there will be very few glue records
                in the delegation area. Seems unlikely that difference
                of opinion of one octet is going to change planning
                very much. The fact that someone can concoct an
                experiment where really long name breaks model,
                doesn't matter. When people are asking for names that
                really do exist, you care if they got enough glue. So
                for my part only thing that matters is that I take out
                the number and reference 1035. Until someone writes
                critique of 1035, that's good enough for me.

Olaf Kolkman:   Second argument for all you ever wanted to know about
                DNS but were afraid to ask, would be handy to have.

Paul Vixie:     In terms of process, I do not think this draft is
                ready to progress, because no-one complained. So until
                I have some feeling that someone other than me has
                seen this text, I will say it's not ready to go
                forward. 
 
Rob Austein:    So given that we had a number of people claiming this
                was important work, suggests that there is some work
                to be done in terms of reading doc that hasn't
                happened yet. You're all slackers. Go read the document!

David Meyer:    On to the Non-WG documents...

Pekka Savola:   There was one WG doc that has expired a long time ago
                which hasn't been discussed - don't publish
                unreachable draft. Should work on it or not?

Rob Austein:    The author has in fact said he has no time to work on
                it anymore. thought we had a volunteer, have to check
                notes, have not  made obvious progress on it. Do
                people still feel it's useful? Itojun wanted it. I
                dropped ball on this one, will consult notes. 

David Meyer:    So these were the other drafts that had expired. A
                couple of them have been updated since I made these
                slides. Not sure there's anything to say about them
                other than that they're expired, we've been through
                these a couple of times, wanted to know if anybody
                thought this was work that needs to be brought back or
                let it die (dynreverse, interim-signed) 

Tim Chown:      I think dynreverse is important.

Alain Durand:   Thank you for volunteering to work on it with me.

Rob Austein:    Protocol change?

Alain Durand:   Depends on what you call protocol.

Rob Austein:    Change to whole bunch of deployed code. Dubious about
                this one fitting here.

Alain Durand:   I don't care about this particular draft, way of
                solving problem, but do care to have one solution for
                what to do with reverse DNS. In v4 ISP used to do
                prepopulation, would like to see  solution. Don't care
                what it is. 

Tim Chown:      I'm not saying this document is the perfect way, but this
                is important topic.

Rob Austein:    You're volunteering.

David Meyer:    What I had on agenda next was IPv6 config opts. Would
                like to leave for last. Let's go on to Peter.

Peter Koch:     Would like to ask WG question regarding an idea. Using
                SRV records in DNS to do something that has nothing to
                do with DNS. At the moment we have four regional
                internet registries, you ask for IP addresses, receive
                some information, who to contact for that
                address. Which whois server do I query. Would like
                client to figure it out. 

                Suggestion on table - draft-sanz-whois-srv-01.txt.

Pekka Savola:   Can we assume that hte division between different
                registries will be forever on first byte boundary?

Audience:       no.

Pekka Savola:   Does it work if we can't assume that?

Peter Koch:     No we can't know forever, but where's the problem at
                the moment. Currently the RIRs receive more than /8
                worth of address space. If we have non-octet
                boundaries, could take it down the path, distributing
                it on the next level. 

Paul Vixie:     First, the SRV records in question would have to be at
                apexes of delegated part of tree, not in in-addr zone,
                because can't have anything at point above zone cut. A
                query for these would be referred to authority zone
                for these, which is actually a good thing. With regard
                to CIDR allocations, ipv6 tree, we really need to be
                looking at RFC 1101 as far as networking certainly the
                bind resolver has been able to look up RFC 1101 info -
                getnetbyaddr, this works even in case of RFC 2317 or
                other CIDR delegations. Unfortunate that it requires
                lookup of A record to find mask, but can be done. If
                you were to cast this in terms of additional data to
                go into RFC 1101 network naming schema, this would be a
                wonderful thing.

Peter Koch:     So you are saying that this is only useful in
                conjunction with RFC 1101?

Paul Vixie:     Yes. We have to be able to cover that whole area. This
                is an odd form of label stripping. May be a particular
                WHOIS server for 193.10. Start by looking at /32
                level, don't have to check every bit. RFC 1101 gives way
                to find netmask for closest enclosing network. This is
                a good idea, excellent convention, I know that it
                needs to be done in bottom up fashion rather than
                top-down fashion. This is a better solution, but
                requires RFC 1101. 

Peter Koch:     I again beg to differ. What I was afraid to suggest
                was as you suggested, there may be a more specific
                responsible whois server for /32. So sure you could do
                that, but don't see where RFC 1101 comes into the
				thing there. 

Paul Vixie:     RFC 1101 gives you way to discover that there is a /15
				or a /27 or something. 

Peter:          You still have the closest enclosing delegation on
                octet boundary.

Paul Vixie:     Most frequent use of this other than data mining and
                spamming is complaining about them, need to go to
                closest enclosing. 

Russ Mundy:     We're co-chairing a project that's been underway for
                short length of time that focuses on getting DNSSEC
                deployed. Trying to provide a structure/org that's a
                program office for facilitating things that need to
                happen for DNSSEC to get out there. Need to identify
                what needs to happen. Trying to collect peoples' views
                on what needs to happen. Steve has web site,
                dnssec-deployment.org. We look forward to having folks
                join in, provide criticism and information, working
                with everybody. 

Steve Crocker:  You covered it pretty well. I would emphasize is that
                focus is on post-ietf process. What do you do after
                specs are done. There's a host of little problems,
                chicken-and-egg. Who holds the root key. What if you
                ask for signed, get back unsigned. Verisign has
                created its own DNSSEC consortium. I imagine there
                will be  other specialized groups that focus on stuff.

David Meyer:    Pekka, come up please. We have three more agenda
                items. RIPE survey, DNSSEC, EPP if Scott is
                here. Brief review of DNS config options work.

Pekka Savola:   David Malone asked me to present this. IPv6
                lookups. This misbehavior towards certain kinds of
                queries, esp. IPv6 lookups. Took quite a bit of logs
                and found over 20k DNS servers, did a query looking up
                how many had AAAA records or how many had problems
                looking up them. Not sure if this shows, but the thing
                was that 0% have AAA records, 80% have misbehavior. 

                So there's a big problem for IPv6 hosts. Something
                needs to be done about it. What to do is good
                question. Should we set up  hall of shame?

Scott Hollenbeck: Author of EPP. Work of provreg WG. This doc is
                individual submission, tracking progress of EPP and 
                DNSSEC. (reads notes) 

Rob Austein:    The way Scott phrased it, I think interval is
                recommendation. 

Russ Mundy:     I'm not sure if it's a work item for this WG because
                it's part of a space that WG hasn't dealt with in the
                past. I think it's very important work that needs to
                be done whether part of this WG or not. 

Rob Austein:    I asked Scott to bring this here. This is not DNSEXT
                work because it's not DNS protocol. Not really EPP
                work. This is really about what does DNSSEC need. So
                this seems like the right place to come to get
                help. Don't care if WG adopts it. 

Ed Lewis:       Its a good thing to discuss here. One operator said
                would like to see registries (?) in  common. EPP is
                primarily used in one set of registries, but not all
                registries. Would be good forum for operators to say
                how all registries should treat ???

Scott Hollenbeck: Quick note to ML. Will do.

David Meyer:    DNS configuration options draft. Advisory doc to
                IESG. Wanted to see fi there were solid objections to
                what's in draft, if not, WGLC. Let me remind you of
                the three things. If you've been asleep for last
                couple of years, these are the three options. RA,
                DHCP, WKA. What we want is to move this doc through
                WGLC, get it to  informational, if you have any
                objections, sense that some issue that you have isn't
                covered, please speak up. 

Rob Austein:    Documenting state of inconclusive discussion we've had
                over and over again. If it covers all issues
                adequately, we are done. If there is something
                missing, tell us now.

David Meyer:    Should really get it to informational (after all, this
                is the third time draft has been written).

David Kessens:  Major issues only. No nit-picking please.

David Meyer:    Reminder: this is not a proposal - just documenting
                what has been proposed.

Erik Nordmark:  Seems to make some performance claims based on
                unstated assumptions. E.g. claims that RAs are
                better. Sending this stuff many times a day in case it
                changes. Seems like wasting bytes. Don't know what to
                do about performance claims. Seems to need a bit more
                rigor. 

Rob Austein:    Needs more eyes on that part of text. It's just bytes
                in a message that's going out anyway.

Erik Nordmark:  May be a lot more bytes.

Rob Austein:    Right, so we should back it up.

Jinmei Tatuya:  Not making objection, but my understanding there are
                several substantial comments on previous draft. There
                are significant  changes from previous version, should
                issue last call again. Make solid consensus. Not
                necessarily going to push this idea if you are
                particularly in hurry. 

Rob Austein:    We're in a hurry because in order to get this done we
                had a deadline. The AD can speak for self. AD will be
                cool with taking more time for WGLC if we're making
                serious progress by doing so. Don't want it to drag on
                forever. 

David Kessens:  I can go for it.

-----
AGENDA

 o Administriva                      2 minutes

   - Mailing list: majordomo@lists.uoregon.edu
     subscribe dnsop

   - Scribe?

   - Blue Sheets

 o Agenda Bashing                    5 minutes
   Meyer                                           

 o Review and status of work items           55 minutes

   Active Drafts
   -------------
   draft-ietf-dnsop-dnssec-operational-practices-01.txt   5 minutes
    Kolkman et al
   draft-ietf-dnsop-inaddr-required-05.txt                5 minutes
     Senie
   draft-ietf-dnsop-ipv6-dns-issues-07.txt                2 minutes
    Durand, et al 
    IESG Evaluation::Revised ID Needed (Informational)
   draft-ietf-dnsop-ipv6-transport-guidelines-02.txt      2 minutes
    Durand, et al 
    RFC Ed Queue (BCP)
   draft-ietf-dnsop-key-rollover-requirements-00.txt      5 minutes
    Guette, et al
   draft-ietf-dnsop-misbehavior-against-aaaa-01.txt       2 minutes
    Morishita, et al.
    IESG Evaluation::AD Followup (Informational)
   draft-ietf-dnsop-ohta-shared-root-server-03.txt        1 minute
    Ohta
   draft-ietf-dnsop-serverid-02.txt                       2 minutes
    Woolf
   draft-ietf-dnsop-bad-dns-res-02.txt                   15 minutes
    Larson/Barber

   Expired WG documents
   ---------------------
   draft-ietf-dnsop-resolver-rollover-01.txt              2 minutes
    expired (Kolkman)

   AD is watching
   ---------------------
   draft-ietf-dnsop-respsize-01.txt                       5 minutes
    expired (Vixie/Kato)
   draft-kato-dnsop-local-zones-01.txt                    5 minutes
    expired/no WG document

   Non-WG Documents
   ------------------------
   draft-durand-dnsop-dynreverse-01.txt                   2 minutes
    expired
   draft-ihren-dnsop-interim-signed-root-02.txt           2 minutes
    expired
   draft-yasuhiro-dnsop-increasing-dns-server-01.txt      5 minutes
    expired

 o DNSSEC Deployment Activity                 5 minutes
   Steve Crocker/Russ Mundy

 o IPv6 DNS Configuration Options                        15 minutes

   draft-ietf-dnsop-ipv6-dns-configuration-01.txt
    Jeong, et al

 o RIPE survey                       10 minutes
   draft-ietf-dnsop-misbehavior-against-aaaa-01.txt
   http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-dns-malone.pdf
   Savola, et al.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Tue Aug 17 20:12:00 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24156
	for <dnsop-archive@lists.ietf.org>; Tue, 17 Aug 2004 20:11:59 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HLafFN021997;
	Tue, 17 Aug 2004 14:36:41 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7HLafVR021995;
	Tue, 17 Aug 2004 14:36:41 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7HLadsd021965
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Tue, 17 Aug 2004 14:36:40 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i7HLZljO032313
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 17 Aug 2004 17:35:57 -0400
Date: Tue, 17 Aug 2004 17:35:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: David Meyer <dmm@1-4-5.net>, <sra@isc.org>
cc: dnsop@lists.uoregon.edu, <ietf@ietf.org>
Subject: Re: [dnsop] draft DNSOP minutes (IETF 60)
In-Reply-To: <20040817042058.GA17957@1-4-5.net>
Message-ID: <Pine.LNX.4.44.0408171716550.31857-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Dean Anderson <dean@av8.com>

On Mon, 16 Aug 2004, David Meyer wrote:

> David Meyer:    inaddr-required draft, very little activity.
> 
> Rob Austein:    This one's come up before. One issue is that some
>                 people never get past draft filename. If you look at
>                 the title it doesn't match that. We have one extremely
>                 vocal opponent of this draft who tries very hard to
>                 trash the discussion of it - if he does that again we
>                 will kick him off the list. 

I presume this is directed at me, even though I'm not the only opponent of
this draft, nor even the only vocal opponent.  But before I assume this,
and renew complaints about inappropriate activity by Mr. Austein in
relation to keeping this draft alive despite lack of interest, and despite
numerous editing and factual errors in the draft, and complaints of his
inappropriate action against Av8 Internet and myself in refusing to accept
email from Av8 Internet, refusing not just me personally, but email from
all of Av8 Internet to his official IETF address sra@isc.org, and falsely
claiming that Av8 Internet's address hijacked.  There are legal
consequences for these abuses, and the IETF has been previously notified
of this.

In any case, neither I nor anyone else has "trashed discussion" of this
draft on the DNSOP list, nor would it be appropriate to kick any opponent
of this draft off the DNSOP list.  This threat is yet another in a series
of inappropriate actions by Mr. Austein in relation to this draft.  

The discussion by the opposition has centered around the false and
misleading statements in the draft describing the policies of other
organizations, and other errors.  Exposing those errors and
inconsistencies is not "trashing the discussion".

The title is misleading given the apparent contents of the draft, but that
is only because the draft is internally inconsistent between its early
paragraphs and its later paragraphs. These inconsistent statements were
added after the notion of making in-addr required was very widely rejected
by nearly all participants.  Despite the introductory paragraphs which
seem to say otherwise, the purpose of the authors in writing this draft is
to make in-addr required, and that proposal has been widely rejected,
despite Mr. Austein's efforts to keep the idea alive.


Dean Anderson
Av8 Internet, Inc


.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Wed Aug 18 11:11:56 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12211
	for <dnsop-archive@lists.ietf.org>; Wed, 18 Aug 2004 11:11:55 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7ICKYlK022363;
	Wed, 18 Aug 2004 05:20:34 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7ICKYVI022362;
	Wed, 18 Aug 2004 05:20:34 -0700 (PDT)
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7ICKWJR022349
	for <dnsop@lists.uoregon.edu>; Wed, 18 Aug 2004 05:20:33 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:fd93:fff3:7dbd:fb9f])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 8D7D115265; Wed, 18 Aug 2004 21:20:31 +0900 (JST)
Date: Wed, 18 Aug 2004 21:20:29 +0900
Message-ID: <y7vr7q4skmq.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: David Meyer <dmm@1-4-5.net>
Cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] FYI (xml2rfc update)
In-Reply-To: <20040817141654.GB23036@1-4-5.net>
References: <20040817141654.GB23036@1-4-5.net>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>

(Sorry for the off topic - I don't expect this will grow long)

>>>>> On Tue, 17 Aug 2004 07:16:54 -0700, 
>>>>> David Meyer <dmm@1-4-5.net> said:

>>> 1. v1.25 was released yesterday. numerous bug fixes, no new 
>>> functionality
>>> 
>>> http://xml.resource.org/

v1.25 produces yet another boilerplate:

   This document is an Internet-Draft and is subject to all provisions
   of section 3 of RFC 3667.  By submitting this Internet-Draft, each
   author represents that any applicable patent or other IPR claims of
   which he or she is aware have been or will be disclosed, and any of
   which he or she become aware will be disclosed, in accordance with
   RFC 3668.

which is quite different from the one specified in the I-D guidelines
page:
http://www.ietf.org/ietf/1id-guidelines.txt

Google took me to some links mentioning thv xml2rfc-v1.25 boilerplate,
but I could not be sure if this is an agreed statement.  Can someone
clarify the status on this?

Thanks,

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Wed Aug 18 20:01:52 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02244
	for <dnsop-archive@lists.ietf.org>; Wed, 18 Aug 2004 20:01:52 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7ILHL9i020748;
	Wed, 18 Aug 2004 14:17:21 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7ILHLbV020745;
	Wed, 18 Aug 2004 14:17:21 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7ILHJ7X020674
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Wed, 18 Aug 2004 14:17:20 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i7ILGgBO025999
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 18 Aug 2004 17:16:42 -0400
Date: Wed, 18 Aug 2004 17:16:42 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] draft DNSOP minutes (IETF 60)
Message-ID: <Pine.LNX.4.44.0408181706310.24908-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Dean Anderson <dean@av8.com>

Another fake bounce from Mr. Austein.

It was also pointed out that Mr. Austein also fails to disclose his
conflict of interest with Av8 Internet according to the ISOC Code of
Conduct: http://www.isoc.org/members/codeconduct.shtml

  8. In  the case of financial or material conflict between personal and 
  professional interests, or between two professional interests,
  declare this conflict to all interested parties and if appropriate 
  in public.

Given the other abuses, this is probably a nit.

Dean Anderson
Av8 Internet, Inc

---------- Forwarded message ----------
Date: Tue, 17 Aug 2004 17:36:40 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON@cirrus.av8.net>
To: dean@av8.com
Subject: Returned mail: see transcript for details

The original message was received at Tue, 17 Aug 2004 17:35:57 -0400
from cirrus.av8.net [130.105.36.66]

   ----- The following addresses had permanent fatal errors -----
<sra@isc.org>
    (reason: 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66)

   ----- Transcript of session follows -----
... while talking to mx-1.isc.org.:
>>> DATA
<<< 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66
550 5.1.1 <sra@isc.org>... User unknown
<<< 554 Error: no valid recipients


.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Thu Aug 26 02:54:27 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11567
	for <dnsop-archive@lists.ietf.org>; Thu, 26 Aug 2004 02:54:26 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7Q5rjG5016393;
	Wed, 25 Aug 2004 22:53:45 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7Q5rjv4016391;
	Wed, 25 Aug 2004 22:53:45 -0700 (PDT)
Received: from delta.noi.kre.to (203-69-237-46.HINET-IP.hinet.net [203.69.237.46])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7Q5rfqV016091
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Wed, 25 Aug 2004 22:53:44 -0700 (PDT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.noi.kre.to (8.12.9/8.11.6) with ESMTP id i7Q5kxx8007805;
	Thu, 26 Aug 2004 12:46:59 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Edward Lewis <edlewis@arin.net>
cc: Pekka Savola <pekkas@netcore.fi>, namedroppers@ops.ietf.org,
        dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface 
In-Reply-To: <a06020403bd2f4d764c4b@[192.168.1.100]> 
References: <a06020403bd2f4d764c4b@[192.168.1.100]>  <Pine.LNX.4.44.0407300030520.25726-100000@netcore.fi> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 26 Aug 2004 12:46:59 +0700
Message-ID: <1836.1093499219@munnari.OZ.AU>
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Robert Elz <kre@munnari.OZ.AU>

    Date:        Thu, 29 Jul 2004 21:15:36 -0400
    From:        Edward Lewis <edlewis@arin.net>
    Message-ID:  <a06020403bd2f4d764c4b@[192.168.1.100]>

Sorry I'm coming to this very very late, but I looked quite a bit ahead
in the list, and didn't see a reply like the one I'd like to make (though
I don't claim an exhaustive search - I still am > 200 messages behind).

  | At 0:42 +0300 7/30/04, Pekka Savola wrote:
  | >Rather, it's "the minimum how long the DNS server asserts that this
  | >address corresponding to the name I asked will be valid".
  | 
  | This is what I am afraid of. ;)

Pekka used the wrong word.   "valid" isn't what he really meant,
"consistent" was.

  | A DNS server makes no assurance of the accuracy, etc., of the data it 
  | serves.

This is all 100% irrelevant to the point at hand (though perhaps justified
by the use of the word "valid" in the earlier message).

What matters here is that if I get an answer with a TTL of N, I can
reasonably expect that the answer will be consistent for the next N
seconds - technically I can even demand it, but almost no DNS operators
bother to use the TTL correctly enough for that (neither do they mostly
care that for a period the end users are getting old answers).

An application that gets an answer that says TTL=N and queries again for
the same query within the next N seconds is just imposing needless work
on the network - whether anyone cares or not is a different question, most
people don't - but it is also imposing needless costs and delays on the
application, and an application that is aiming for snappy response is going
to want to minimise that.

Note that unless the application is bypassing DNS caching (and has a way
to achieve that reliably, in the presence of devices that redirect
packets aimed at certain ports to other than the address in the packet)
asking again within the TTL period is pointless - even if the auth server
has changed the data in the intervening period, the cache has no way to
know that, and is simply going to return the same answers again.

The TTL is just as vital a part of the DNS answer as the RDATA, and should
have always been exposed to the end applications - the only thing that
prevented that from happening was the way that the the API was shoe-horned
into the old gethostbyname() and struct hostinfo which fetched its data from
HOSTS.TXT (via /etc/hosts) and for which there was no TTL concept.  If
it hadn't been for that, the TTL would almost certainly have been exposed
from the beginning.   That it remains unexposed after we have invented new
APIs is a travesty.

  | Although DNS is quite capable of carrying changing information 
  | (thanks to dynamic update), I don't think any application would be 
  | wise to rely on polling DNS to discover changed data.

I disagree with that as well.   The DNS is how the clients find the
address to connect to.   If the server is supposed to be providing a
service for name N, and the DNS says that name N translates into address
X, then the server must answer to address X.   If the DNS changes the
address mapping from X to Y, then at that point, and only at that point,
the server needs to be listening on Y (doesn't hurt to have started
earlier, but achieves nothing very useful).

  | This entire thread is from my reacting to the desire to expose the 
  | TTL from the resolver to application.  My message is mostly one of 
  | concern - that applications need to understand what the TTL means.

Absolutely, I agree with that.   But it isn't that hard.

The problem with treating the DNS data as "timeless" as an earlier
message from you claimed, is that most people treat timeless as
meaning "eternal" or "forever" - where I suspect that you probably
really meant "no time values supplied".   Providing an explicit
time to live should at least get applications to stop treating the
data as if it came from /etc/hosts, and could really never change
(or not without a local human to cause it, who can also touch the
applications at the same time).

  | From my experience (going back in time), I'd try to avoid the TTL as 
  | a meaningful interface element - perhaps just from the principle of 
  | network layering.  If you view the application as a layer above DNS, 
  | then using DNS internal data (the TTL) is a "layering violation."

This is simply nonsense - both as a concept ("layering" applies to models,
which are anaylsis tools, and should be left to that realm) and in particular
in this case, the TTL is part of the answer - separated from the RDATA to make 
it easier for fairly dumb caches.

  | Remember - TTL's don't account for the rapidity of dynamic updates - 
  | and I think that's more important in the example you've described.

No, they don't - but nor do caches, unless the TTLs are set so as to
cause that to happen - and it is the caches that give the vast majority
of the answers, not the auth servers (auth servers spend most of their
effort giving negative answers, not positive ones).

kre

.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From owner-dnsop@lists.uoregon.edu  Thu Aug 26 13:47:49 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22900
	for <dnsop-archive@lists.ietf.org>; Thu, 26 Aug 2004 13:47:48 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7QGiRX8003078;
	Thu, 26 Aug 2004 09:44:27 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i7QGiRVD003072;
	Thu, 26 Aug 2004 09:44:27 -0700 (PDT)
Received: from mail.verisignlabs.com (cliffie.verisignlabs.com [65.201.175.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i7QGiPC1002491
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Thu, 26 Aug 2004 09:44:26 -0700 (PDT)
Received: from dul1shollenbl1 ([::ffff:216.168.239.87])
  (AUTH: LOGIN shollenb, SSL: TLSv1/SSLv3,128bits,RC4-MD5)
  by mail.verisignlabs.com with esmtp; Thu, 26 Aug 2004 12:44:19 -0400
  id 002F4048.412E1363.00006BDE
From: "Scott Hollenbeck" <sah@428cobrajet.net>
To: "'Samuel Weiler'" <weiler@tislabs.com>, dnsop@lists.uoregon.edu
Cc: sah@428cobrajet.net
Subject: RE: [dnsop] DNSSEC and EPP Review Request
Date: Thu, 26 Aug 2004 12:44:55 -0400
Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF02E0F82D@vsvapostal8.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
In-Reply-To: <Pine.GSO.4.55.0408261131300.27165@filbert>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by darkwing.uoregon.edu id i7QGiQC0003000
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Scott Hollenbeck" <sah@428cobrajet.net>
Content-Transfer-Encoding: 8bit

Thanks for the comments, Sam.  More below.

-Scott-

> -----Original Message-----
> From: Samuel Weiler [mailto:weiler@tislabs.com] 
> Sent: Thursday, August 26, 2004 11:34 AM
> To: dnsop@lists.uoregon.edu
> Cc: Scott Hollenbeck
> Subject: Re: [dnsop] DNSSEC and EPP Review Request
> 
> 
> Comments on draft-hollenbeck-epp-secdns-03.txt:
> 
> Perhaps I'm missing something, but Section 2.2 and Section 7 (security
> considerations) both refer to sending signatures, presumably over EPP,
> yet I see no mention of those data elements in the schema.  Which is
> correct?  I suspect it's sufficient to say "you need to authenticate
> this somehow", which section 7 does.

Section 4, this element:

<element name="sigVal" type="secDNS:keySigType"/>

> In section 3.1.2, the nxt attribute implies the use of opt-in.  This
> should probably be removed or discussed only as a "future extension"
> bit.  Also s/NXT/NSEC/.

Thanks for catching this.  It's an artifact of older thinking.

> There are elements for start/end dates on publication, but nothing for
> sig lifetime.  It may be useful for a client to be able to request a
> sig lifetime much shorter than the EXPECTED key publication interval.
> If the start/end dates are meant to be that, this needs to be
> clarified.

OK, what's really useful from a deployment perspective?  Are the start-end
dates good enough, or is something else needed?  What are the implications
of the sig lifetime and start-end dates being different?  I'm open to ideas.

> The startDate/endDate elements appear to be part of dsData but not key
> (they're in keyData, but not key).  The rem element requires either a
> key or dsData.  Hence, rem'ing a dsData appears to require sending
> those dates.  It may not be wise to require the registrar to remember
> what start/end dates it (or another registrar) originally requested in
> order to remove a DS record.

Clients don't have to remember the dates.  They can be retrieved via an
<info> query.  The text makes that clear, but I suppose the example could be
better.

> Also: can you remove something created
> as keyData by removing dsData? Or the other way around?  I'm surprised
> that rem requires recitation of the entire old dsData when chg does
> not.

Nope, there's a one-for-one relationship.

> Formats of data: the date field formats aren't specified.  For other
> fields, refer specificallly to the "presentation formats" in 2535 (and
> successor docs).  Consider whether you need any further escaping or
> other encoding for each field.

Date field formats are specified in the schema using the XML Schema
"dateTime" data type.  Other field formats *are* referenced to
draft-ietf-dnsext-dnssec-records.  Did I miss something somewhere?

> Update the doc to reference DNSSECbis.

Where (section 1 maybe?) and in what context?  There is no outdated
reference to replace.

-Scott-


.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html


From ebenezeressoka44@handbag.com  Tue Aug 31 23:25:29 2004
Received: from mk-smarthost-4.mail.uk.tiscali.com (mk-smarthost-4.mail.uk.tiscali.com [212.74.114.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27783
	for <dnsop-archive@lists.ietf.org>; Tue, 31 Aug 2004 23:25:28 -0400 (EDT)
From: ebenezeressoka44@handbag.com
Received: from mk-cpfront-3.mail.uk.tiscali.com ([212.74.114.5]:33661 helo=mk-cpfrontend.uk.tiscali.com)
	by mk-smarthost-4.mail.uk.tiscali.com with esmtp (Exim 4.30)
	id 1C2Ljz-000P5c-Q0; Wed, 01 Sep 2004 04:24:55 +0100
Received: from [216.139.170.170] by mk-cpfrontend.uk.tiscali.com with HTTP; Wed, 1 Sep 2004 04:24:54 +0100
Date: Wed, 1 Sep 2004 10:24:54 +0700
Message-ID: <4124B98A0006A9C8@mk-cpfrontend-3.mail.uk.tiscali.com>
Subject: Banque Internationale pour le Commerce et
To: ebenezeressoka44@handbag.com
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Banque Internationale pour le Commerce et
l'Industrie de la C=F4te d'Ivoire
01 BP 1398 ABIDJAN 01.
Dear Sir,
We want to transfer to overseas (+ACQ-
52,000.000.00euro) Fifty two million Euro only) from a
Bank in Africa, I want to ask you to quietly look for
a reliable and honest person who will be capable and
fit to provide either an existing bank account or to
set up a new Bank a/c immediately to receive this
money, even an empty a/c can serve to receive this
money, as long as you will remain honest to me till
the end for this important  business trusting in you
and believing in God that  you will never let me down
either now or in future.
I am Dr.Ebenezer Essoka the Auditor General of a
bank in Africa, during the course of our auditing, I
discovered a floating fund in an account opened in
the bank in 1999 and since 2002 nobody has operated
on this account again, after going through some old
files in the records I discovered that the owner of
the account died without a +AFs-heir+AF0- hence the
money is floating and if I do not remit this money out
urgently it will be forfeited for nothing.
The owner of this account is Micheal Brown, a
foreigner, and an Industrialist, who died since 2000
and no other person knows about this account or
anything
concerning it, the account has no other beneficiary
and my investigation proved to me as well that
Micheal Brown until his death was the manager
of Brown Coy.(pty). CI.
We will start the first transfer with two million
+AFsAJA-2,000.000+AF0- upon successful transaction
without any disappointment from your side, we shall
re-apply for the payment of the remaining amount to
your account.
The amount involved is (52M euro) Fifty two million
euro only. I want to first transfer +ACQ-2,000.000
+AFs- two million euro from this money into a safe
foreigners account abroad before the rest, but I don't
know any foreigner, I am only contacting you as
a foreigner because this money can not be approved
to a local person here, without valid international
foreign passport, but can only be approved to a
foreigner with valid international passport or
drivers license and foreign a/c because the money is
in Euro currency and the former owner of the a/c Mr.
Micheal Brown is a foreigner too, +AFs-and the money
can
only be approved into a foreign a/c.
However, we will sign a binding agreement, to bind
us together. I got your contact address from my
Secretary who operates computer. I am revealing this
to you with believe in God that you will never let me
down in this business, you are the first and the only
person that I am contacting for this business, so
please reply urgently so that I will inform you on the
next step to take urgently. Send also your private
telephone and fax numbers including the full details
of the account to be used for the deposit.
I want us to meet face to face to build confidence
and to sign a binding agreement that will bind us
together before transferring the money to any
account of your choice where the fund will be safe
before we fly to your country for withdrawal, sharing
and investments.
I need your full co-operation to make this work
fine because the management is ready to approve this
payment to any foreigner who has correct information
of this account, which I will give to you, upon your
positive response and once I am convinced that you
are capable and will meet up with instructions of
a key bank official who is deeply involved with me in
this business.
I need your strong assurance that you will never,
never let me down.
With my influence and the position of the bank
official, we can transfer this
money to any foreigner's reliable account which you
can provide with assurance that this money will be
intact pending our physical arrival in your country
for sharing. The bank official will destroy all
documents of transaction immediately we receive this
money leaving no trace to any place and to build
confidence you can come immediately to discuss
with me face to face after which I will make this
remittance in your presence and three of us will fly
to your country at least two days ahead of the money
going into the account.
I will apply for annual leave to get visa
immediately I hear from you that you are ready to act
and receive this fund in your account. I will use my
position and influence to obtain all legal approvals
for onward transfer of this money to your account
with appropriate clearance from the relevant
ministries
and foreign exchange departments.
At the conclusion of this business, you will be
given 35+ACU- of the total amount, 60+ACU- will be for
me,
while 5+ACU- will be for expenses both parties might
have
incurred during the process of transferring.

I look forward to your earliest reply.ebenezeressoka2001@yahoo.com
Dr.Ebenezer Essoka




__________________________________________________________________
Get Tiscali Broadband From =A315:99
http://www.tiscali.co.uk/products/broadbandhome/





