From owner-dnsop@lists.uoregon.edu  Thu Jul  1 12:53:16 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 MAA16789
	for <dnsop-archive@lists.ietf.org>; Thu, 1 Jul 2004 12:53:16 -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 i61FbKa6001543;
	Thu, 1 Jul 2004 08:37:20 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i61FbKHD001541;
	Thu, 1 Jul 2004 08:37:20 -0700 (PDT)
Received: from web53907.mail.yahoo.com (web53907.mail.yahoo.com [206.190.36.217])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with SMTP id i61FbID8001454
	for <dnsop@lists.uoregon.edu>; Thu, 1 Jul 2004 08:37:18 -0700 (PDT)
Message-ID: <20040701153659.28277.qmail@web53907.mail.yahoo.com>
Received: from [211.33.115.226] by web53907.mail.yahoo.com via HTTP; Thu, 01 Jul 2004 08:36:58 PDT
Date: Thu, 1 Jul 2004 08:36:58 -0700 (PDT)
From: Jaehoon Jeong <jaehoon_paul@yahoo.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
To: dnsop@lists.uoregon.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Jaehoon Jeong <jaehoon_paul@yahoo.com>

Hi all,

First of all, I sincerely appreciate your contribution
to this draft.

I'd like to give you a revised version of "IPv6 Host
Configuration of DNS Server Information Approaches":

http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-02.txt

On this version, I think, I have reflected your
comments and suggestions. If there is anything
omitted, please let me know it. :-)

The noticeable changes are as follows:

1. For Normative Reference Problem, I have moved RA
option and Well-known anycast addresses approach
drafts into Informative References section.

2. I have unified Recursive DNS Server as RDNSS
instead of DNS server. In some cases, I let "DNS
server" be used for context.

If this version is ok to you, I'll submit it to IETF.

Thanks.

Paul

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
.
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  Fri Jul  2 14:55: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 OAA28507
	for <dnsop-archive@lists.ietf.org>; Fri, 2 Jul 2004 14:55:43 -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 i62H7sGL008221;
	Fri, 2 Jul 2004 10:07:54 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i62H7sY4008215;
	Fri, 2 Jul 2004 10:07:54 -0700 (PDT)
Received: from aptop.autonomica.net (as5-4-6.spa.s.bonet.se [217.215.75.155])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i62H7p61008127
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Fri, 2 Jul 2004 10:07:52 -0700 (PDT)
Received: from aptop.autonomica.net (localhost [127.0.0.1])
	by aptop.autonomica.net (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id i62H7p7P003831
	for <dnsop@lists.uoregon.edu>; Fri, 2 Jul 2004 19:07:52 +0200 (CEST)
To: dnsop@lists.uoregon.edu
Subject: [dnsop] Old dnsop@cafax.se now gone.
From: Lars-Johan Liman <liman@autonomica.se>
Date: 02 Jul 2004 19:07:51 +0200
Message-ID: <22n02itk0o.fsf@aptop.autonomica.net>
Lines: 11
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Lars-Johan Liman <liman@autonomica.se>

Per request from list members and the chairs, the forwarding mail
pointers at <dnsop@cafax.se> have been removed. Thus, the old mailing
list address does no longer work. This is yet another step to mitigate
the amount of spam that hits you.

Please use the new list address <dnsop@lists.uoregon.edu>, as the
majority of you, no doubt, alredy do.

				Cheers,
				  /Liman
                                  former DNSOP chair

.
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  Fri Jul  2 17:49: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 RAA08760
	for <dnsop-archive@lists.ietf.org>; Fri, 2 Jul 2004 17:49:30 -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 i62K86Y2014462;
	Fri, 2 Jul 2004 13:08:06 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i62K86il014459;
	Fri, 2 Jul 2004 13:08:06 -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 i62K85B7014452
	for <dnsop@lists.uoregon.edu>; Fri, 2 Jul 2004 13:08:06 -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 i62K84wt007051;
	Fri, 2 Jul 2004 13:08:04 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i62K84dx007050;
	Fri, 2 Jul 2004 13:08:04 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 2 Jul 2004 13:08:04 -0700
From: David Meyer <dmm@1-4-5.net>
To: Lars-Johan Liman <liman@autonomica.se>
Cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Old dnsop@cafax.se now gone.
Message-ID: <20040702200804.GA7029@1-4-5.net>
References: <22n02itk0o.fsf@aptop.autonomica.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <22n02itk0o.fsf@aptop.autonomica.net>
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>

	Lars-Johan,

On Fri, Jul 02, 2004 at 07:07:51PM +0200, Lars-Johan Liman wrote:
>> Per request from list members and the chairs, the forwarding mail
>> pointers at <dnsop@cafax.se> have been removed. Thus, the old mailing
>> list address does no longer work. This is yet another step to mitigate
>> the amount of spam that hits you.
>> 
>> Please use the new list address <dnsop@lists.uoregon.edu>, as the
>> majority of you, no doubt, alredy do.

	I'll just speak for the community at large and thank you
	for your expert stewardship of dnsop@cafax.se over the
	years. It is much appreciated.  

	Dave
.
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 Jul  6 09: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 JAA12404
	for <dnsop-archive@lists.ietf.org>; Tue, 6 Jul 2004 09:09:49 -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 i66BetaS011661;
	Tue, 6 Jul 2004 04:40:55 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i66BetnY011657;
	Tue, 6 Jul 2004 04:40:55 -0700 (PDT)
Received: from mail.enyo.de (mail.enyo.de [212.9.189.167])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i66Beqrt011368
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Tue, 6 Jul 2004 04:40:54 -0700 (PDT)
Received: (debugging) helo=deneb.enyo.de ip=212.9.189.171 name=deneb.enyo.de
Received: from deneb.enyo.de ([212.9.189.171])
	by mail.enyo.de with esmtp id 1BhoJd-00089P-Jr
	for dnsop@lists.uoregon.edu; Tue, 06 Jul 2004 13:40:49 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.34)
	id 1BhoJc-0001W4-9M
	for dnsop@lists.uoregon.edu; Tue, 06 Jul 2004 13:40:48 +0200
To: dnsop@lists.uoregon.edu
Subject: [dnsop] Session IDs in domain names
From: Florian Weimer <fw@deneb.enyo.de>
Date: Tue, 06 Jul 2004 13:40:48 +0200
Message-ID: <87u0wl8itb.fsf@deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Florian Weimer <fw@deneb.enyo.de>

A few services embed session IDs in domain names.  This has some
advantages for certain web-based applications (for example, URL
rewriting is not required to include a session ID in URLs if cookies
are turned off).  However, the drawbacks seem to be more severe: It's
not possible to protect the session IDs in domain names against
eavesdropping, and the RRs put an unnecessary burden on caching
resolvers.

Is there some kind of best practices document to discurage this
approach, or do you think the fact that this idea has been patented is
discouragement enough.
.
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 Jul  6 17:35: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 RAA25128
	for <dnsop-archive@lists.ietf.org>; Tue, 6 Jul 2004 17:35:35 -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 i66K8QkI017581;
	Tue, 6 Jul 2004 13:08:26 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i66K8Qg1017577;
	Tue, 6 Jul 2004 13:08:26 -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 i66K8PZL017496
	for <dnsop@lists.uoregon.edu>; Tue, 6 Jul 2004 13:08:25 -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 i66K8PgQ021746
	for <dnsop@lists.uoregon.edu>; Tue, 6 Jul 2004 13:08:25 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i66K8PR3021745
	for dnsop@lists.uoregon.edu; Tue, 6 Jul 2004 13:08:25 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 6 Jul 2004 13:08:25 -0700
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
Subject: [dnsop] Note to I-D authors/editors: cutoff dates; new I-D guidelines
Message-ID: <20040706200825.GE21691@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>

Here are the cut-off dates for the upcoming 60th IETF meeting:

  Mon Jul 12, 0900 EDT: cutoff for initial (-00) I-D submissions
  Mon Jul 19, 0900 EDT: final cutoff for I-D submission

In addition, please note that the I-D boilerplate was updated
recently.  In this context, the following recent announcement from the
IESG is helpful:

----------------------------------------------------------------------
The IESG has emitted new versions of the following guideline documents:

"Guidelines to authors of Internet-Drafts"
http://www.ietf.org/ietf/1id-guidelines.txt, which has been
updated to reflect the new IPR policy RFCs (3667 and 3668): Note
that in this process, we discovered a bug in one of the RFCs; the
documentc ontains a temporary fix, but the details of a permanent
fix are still being worked out on the IPR WG list. 

"Checklist for Internet-Drafts submitted for RFC publication"
http://www.ietf.org/ID-Checklist.html

This has had a more thorough review/revision, and should be
re-read by all participants. Note in particular the new language
about IANA considerations. 
----------------------------------------------------------------------

If you use the xml2rfc toolset from http://xml.resource.org, you
basically have to upgrade to the most recent version of the tool,
and use the right declarations to select the most suitable
variant of boilerplate.


Dave & Rob

[Note derived from the original from Simon Leinen <simon@limmat.switch.ch>]
.
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 Jul  6 17:53:13 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 RAA26443
	for <dnsop-archive@lists.ietf.org>; Tue, 6 Jul 2004 17:53:12 -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 i66KMbQS012284;
	Tue, 6 Jul 2004 13:22:37 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i66KMbaY012275;
	Tue, 6 Jul 2004 13:22:37 -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 i66KMabs012217
	for <dnsop@lists.uoregon.edu>; Tue, 6 Jul 2004 13:22:36 -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 i66KM5wB021839;
	Tue, 6 Jul 2004 13:22:05 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i66KM5ag021838;
	Tue, 6 Jul 2004 13:22:05 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 6 Jul 2004 13:22:05 -0700
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
Cc: agenda@ietf.org
Subject: [dnsop] draft DNSOP agenda for IETF 60 (San Diego)
Message-ID: <20040706202205.GB21774@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's the draft agenda (subject to change, of
	course). Please let us know if you have additions,
	deletions, and/or corrections. BTW, if it turns out that
	we are able to clear up the state of some of our
	documents before the meeting (specifically those
	currently being evaluated by the IESG), then we will drop
	them off the face to face agenda.  

	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>

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 minues
    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 mintes
    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-bad-dns-res-02.txt                   15 minutes
    Larson/Barber

   Expired WG documents
   ---------------------
   draft-ietf-dnsop-resolver-rollover-01.txt              2 minutes
    expired (Kolkman)
   draft-ietf-dnsop-serverid-02.txt                       2 minutes
    expired (Conrad/Suzanne Woolf)

   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      2 minutes
    expired

 o IPv6 DNS Configuration Options                        15 minutes

   draft-ietf-dnsop-ipv6-dns-configuration-01.txt
    Jeong, 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  Wed Jul  7 05:37: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 FAA06763
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 05:37: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 i678Hq5F004935;
	Wed, 7 Jul 2004 01:17:52 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i678HpwD004931;
	Wed, 7 Jul 2004 01:17:51 -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 i678HoVQ004814
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 01:17:50 -0700 (PDT)
Received: (qmail 45755 invoked from network); 7 Jul 2004 08:21:05 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 7 Jul 2004 08:21:05 -0000
Message-ID: <40EBB2F5.8060106@necom830.hpcl.titech.ac.jp>
Date: Wed, 07 Jul 2004 17:23:17 +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: Jaehoon Jeong <jaehoon_paul@yahoo.com>
CC: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information
 Approaches"
References: <20040701153659.28277.qmail@web53907.mail.yahoo.com>
In-Reply-To: <20040701153659.28277.qmail@web53907.mail.yahoo.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

Jaehoon Jeong;

Hi,

Attached is my suggestion of modification reflecting the fact that
ND runs poorly over WLAN.


						Masataka Ohta
--
In 3.1,

   Through ND protocol and RDNSS 
   option along with prefix information option, an IPv6 host can 
   perform its network configuration of its IPv6 address and RDNSS 
   simultaneously [3][4].  The RA option for RDNSS can be used on any 
+  network that supports the use of ND.  However, RA approach performs
+  poorly in some wireless environment where RA message is used for 
+  IPv6 address autoconfiguration, such as WLAN networks. 
 
+  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]. 


    
+  4) This mechanism does not work over a broad range of scenarios and 
+  leverages IPv6 ND.  It works well on links that support broadcast reliably 
+  (e.g., Ethernet LANs) but not necessarily on other links (e.g., wireless LANs).
+
   5) The RA approach could be used as a model for other similar types



3.1.3 Observations 
    
   The proposed RDNSS RA option along with IPv6 ND and Auto-
   configuration allows a host to obtain all of the information it 
   needs to access basic Internet services like the web, email, ftp, 
   etc.  This is preferable in environments where hosts use RAs to 
   autoconfigure their addresses and all hosts on the subnet share the
+  same router and server addresses.  It is preferable if the 
   configuration information can be obtained from a single mechanism, 
   it does not add additional delay, and it uses a minimum of 
+  bandwidth. Environments like this may include homes, public cellular
+  networks, and enterprise environments where 
+  no per host configuration is needed but excludes public WLAN hot spots, 


.
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 Jul  7 06:00:21 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 GAA07865
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 06:00:21 -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 i678ZSPM024411;
	Wed, 7 Jul 2004 01:35:28 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i678ZSDa024404;
	Wed, 7 Jul 2004 01:35:28 -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 i678ZQrN024067
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 01:35:26 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i678ZKX31907
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 11:35:21 +0300
Date: Wed, 7 Jul 2004 11:35:20 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information
 Approaches"
In-Reply-To: <20040616202111.GA13155@1-4-5.net>
Message-ID: <Pine.LNX.4.44.0407071133090.31622-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 Wed, 16 Jun 2004, David Meyer wrote:
> 	ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-configuration-01.txt
> 
> 	Please review the document carefully, and send your
> 	feedback to the list.  Please also indicate whether or
> 	not you believe that this document is ready to go to the
> 	IESG. Note that this is a somewhat unusal case as the
> 	IESG requested this document.

A few comments below.  In general, I think the document was pretty
good, and with some amount of tuning should be "good enough".

....

This approach has an issue that the DNS
   information needs to be configured in the routers doing the
   advertisements.  The configuration of DNS server address can be
   performed manually by operator or automatically DHCPv6 client
   running on the router.

==> as discussed separately, and commented by Ted Lemon on the list on Jun
22, configuring the DNS information may or may not be an issue.

RA approach is
   light-weight especially in wireless environment where RA message is
   used for IPv6 address autoconfiguration, such as cellular networks.

==> I recall Hesham Soliman saying on IPv6 WG list that the /64 is assigned
on a cellular node with the v6 PDP context activation?  That is, he argued
that there's no need for proxy-ND on the cellular node, as the /64 is
assigned independently.  The only way to interpret AFAICS is that ND is not
used for SLAAC on those hosts, or we were talking of different things.

   The RA approach is useful in environments where the addresses of
   the recursive DNS servers is 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 recursive server address [5].

==> This assumes, I think, that the ultimate RA option will include the
lifetime field, of course ;-).  Looking at it from the implementation
point-of-view, lifetime would seem to make matters a bit more complex. 
Instead of just writing resolv.conf (or equivalent) and being done, you'll
have to have a deamon around (or a program that's called at the defined
intervals) that keeps monitoring the lifetime of the servers all the time.  

I'm not saying that lifetime is bad, but it seem like a non-trivial
exercise, and to be more in line with the rest of the ND framework, it would
be better if it wasn't there. (typically, the IP addresses which do have
lifetime are handled quite a bit differently in the systems than DNS
servers..)

3.1.2 Disadvantages
                                                                                                                                        
   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 need kernel compilation.  DHCPv6, however, has
   more flexibility for extension of service discovery because it is
   an application layer protocol.

==> The kernel part extension has a (minor) point, but the compilation issue
doesn't seem too convincing to me.  However, this doesn't spell out IMHO the
real thing being in kernel causes.  I.e., writing and rewriting resolv.conf
from the kernel is probably unacceptable, and much easier if done by the
user-land process.  Of course, one approach to solve this is to have a
daemon listening to what the kernel conveys, and have the daemon do these
steps -- but such a daemon is not necessary with the current ND framework!

   3) DHCPv6 allows for the configuration of a host with information
   specific to that host, so that hosts on the same link can be
   configured with different DNS recursive name servers as well as
   other configuration information.  This capability is important in
   some network deployments such as service provider networks or WiFi
   hotspots.

==> how is this important e.g., on WiFi hotspots?  I'm not sure if I know
what kind of host-specific things you're referring to here, maybe elaborate
a bit ?

   5) Hosts in some environments are likely to need DHCPv6 for other
   configuration information.

==> this is a rather vague statement (and a strong one, when true) -- would
it make sense to try to clarify it a bit more? ("some environments" in
particular).

  7) Interoperability among independent implementations demonstrated
   at TAHI and Connectathon.

==> s/demonstrated/has been demonstrated/

   DNS clients have redundancy by having multiple resolvers that there
   should be multiple well-known anycast addresses configured on
   clients.

==> something missing before 'that' ?

4. Interworking among IPv6 DNS Configuration Approaches

==> this takes no stance on interworking/precedence when O bit is set, *and*
RA includes an RDNSS option ?

In
   order to fly anycast approach with the other solutions, there are
   three options.

==> should you try to summarize if any of these approaches is preferable, or
something?  Currently, you make no recommendations or provide any analysis
on which approach would be best?

5.1 ISP Network

==> you need to be clearer where whether you're talking about distributing
DNS information from the PE (or some other router) to the CPE, from CPE to
the customer, or what.  Also remember that there isn't necessarily a CPE
router in the network at all.. (dial-ups, bridge-mode xDSL, etc.).

5.1.1 RA Option Approach
                                                                                                                                        
   RA extension for recursive DNS server can be used to allow a host
   to get its recursive DNS server as well as IPv6 prefix at the same
   time through a new DNS option [5] within RA message when the host
   is attached to a new subnet.

==> are you making some assumption about prefix delegation (if prefix = /48)
or advertisement (if prefix = /64) here?  As it is, there is no adopted
mechanism to have RA provide the prefix at the same time (unless you meant a
/64 advertisement).

5.4.1 Case A: Gateway does not provide IPv6 at all

==> shouldn't this be mostly a non-op in this discussion?  I mean, if the
gateway doesn't provide v6, then some node inside the network must be
dual-stack to do tunneling.  If a node needs to be dual-stack, it can use
IPv4 DNS servers without problems.  Or are you concerned that in such a
network where v6 support is not provided there would be v6-only hosts in the
network?  In that case I guess you're down to the case where the customer
has a node which is set up as a dual-stack router.

5.4.2 Case B: A dual-stack gateway connected to a dual-stack ISP
                                                                                                                                        
   This is similar to a typical IPv4 home user scenario, where DNS
   configuration parameters are obtained using DHCP.  Except that
   Stateless DHCPv6 is used, as opposed to the IPv4 scenario where the
   DHCP server is stateful (maintains the state for clients).

==> again, are you talking of PE-CPE config or CPE-customer config?  Again,
do you assume /64 prefixes or how do you envision prefix delegation being
done?

5.4.3 Case C: A dual-stack gateway connected to an IPv4-only ISP
                                                                                                                                        
   This is similar to Case B.  The tunnel for IPv6 connectivity
   originates from the dual-stack gateway instead of the host.

==> did you mean similar to case A?

5.4.4 Case D: A gateway connected to an IPv6-only ISP
                                                                                                                                        
   This is similar to Case B.

==> not quite?  the gateway either has no v4 at all, and can't act as a "DNS
proxy", or it has a tunnel some other ISP else where it can send v4 packets.


-- 
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  Wed Jul  7 12:07: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 MAA27848
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 12:07: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 i67EfPuZ029288;
	Wed, 7 Jul 2004 07:41:25 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67EfPo3029282;
	Wed, 7 Jul 2004 07:41:25 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i67EfOXc028946
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 07:41:24 -0700 (PDT)
Received: from rtp-core-2.cisco.com (64.102.124.13)
  by rtp-iport-2.cisco.com with ESMTP; 07 Jul 2004 10:40:47 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i67EfG8p020845
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 10:41:17 -0400 (EDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.119])
	by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AJY46061;
	Wed, 7 Jul 2004 10:41:15 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 07 Jul 2004 10:41:13 -0400
To: dnsop@lists.uoregon.edu
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server
  Information Approaches" 
In-Reply-To: <200406301642.i5UGgpBT012421@rotala.raleigh.ibm.com>
References: <Message from sra@isc.org of "Thu, 24 Jun 2004 15:41:32 EDT." <20040624194217.C81F542B2@thrintun.hactrn.net>
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>

I agree with Thomas and Rob that "IPv6 Host Configuration of DNS Server
Information Approaches" should be published as an RFC so that the content of
the document is retained permanently.  I like Thomas' suggestion to
eliminate the dependency on publication of the specific drafts as RFCs by
including a summary description of the basic approach in those drafts and
recommend we make that change to "IPv6 Host Configuration of DNS Server
Information Approaches".

- Ralph

At 12:42 PM 6/30/2004 -0400, Thomas Narten wrote:
>FWIW, I largely agree with the points Rob made below.
>
>Also, on the topic of normative references, another aspect of the
>discussion is whether a reference is being provided, say "as an
>example" of one way one might do something, or whether it is being
>provided as _THE_ way of doing something. The former does not need to
>be a normatie reference, while the latter more likely is.
>
>I assume that some of the specific IDs being mentioned are really an
>example of one general way to do it, but not necessary the _only_
>way. Or the idea is so obvious, that a one-paragraph (or sentence?)
>description is enough for the reader to understand the basic approach
>(i.e, the type of understanding needed for this docuenmt). E.g., for
>something like "put the address of a DNS server into an RA", I doubt
>one needs to go and read a spec with the details to understand the
>general idea enough to talk about its pros and cons.
>
>So, to me, it's not at all clear that some of the related IDs need to
>be cited normatively.  Indeed, one woudl hope that this document is
>reasonably self-contained.
>
>Thomas
>
>Rob Austein <sra@isc.org> writes:
>
> > At Thu, 24 Jun 2004 07:50:44 -0700, David Meyer wrote:
> > >
> > > On Thu, Jun 24, 2004 at 03:10:29PM +0900, Masataka Ohta wrote:
> > > >> ...
> > > >> However, are there any possibility that the ID become an RFC?
> > > >>
> > > >> I think it does not have to be.
> > >
> > >     Seems to me that we should publish it as informational to
> > >     capture the work that has been done. In any event, we
> > >     should adhere to the publication standards.
>
> > Disclaimer: our area directors asked the WG to take this approach as a
> > way of wrapping up our work on this topic, and they can of course
> > speak for themselves.  The following is just my opinion based on my
> > understanding of their thinking.
>
> > I'm pretty sure that a large part of the point of the exercise is to
> > publish the document in permanent form.  We were not able to reach
> > consensus on a way forward, so we're trying to write down what we've
> > learned about each of the several options during the course of years
> > of nonterminating discussion, as fairly as possible given that we
> > don't have consensus on the right approach.
>
> > A well-written document of this type serves at least two purposes:
>
> > a) It's a briefing document for anybody (eg, the IESG) who might need
> >    to make informed decisions in this space at some time in the
> >    future.
>
> > b) It offers a relatively constructive way of breaking out of the
> >    endless discussion loop, by providing a relatively objective
> >    criterion by which we (or somebody) can determine whether a new
> >    discussion on this topic is genuinely new or is just the same old
> >    nonterminating discussion yet again.  In the latter case, a good
> >    document will at least allow us (or somebody) to cut to the chase
> >    and ask whether anything has changed since the last time around,
> >    rather than having to reevolve the whole line of argument, bring a
> >    new group of participants up to speed, and so forth.
>
> > One way of looking at this is that, when an argument can't be resolved
> > and the participants need to resign themselves to agreeing to
> > disagree, it is sometimes useful to spell out in some detail precisely
> > what it is on which they have agreed to disagree. :)
> > .
> > 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

.
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 Jul  7 13:01:53 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 NAA01104
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 13:01:53 -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 i67FMuNM020842;
	Wed, 7 Jul 2004 08:22:56 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67FMune020841;
	Wed, 7 Jul 2004 08:22:56 -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 i67FMtta020803
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 08:22:55 -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 i67FMt48003191
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 08:22:55 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i67FMt0F003190
	for dnsop@lists.uoregon.edu; Wed, 7 Jul 2004 08:22:55 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 7 Jul 2004 08:22:55 -0700
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
Subject: [dnsop] Internet-Draft Submission Cutoff Dates for the 60th IETF Meeting in San Diego, CA
Message-ID: <20040707152255.GC3166@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>

	In the event that you missed it....

>> ---------- Forwarded message ----------
>> Date: Tue, 06 Jul 2004 12:07:50 -0400
>> From: Internet-Drafts@ietf.org
>> To: ietf-announce@ietf.org
>> Subject: Internet-Draft Submission Cutoff Dates for the 60th IETF Meeting
>>     in San Diego, CA 
>> 
>> There are two (2) Internet-Draft cutoff dates for the 60th IETF Meeting 
>> in San Diego, CA:
>> 
>> July 12th: Cutoff Date for Initial Internet-Draft Submissions (new documents)
>> 
>> All initial Internet-Drafts (-00) and updates to initial Internet-Drafts must be 
>> submitted by Monday, July 12th, at 09:00 ET. As always, all initial submissions 
>> (-00) with a filename beginning with "draft-ietf" MUST be approved by the appropriate
>> WG Chair before they can be processed or announced. WG Chair approval MUST be 
>> received by Thursday, July 8th, at 09:00 ET.
>> 
>> July 19th: Cutoff Date for Revised Internet-Draft Submissions (-01 and higher)
>> 
>> All revised Internet-Drafts (-01 and higher) must be submitted by Monday, 
>> July 19th, at 09:00 ET.
>> 
>> Initial and revised Internet-Drafts received after their respective cutoff dates 
>> will NOT be made available in the Internet-Drafts directory OR announced, and will 
>> have to be resubmitted.  Please do NOT wait until the last minute to submit.  
>> The Secretariat will begin accepting Internet-Draft submissions starting Monday, 
>> August 9th.
>> 
>> Thank you for your understanding and cooperation. If you have any questions or 
>> concerns, then please send a message to internet-drafts@ietf.org.
>> 
>> FYI: The Internet-Draft cutoff dates as well as other significant dates for the 60th 
>> IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_60.html.
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf-announce
>> 
.
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 Jul  7 13:48: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 NAA03733
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 13:48: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 i67GAsFX001457;
	Wed, 7 Jul 2004 09:10:55 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67GAsLv001446;
	Wed, 7 Jul 2004 09:10:54 -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 i67GAsIN001369
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 09:10:54 -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 i67G985O003673;
	Wed, 7 Jul 2004 09:09:08 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i67G98Wk003672;
	Wed, 7 Jul 2004 09:09:08 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 7 Jul 2004 09:09:08 -0700
From: David Meyer <dmm@1-4-5.net>
To: Ralph Droms <rdroms@cisco.com>
Cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
Message-ID: <20040707160908.GA3599@1-4-5.net>
References: <20040624194217.C81F542B2@thrintun.hactrn.net> <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com>
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 Wed, Jul 07, 2004 at 10:41:13AM -0400, Ralph Droms wrote:
>> I agree with Thomas and Rob that "IPv6 Host Configuration of DNS Server
>> Information Approaches" should be published as an RFC so that the content of
>> the document is retained permanently.  I like Thomas' suggestion to
>> eliminate the dependency on publication of the specific drafts as RFCs by
>> including a summary description of the basic approach in those drafts and
>> recommend we make that change to "IPv6 Host Configuration of DNS Server
>> Information Approaches".

	For the most part, we can declare WG consensus on the
	publication issue (i.e., clearly we want to capture this
	work this time out). 

	Regarding logistics:

	The extended WCLC for this document ends today. What I
	would like the authors to do is as follows:

	(i).	Eliminate normative references as proposed by
		Thomas (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)

	(ii).	Address the comments from Ohta-san
		(http://www.uoregon.edu/~llynch/dnsop/msg02966.html)

	(iii).	Address the comments from Pekka
		(http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
	

	Once this is done, post a the -02 draft to the I-D
	repository and we'll send it on to our ADs.

	Thanks,

	Dave
.
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 Jul  7 14:11:21 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 OAA05184
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 14:11:20 -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 i67GfGjm008216;
	Wed, 7 Jul 2004 09:41:16 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67GfGjS008209;
	Wed, 7 Jul 2004 09:41:16 -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 i67GfGZs008146
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 09:41:16 -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 i67GeI1K004279;
	Wed, 7 Jul 2004 09:40:18 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i67GeIrj004278;
	Wed, 7 Jul 2004 09:40:18 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 7 Jul 2004 09:40:18 -0700
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
Cc: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
Message-ID: <20040707164018.GA4240@1-4-5.net>
References: <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com> <20040624194217.C81F542B2@thrintun.hactrn.net> <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com> <4.3.2.7.2.20040707121844.0293cd58@flask.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20040707121844.0293cd58@flask.cisco.com>
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 Wed, Jul 07, 2004 at 12:19:28PM -0400, Ralph Droms wrote:
>> Jinmei-san contributed some comments 
>> (http://www.uoregon.edu/~llynch/dnsop/msg02915.html) that I think the 
>> authors should address as well.

	Yes, thanks Ralph; sorry for overlooking that one; it
	should definitely be addressed. Authors, just to review
	the current list:

	(i).    Eliminate normative references as proposed by Thomas
		(http://www.uoregon.edu/~llynch/dnsop/msg02959.html)

	(ii).   Address the comments from Ohta-san
		(http://www.uoregon.edu/~llynch/dnsop/msg02966.html)

	(iii).	Address the comments from Pekka
		(http://www.uoregon.edu/~llynch/dnsop/msg02967.html)

	(iv).	Address the comments from Jinmei-san
		(http://www.uoregon.edu/~llynch/dnsop/msg02915.html)

	Thanks,

	Dave

>> 
>> - Ralph
>> 
>> At 09:09 AM 7/7/2004 -0700, David Meyer wrote:
>> >On Wed, Jul 07, 2004 at 10:41:13AM -0400, Ralph Droms wrote:
>> >>> I agree with Thomas and Rob that "IPv6 Host Configuration of DNS Server
>> >>> Information Approaches" should be published as an RFC so that the 
>> >content of
>> >>> the document is retained permanently.  I like Thomas' suggestion to
>> >>> eliminate the dependency on publication of the specific drafts as RFCs 
>> >by
>> >>> including a summary description of the basic approach in those drafts 
>> >and
>> >>> recommend we make that change to "IPv6 Host Configuration of DNS Server
>> >>> Information Approaches".
>> >
>> >        For the most part, we can declare WG consensus on the
>> >        publication issue (i.e., clearly we want to capture this
>> >        work this time out).
>> >
>> >        Regarding logistics:
>> >
>> >        The extended WCLC for this document ends today. What I
>> >        would like the authors to do is as follows:
>> >
>> >        (i).    Eliminate normative references as proposed by
>> >                Thomas (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
>> >
>> >        (ii).   Address the comments from Ohta-san
>> >                (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
>> >
>> >        (iii).  Address the comments from Pekka
>> >                (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
>> >
>> >
>> >        Once this is done, post a the -02 draft to the I-D
>> >        repository and we'll send it on to our ADs.
>> >
>> >        Thanks,
>> >
>> >        Dave
.
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 Jul  7 14:20: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 OAA05794
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 14:20: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 i67GJeUF008176;
	Wed, 7 Jul 2004 09:19:40 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67GJelA008173;
	Wed, 7 Jul 2004 09:19:40 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i67GJdcZ007778
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 09:19:39 -0700 (PDT)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 07 Jul 2004 09:20:03 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i67GJVSc012195;
	Wed, 7 Jul 2004 09:19:32 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.119])
	by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AJY55357;
	Wed, 7 Jul 2004 12:19:30 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040707121844.0293cd58@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 07 Jul 2004 12:19:28 -0400
To: David Meyer <dmm@1-4-5.net>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server
  Information Approaches"
Cc: dnsop@lists.uoregon.edu
In-Reply-To: <20040707160908.GA3599@1-4-5.net>
References: <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com>
 <20040624194217.C81F542B2@thrintun.hactrn.net>
 <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com>
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>

Jinmei-san contributed some comments 
(http://www.uoregon.edu/~llynch/dnsop/msg02915.html) that I think the 
authors should address as well.

- Ralph

At 09:09 AM 7/7/2004 -0700, David Meyer wrote:
>On Wed, Jul 07, 2004 at 10:41:13AM -0400, Ralph Droms wrote:
> >> I agree with Thomas and Rob that "IPv6 Host Configuration of DNS Server
> >> Information Approaches" should be published as an RFC so that the 
> content of
> >> the document is retained permanently.  I like Thomas' suggestion to
> >> eliminate the dependency on publication of the specific drafts as RFCs by
> >> including a summary description of the basic approach in those drafts and
> >> recommend we make that change to "IPv6 Host Configuration of DNS Server
> >> Information Approaches".
>
>         For the most part, we can declare WG consensus on the
>         publication issue (i.e., clearly we want to capture this
>         work this time out).
>
>         Regarding logistics:
>
>         The extended WCLC for this document ends today. What I
>         would like the authors to do is as follows:
>
>         (i).    Eliminate normative references as proposed by
>                 Thomas (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
>
>         (ii).   Address the comments from Ohta-san
>                 (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
>
>         (iii).  Address the comments from Pekka
>                 (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
>
>
>         Once this is done, post a the -02 draft to the I-D
>         repository and we'll send it on to our ADs.
>
>         Thanks,
>
>         Dave

.
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 Jul  7 14:34: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 OAA06563
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 14:34:18 -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 i67H7D2F013433;
	Wed, 7 Jul 2004 10:07:13 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67H7DZl013432;
	Wed, 7 Jul 2004 10:07:13 -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 i67H7BRD013329
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 10:07:11 -0700 (PDT)
Received: (qmail 48160 invoked from network); 7 Jul 2004 17:10:32 -0000
Received: from yahoobb219001188049.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.1.188.49)
  by necom830.hpcl.titech.ac.jp with SMTP; 7 Jul 2004 17:10:32 -0000
Message-ID: <40EC2F06.9060809@necom830.hpcl.titech.ac.jp>
Date: Thu, 08 Jul 2004 02:12:38 +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: David Meyer <dmm@1-4-5.net>
CC: dnsop@lists.uoregon.edu, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information
 Approaches"
References: <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com> <20040624194217.C81F542B2@thrintun.hactrn.net> <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com> <4.3.2.7.2.20040707121844.0293cd58@flask.cisco.com> <20040707164018.GA4240@1-4-5.net>
In-Reply-To: <20040707164018.GA4240@1-4-5.net>
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

David Meyer;

>>>Jinmei-san contributed some comments 
>>>(http://www.uoregon.edu/~llynch/dnsop/msg02915.html) that I think the 
>>>authors should address as well.

Can I interpret your statement that it includes follow-ups on
Jinmei-san's contribution should also be addressed?

							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  Wed Jul  7 14:42:59 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 OAA07135
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 14:42: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 i67HMc0N008272;
	Wed, 7 Jul 2004 10:22:38 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67HMc1c008271;
	Wed, 7 Jul 2004 10:22:38 -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 i67HMbfF008245
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 10:22:37 -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 i67HMX3s005121;
	Wed, 7 Jul 2004 10:22:33 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i67HMXTt005120;
	Wed, 7 Jul 2004 10:22:33 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 7 Jul 2004 10:22:33 -0700
From: David Meyer <dmm@1-4-5.net>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dnsop@lists.uoregon.edu, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
Message-ID: <20040707172233.GA5108@1-4-5.net>
References: <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com> <20040624194217.C81F542B2@thrintun.hactrn.net> <4.3.2.7.2.20040707103627.02836f10@flask.cisco.com> <4.3.2.7.2.20040707121844.0293cd58@flask.cisco.com> <20040707164018.GA4240@1-4-5.net> <40EC2F06.9060809@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40EC2F06.9060809@necom830.hpcl.titech.ac.jp>
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 Thu, Jul 08, 2004 at 02:12:38AM +0900, Masataka Ohta wrote:
>> David Meyer;
>> 
>> >>>Jinmei-san contributed some comments 
>> >>>(http://www.uoregon.edu/~llynch/dnsop/msg02915.html) that I think the 
>> >>>authors should address as well.
>> 
>> Can I interpret your statement that it includes follow-ups on
>> Jinmei-san's contribution should also be addressed?

Ohta-san,

Not exactly sure what you're referring to, but there are issues
in Jimnei-san's email that need to be addressed. Dave
.
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 Jul  7 15: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 PAA13630
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 15:47: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 i67IKJv0012369;
	Wed, 7 Jul 2004 11:20:19 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67IKIb5012363;
	Wed, 7 Jul 2004 11:20:18 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i67IKICB012061
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 11:20:18 -0700 (PDT)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 07 Jul 2004 11:20:43 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i67IKASc003229;
	Wed, 7 Jul 2004 11:20:11 -0700 (PDT)
Received: from satapati-u10.cisco.com (satapati-u10.cisco.com [128.107.162.133])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with ESMTP id AVD58889;
	Wed, 7 Jul 2004 11:19:00 -0700 (PDT)
Date: Wed, 7 Jul 2004 11:20:10 -0700 (PDT)
From: Suresh Satapati <satapati@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information
 Approaches"
In-Reply-To: <Pine.LNX.4.44.0407071133090.31622-100000@netcore.fi>
Message-ID: <Pine.GSO.4.58.0407071110510.10288@satapati-u10.cisco.com>
References: <Pine.LNX.4.44.0407071133090.31622-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Suresh Satapati <satapati@cisco.com>

Pekka,

> 5.4.1 Case A: Gateway does not provide IPv6 at all
>
> ==> shouldn't this be mostly a non-op in this discussion?  I mean, if the
> gateway doesn't provide v6, then some node inside the network must be
> dual-stack to do tunneling.  If a node needs to be dual-stack, it can use
> IPv4 DNS servers without problems.  Or are you concerned that in such a

In this document, we are interested in "IPv6" (but not IPv4) DNS Server
config approaches. I do agree with your statement that hosts can use
IPv4 DNS servers, but that isn't what we are concerened about here.

> network where v6 support is not provided there would be v6-only hosts in the
> network?  In that case I guess you're down to the case where the customer
> has a node which is set up as a dual-stack router.

Agreed. Which is why we'd need the config mechanism has to be some form
of a tunnel.

>
> 5.4.2 Case B: A dual-stack gateway connected to a dual-stack ISP
>
>    This is similar to a typical IPv4 home user scenario, where DNS
>    configuration parameters are obtained using DHCP.  Except that
>    Stateless DHCPv6 is used, as opposed to the IPv4 scenario where the
>    DHCP server is stateful (maintains the state for clients).
>
> ==> again, are you talking of PE-CPE config or CPE-customer config?  Again,
> do you assume /64 prefixes or how do you envision prefix delegation being
> done?

Is there a value in dissecting further ? I thought Stateless DHCPv6
spec does describe how to do this.

>
> 5.4.3 Case C: A dual-stack gateway connected to an IPv4-only ISP
>
>    This is similar to Case B.  The tunnel for IPv6 connectivity
>    originates from the dual-stack gateway instead of the host.
>
> ==> did you mean similar to case A?

I originally wrote 'case A'. I think Jeong changed it based on Christian's
comments. I have to go back and read what his comments were..

>
> 5.4.4 Case D: A gateway connected to an IPv6-only ISP
>
>    This is similar to Case B.
>
> ==> not quite?  the gateway either has no v4 at all, and can't act as a "DNS
> proxy", or it has a tunnel some other ISP else where it can send v4 packets.
>

Again, are we interested in IPv4 at all here ? If not, I dont think the
current text should change.


>
> --
> 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 Jul  7 18:56: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 SAA26073
	for <dnsop-archive@lists.ietf.org>; Wed, 7 Jul 2004 18:56: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 i67LDL1d000746;
	Wed, 7 Jul 2004 14:13:21 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i67LDLln000735;
	Wed, 7 Jul 2004 14:13:21 -0700 (PDT)
Received: from web53903.mail.yahoo.com (web53903.mail.yahoo.com [206.190.36.126])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with SMTP id i67LDKGc000204
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 14:13:20 -0700 (PDT)
Message-ID: <20040707211314.27506.qmail@web53903.mail.yahoo.com>
Received: from [211.33.115.164] by web53903.mail.yahoo.com via HTTP; Wed, 07 Jul 2004 14:13:14 PDT
Date: Wed, 7 Jul 2004 14:13:14 -0700 (PDT)
From: Jaehoon Jeong <jaehoon_paul@yahoo.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
To: David Meyer <dmm@1-4-5.net>
Cc: dnsop@lists.uoregon.edu
In-Reply-To: <20040707164018.GA4240@1-4-5.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Jaehoon Jeong <jaehoon_paul@yahoo.com>

Hi Dave,

As I sent an email last week, 
http://www.uoregon.edu/~llynch/dnsop/msg02960.html

I think that I solved (i) and (iv) comments in the new
version:

http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-02.txt

Therefore, I'll reflect (ii) and (iii) comments on our
02 version and submit it to IETF.
Could David and others check this?

Thanks.

Jaehoon Paul Jeong

--- David Meyer <dmm@1-4-5.net> wrote:
> On Wed, Jul 07, 2004 at 12:19:28PM -0400, Ralph
> Droms wrote:
> >> Jinmei-san contributed some comments 
> >>
> (http://www.uoregon.edu/~llynch/dnsop/msg02915.html)
> that I think the 
> >> authors should address as well.
> 
> 	Yes, thanks Ralph; sorry for overlooking that one;
> it
> 	should definitely be addressed. Authors, just to
> review
> 	the current list:
> 
> 	(i).    Eliminate normative references as proposed
> by Thomas
> 	
> (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
> 
> 	(ii).   Address the comments from Ohta-san
> 	
> (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
> 
> 	(iii).	Address the comments from Pekka
> 	
> (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
> 
> 	(iv).	Address the comments from Jinmei-san
> 	
> (http://www.uoregon.edu/~llynch/dnsop/msg02915.html)
> 
> 	Thanks,
> 
> 	Dave
> 
> >> 
> >> - Ralph
> >> 
> >> At 09:09 AM 7/7/2004 -0700, David Meyer wrote:
> >> >On Wed, Jul 07, 2004 at 10:41:13AM -0400, Ralph
> Droms wrote:
> >> >>> I agree with Thomas and Rob that "IPv6 Host
> Configuration of DNS Server
> >> >>> Information Approaches" should be published
> as an RFC so that the 
> >> >content of
> >> >>> the document is retained permanently.  I like
> Thomas' suggestion to
> >> >>> eliminate the dependency on publication of
> the specific drafts as RFCs 
> >> >by
> >> >>> including a summary description of the basic
> approach in those drafts 
> >> >and
> >> >>> recommend we make that change to "IPv6 Host
> Configuration of DNS Server
> >> >>> Information Approaches".
> >> >
> >> >        For the most part, we can declare WG
> consensus on the
> >> >        publication issue (i.e., clearly we want
> to capture this
> >> >        work this time out).
> >> >
> >> >        Regarding logistics:
> >> >
> >> >        The extended WCLC for this document ends
> today. What I
> >> >        would like the authors to do is as
> follows:
> >> >
> >> >        (i).    Eliminate normative references
> as proposed by
> >> >                Thomas
> (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
> >> >
> >> >        (ii).   Address the comments from
> Ohta-san
> >> >               
> (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
> >> >
> >> >        (iii).  Address the comments from Pekka
> >> >               
> (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
> >> >
> >> >
> >> >        Once this is done, post a the -02 draft
> to the I-D
> >> >        repository and we'll send it on to our
> ADs.
> >> >
> >> >        Thanks,
> >> >
> >> >        Dave
> .
> dnsop
>
resources:_____________________________________________________
> web user interface:
> http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive:
> http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
.
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 Jul  8 04:21:57 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 EAA06069
	for <dnsop-archive@lists.ietf.org>; Thu, 8 Jul 2004 04:21:56 -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 i686nhmR014944;
	Wed, 7 Jul 2004 23:49:43 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i686nhLi014943;
	Wed, 7 Jul 2004 23:49:43 -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 i686ngmv014907
	for <dnsop@lists.uoregon.edu>; Wed, 7 Jul 2004 23:49:42 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1048:200:39ff:fed7:e2e4])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 2AF8515263; Thu,  8 Jul 2004 15:49:41 +0900 (JST)
Date: Thu, 08 Jul 2004 15:49:39 +0900
Message-ID: <y7v1xjnyovw.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: Jaehoon Jeong <jaehoon_paul@yahoo.com>
Cc: David Meyer <dmm@1-4-5.net>, dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
In-Reply-To: <20040707211314.27506.qmail@web53903.mail.yahoo.com>
References: <20040707164018.GA4240@1-4-5.net>
	 <20040707211314.27506.qmail@web53903.mail.yahoo.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, 7 Jul 2004 14:13:14 -0700 (PDT), 
>>>>> Jaehoon Jeong <jaehoon_paul@yahoo.com> said:

> As I sent an email last week, 
> http://www.uoregon.edu/~llynch/dnsop/msg02960.html

> I think that I solved (i) and (iv) comments in the new
> version:

> http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-02.txt

> Therefore, I'll reflect (ii) and (iii) comments on our
> 02 version and submit it to IETF.
> Could David and others check this?

(Just to avoid a possible dead-lock)
I'm afraid I won't have enough time to review the pre-submit version
of the draft.  I'll check the submitted version to see if my comments
are properly addressed.

					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 Jul  8 07:06:45 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 HAA13148
	for <dnsop-archive@lists.ietf.org>; Thu, 8 Jul 2004 07:06: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 i688Bt6b005486;
	Thu, 8 Jul 2004 01:11:55 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i688BtJm005485;
	Thu, 8 Jul 2004 01:11:55 -0700 (PDT)
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i688BrHv005117
	for <dnsop@lists.uoregon.edu>; Thu, 8 Jul 2004 01:11:54 -0700 (PDT)
Received: from paul3 (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i688TwxB021434
	for <dnsop@lists.uoregon.edu>; Thu, 8 Jul 2004 17:29:58 +0900 (KST)
Message-ID: <008601c464c3$34b0aa50$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: <dnsop@lists.uoregon.edu>
References: <20040707211314.27506.qmail@web53903.mail.yahoo.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
Date: Thu, 8 Jul 2004 17:11:43 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by darkwing.uoregon.edu id i688BsHv005453
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Content-Transfer-Encoding: 8bit

Hi all,

I have reflected (ii) and (iii) on 02 version in addition to (i) and (iv).
You can find the new version in the following link:
http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-02.txt

If you have another comment or think there is still something resolved, let me know it. 
I'll submit it to the IETF secretariat next Monday.

Thanks.

Paul

----- Original Message ----- 
From: "Jaehoon Jeong" <jaehoon_paul@yahoo.com>
To: "David Meyer" <dmm@1-4-5.net>
Cc: <dnsop@lists.uoregon.edu>
Sent: Thursday, July 08, 2004 6:13 AM
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"


> 
> Hi Dave,
> 
> As I sent an email last week, 
> http://www.uoregon.edu/~llynch/dnsop/msg02960.html
> 
> I think that I solved (i) and (iv) comments in the new
> version:
> 
> http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-02.txt
> 
> Therefore, I'll reflect (ii) and (iii) comments on our
> 02 version and submit it to IETF.
> Could David and others check this?
> 
> Thanks.
> 
> Jaehoon Paul Jeong
> 
> --- David Meyer <dmm@1-4-5.net> wrote:
> > On Wed, Jul 07, 2004 at 12:19:28PM -0400, Ralph
> > Droms wrote:
> > >> Jinmei-san contributed some comments 
> > >>
> > (http://www.uoregon.edu/~llynch/dnsop/msg02915.html)
> > that I think the 
> > >> authors should address as well.
> > 
> > Yes, thanks Ralph; sorry for overlooking that one;
> > it
> > should definitely be addressed. Authors, just to
> > review
> > the current list:
> > 
> > (i).    Eliminate normative references as proposed
> > by Thomas
> > 
> > (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
> > 
> > (ii).   Address the comments from Ohta-san
> > 
> > (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
> > 
> > (iii). Address the comments from Pekka
> > 
> > (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
> > 
> > (iv). Address the comments from Jinmei-san
> > 
> > (http://www.uoregon.edu/~llynch/dnsop/msg02915.html)
> > 
> > Thanks,
> > 
> > Dave
> > 
> > >> 
> > >> - Ralph
> > >> 
> > >> At 09:09 AM 7/7/2004 -0700, David Meyer wrote:
> > >> >On Wed, Jul 07, 2004 at 10:41:13AM -0400, Ralph
> > Droms wrote:
> > >> >>> I agree with Thomas and Rob that "IPv6 Host
> > Configuration of DNS Server
> > >> >>> Information Approaches" should be published
> > as an RFC so that the 
> > >> >content of
> > >> >>> the document is retained permanently.  I like
> > Thomas' suggestion to
> > >> >>> eliminate the dependency on publication of
> > the specific drafts as RFCs 
> > >> >by
> > >> >>> including a summary description of the basic
> > approach in those drafts 
> > >> >and
> > >> >>> recommend we make that change to "IPv6 Host
> > Configuration of DNS Server
> > >> >>> Information Approaches".
> > >> >
> > >> >        For the most part, we can declare WG
> > consensus on the
> > >> >        publication issue (i.e., clearly we want
> > to capture this
> > >> >        work this time out).
> > >> >
> > >> >        Regarding logistics:
> > >> >
> > >> >        The extended WCLC for this document ends
> > today. What I
> > >> >        would like the authors to do is as
> > follows:
> > >> >
> > >> >        (i).    Eliminate normative references
> > as proposed by
> > >> >                Thomas
> > (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
> > >> >
> > >> >        (ii).   Address the comments from
> > Ohta-san
> > >> >               
> > (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
> > >> >
> > >> >        (iii).  Address the comments from Pekka
> > >> >               
> > (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
> > >> >
> > >> >
> > >> >        Once this is done, post a the -02 draft
> > to the I-D
> > >> >        repository and we'll send it on to our
> > ADs.
> > >> >
> > >> >        Thanks,
> > >> >
> > >> >        Dave
> > .
> > dnsop
> >
> resources:_____________________________________________________
> > web user interface:
> > http://darkwing.uoregon.edu/~llynch/dnsop.html
> > mhonarc archive:
> > http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> > 
> 
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
> http://promotions.yahoo.com/new_mail
> .
> 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 Jul  8 11:32:58 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 LAA02691
	for <dnsop-archive@lists.ietf.org>; Thu, 8 Jul 2004 11:32:57 -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 i68Dl3P7002248;
	Thu, 8 Jul 2004 06:47:03 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i68Dl3xo002247;
	Thu, 8 Jul 2004 06:47:03 -0700 (PDT)
Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i68Dl1qm002076
	for <dnsop@lists.uoregon.edu>; Thu, 8 Jul 2004 06:47:02 -0700 (PDT)
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i68Dl0nE015549
	for <dnsop@lists.uoregon.edu>; Thu, 8 Jul 2004 14:47:00 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id OAA08647
	for <dnsop@lists.uoregon.edu>; Thu, 8 Jul 2004 14:46:58 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i68Dkwx16467
	for dnsop@lists.uoregon.edu; Thu, 8 Jul 2004 14:46:58 +0100
Date: Thu, 8 Jul 2004 14:46:58 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
Message-ID: <20040708134658.GA5369@login.ecs.soton.ac.uk>
References: <Pine.LNX.4.44.0407071133090.31622-100000@netcore.fi> <Pine.GSO.4.58.0407071110510.10288@satapati-u10.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.58.0407071110510.10288@satapati-u10.cisco.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Tim Chown <tjc@ecs.soton.ac.uk>

On Wed, Jul 07, 2004 at 11:20:10AM -0700, Suresh Satapati wrote:
> Pekka,
> 
> > 5.4.1 Case A: Gateway does not provide IPv6 at all
> >
> > ==> shouldn't this be mostly a non-op in this discussion?  I mean, if the
> > gateway doesn't provide v6, then some node inside the network must be
> > dual-stack to do tunneling.  If a node needs to be dual-stack, it can use
> > IPv4 DNS servers without problems.  Or are you concerned that in such a
> 
> In this document, we are interested in "IPv6" (but not IPv4) DNS Server
> config approaches. I do agree with your statement that hosts can use
> IPv4 DNS servers, but that isn't what we are concerened about here.

Except that this whole IPv6 DNS discovery issue has slipped because people
have been relying on the crutch of IPv4 DNS transport.

Tim
.
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 Jul  8 13:10:42 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 NAA10112
	for <dnsop-archive@lists.ietf.org>; Thu, 8 Jul 2004 13:10: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 i68Fb3Bh008845;
	Thu, 8 Jul 2004 08:37:03 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i68Fb34Y008840;
	Thu, 8 Jul 2004 08:37:03 -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 i68Fb2FK008783
	for <dnsop@lists.uoregon.edu>; Thu, 8 Jul 2004 08:37:02 -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 i68FavqL020151;
	Thu, 8 Jul 2004 08:36:57 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i68FavFw020150;
	Thu, 8 Jul 2004 08:36:57 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 8 Jul 2004 08:36:57 -0700
From: David Meyer <dmm@1-4-5.net>
To: Jaehoon Paul Jeong <paul@etri.re.kr>
Cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
Message-ID: <20040708153657.GA20127@1-4-5.net>
References: <20040707211314.27506.qmail@web53903.mail.yahoo.com> <008601c464c3$34b0aa50$c470fe81@etri.re.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <008601c464c3$34b0aa50$c470fe81@etri.re.kr>
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>


	Thanks Paul,

	Dave


On Thu, Jul 08, 2004 at 05:11:43PM +0900, Jaehoon Paul Jeong wrote:
>> Hi all,
>> 
>> I have reflected (ii) and (iii) on 02 version in addition to (i) and (iv).
>> You can find the new version in the following link:
>> http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-02.txt
>> 
>> If you have another comment or think there is still something resolved, let me know it. 
>> I'll submit it to the IETF secretariat next Monday.
>> 
>> Thanks.
>> 
>> Paul
>> 
>> ----- Original Message ----- 
>> From: "Jaehoon Jeong" <jaehoon_paul@yahoo.com>
>> To: "David Meyer" <dmm@1-4-5.net>
>> Cc: <dnsop@lists.uoregon.edu>
>> Sent: Thursday, July 08, 2004 6:13 AM
>> Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information Approaches"
>> 
>> 
>> > 
>> > Hi Dave,
>> > 
>> > As I sent an email last week, 
>> > http://www.uoregon.edu/~llynch/dnsop/msg02960.html
>> > 
>> > I think that I solved (i) and (iv) comments in the new
>> > version:
>> > 
>> > http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf-dnsop-ipv6-dns-configuration-02.txt
>> > 
>> > Therefore, I'll reflect (ii) and (iii) comments on our
>> > 02 version and submit it to IETF.
>> > Could David and others check this?
>> > 
>> > Thanks.
>> > 
>> > Jaehoon Paul Jeong
>> > 
>> > --- David Meyer <dmm@1-4-5.net> wrote:
>> > > On Wed, Jul 07, 2004 at 12:19:28PM -0400, Ralph
>> > > Droms wrote:
>> > > >> Jinmei-san contributed some comments 
>> > > >>
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02915.html)
>> > > that I think the 
>> > > >> authors should address as well.
>> > > 
>> > > Yes, thanks Ralph; sorry for overlooking that one;
>> > > it
>> > > should definitely be addressed. Authors, just to
>> > > review
>> > > the current list:
>> > > 
>> > > (i).    Eliminate normative references as proposed
>> > > by Thomas
>> > > 
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
>> > > 
>> > > (ii).   Address the comments from Ohta-san
>> > > 
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
>> > > 
>> > > (iii). Address the comments from Pekka
>> > > 
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
>> > > 
>> > > (iv). Address the comments from Jinmei-san
>> > > 
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02915.html)
>> > > 
>> > > Thanks,
>> > > 
>> > > Dave
>> > > 
>> > > >> 
>> > > >> - Ralph
>> > > >> 
>> > > >> At 09:09 AM 7/7/2004 -0700, David Meyer wrote:
>> > > >> >On Wed, Jul 07, 2004 at 10:41:13AM -0400, Ralph
>> > > Droms wrote:
>> > > >> >>> I agree with Thomas and Rob that "IPv6 Host
>> > > Configuration of DNS Server
>> > > >> >>> Information Approaches" should be published
>> > > as an RFC so that the 
>> > > >> >content of
>> > > >> >>> the document is retained permanently.  I like
>> > > Thomas' suggestion to
>> > > >> >>> eliminate the dependency on publication of
>> > > the specific drafts as RFCs 
>> > > >> >by
>> > > >> >>> including a summary description of the basic
>> > > approach in those drafts 
>> > > >> >and
>> > > >> >>> recommend we make that change to "IPv6 Host
>> > > Configuration of DNS Server
>> > > >> >>> Information Approaches".
>> > > >> >
>> > > >> >        For the most part, we can declare WG
>> > > consensus on the
>> > > >> >        publication issue (i.e., clearly we want
>> > > to capture this
>> > > >> >        work this time out).
>> > > >> >
>> > > >> >        Regarding logistics:
>> > > >> >
>> > > >> >        The extended WCLC for this document ends
>> > > today. What I
>> > > >> >        would like the authors to do is as
>> > > follows:
>> > > >> >
>> > > >> >        (i).    Eliminate normative references
>> > > as proposed by
>> > > >> >                Thomas
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02959.html)
>> > > >> >
>> > > >> >        (ii).   Address the comments from
>> > > Ohta-san
>> > > >> >               
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02966.html)
>> > > >> >
>> > > >> >        (iii).  Address the comments from Pekka
>> > > >> >               
>> > > (http://www.uoregon.edu/~llynch/dnsop/msg02967.html)
>> > > >> >
>> > > >> >
>> > > >> >        Once this is done, post a the -02 draft
>> > > to the I-D
>> > > >> >        repository and we'll send it on to our
>> > > ADs.
>> > > >> >
>> > > >> >        Thanks,
>> > > >> >
>> > > >> >        Dave
>> > > .
>> > > dnsop
>> > >
>> > resources:_____________________________________________________
>> > > web user interface:
>> > > http://darkwing.uoregon.edu/~llynch/dnsop.html
>> > > mhonarc archive:
>> > > http://darkwing.uoregon.edu/~llynch/dnsop/index.html
>> > > 
>> > 
>> > 
>> > 
>> > 
>> > __________________________________
>> > Do you Yahoo!?
>> > Yahoo! Mail - 50x more storage than other providers!
>> > http://promotions.yahoo.com/new_mail
>> > .
>> > 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
.
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 Jul  8 16:25:25 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 QAA26232
	for <dnsop-archive@lists.ietf.org>; Thu, 8 Jul 2004 16:25:24 -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 i68IsXxn027438;
	Thu, 8 Jul 2004 11:54:33 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i68IsWUS027427;
	Thu, 8 Jul 2004 11:54:32 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i68IsWsI026985
	for <dnsop@lists.uoregon.edu>; Thu, 8 Jul 2004 11:54:32 -0700 (PDT)
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i68IdpZr015685;
	Thu, 8 Jul 2004 11:39:52 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.119])
	by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AJZ48046;
	Thu, 8 Jul 2004 14:39:50 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040708141203.028f0ee8@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 08 Jul 2004 14:39:47 -0400
To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server
  Information Approaches"
Cc: <dnsop@lists.uoregon.edu>
In-Reply-To: <008601c464c3$34b0aa50$c470fe81@etri.re.kr>
References: <20040707211314.27506.qmail@web53903.mail.yahoo.com>
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>

I have a couple of comments on the revised doc at
http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf
-dnsop-ipv6-dns-configuration-02.txt

1. Section 5.1 describes (implicitly) an ISP scenario in which the CPE is a
router and there is a customer network behind the CPE.  However, section
5.1.1 describes a scenario in which the CPE is a host that is directly
connected to the ISP network.  I found the jump between scenarios a little
confusing wihtout more warning that two scenarios were being described.  I
also was confused by the last paragraph in 5.1.1, which (I think) applies to
the CPE/host scenario and not the CPE/router scenario.  If others also find
the existing text less than clear, perhaps the following text would improve
the clarity:

   5.1 ISP Network

      A characteristic of ISP network is that multiple Customer
      Premises Equipment (CPE) devices are connected to IPv6 PE
      (Provider Edge) routers and each PE connects multiple CPE devices
      to the backbone network infrastructure [11].  The CPEs may be
      hosts or routers.

      In the case where the CPE is a router, there is a customer
      network that is connected to the ISP backbone through the CPE.
      Typically, each customer network gets a different IPv6 prefix
      from an IPv6 PE router, but the same RDNSS configuration will be
      distributed.

      This section discusses how the different approaches to
      distributing DNS information are compared in an ISP network.

   5.1.1 RA Option Approach

      When the CPE is a host, the RA option for RDNSS can be used to
      allow the CPE to get RDNSS information as well as /64 prefix
      information for SLAC at the same time when the host is attached
      to a new subnet [8]. Because an IPv6 host must receive at least
      one RA message for stateless address autoconfiguration and router
      configuration, the host could receive RDNSS configuration
      information in that RA without the overhead of an additional
      message exchange.

      When the CPE is a router, the CPE may accept the RDNSS
      information from the RA on the interface connected to the ISP,
      and copy that information into the RAs advertised in the customer
      network.

      This approach is more valuable in the mobile host scenario, in
      which the host must receive at least an RA message for detecting
      a new network, than in other scenarios generally although
      administrator should configure RDNSS information on the routers.
      Secure ND [12] can provide extended security when using RA
      message.

2. I doubt the configuration mechanism described in section 5.2.1 would be
used in practice and I think we should omit section 5.2.1.

3. Regarding section 5.3.1:

At 11:35 AM 7/7/2004 +0300, Pekka Savola wrote:
>RA approach is
>    light-weight especially in wireless environment where RA message is
>    used for IPv6 address autoconfiguration, such as cellular networks.
>
>==> I recall Hesham Soliman saying on IPv6 WG list that the /64 is assigned
>on a cellular node with the v6 PDP context activation?  That is, he argued
>that there's no need for proxy-ND on the cellular node, as the /64 is
>assigned independently.  The only way to interpret AFAICS is that ND is not
>used for SLAAC on those hosts, or we were talking of different things.

What is the current state of the use of ND/RA and SLAC in 3GPP in 3GPP, and
are there any planned extensions to use ND/RA and SLAC in the future?  If
ND/RA and SLAC are not currently used, some of the stated advantages of the
RA option approach should be reconsidered.  That is, if the use of the RA
option requires implementation and deployment of ND/RA where it is not
specified now in 3GPP, deployment of the RA option would seem to require
roughly the same amount of specification, implementation, deployment and
traffic overhead as the DHCPv6 option.

4. I don't think Jinmei-san's issues 6 and 13 from
http://www.uoregon.edu/~llynch/dnsop/msg02915.html were addressed.

- 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  Fri Jul  9 04:59:37 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 EAA12197
	for <dnsop-archive@lists.ietf.org>; Fri, 9 Jul 2004 04:59:37 -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 i6971pZc024873;
	Fri, 9 Jul 2004 00:01:51 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6971pBs024872;
	Fri, 9 Jul 2004 00:01:51 -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 i6971nTx024821
	for <dnsop@lists.uoregon.edu>; Fri, 9 Jul 2004 00:01:50 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6971WN11449;
	Fri, 9 Jul 2004 10:01:37 +0300
Date: Fri, 9 Jul 2004 10:01:32 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Rob Austein <sra@isc.org>
cc: dnsop@lists.uoregon.edu, <ph10@cam.ac.uk>
Subject: Re: [dnsop] draft-ietf-dnsop-dontpublish-unreachable-03.txt
In-Reply-To: <20040508025923.ECFDD42B2@thrintun.hactrn.net>
Message-ID: <Pine.LNX.4.44.0407090952590.9702-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>

Did anything come out of this?

I note that I-D.ietf-dnsop-dontpublish-unreachable has already been 
purged from Marshall's xml2rfc I-D database, and I'd have liked to 
reference it :)

On Fri, 7 May 2004, Rob Austein wrote:
> At Thu, 06 May 2004 17:26:34 +0900, Jun-ichiro itojun Hagino wrote:
> > 
> > 	could you tell me what happened to
> > 	draft-ietf-dnsop-dontpublish-unreachable-03.txt?  it has been expired
> > 	for some time now.  i think it is a good document...
> 
> I thought it was useful too.  If I recall the history of this one
> correctly, it was a WG document which a number of people liked, but
> the WG ratholed discussing how many angels can dance on the word
> "unreachable", why firewalls are an offense before God, Man, and Small
> Furry Creature From Alpha Centauri, and other nonterminating topics.
> The author, not being totally out of his mind, eventually found
> something more productive to do with his time.
> 
> This document is not on the WG's current charter, because the last
> time we asked for a volunteer, the silence was deafening.  Absent
> somebody willing to work on it, there is no point in asking our ADs to
> let us put it back on the charter.
> 
> So: who cares about bringing this one back enough to work on it?
> 
> Given what happened the last time that I foolishly asserted from
> memory that an author had given up on a DNSOP WG doc, let me phrase
> this as a two part question:
> 
> a) Is the author interested in bringing back this document?  If so, he
>    of course has dibs.
> 
> b) Otherwise, is there somebody else who would be interested in
>    picking up the pen?
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> 

-- 
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  Fri Jul  9 06:46: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 GAA16804
	for <dnsop-archive@lists.ietf.org>; Fri, 9 Jul 2004 06:46:10 -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 i698bpMb002367;
	Fri, 9 Jul 2004 01:37:51 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i698bpvW002366;
	Fri, 9 Jul 2004 01:37:51 -0700 (PDT)
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i698bnX5002322
	for <dnsop@lists.uoregon.edu>; Fri, 9 Jul 2004 01:37:50 -0700 (PDT)
Received: from paul3 (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i698tcxB005258;
	Fri, 9 Jul 2004 17:55:38 +0900 (KST)
Message-ID: <016501c4658f$f54f9a60$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: "Ralph Droms" <rdroms@cisco.com>, <juha.wiljakka@nokia.com>,
        <jinmei@isl.rdc.toshiba.co.jp>, <mohta@necom830.hpcl.titech.ac.jp>
Cc: <dnsop@lists.uoregon.edu>
References: <20040707211314.27506.qmail@web53903.mail.yahoo.com> <4.3.2.7.2.20040708141203.028f0ee8@flask.cisco.com>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server  Information Approaches"
Date: Fri, 9 Jul 2004 17:37:23 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by darkwing.uoregon.edu id i698bpX5002359
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Content-Transfer-Encoding: 8bit

Hi Ralph,

Your suggestion looks very good.
I need the help of several people:
Juha, Jinmei-san and Ohta-san.

----- Original Message ----- 
From: "Ralph Droms" <rdroms@cisco.com>
> 
> I have a couple of comments on the revised doc at
> http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-ietf
> -dnsop-ipv6-dns-configuration-02.txt
> 
> 1. Section 5.1 describes (implicitly) an ISP scenario in which the CPE is a
> router and there is a customer network behind the CPE.  However, section
> 5.1.1 describes a scenario in which the CPE is a host that is directly
> connected to the ISP network.  I found the jump between scenarios a little
> confusing wihtout more warning that two scenarios were being described.  I
> also was confused by the last paragraph in 5.1.1, which (I think) applies to
> the CPE/host scenario and not the CPE/router scenario.  If others also find
> the existing text less than clear, perhaps the following text would improve
> the clarity:
> 
>    5.1 ISP Network
> 
>       A characteristic of ISP network is that multiple Customer
>       Premises Equipment (CPE) devices are connected to IPv6 PE
>       (Provider Edge) routers and each PE connects multiple CPE devices
>       to the backbone network infrastructure [11].  The CPEs may be
>       hosts or routers.
> 
>       In the case where the CPE is a router, there is a customer
>       network that is connected to the ISP backbone through the CPE.
>       Typically, each customer network gets a different IPv6 prefix
>       from an IPv6 PE router, but the same RDNSS configuration will be
>       distributed.
> 
>       This section discusses how the different approaches to
>       distributing DNS information are compared in an ISP network.
> 
>    5.1.1 RA Option Approach
> 
>       When the CPE is a host, the RA option for RDNSS can be used to
>       allow the CPE to get RDNSS information as well as /64 prefix
>       information for SLAC at the same time when the host is attached
>       to a new subnet [8]. Because an IPv6 host must receive at least
>       one RA message for stateless address autoconfiguration and router
>       configuration, the host could receive RDNSS configuration
>       information in that RA without the overhead of an additional
>       message exchange.
> 
>       When the CPE is a router, the CPE may accept the RDNSS
>       information from the RA on the interface connected to the ISP,
>       and copy that information into the RAs advertised in the customer
>       network.
> 
>       This approach is more valuable in the mobile host scenario, in
>       which the host must receive at least an RA message for detecting
>       a new network, than in other scenarios generally although
>       administrator should configure RDNSS information on the routers.
>       Secure ND [12] can provide extended security when using RA
>       message.
> 

o Okay, I agree at the above text.
I have reflected this on our new version just now.

> 2. I doubt the configuration mechanism described in section 5.2.1 would be
> used in practice and I think we should omit section 5.2.1.
> 

o Okay, I'll omit subsection 5.2.1, which was written by myself, from our draft.

> 3. Regarding section 5.3.1:
> 
> At 11:35 AM 7/7/2004 +0300, Pekka Savola wrote:
> >RA approach is
> >    light-weight especially in wireless environment where RA message is
> >    used for IPv6 address autoconfiguration, such as cellular networks.
> >
> >==> I recall Hesham Soliman saying on IPv6 WG list that the /64 is assigned
> >on a cellular node with the v6 PDP context activation?  That is, he argued
> >that there's no need for proxy-ND on the cellular node, as the /64 is
> >assigned independently.  The only way to interpret AFAICS is that ND is not
> >used for SLAAC on those hosts, or we were talking of different things.
> 
> What is the current state of the use of ND/RA and SLAC in 3GPP in 3GPP, and
> are there any planned extensions to use ND/RA and SLAC in the future?  If
> ND/RA and SLAC are not currently used, some of the stated advantages of the
> RA option approach should be reconsidered.  That is, if the use of the RA
> option requires implementation and deployment of ND/RA where it is not
> specified now in 3GPP, deployment of the RA option would seem to require
> roughly the same amount of specification, implementation, deployment and
> traffic overhead as the DHCPv6 option.
> 

o About this, Juha seems to be able to suggest his opinion.

> 4. I don't think Jinmei-san's issues 6 and 13 from
> http://www.uoregon.edu/~llynch/dnsop/msg02915.html were addressed.
> 

o About issue 6 related to RA approach, I  took Jinmei's second suggestion.
I omitted a word "simple" from the RA text.
The modified text is as follows;
--------------------------------------------------------------------------------------
3.1.1  Advantages

The RA option for RDNSS has a number of advantages.  These include:

 1) The RA option is an extension of existing ND/Autoconfig  mechanisms [3][4].
    No new protocol mechanisms are needed for extending an ND implementation to
    support this option.

--------------------------------------------------------------------------------------

o About issue 13 related to WKA approach,
the reorganization of the text can be done by Ohta-san in order to harmonize with other approaches.

After I listen to others' text contribution or opinion, I'll reflect them on 02 version and submit it.

Thanks for your work in advance.

Paul

> - Ralph
> 
> .
> 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  Fri Jul  9 11:08: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 LAA04507
	for <dnsop-archive@lists.ietf.org>; Fri, 9 Jul 2004 11:08: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 i69DdERo010251;
	Fri, 9 Jul 2004 06:39:14 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i69DdEN9010250;
	Fri, 9 Jul 2004 06:39:14 -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 i69DdC3F010233
	for <dnsop@lists.uoregon.edu>; Fri, 9 Jul 2004 06:39:13 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:adbf:fe5a:f394:422f])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 4FD6F1525D; Fri,  9 Jul 2004 22:39:11 +0900 (JST)
Date: Fri, 09 Jul 2004 22:39:09 +0900
Message-ID: <y7vwu1d1erm.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Cc: "Ralph Droms" <rdroms@cisco.com>, <juha.wiljakka@nokia.com>,
        <mohta@necom830.hpcl.titech.ac.jp>, <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server  Information Approaches"
In-Reply-To: <016501c4658f$f54f9a60$c470fe81@etri.re.kr>
References: <20040707211314.27506.qmail@web53903.mail.yahoo.com>
	 <4.3.2.7.2.20040708141203.028f0ee8@flask.cisco.com>
	 <016501c4658f$f54f9a60$c470fe81@etri.re.kr>
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 Fri, 9 Jul 2004 17:37:23 +0900, 
>>>>> "Jaehoon Paul Jeong" <paul@etri.re.kr> said:

> Your suggestion looks very good.
> I need the help of several people:
> Juha, Jinmei-san and Ohta-san.

I'll try to find time to review it within 24 hours, but if I miss the
deadline, please just go ahead (though I reserve the right to make
comments later:-).

					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  Sat Jul 10 07:01: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 HAA06605
	for <dnsop-archive@lists.ietf.org>; Sat, 10 Jul 2004 07:01:10 -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 i6A935wx019614;
	Sat, 10 Jul 2004 02:03:05 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6A9351Y019613;
	Sat, 10 Jul 2004 02:03:05 -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 i6A933qF019598
	for <dnsop@lists.uoregon.edu>; Sat, 10 Jul 2004 02:03:04 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:790c:59a:9e43:39d4])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id AA9021525D; Sat, 10 Jul 2004 18:03:02 +0900 (JST)
Date: Sat, 10 Jul 2004 18:03:00 +0900
Message-ID: <y7vllhs1bgb.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Cc: "Ralph Droms" <rdroms@cisco.com>, <juha.wiljakka@nokia.com>,
        <mohta@necom830.hpcl.titech.ac.jp>, <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server  Information Approaches"
In-Reply-To: <016501c4658f$f54f9a60$c470fe81@etri.re.kr>
	 <4.3.2.7.2.20040622154928.0355a1f0@mailhost.iprg.nokia.com>
	 <008601c464c3$34b0aa50$c470fe81@etri.re.kr>
	 <y7vhdt4tan2.wl@ocean.jinmei.org>
References: <20040707211314.27506.qmail@web53903.mail.yahoo.com>
	 <4.3.2.7.2.20040708141203.028f0ee8@flask.cisco.com>
	 <016501c4658f$f54f9a60$c470fe81@etri.re.kr>
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 Fri, 9 Jul 2004 17:37:23 +0900, 
>>>>> "Jaehoon Paul Jeong" <paul@etri.re.kr> said:

> Your suggestion looks very good.
> I need the help of several people:
> Juha, Jinmei-san and Ohta-san.

I guess you need my help for the last one, so I'll concentrate on that
part.

>> 4. I don't think Jinmei-san's issues 6 and 13 from
>> http://www.uoregon.edu/~llynch/dnsop/msg02915.html were addressed.
>> 

> o About issue 6 related to RA approach, I  took Jinmei's second suggestion.
> I omitted a word "simple" from the RA text.
> The modified text is as follows;
> --------------------------------------------------------------------------------------
> 3.1.1  Advantages

> The RA option for RDNSS has a number of advantages.  These include:

>  1) The RA option is an extension of existing ND/Autoconfig  mechanisms [3][4].
>     No new protocol mechanisms are needed for extending an ND implementation to
>     support this option.

> --------------------------------------------------------------------------------------

This does not address the first part of my concern: the meaning of
"(no) new protocol mechanisms" is vague (and can be unfair).
According to the response from Bob (Hinden), it should mean:

> The intent of "no new protocol mechanisms" text was it was only necessary 
> to define a new option, not change the ND protocol.  Just the same as if 
> one was to define a new DHCP option, the protocol mechanisms of the DHCP do 
> not need to change.  Does that help?

(see also
http://darkwing.uoregon.edu/~llynch/dnsop/msg02952.html
as a reference)

With this clarification, the text should rather be:

  1) The RA option is an extension of existing ND/Autoconfig
     mechanisms [3][4], and does not require a change in the base ND
     protocol.

But we then need to face the fairness issue I pointed out.  This
"advantage" also applies to the other mechanisms.  Actually, we don't
even need any new options for the DHCPv6 and WKA approaches.  So, to
be fair, I'd recommend either

A: just remove this advantage because this property is common for all
   the approaches.  (I prefer this option)

or

B: make similar points for the other approaches as well.  For example,
   revise item 6 of Section 3.2.1

   from

   6) The specification for configuration of DNS recursive name 
   servers through DHCPv6 is available as an RFC. 

   to

   6) The specification for configuration of DNS recursive name 
   servers through DHCPv6 is available as an RFC.  No new protocol
   extensions such as new options are necessary.

> o About issue 13 related to WKA approach,
> the reorganization of the text can be done by Ohta-san in order to harmonize with other approaches.

I guess you requested Ohta-san's help here, but if I need to say
something as the one who made the original comment, I don't think this
is a show-stopper while the change would make the document more
reader-friendly.  In fact, I noted in my original comment that:

> 13. Section 3.3 (Well-known Anycast Addresses)

> Readers would expect the same organization for this section as that
> for Sections 3.1 and 3.2: general description, advantages,
> disadvantages, and observation.  It might be helpful for readers if
> Section 3.3 can use the same organization.

> (This is just a comment, and not a requirement for advancing the
> document)

					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  Mon Jul 12 04:58:01 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 EAA23727
	for <dnsop-archive@lists.ietf.org>; Mon, 12 Jul 2004 04:58:01 -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 i6C7HXIu022003;
	Mon, 12 Jul 2004 00:17:33 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6C7HXBw022002;
	Mon, 12 Jul 2004 00:17:33 -0700 (PDT)
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6C7HVOa021957
	for <dnsop@lists.uoregon.edu>; Mon, 12 Jul 2004 00:17:32 -0700 (PDT)
Received: from paul3 (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i6C7ZbxB006788;
	Mon, 12 Jul 2004 16:35:37 +0900 (KST)
Message-ID: <004501c467e0$460e6420$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: <jinmei@isl.rdc.toshiba.co.jp>
Cc: <mohta@necom830.hpcl.titech.ac.jp>, <dnsop@lists.uoregon.edu>
References: <20040707211314.27506.qmail@web53903.mail.yahoo.com> <4.3.2.7.2.20040708141203.028f0ee8@flask.cisco.com> <016501c4658f$f54f9a60$c470fe81@etri.re.kr> <y7vllhs1bgb.wl@ocean.jinmei.org>
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server  Information Approaches"
Date: Mon, 12 Jul 2004 16:17:21 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by darkwing.uoregon.edu id i6C7HWOa021995
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Content-Transfer-Encoding: 8bit

Hi Jinmei-san,
Look at the inlines.

----- Original Message ----- 
From: <JINMEI Tatuya>
Sent: Saturday, July 10, 2004 6:03 PM
>
> >>>>> On Fri, 9 Jul 2004 17:37:23 +0900, 
> >>>>> "Jaehoon Paul Jeong" <paul@etri.re.kr> said:
> 
> > Your suggestion looks very good.
> > I need the help of several people:
> > Juha, Jinmei-san and Ohta-san.
> 
> I guess you need my help for the last one, so I'll concentrate on that
> part.
> 
> >> 4. I don't think Jinmei-san's issues 6 and 13 from
> >> http://www.uoregon.edu/~llynch/dnsop/msg02915.html were addressed.
> >> 
> 
> > o About issue 6 related to RA approach, I  took Jinmei's second suggestion.
> > I omitted a word "simple" from the RA text.
> > The modified text is as follows;
> > --------------------------------------------------------------------------------------
> > 3.1.1  Advantages
> 
> > The RA option for RDNSS has a number of advantages.  These include:
> 
> >  1) The RA option is an extension of existing ND/Autoconfig  mechanisms [3][4].
> >     No new protocol mechanisms are needed for extending an ND implementation to
> >     support this option.
> 
> > --------------------------------------------------------------------------------------
> 
> This does not address the first part of my concern: the meaning of
> "(no) new protocol mechanisms" is vague (and can be unfair).
> According to the response from Bob (Hinden), it should mean:
> 
> > The intent of "no new protocol mechanisms" text was it was only necessary 
> > to define a new option, not change the ND protocol.  Just the same as if 
> > one was to define a new DHCP option, the protocol mechanisms of the DHCP do 
> > not need to change.  Does that help?
> 
> (see also
> http://darkwing.uoregon.edu/~llynch/dnsop/msg02952.html
> as a reference)
> 
> With this clarification, the text should rather be:
> 
>   1) The RA option is an extension of existing ND/Autoconfig
>      mechanisms [3][4], and does not require a change in the base ND
>      protocol.
> 
> But we then need to face the fairness issue I pointed out.  This
> "advantage" also applies to the other mechanisms.  Actually, we don't
> even need any new options for the DHCPv6 and WKA approaches.  So, to
> be fair, I'd recommend either
> 
> A: just remove this advantage because this property is common for all
>    the approaches.  (I prefer this option)
> 
> or
> 
> B: make similar points for the other approaches as well.  For example,
>    revise item 6 of Section 3.2.1
> 
>    from
> 
>    6) The specification for configuration of DNS recursive name 
>    servers through DHCPv6 is available as an RFC. 
> 
>    to
> 
>    6) The specification for configuration of DNS recursive name 
>    servers through DHCPv6 is available as an RFC.  No new protocol
>    extensions such as new options are necessary.
> 

The second alternative looks good because this feature is an advantage for each approach.
For the fairness, I'll include the feature in each approach's advantage.

> > o About issue 13 related to WKA approach,
> > the reorganization of the text can be done by Ohta-san in order to harmonize with other approaches.
> 
> I guess you requested Ohta-san's help here, but if I need to say
> something as the one who made the original comment, I don't think this
> is a show-stopper while the change would make the document more
> reader-friendly.  In fact, I noted in my original comment that:
> 

I expect Ohta-san to send his new text to me soon.
As soon as I receive it, I'll recompile our draft and submit it to the IETF secretariat.

Thanks again for your contribution.

Paul

> > 13. Section 3.3 (Well-known Anycast Addresses)
> 
> > Readers would expect the same organization for this section as that
> > for Sections 3.1 and 3.2: general description, advantages,
> > disadvantages, and observation.  It might be helpful for readers if
> > Section 3.3 can use the same organization.
> 
> > (This is just a comment, and not a requirement for advancing the
> > document)
> 
> 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
> 

.
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 Jul 14 09:01: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 JAA13763
	for <dnsop-archive@lists.ietf.org>; Wed, 14 Jul 2004 09:01: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 i6EA4wY0003471;
	Wed, 14 Jul 2004 03:04:58 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6EA4wQV003463;
	Wed, 14 Jul 2004 03:04: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 i6EA4o54002774
	for <dnsop@lists.uoregon.edu>; Wed, 14 Jul 2004 03:04:51 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6EA4iX30156;
	Wed, 14 Jul 2004 13:04:44 +0300
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
Message-ID: <Pine.LNX.4.44.0407141249240.26359-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>

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.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-08pre-diff.html
http://www.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-08pre.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


From owner-dnsop@lists.uoregon.edu  Wed Jul 14 10:33: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 KAA20534
	for <dnsop-archive@lists.ietf.org>; Wed, 14 Jul 2004 10:33:30 -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 i6EBtn95019467;
	Wed, 14 Jul 2004 04:55:49 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6EBtnxl019466;
	Wed, 14 Jul 2004 04:55:49 -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 i6EBtl29019116
	for <dnsop@lists.uoregon.edu>; Wed, 14 Jul 2004 04:55:48 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6EBtQV31650;
	Wed, 14 Jul 2004 14:55:26 +0300
Date: Wed, 14 Jul 2004 14:55:26 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Suresh Satapati <satapati@cisco.com>
cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] WGLC for "IPv6 Host Configuration of DNS Server Information
 Approaches"
In-Reply-To: <Pine.GSO.4.58.0407071110510.10288@satapati-u10.cisco.com>
Message-ID: <Pine.LNX.4.44.0407141447550.31540-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 Wed, 7 Jul 2004, Suresh Satapati wrote:
> > 5.4.1 Case A: Gateway does not provide IPv6 at all
> >
> > ==> shouldn't this be mostly a non-op in this discussion?  I mean, if the
> > gateway doesn't provide v6, then some node inside the network must be
> > dual-stack to do tunneling.  If a node needs to be dual-stack, it can use
> > IPv4 DNS servers without problems.  Or are you concerned that in such a
> 
> In this document, we are interested in "IPv6" (but not IPv4) DNS Server
> config approaches. I do agree with your statement that hosts can use
> IPv4 DNS servers, but that isn't what we are concerened about here.

OK, but..

> > network where v6 support is not provided there would be v6-only hosts in the
> > network?  In that case I guess you're down to the case where the customer
> > has a node which is set up as a dual-stack router.
> 
> Agreed. Which is why we'd need the config mechanism has to be some form
> of a tunnel.

.. this probably has an impact if you consider the mechanisms for 
configuring the CPE or the node acting as v6 CPE.

For those nodes inside the network .. there's probably little 
difference.

> > 5.4.2 Case B: A dual-stack gateway connected to a dual-stack ISP
> >
> >    This is similar to a typical IPv4 home user scenario, where DNS
> >    configuration parameters are obtained using DHCP.  Except that
> >    Stateless DHCPv6 is used, as opposed to the IPv4 scenario where the
> >    DHCP server is stateful (maintains the state for clients).
> >
> > ==> again, are you talking of PE-CPE config or CPE-customer config?  Again,
> > do you assume /64 prefixes or how do you envision prefix delegation being
> > done?
> 
> Is there a value in dissecting further ? I thought Stateless DHCPv6
> spec does describe how to do this.

The text above needs to be clearer whether you thought to apply 
stateless DHCPv6 to configure the parameters on the CPE, or to apply 
it to configure the parameters at the nodes in the network.

This also has a connection with prefix delegation (with DHCP), as it
requires full DHCP, not stateless.

> > 5.4.3 Case C: A dual-stack gateway connected to an IPv4-only ISP
> >
> >    This is similar to Case B.  The tunnel for IPv6 connectivity
> >    originates from the dual-stack gateway instead of the host.
> >
> > ==> did you mean similar to case A?
> 
> I originally wrote 'case A'. I think Jeong changed it based on Christian's
> comments. I have to go back and read what his comments were..

OK

> > 5.4.4 Case D: A gateway connected to an IPv6-only ISP
> >
> >    This is similar to Case B.
> >
> > ==> not quite?  the gateway either has no v4 at all, and can't act as a "DNS
> > proxy", or it has a tunnel some other ISP else where it can send v4 packets.
> 
> Again, are we interested in IPv4 at all here ? If not, I dont think the
> current text should change.

There is a difference if you consider how you would configure DNS
servers on the CPE.  If the CPE has v4 capability, you don't need to
(but you still can), as the CPE could act as a resolver.  If it
doesn't have v4 capability, it needs to be configured with an address
of a recursive resolver.

-- 
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  Wed Jul 14 13:18: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 NAA29902
	for <dnsop-archive@lists.ietf.org>; Wed, 14 Jul 2004 13:18: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 i6EE27kQ017298;
	Wed, 14 Jul 2004 07:02:07 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6EE27qj017292;
	Wed, 14 Jul 2004 07:02:07 -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 i6EE24YJ016841
	for <dnsop@lists.uoregon.edu>; Wed, 14 Jul 2004 07:02:04 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6EE1uM01168;
	Wed, 14 Jul 2004 17:01:57 +0300
Date: Wed, 14 Jul 2004 17:01:56 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@lists.uoregon.edu
cc: namedroppers@ops.ietf.org, <narten@us.ibm.com>
Subject: [dnsop] dnsop-ipv6-dns-issues: handling of additional data and TTL w/ caching
Message-ID: <Pine.LNX.4.44.0407141613360.32682-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>

Hi,

(also to dnsext WG)

Thomas Narten provided extensive feedback 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.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-08pre-diff.html
http://www.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-08pre.txt

but there are still a few where it might be useful to get feedback
from the WG(s).  Most of the discussion was on section 4.4 on the
handling of additional data -- a subject that was already discussed
briefly on the list around May 6, but did not have a clear conclusion
(thread below):

http://ops.ietf.org/lists/namedroppers/namedroppers.2004/msg00406.html 

I've tried to summarize the discussion below *)

Now, Thomas brought up a lot of the same issues at IESG evaluation, 
and I thought we should try again to see if there could be some 
consensus on how to move forward.

....

I think we have achieved at least the follows (please yell if not the 
case):

 a) If some critical additional data RRsets wouldn't fit, you set the 
TC bit even if some RRsets did fit.

 b) If some courtesy additional data RRsets wouldn't fit, you never
set the TC bit, but rather remove (at least some of) the courtesy
RRsets.

 c) DNS servers should implement sanity checks on the resulting glue,
e.g., to disable circular dependencies.  Then the responding servers
can use at-or-below-a-zone-cut criterion to determine whether the
additional data is critical or not.

Now, there are still (IMHO) many open issues:

 1) if some critical additional data RRsets would fit, but some 
wouldn't, and TC has to be set (see above), should one rather remove 
the additional data that did fit, keep it, or leave unspecified?

 2) if some courtesy additional data RRsets would fit, but some
wouldn't, and some will have to be removed from the response (no TC is
set, see above), what to do -- remove all courtesy RRsets, keep all
that fit, or leave unspecified?
 
 3) is it acceptable to use the transport used in the DNS query as a 
hint which records to keep if not removing all the RRsets, if:
   a) having to decide which critical additional data to keep, or
   b) having to decide which courtesy additional data to keep?

 4) (this issue was discussed in section 4.5) if one RRset has TTL of
100 seconds, and another the TTL of 300 seconds, what should the
caching server do after 100 seconds?  Keep returning just one RRset
when returning additional data, or discard the other RRset from the
cache?

 5) How do we move forward from here?  If we manage to get to some 
form of consensus, how do we record it:
   a) just in draft-ietf-dnsop-ipv6-dns-issues (note that it's 
      Informational category only!),
   b) a separate BCP or similar by DNSEXT WG(?), clarifying and giving 
      recommendations,
   c) something else, what?

Thoughts, opinions, etc.?  Fire away!

(I'm trying to submit a revised document prior to the cut-off in any 
case, no matter how this turns out..)

A few of my personal thoughts below the summary.

*) a summary attempt of the past discussion below.
======== 
Edward Lewis (on dnsop) thought that omitting vs including courtesy
additional data was a tradeoff at the server end (issue about handling
the new query vs potentially misleading the client), and that TC bit
should only be set if critical additional data was left behind.

Robert Elz thought that the servers could add also add full RRsets,
even if not all of them, if they want to.  Similarly, he would rather
return only part of the courtesy data than set the TC bit.  He was of
two minds about whether to set TC bit when all of courtesy additional
data won't fit (but slightly leaning on TC bit, except if some
additional data could fit and be included in a round-robin fashion);
Robert also called for measurements on this.

Paul Vixie thought that just simply setting TC bit if anything doesn't
fit is a good idea if we don't have measurements to justify another
kind of approach.

Matt Larson commented on the definition of glue; the responding server
can know whether the data is critical just by looking whether it's
at-or-below-a-zone-cut.  Masataka Ohta commented that this isn't
sufficient if e.g. "org" zone is served by an "edu" server and vice
versa.  Mark Andrews rebutted that we don't have to support all the
combinations if it makes managing the DNS impossible; DNS server
software have included checks to avoid circular dependencies.

Masataka Ohta also participated in the discussion, and Andreas
Gustafsson clarified Paul Vixie's comment.
=========

As for my personal take, if interested:

My argument is that it would be best to return everything, or as
little as possible.  Not whatever you think you feel like you want to
send.  The reasoning here is that that if the user/application is
interested in both A and AAAA records (this doesn't matter if (s)he's
only interested in one), the DNS should either try to ensure (as far
as possible) it's giving a full view, or just basically say to the
user, "query yourself what you want, here's the critical info you
need for those queries".

This is based on the assumption that if the DNS servers start
second-guessing what kind of information the end-user would prefer
(e.g., by looking at the transport used), it's likely going to go
wrong because the DNS server asking for the records from the
second-guessing DNS server is likely going to be acting as a recursive
resolver, and it doesn't really indicate *at all* which IP version the
application wants to prefer (or not), or which kind IP version is
available in the first place.

So, relating to the questions above:

1) not much preference here
2) remove all courtesy data
3) I'd rather not to look at the transport used, but 3.a) would be 
   acceptable, 3.b) not (per 2)
4) I'd prefer discarding all the RRsets from the cache when the one 
   with the shortest TTL one times out, this ensures an "everything or 
   nothing" approach.
5) A separate document might be good so that this doesn't get lost 
   within an Informational document.

-- 
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  Mon Jul 19 16:31:05 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 QAA23670
	for <dnsop-archive@lists.ietf.org>; Mon, 19 Jul 2004 16:31:04 -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 i6JJLHhO005237;
	Mon, 19 Jul 2004 12:21:18 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6JJLHHU005236;
	Mon, 19 Jul 2004 12:21:17 -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 i6JJLGil005115
	for <dnsop@lists.uoregon.edu>; Mon, 19 Jul 2004 12:21:16 -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 PAA18064;
	Mon, 19 Jul 2004 15:21:13 -0400 (EDT)
Message-Id: <200407191921.PAA18064@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-configuration-02.txt
Date: Mon, 19 Jul 2004 15:21:13 -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		: IPv6 Host Configuration of DNS Server Information Approaches
	Author(s)	: J. Jeong
	Filename	: draft-ietf-dnsop-ipv6-dns-configuration-02.txt
	Pages		: 24
	Date		: 2004-7-19
	
This document describes three approaches for IPv6 recursive DNS 
   server address configuration.  It details the operational 
   attributes of three solutions: RA option, DHCPv6 option, and Well-
   known anycast addresses for recursive DNS servers.  Additionally, 
   it suggests four deployment scenarios considering multi-solution 
   resolution.  Therefore, this document will give the audience a 
   guideline of IPv6 DNS configuration to select approaches suitable 
   for their host DNS configuration.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-configuration-02.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-configuration-02.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-configuration-02.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-7-19152221.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsop-ipv6-dns-configuration-02.txt

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

Content-Type: text/plain
Content-ID:	<2004-7-19152221.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 Jul 19 16:32: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 QAA23975
	for <dnsop-archive@lists.ietf.org>; Mon, 19 Jul 2004 16:31: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 i6JJLfWF006823;
	Mon, 19 Jul 2004 12:21:42 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6JJLf1J006808;
	Mon, 19 Jul 2004 12:21:41 -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 i6JJLeGo006722
	for <dnsop@lists.uoregon.edu>; Mon, 19 Jul 2004 12:21:40 -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 PAA18096;
	Mon, 19 Jul 2004 15:21:38 -0400 (EDT)
Message-Id: <200407191921.PAA18096@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-08.txt
Date: Mon, 19 Jul 2004 15:21:37 -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-08.txt
	Pages		: 30
	Date		: 2004-7-19
	
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-08.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-08.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-08.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-7-19152227.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID:	<2004-7-19152227.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 Jul 19 21:46:57 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 VAA20473
	for <dnsop-archive@lists.ietf.org>; Mon, 19 Jul 2004 21:46:57 -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 i6K0WxVQ027471;
	Mon, 19 Jul 2004 17:32:59 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6K0WxGh027467;
	Mon, 19 Jul 2004 17:32:59 -0700 (PDT)
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6K0WvId026876
	for <dnsop@lists.uoregon.edu>; Mon, 19 Jul 2004 17:32:58 -0700 (PDT)
Received: from paul3 (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i6K0p9xB006779
	for <dnsop@lists.uoregon.edu>; Tue, 20 Jul 2004 09:51:10 +0900 (KST)
Message-ID: <009a01c46df1$167c3040$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: <dnsop@lists.uoregon.edu>
Subject: [dnsop] Fw: Updated IPv6 WG Agenda
Date: Tue, 20 Jul 2004 09:32:49 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by darkwing.uoregon.edu id i6K0WxId027424
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Content-Transfer-Encoding: 8bit

FYI

In this 60th IETF meeting, there will be discussion on IPv6 DNS Configuration at IPv6 wg.

Paul

----- Original Message ----- 
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: "Brian Haberman" <brian@innovationslab.net>; <ipv6@ietf.org>
> Hi Brian,
> 
> For DNS configuration, there are some updates:
> draft-ietf-dnsop-ipv6-dns-configuration-01.txt --> draft-ietf-dnsop-ipv6-dns-configuration-02.txt
> 
> DNSOP wg will submit this revised draft to the IESG soon.
> 
> Especially, the draft of RA option for recursive DNS server has been updated:
> draft-ietf-dnsop-ipv6-dns-configuration-02.txt
> 
> These drafts will be announced by IETF soon.
> 
> I think that they can be used as base documents for our discussion.
> 
> Paul
> ------------------------------------------------------
> Jaehoon Paul Jeong (Research Engineer)
> TEL. +82-42-860-1664
> Mobile +82-16-711-1765
> 161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea
> NGI Standardization Research Team/PEC/ETRI
> Homepage: http://www.adhoc.6ants.net/~paul
> 
> ----- Original Message ----- 
> From: "Brian Haberman" <brian@innovationslab.net>
> >       * DNS configuration (RA option)         chairs          10 minutes
> >            - draft-ietf-dnsop-ipv6-dns-configuration-01.txt
> >            - Goal: Should the WG be doing something?
> 
> 


--------------------------------------------------------------------------------


> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

.
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 Jul 20 00:07:21 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 AAA29349
	for <dnsop-archive@lists.ietf.org>; Tue, 20 Jul 2004 00:07:21 -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 i6K2tTuP022183;
	Mon, 19 Jul 2004 19:55:29 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6K2tTfM022174;
	Mon, 19 Jul 2004 19:55: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 i6K2tRDt021535
	for <dnsop@lists.uoregon.edu>; Mon, 19 Jul 2004 19:55:28 -0700 (PDT)
Received: from rtp-core-2.cisco.com (64.102.124.13)
  by rtp-iport-1.cisco.com with ESMTP; 19 Jul 2004 23:00:08 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6K2tIP9010644;
	Mon, 19 Jul 2004 22:55:18 -0400 (EDT)
Received: from rdroms-w2k01.cisco.com (rtp-vpn2-188.cisco.com [10.82.240.188])
	by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AKF76803;
	Mon, 19 Jul 2004 22:55:18 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040719225417.02a6f8e8@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 19 Jul 2004 22:56:31 -0400
To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dnsop] Fw: Updated IPv6 WG Agenda
Cc: <dnsop@lists.uoregon.edu>, ipv6@ietf.org
In-Reply-To: <009a01c46df1$167c3040$c470fe81@etri.re.kr>
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>

What will be the topic of the discussion?

The draft we're preparing in dnsop 
(draft-ietf-dnsop-ipv6-dns-configuration-02.txt) is intended for the IESG, 
I think.  Is it premature to discuss anything in the ipv6 WG prior to the 
IESG evaluation?

- Ralph

At 09:32 AM 7/20/2004 +0900, Jaehoon Paul Jeong wrote:
>FYI
>
>In this 60th IETF meeting, there will be discussion on IPv6 DNS 
>Configuration at IPv6 wg.
>
>Paul
>
>----- Original Message -----
>From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
>To: "Brian Haberman" <brian@innovationslab.net>; <ipv6@ietf.org>
> > Hi Brian,
> >
> > For DNS configuration, there are some updates:
> > draft-ietf-dnsop-ipv6-dns-configuration-01.txt --> 
> draft-ietf-dnsop-ipv6-dns-configuration-02.txt
> >
> > DNSOP wg will submit this revised draft to the IESG soon.
> >
> > Especially, the draft of RA option for recursive DNS server has been 
> updated:
> > draft-ietf-dnsop-ipv6-dns-configuration-02.txt
> >
> > These drafts will be announced by IETF soon.
> >
> > I think that they can be used as base documents for our discussion.
> >
> > Paul
> > ------------------------------------------------------
> > Jaehoon Paul Jeong (Research Engineer)
> > TEL. +82-42-860-1664
> > Mobile +82-16-711-1765
> > 161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea
> > NGI Standardization Research Team/PEC/ETRI
> > Homepage: http://www.adhoc.6ants.net/~paul
> >
> > ----- Original Message -----
> > From: "Brian Haberman" <brian@innovationslab.net>
> > >       * DNS configuration (RA option)         chairs          10 minutes
> > >            - draft-ietf-dnsop-ipv6-dns-configuration-01.txt
> > >            - Goal: Should the WG be doing something?
> >
> >
>
>
>--------------------------------------------------------------------------------
>
>
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>
>.
>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  Tue Jul 20 16:43:09 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 QAA29716
	for <dnsop-archive@lists.ietf.org>; Tue, 20 Jul 2004 16:43:08 -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 i6KJeqd5021159;
	Tue, 20 Jul 2004 12:40:52 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6KJeqwJ021154;
	Tue, 20 Jul 2004 12:40:52 -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 i6KJeobE021096
	for <dnsop@lists.uoregon.edu>; Tue, 20 Jul 2004 12:40:51 -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 PAA20502;
	Tue, 20 Jul 2004 15:40:48 -0400 (EDT)
Message-Id: <200407201940.PAA20502@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-serverid-02.txt
Date: Tue, 20 Jul 2004 15:40:48 -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		: Identifying an Authoritative Name Server
	Author(s)	: D. Conrad, S. Woolf
	Filename	: draft-ietf-dnsop-serverid-02.txt
	Pages		: 11
	Date		: 2004-7-20
	
With the increased use of DNS anycast, load balancing, and other
   mechanisms allowing more than one DNS name server to share a single
   IP address, it is sometimes difficult to tell which of a pool of name
   servers has answered a particular query.  A standardized mechanism to
   determine the identity of a name server responding to a particular
   query would be useful, particularly as a diagnostic aid.  Existing ad
   hoc mechanisms for addressing this concern are not adequate.  This
   document attempts to describe the common ad hoc solution to this
   problem, including its advantages and disadvantasges, and to
   characterize an improved mechanism.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-serverid-02.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-serverid-02.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-serverid-02.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-7-20155255.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsop-serverid-02.txt

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

Content-Type: text/plain
Content-ID:	<2004-7-20155255.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 Jul 20 17:30:16 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 QAA29717
	for <dnsop-archive@lists.ietf.org>; Tue, 20 Jul 2004 16:43:08 -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 i6KJeTt1020783;
	Tue, 20 Jul 2004 12:40:29 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6KJeT7n020782;
	Tue, 20 Jul 2004 12:40:29 -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 i6KJeRC9020752
	for <dnsop@lists.uoregon.edu>; Tue, 20 Jul 2004 12:40:28 -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 PAA20472;
	Tue, 20 Jul 2004 15:40:24 -0400 (EDT)
Message-Id: <200407201940.PAA20472@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-respsize-01.txt
Date: Tue, 20 Jul 2004 15:40:24 -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		: DNS Response Size Issues
	Author(s)	: P. Vixie, A. Kato
	Filename	: draft-ietf-dnsop-respsize-01.txt
	Pages		: 8
	Date		: 2004-7-20
	
With a mandated default minimum maximum message size of 512 octets,
the DNS protocol presents some special problems for zones wishing to
expose a moderate or high number of authority servers (NS RRs).  This
document explains the operational issues caused by, or related to
this response size limit.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-respsize-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-respsize-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-respsize-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-7-20155245.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsop-respsize-01.txt

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

Content-Type: text/plain
Content-ID:	<2004-7-20155245.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  Wed Jul 21 17:07: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 RAA01761
	for <dnsop-archive@lists.ietf.org>; Wed, 21 Jul 2004 17:07:33 -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 i6LJThk2014544;
	Wed, 21 Jul 2004 12:29:43 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6LJTgMn014535;
	Wed, 21 Jul 2004 12:29:42 -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 i6LJTfVa014395
	for <dnsop@lists.uoregon.edu>; Wed, 21 Jul 2004 12:29:41 -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 PAA16105;
	Wed, 21 Jul 2004 15:29:38 -0400 (EDT)
Message-Id: <200407211929.PAA16105@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-bad-dns-res-02.txt
Date: Wed, 21 Jul 2004 15:29:38 -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		: Observed DNS Resolution Misbehavior
	Author(s)	: M. Larson, P. Barber
	Filename	: draft-ietf-dnsop-bad-dns-res-02.txt
	Pages		: 21
	Date		: 2004-7-21
	
This memo describes DNS name server and resolver behavior that
   results in a significant query volume sent to the root and top-level
   domain (TLD) name servers.  In some cases we recommend minor
   additions to the DNS protocol specification and corresponding changes
   in iterative resolver implementations to alleviate these unnecessary
   queries.  The recommendations made in this document are a direct
   byproduct of observation and analysis of abnormal query traffic
   patterns seen at two of the thirteen root name servers and all
   thirteen com/net TLD name servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-bad-dns-res-02.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-bad-dns-res-02.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-bad-dns-res-02.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-7-21152559.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsop-bad-dns-res-02.txt

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

Content-Type: text/plain
Content-ID:	<2004-7-21152559.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  Thu Jul 22 07:58: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 HAA12671
	for <dnsop-archive@lists.ietf.org>; Thu, 22 Jul 2004 07:58:35 -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 i6MAnJN4013268;
	Thu, 22 Jul 2004 03:49:19 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6MAnJxC013255;
	Thu, 22 Jul 2004 03:49:19 -0700 (PDT)
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6MAnHAo012537
	for <dnsop@lists.uoregon.edu>; Thu, 22 Jul 2004 03:49:18 -0700 (PDT)
Received: from paul3 (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i6MB6mxB011349;
	Thu, 22 Jul 2004 20:06:48 +0900 (KST)
Message-ID: <01a501c46fd9$6b60f840$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: "Ralph Droms" <rdroms@cisco.com>
Cc: <dnsop@lists.uoregon.edu>, <ipv6@ietf.org>
References: <4.3.2.7.2.20040719225417.02a6f8e8@flask.cisco.com>
Subject: Re: [dnsop] Fw: Updated IPv6 WG Agenda
Date: Thu, 22 Jul 2004 19:48:26 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by darkwing.uoregon.edu id i6MAnIAo013185
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Content-Transfer-Encoding: 8bit

You're right.

I intended that IPv6 WG chairs will report the status of draft-ietf-dnsop-ipv6-dns-configuration-02.txt to IPv6 members
because IPv6 DNS Configuration is an important issue to IPv6 WG.
Though RA approach is one of three condidates, it depends on IESG's decision to decide RA approach as another standard for
IPv6 Host DNS configuration.
In this meeting, it seems more suitable to discuss only on draft-ietf-dnsop-ipv6-dns-configuration-02.txt.

Thanks.

Paul

----- Original Message ----- 
From: "Ralph Droms" <rdroms@cisco.com>
To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Cc: <dnsop@lists.uoregon.edu>; <ipv6@ietf.org>
Sent: Tuesday, July 20, 2004 11:56 AM
Subject: Re: [dnsop] Fw: Updated IPv6 WG Agenda


> 
> What will be the topic of the discussion?
> 
> The draft we're preparing in dnsop 
> (draft-ietf-dnsop-ipv6-dns-configuration-02.txt) is intended for the IESG, 
> I think.  Is it premature to discuss anything in the ipv6 WG prior to the 
> IESG evaluation?
> 
> - Ralph
> 
> At 09:32 AM 7/20/2004 +0900, Jaehoon Paul Jeong wrote:
> >FYI
> >
> >In this 60th IETF meeting, there will be discussion on IPv6 DNS 
> >Configuration at IPv6 wg.
> >
> >Paul
> >
> >----- Original Message -----
> >From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
> >To: "Brian Haberman" <brian@innovationslab.net>; <ipv6@ietf.org>
> > > Hi Brian,
> > >
> > > For DNS configuration, there are some updates:
> > > draft-ietf-dnsop-ipv6-dns-configuration-01.txt --> 
> > draft-ietf-dnsop-ipv6-dns-configuration-02.txt
> > >
> > > DNSOP wg will submit this revised draft to the IESG soon.
> > >
> > > Especially, the draft of RA option for recursive DNS server has been 
> > updated:
> > > draft-ietf-dnsop-ipv6-dns-configuration-02.txt
> > >
> > > These drafts will be announced by IETF soon.
> > >
> > > I think that they can be used as base documents for our discussion.
> > >
> > > Paul
> > > ------------------------------------------------------
> > > Jaehoon Paul Jeong (Research Engineer)
> > > TEL. +82-42-860-1664
> > > Mobile +82-16-711-1765
> > > 161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea
> > > NGI Standardization Research Team/PEC/ETRI
> > > Homepage: http://www.adhoc.6ants.net/~paul
> > >
> > > ----- Original Message -----
> > > From: "Brian Haberman" <brian@innovationslab.net>
> > > >       * DNS configuration (RA option)         chairs          10 minutes
> > > >            - draft-ietf-dnsop-ipv6-dns-configuration-01.txt
> > > >            - Goal: Should the WG be doing something?
> > >
> > >
> >
> >
> >--------------------------------------------------------------------------------
> >
> >
> > > --------------------------------------------------------------------
> > > IETF IPv6 working group mailing list
> > > ipv6@ietf.org
> > > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > > --------------------------------------------------------------------
> > >
> >
> >.
> >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
> 

.
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 Jul 24 14:51: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 OAA04590
	for <dnsop-archive@lists.ietf.org>; Sat, 24 Jul 2004 14:51: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 i6OHVf8D010906;
	Sat, 24 Jul 2004 10:31:41 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6OHVfVp010895;
	Sat, 24 Jul 2004 10:31:41 -0700 (PDT)
Received: from smtp-mx-05.ti.local (host191180.arnet.net.ar [200.45.191.180] (may be forged))
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6OHVc0F010155
	for <dnsop@lists.uoregon.edu>; Sat, 24 Jul 2004 10:31:39 -0700 (PDT)
Received: from smtp-mx-04.ti.local ([192.168.220.23]) by smtp-mx-05.ti.local with Microsoft SMTPSVC(5.0.2195.6713);
	 Sat, 24 Jul 2004 14:31:18 -0300
Received: from mail pickup service by smtp-mx-04.ti.local with Microsoft SMTPSVC;
	 Sat, 24 Jul 2004 14:31:13 -0300
Received: from qsmtp-mx-03.arnet.com.ar ([200.45.191.166]) by smtp-mx-04.ti.local with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 21 Jul 2004 17:23:57 -0300
Received: (qmail 19450 invoked from network); 21 Jul 2004 20:21:24 -0000
Received: from unknown (HELO megatron.ietf.org) (132.151.6.71)
  by host191166.arnet.net.ar with SMTP; 21 Jul 2004 20:21:23 -0000
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnMxh-0006ap-FJ; Wed, 21 Jul 2004 15:41:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnMmb-0002fT-4f
	for i-d-announce@megatron.ietf.org; Wed, 21 Jul 2004 15:29:41 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16105;
	Wed, 21 Jul 2004 15:29:38 -0400 (EDT)
Message-Id: <200407211929.PAA16105@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 21 Jul 2004 15:29:38 -0400
Cc: dnsop@lists.uoregon.edu
Subject: [dnsop] I-D ACTION:draft-ietf-dnsop-bad-dns-res-02.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-OriginalArrivalTime: 21 Jul 2004 20:23:57.0524 (UTC) FILETIME=[A6906140:01C46F60]
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		: Observed DNS Resolution Misbehavior
	Author(s)	: M. Larson, P. Barber
	Filename	: draft-ietf-dnsop-bad-dns-res-02.txt
	Pages		: 21
	Date		: 2004-7-21
	
This memo describes DNS name server and resolver behavior that
   results in a significant query volume sent to the root and top-level
   domain (TLD) name servers.  In some cases we recommend minor
   additions to the DNS protocol specification and corresponding changes
   in iterative resolver implementations to alleviate these unnecessary
   queries.  The recommendations made in this document are a direct
   byproduct of observation and analysis of abnormal query traffic
   patterns seen at two of the thirteen root name servers and all
   thirteen com/net TLD name servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-bad-dns-res-02.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-bad-dns-res-02.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-bad-dns-res-02.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-7-21152559.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsop-bad-dns-res-02.txt

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--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 Jul 26 06:50:21 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 GAA14125
	for <dnsop-archive@lists.ietf.org>; Mon, 26 Jul 2004 06:50:21 -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 i6Q9in7H011066;
	Mon, 26 Jul 2004 02:44:49 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6Q9inh5011062;
	Mon, 26 Jul 2004 02:44:49 -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 i6Q9ifgj009189
	for <dnsop@lists.uoregon.edu>; Mon, 26 Jul 2004 02:44:42 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6Q9iZq10161;
	Mon, 26 Jul 2004 12:44:35 +0300
Date: Mon, 26 Jul 2004 12:44:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@lists.uoregon.edu
cc: namedroppers@ops.ietf.org, <narten@us.ibm.com>
Subject: Re: [dnsop] dnsop-ipv6-dns-issues: handling of additional data and
 TTL w/ caching
In-Reply-To: <Pine.LNX.4.44.0407141613360.32682-100000@netcore.fi>
Message-ID: <Pine.LNX.4.44.0407261217330.7284-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>

Hi,

Unfortunately there weren't follow-ups to this, so I just had to 
revise the draft on my own the best I could and submit:

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

Various htmlwdiffs are available at:
 http://www.netcore.fi/pekkas/ietf/temp/

Comments are still appreciated.

On Wed, 14 Jul 2004, Pekka Savola wrote:
> (also to dnsext WG)
> 
> Thomas Narten provided extensive feedback 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.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-08pre-diff.html
> http://www.netcore.fi/pekkas/ietf/temp/draft-ietf-dnsop-ipv6-dns-issues-08pre.txt
> 
> but there are still a few where it might be useful to get feedback
> from the WG(s).  Most of the discussion was on section 4.4 on the
> handling of additional data -- a subject that was already discussed
> briefly on the list around May 6, but did not have a clear conclusion
> (thread below):
> 
> http://ops.ietf.org/lists/namedroppers/namedroppers.2004/msg00406.html 
> 
> I've tried to summarize the discussion below *)
> 
> Now, Thomas brought up a lot of the same issues at IESG evaluation, 
> and I thought we should try again to see if there could be some 
> consensus on how to move forward.
> 
> ....
> 
> I think we have achieved at least the follows (please yell if not the 
> case):
> 
>  a) If some critical additional data RRsets wouldn't fit, you set the 
> TC bit even if some RRsets did fit.
> 
>  b) If some courtesy additional data RRsets wouldn't fit, you never
> set the TC bit, but rather remove (at least some of) the courtesy
> RRsets.
> 
>  c) DNS servers should implement sanity checks on the resulting glue,
> e.g., to disable circular dependencies.  Then the responding servers
> can use at-or-below-a-zone-cut criterion to determine whether the
> additional data is critical or not.
> 
> Now, there are still (IMHO) many open issues:
> 
>  1) if some critical additional data RRsets would fit, but some 
> wouldn't, and TC has to be set (see above), should one rather remove 
> the additional data that did fit, keep it, or leave unspecified?
> 
>  2) if some courtesy additional data RRsets would fit, but some
> wouldn't, and some will have to be removed from the response (no TC is
> set, see above), what to do -- remove all courtesy RRsets, keep all
> that fit, or leave unspecified?
>  
>  3) is it acceptable to use the transport used in the DNS query as a 
> hint which records to keep if not removing all the RRsets, if:
>    a) having to decide which critical additional data to keep, or
>    b) having to decide which courtesy additional data to keep?
> 
>  4) (this issue was discussed in section 4.5) if one RRset has TTL of
> 100 seconds, and another the TTL of 300 seconds, what should the
> caching server do after 100 seconds?  Keep returning just one RRset
> when returning additional data, or discard the other RRset from the
> cache?
> 
>  5) How do we move forward from here?  If we manage to get to some 
> form of consensus, how do we record it:
>    a) just in draft-ietf-dnsop-ipv6-dns-issues (note that it's 
>       Informational category only!),
>    b) a separate BCP or similar by DNSEXT WG(?), clarifying and giving 
>       recommendations,
>    c) something else, what?
> 
> Thoughts, opinions, etc.?  Fire away!
> 
> (I'm trying to submit a revised document prior to the cut-off in any 
> case, no matter how this turns out..)
> 
> A few of my personal thoughts below the summary.
> 
> *) a summary attempt of the past discussion below.
> ======== 
> Edward Lewis (on dnsop) thought that omitting vs including courtesy
> additional data was a tradeoff at the server end (issue about handling
> the new query vs potentially misleading the client), and that TC bit
> should only be set if critical additional data was left behind.
> 
> Robert Elz thought that the servers could add also add full RRsets,
> even if not all of them, if they want to.  Similarly, he would rather
> return only part of the courtesy data than set the TC bit.  He was of
> two minds about whether to set TC bit when all of courtesy additional
> data won't fit (but slightly leaning on TC bit, except if some
> additional data could fit and be included in a round-robin fashion);
> Robert also called for measurements on this.
> 
> Paul Vixie thought that just simply setting TC bit if anything doesn't
> fit is a good idea if we don't have measurements to justify another
> kind of approach.
> 
> Matt Larson commented on the definition of glue; the responding server
> can know whether the data is critical just by looking whether it's
> at-or-below-a-zone-cut.  Masataka Ohta commented that this isn't
> sufficient if e.g. "org" zone is served by an "edu" server and vice
> versa.  Mark Andrews rebutted that we don't have to support all the
> combinations if it makes managing the DNS impossible; DNS server
> software have included checks to avoid circular dependencies.
> 
> Masataka Ohta also participated in the discussion, and Andreas
> Gustafsson clarified Paul Vixie's comment.
> =========
> 
> As for my personal take, if interested:
> 
> My argument is that it would be best to return everything, or as
> little as possible.  Not whatever you think you feel like you want to
> send.  The reasoning here is that that if the user/application is
> interested in both A and AAAA records (this doesn't matter if (s)he's
> only interested in one), the DNS should either try to ensure (as far
> as possible) it's giving a full view, or just basically say to the
> user, "query yourself what you want, here's the critical info you
> need for those queries".
> 
> This is based on the assumption that if the DNS servers start
> second-guessing what kind of information the end-user would prefer
> (e.g., by looking at the transport used), it's likely going to go
> wrong because the DNS server asking for the records from the
> second-guessing DNS server is likely going to be acting as a recursive
> resolver, and it doesn't really indicate *at all* which IP version the
> application wants to prefer (or not), or which kind IP version is
> available in the first place.
> 
> So, relating to the questions above:
> 
> 1) not much preference here
> 2) remove all courtesy data
> 3) I'd rather not to look at the transport used, but 3.a) would be 
>    acceptable, 3.b) not (per 2)
> 4) I'd prefer discarding all the RRsets from the cache when the one 
>    with the shortest TTL one times out, this ensures an "everything or 
>    nothing" approach.
> 5) A separate document might be good so that this doesn't get lost 
>    within an Informational document.
> 
> 

-- 
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  Mon Jul 26 09:16:42 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 JAA23963
	for <dnsop-archive@lists.ietf.org>; Mon, 26 Jul 2004 09:16: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 i6QBrZ5A022148;
	Mon, 26 Jul 2004 04:53:35 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6QBrYEA022141;
	Mon, 26 Jul 2004 04:53: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 i6QBrX21022043
	for <dnsop@lists.uoregon.edu>; Mon, 26 Jul 2004 04:53:34 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1048:7d91:64be:e17:f09d])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 39D6D15272
	for <dnsop@lists.uoregon.edu>; Mon, 26 Jul 2004 20:53:32 +0900 (JST)
Date: Mon, 26 Jul 2004 20:53:31 +0900
Message-ID: <y7vsmbfkmro.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] I-D ACTION:draft-ietf-dnsop-bad-dns-res-02.txt
In-Reply-To: <200407211929.PAA16105@ietf.org>
References: <200407211929.PAA16105@ietf.org>
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, 21 Jul 2004 15:29:38 -0400, 
>>>>> Internet-Drafts@ietf.org said:

> 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		: Observed DNS Resolution Misbehavior
> 	Author(s)	: M. Larson, P. Barber
> 	Filename	: draft-ietf-dnsop-bad-dns-res-02.txt
> 	Pages		: 21
> 	Date		: 2004-7-21

Hmm, the revision number does not seem to be incremented from the
previous one:

DNS Operations                                                 M. Larson
Internet-Draft                                                 P. Barber
Expires: August 16, 2004                                        VeriSign
                                                       February 16, 2004


                  Observed DNS Resolution Misbehavior
                    draft-ietf-dnsop-bad-dns-res-02

But there appear to be differences between the two documents
(non-trivial ones such as the issue date).  And from a quick glance,
the new version does not seem to address my comments on the previous
one:
  http://darkwing.uoregon.edu/~llynch/dnsop/msg02958.html

If this simply means the author decided to reject the comments, then
it's okay (though I'll be sad then).  But at least I've not seen any
responses to the comments, either positive or negative, so I'm making
an explicit note just in case.

					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 Jul 27 04:05:06 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 EAA26585
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 04:05:06 -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 i6R76PpB019960;
	Tue, 27 Jul 2004 00:06:25 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6R76Pf6019958;
	Tue, 27 Jul 2004 00:06:25 -0700 (PDT)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6R76NGm019441
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 00:06:24 -0700 (PDT)
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I1I0070112IFV@mailout2.samsung.com> for dnsop@lists.uoregon.edu; Tue,
 27 Jul 2004 16:06:19 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I1I0075J12ILO@mailout2.samsung.com> for
 dnsop@lists.uoregon.edu; Tue, 27 Jul 2004 16:06:18 +0900 (KST)
Received: from Radhakrishnan ([107.108.71.64])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I1I00AC912HVJ@mmp2.samsung.com> for
 dnsop@lists.uoregon.edu; Tue, 27 Jul 2004 16:06:18 +0900 (KST)
Date: Tue, 27 Jul 2004 12:37:10 +0530
From: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Subject: [dnsop] Light-weight DNS resolver
To: dnsop@lists.uoregon.edu
Message-id: <07d501c473a8$568f5330$40476c6b@sisodomain.com>
Organization: SAMSUNG India Software Operations
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: multipart/alternative;
 boundary="Boundary_(ID_1iVTClch4fENW3ozo7oB3g)"
X-Priority: 3
X-MSMail-priority: Normal
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>

This is a multi-part message in MIME format.

--Boundary_(ID_1iVTClch4fENW3ozo7oB3g)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Hi,
  Can anyone tell me where i can find a free light-weight DNS v4/v6 resolver source-code implemented using c?

Thanks & Regards
S.Radhakrishnan

--Boundary_(ID_1iVTClch4fENW3ozo7oB3g)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp; Can&nbsp;anyone tell me where i can find a 
free light-weight DNS v4/v6 resolver source-code implemented using 
c?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thanks &amp; Regards</FONT></DIV>
<DIV><FONT face=Arial size=2>S.Radhakrishnan</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_1iVTClch4fENW3ozo7oB3g)--
.
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 Jul 27 05:35: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 FAA00582
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 05:35: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 i6R84AE7017278;
	Tue, 27 Jul 2004 01:04:10 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6R84A7l017270;
	Tue, 27 Jul 2004 01:04:10 -0700 (PDT)
Received: from outpost.ds9a.nl (postfix@outpost.ds9a.nl [213.244.168.210])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6R848hR017031
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 01:04:09 -0700 (PDT)
Received: by outpost.ds9a.nl (Postfix, from userid 1000)
	id 7F5F34020; Tue, 27 Jul 2004 10:04:07 +0200 (CEST)
Date: Tue, 27 Jul 2004 10:04:07 +0200
From: bert hubert <ahu@ds9a.nl>
To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Cc: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Light-weight DNS resolver
Message-ID: <20040727080407.GA23720@outpost.ds9a.nl>
Mail-Followup-To: bert hubert <ahu@ds9a.nl>,
	Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>,
	dnsop@lists.uoregon.edu
References: <07d501c473a8$568f5330$40476c6b@sisodomain.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <07d501c473a8$568f5330$40476c6b@sisodomain.com>
User-Agent: Mutt/1.3.28i
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: bert hubert <ahu@ds9a.nl>

On Tue, Jul 27, 2004 at 12:37:10PM +0530, Radhakrishnan Suryanarayanan wrote:
> Hi,
>   Can anyone tell me where i can find a free light-weight DNS v4/v6 resolver source-code implemented using c?

If you can swallow C++, the powerdns recursor is rather small, 1500 lines or
so.

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
.
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 Jul 27 07:26:24 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 HAA06014
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 07:26:23 -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 i6R9nnrB001184;
	Tue, 27 Jul 2004 02:49:50 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6R9nnNV001174;
	Tue, 27 Jul 2004 02:49:49 -0700 (PDT)
Received: from mailout1.samsung.com (mailout1.samsung.com [203.254.224.24])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6R9nmKo000387
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 02:49:48 -0700 (PDT)
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I1I00D6N8MT6C@mailout1.samsung.com> for dnsop@lists.uoregon.edu; Tue,
 27 Jul 2004 18:49:41 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I1I00EJ48LM48@mailout1.samsung.com> for
 dnsop@lists.uoregon.edu; Tue, 27 Jul 2004 18:48:59 +0900 (KST)
Received: from Radhakrishnan ([107.108.71.64])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I1I00LGW8LLC9@mmp1.samsung.com> for
 dnsop@lists.uoregon.edu; Tue, 27 Jul 2004 18:48:58 +0900 (KST)
Date: Tue, 27 Jul 2004 15:19:50 +0530
From: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Subject: Re: [dnsop] Light-weight DNS resolver
To: bert hubert <ahu@ds9a.nl>
Cc: dnsop@lists.uoregon.edu
Message-id: <085501c473bf$10077b10$40476c6b@sisodomain.com>
Organization: SAMSUNG India Software Operations
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <07d501c473a8$568f5330$40476c6b@sisodomain.com>
 <20040727080407.GA23720@outpost.ds9a.nl>
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Content-Transfer-Encoding: 7BIT

Hi,
    I would prefer a one implemented with C language.
Also "drill" is too bare minimum. Some API support along with caching will
be helpful.

Thanks & Regards
Radhakrishnan

----- Original Message ----- 
From: "bert hubert" <ahu@ds9a.nl>
To: "Radhakrishnan Suryanarayanan" <rkrishnan.s@samsung.com>
Cc: <dnsop@lists.uoregon.edu>
Sent: Tuesday, July 27, 2004 1:34 PM
Subject: Re: [dnsop] Light-weight DNS resolver


> On Tue, Jul 27, 2004 at 12:37:10PM +0530, Radhakrishnan Suryanarayanan
wrote:
> > Hi,
> >   Can anyone tell me where i can find a free light-weight DNS v4/v6
resolver source-code implemented using c?
>
> If you can swallow C++, the powerdns recursor is rather small, 1500 lines
or
> so.
>
> -- 
> http://www.PowerDNS.com      Open source, database driven DNS Software
> http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
>

.
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 Jul 27 07:29:30 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 HAA06159
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 07:29: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 i6R9njnW000717;
	Tue, 27 Jul 2004 02:49:45 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6R9njMl000711;
	Tue, 27 Jul 2004 02:49:45 -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 i6R9nhdA029947
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 02:49:44 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6R9nZi19483;
	Tue, 27 Jul 2004 12:49:35 +0300
Date: Tue, 27 Jul 2004 12:49:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: namedroppers@ops.ietf.org
cc: dnsop@lists.uoregon.edu
Subject: [dnsop] getaddrinfo/TTL and resolver application-interface 
Message-ID: <Pine.LNX.4.44.0407271240320.19150-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>

Hi,

draft-gieben-resolver-application-interface-00.txt sketches what kind
of information the application and the resolver could have through an
interface.  This has been discussed in dnsext at least in Feb 2004.  
What has been the outcome?

The reason why I got interested was because section 8.2 of
draft-ietf-dnsop-ipv6-dns-issues-08.txt (see below)  shows that the
application should be able to be aware of the TTL of the records,
easily, so that it could discard expired records from the memory if
it's built around in such a way that it would be feasible to do so.  
As it is, the applications typically query a name when they start and
use it forever, irregardless of the TTL.  (And if the
application-resolver interface needs work in any case....)

IMHO, it seem to be worth adding the TTL information to getaddrinfo()  
functions.

from draft-ietf-dnsop-ipv6-dns-issues-08.txt:

8.2  Renumbering Procedures and Applications' Use of DNS
                                                                                                                
   One of the most difficult problems of systematic IP address
   renumbering procedures [I-D.ietf-v6ops-renumbering-procedure] is that
   an application which looks up a DNS name disregards information such
   as TTL, and uses the result obtained from DNS as long as it happens
   to be stored in the memory of the application.  For applications
   which run for a long time, this could be days, weeks or even months;
   some applications may be clever enough to organize the data
   structures and functions in such a manner that look-ups get refreshed
   now and then.
                                                                                                                
   While the issue appears to have a clear solution, "fix the
   applications", practically this is not reasonable immediate advice;
   the TTL information is not typically available in the APIs and
   libraries (so, the advice becomes "fix the applications, APIs and
   libraries"), and a lot more analysis is needed on how to practically
   go about to achieve the ultimate goal of avoiding using the names
   longer than expected.

-- 
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 Jul 27 08:09: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 IAA08197
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 08:09: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 i6RB6f6Z027802;
	Tue, 27 Jul 2004 04:06:41 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6RB6fVa027794;
	Tue, 27 Jul 2004 04:06:41 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [213.154.224.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6RB6aWH027263
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 04:06:40 -0700 (PDT)
Received: from elektron.atoom.net (f52166.upc-f.chello.nl [80.56.52.166])
	by open.nlnetlabs.nl (8.12.11/8.12.11) with ESMTP id i6RB6XqY095388;
	Tue, 27 Jul 2004 13:06:33 +0200 (CEST)
	(envelope-from miekg@atoom.net)
Received: from elektron.atoom.net (localhost [127.0.0.1])
	by elektron.atoom.net (8.12.11/8.12.11/Debian-5) with ESMTP id i6RB6WXY015397;
	Tue, 27 Jul 2004 13:06:32 +0200
Received: (from miekg@localhost)
	by elektron.atoom.net (8.12.11/8.12.11/Debian-5) id i6RB6V8s015393;
	Tue, 27 Jul 2004 13:06:31 +0200
Date: Tue, 27 Jul 2004 13:06:31 +0200
From: Miek Gieben <miekg@atoom.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: namedroppers@ops.ietf.org, dnsop@lists.uoregon.edu
Subject: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
Message-ID: <20040727110631.GB14975@atoom.net>
Mail-Followup-To: Pekka Savola <pekkas@netcore.fi>,
	namedroppers@ops.ietf.org, dnsop@lists.uoregon.edu
References: <Pine.LNX.4.44.0407271240320.19150-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0407271240320.19150-100000@netcore.fi>
User-Agent: Vim/Mutt/Linux
X-Home: www.miek.nl
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on open.nlnetlabs.nl
X-Virus-Scanned: by amavisd-new
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Miek Gieben <miekg@atoom.net>

[On 27 Jul, @11:49, Pekka wrote in "getaddrinfo/TTL and resolver a ..."]
> Hi,
> 
> draft-gieben-resolver-application-interface-00.txt sketches what kind
> of information the application and the resolver could have through an
> interface.  This has been discussed in dnsext at least in Feb 2004.  
> What has been the outcome?

nothing yet, we had a lot of discussion about it, but nothing
materialized out of it.

Personally I think some other questions also need to be answered,
like:

o what service does the DNS actually provide?
	(it's a naming service, but application seem to want to know 
	more and more about the resolution process. Esp. with DNSSEC).

o where do applications start and resolvers end?
	A seen from the text below, apps now want to know TTLs. Where
	does it stop? 

o Each "application" (IPSEC for instance) has different (security) needs,
 	and has a different set of "local policy" rules. What kind of
	interface is needed to allow for an application to make it's
	own policy decisions?

Following this line of thinking we could come to the conclussion that
an application wants to know the entire resolving chain, from the root
down to the leave node.  But when your local resolver does caching
this might now be available... so there you go....

> The reason why I got interested was because section 8.2 of
> draft-ietf-dnsop-ipv6-dns-issues-08.txt (see below)  shows that the
> application should be able to be aware of the TTL of the records,
> easily, so that it could discard expired records from the memory if
> it's built around in such a way that it would be feasible to do so.  
> As it is, the applications typically query a name when they start and
> use it forever, irregardless of the TTL.  (And if the
> application-resolver interface needs work in any case....)
> 
> IMHO, it seem to be worth adding the TTL information to getaddrinfo()  
> functions.

grtz,
--Miek
.
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 Jul 27 15:35: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 PAA09773
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 15:35: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 i6RIEZq2014806;
	Tue, 27 Jul 2004 11:14:35 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6RIEZuu014804;
	Tue, 27 Jul 2004 11:14:35 -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 i6RIEYsu014781
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 11:14:34 -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 i6RIEYBa017237
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 11:14:34 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.11/Submit) id i6RIEYpQ017236
	for dnsop@lists.uoregon.edu; Tue, 27 Jul 2004 11:14:34 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 27 Jul 2004 11:14:34 -0700
From: David Meyer <dmm@1-4-5.net>
To: dnsop@lists.uoregon.edu
Subject: [dnsop] Current DNSOP Agenda (IETF 60)
Message-ID: <20040727181434.GA17230@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>

	Please see http://www.1-4-5.net/~dmm/IETF/IETF60/DNSOP

	Dave
.
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 Jul 27 16:06:01 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 QAA10917
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 16:06:00 -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 i6RJ2GQa022994;
	Tue, 27 Jul 2004 12:02:16 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6RJ2Ghv022991;
	Tue, 27 Jul 2004 12:02:16 -0700 (PDT)
Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6RJ2E6E022906
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 12:02:15 -0700 (PDT)
Received: from VSVAPOSTALGW1.vcorp.ad.vrsn.com (vsvapostalgw1.vcorp.ad.vrsn.com [10.170.12.38])
	by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i6RJ0hop014940;
	Tue, 27 Jul 2004 15:00:44 -0400 (EDT)
Received: from chinook (chinook.corppc.vrsn.com [10.131.31.52]) by VSVAPOSTALGW1.vcorp.ad.vrsn.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id PN79PXAQ; Tue, 27 Jul 2004 15:02:06 -0400
Received: by chinook (Postfix, from userid 500)
	id A455021305B; Tue, 27 Jul 2004 15:02:06 -0400 (EDT)
Date: Tue, 27 Jul 2004 15:02:06 -0400
From: "Larson, Matt" <mlarson@verisign.com>
To: "JINMEI Tatuya / ?$B?@L@C#:H" <jinmei@isl.rdc.toshiba.co.jp>
Cc: dnsop@lists.uoregon.edu, pbarber@verisign.com
Subject: Re: [dnsop] Re: WGLC for draft-ietf-dnsop-bad-dns-res-02.txt
Message-ID: <20040727190206.GI17724@chinook.corppc.vrsn.com>
References: <200407211929.PAA16105@ietf.org> <y7vsmbfkmro.wl@ocean.jinmei.org> <20040624200408.GA29798@1-4-5.net> <y7vzn6mltfo.wl@ocean.jinmei.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <y7vsmbfkmro.wl@ocean.jinmei.org> <y7vzn6mltfo.wl@ocean.jinmei.org>
User-Agent: Mutt/1.5.6i
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: "Larson, Matt" <mlarson@verisign.com>

On Mon, 26 Jul 2004, JINMEI Tatuya / ?$B?@L@C#:H wrote:
> Hmm, the revision number does not seem to be incremented from the
> previous one:
> [...]
> But there appear to be differences between the two documents
> (non-trivial ones such as the issue date).

I'm not sure what happened.  I definitely submitted -03 to
internet-drafts@ietf.org, but it showed up as -02.

> And from a quick glance,
> the new version does not seem to address my comments on the previous
> one:
>   http://darkwing.uoregon.edu/~llynch/dnsop/msg02958.html
> 
> If this simply means the author decided to reject the comments, then
> it's okay (though I'll be sad then).  But at least I've not seen any
> responses to the comments, either positive or negative, so I'm making
> an explicit note just in case.

I did see your comments and I thank you for sending them.  I apologize
for not responding to them until now.  Please see below for my
response.

On Tue, 29 Jun 2004, JINMEI Tatuya / ?$B?@L@C#:H wrote:
> (explicitly cc'ing to the authors)
> 
> >>>>> On Thu, 24 Jun 2004 13:04:08 -0700, 
> >>>>> David Meyer <dmm@1-4-5.net> said:
> 
> > 	The WGLC on this one was scheduled to end today at 1500
> > 	PDT (GMT/UTC-7). However, there have been several
> > 	comments that need to be resolved before we can go
> > 	forward. We will revisit this one after the authors have
> > 	revised the document.
> 
> In section 2.2.1, the draft says:
> 
>    [...]
>    Implementations that perform lame server caching MUST refrain from
>    sending queries to known lame servers based on a time interval from
>    when the server is discovered to be lame.  [...]
> 
> In general, I agree on this recommendation.  But it might cause a
> rather undesirable result when all authoritative servers seem to be
> lame, since some authoritative server implementations can be lame for
> particular resource record types.  (See Section 4.4 of
> draft-ietf-dnsop-misbehavior-against-aaaa-01.txt for more details)
> 
> Of course, what is wrong here is "lame" authoritative servers.  But
> sometimes we need to explore workaround to deal with real-world's
> problems...

This is true and I overlooked this comment during the revision.
You're right that a sentence or two explaining the unfortunate "lame
by domain name" behavior would be helpful.

> Meanwhile, I'm not sure if the recommendation also applies to the case
> where *all* authoritative servers seem to lame.  In the beginning of
> Section 2.2, the draft says as follows:
> 
>    A more common occurrence is a subset of a zone's name servers being
>    unavailable or misconfigured.
> 
> But I could not be sure if this section (including the recommendation)
> only concentrates on the case where a subset of the servers behave
> badly or it also considers the case where all of them are bad.
> 
> If the intention is the former, then please make it clear throughout
> the section, particularly in Section 2.2.1.
> 
> If the intention is the latter, I hope the document also notes that
> the recommended behavior may sometimes cause undesirable result while
> the behavior generally makes sense.

The section is intended to apply on a per-server basis, i.e., what to
do when a given server is discovered to be lame for a particular zone.
I confess that I re-read the section several times and thought it was
clear.  I could not figure out a way to make it more clear.  Could you
please suggest specific changes?

Matt

.
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 Jul 27 22:17:30 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 WAA28603
	for <dnsop-archive@lists.ietf.org>; Tue, 27 Jul 2004 22:17: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 i6S1Ltbp018436;
	Tue, 27 Jul 2004 18:21:55 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6S1LtS6018434;
	Tue, 27 Jul 2004 18:21:55 -0700 (PDT)
Received: from matureasskickers.net (matureasskickers.net [66.28.14.59])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6S1LsHo018406
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 18:21:54 -0700 (PDT)
Received: from newred.lsi.lan (c-24-7-84-78.client.comcast.net [24.7.84.78])
	(authenticated bits=0)
	by matureasskickers.net (8.12.8/8.12.8) with ESMTP id i6S1Lf0e017056
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 21:21:49 -0400
Received: from [10.42.1.4] (ip-69-33-182-2.atl.megapath.net [69.33.182.2])
	(authenticated bits=0)
	by newred.lsi.lan (8.12.11/8.12.11) with ESMTP id i6S1LQvx005014
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 18:21:34 -0700
Date: Tue, 27 Jul 2004 18:21:26 -0700
From: Kenneth Porter <shiva@sewingwitch.com>
To: dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Light-weight DNS resolver
Message-ID: <1F27C8EB7E8F18D82A11C8C7@[10.42.1.4]>
In-Reply-To: <07d501c473a8$568f5330$40476c6b@sisodomain.com>
References:  <07d501c473a8$568f5330$40476c6b@sisodomain.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: MIMEDefang 2.44
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Kenneth Porter <shiva@sewingwitch.com>
Content-Transfer-Encoding: 7bit

--On Tuesday, July 27, 2004 12:37 PM +0530 Radhakrishnan Suryanarayanan 
<rkrishnan.s@samsung.com> wrote:

>   Can anyone tell me where i can find a free light-weight DNS v4/v6
> resolver source-code implemented using c?

What do you consider "light-weight"? BIND comes with a resolver claimed to 
be so. Grab the sources at the ISC website.




.
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 Jul 28 04:11: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 EAA13048
	for <dnsop-archive@lists.ietf.org>; Wed, 28 Jul 2004 04:11:33 -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 i6S6reoW006348;
	Tue, 27 Jul 2004 23:53:40 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6S6recT006346;
	Tue, 27 Jul 2004 23:53: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 i6S6rcB6006313
	for <dnsop@lists.uoregon.edu>; Tue, 27 Jul 2004 23:53:38 -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 <0I1J00JJ0V58ZR@mailout3.samsung.com> for dnsop@lists.uoregon.edu; Wed,
 28 Jul 2004 15:53:32 +0900 (KST)
Received: from ep_mmp2 (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 <0I1J00681V3EPH@mailout3.samsung.com> for
 dnsop@lists.uoregon.edu; Wed, 28 Jul 2004 15:52:26 +0900 (KST)
Received: from Radhakrishnan ([107.108.71.64])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I1J00BMAV3CVS@mmp2.samsung.com> for
 dnsop@lists.uoregon.edu; Wed, 28 Jul 2004 15:52:26 +0900 (KST)
Date: Wed, 28 Jul 2004 12:23:15 +0530
From: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Subject: Re: [dnsop] Light-weight DNS resolver
To: Kenneth Porter <shiva@sewingwitch.com>, dnsop@lists.uoregon.edu
Message-id: <09cf01c4746f$8faedc90$40476c6b@sisodomain.com>
Organization: SAMSUNG India Software Operations
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <07d501c473a8$568f5330$40476c6b@sisodomain.com>
 <1F27C8EB7E8F18D82A11C8C7@[10.42.1.4]>
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Content-Transfer-Encoding: 7BIT

Hi,
  I want to port a DNSv4/v6 client to an embedded system.
The DNS client should have :-
(1) A Resolver
(2) Cache
(3) API support like gethostbyname,getnamebyhost and getaddrinfo.

This is what i call a light-weight DNS resolver.

BIND is very huge for use in embedded systems and also resolver & nameserver
daemon are inter-dependent.

Can anyone help me?

Thanks
Radhakrishnan
----- Original Message ----- 
From: "Kenneth Porter" <shiva@sewingwitch.com>
To: <dnsop@lists.uoregon.edu>
Sent: Wednesday, July 28, 2004 6:51 AM
Subject: Re: [dnsop] Light-weight DNS resolver


> --On Tuesday, July 27, 2004 12:37 PM +0530 Radhakrishnan Suryanarayanan
> <rkrishnan.s@samsung.com> wrote:
>
> >   Can anyone tell me where i can find a free light-weight DNS v4/v6
> > resolver source-code implemented using c?
>
> What do you consider "light-weight"? BIND comes with a resolver claimed to
> be so. Grab the sources at the ISC website.
>
>
>
>
> .
> 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 Jul 28 05:46: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 FAA17437
	for <dnsop-archive@lists.ietf.org>; Wed, 28 Jul 2004 05:46:04 -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 i6S8Lfa3016742;
	Wed, 28 Jul 2004 01:21:41 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6S8LfV7016741;
	Wed, 28 Jul 2004 01:21:41 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.67])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6S8Ld1K016725
	for <dnsop@lists.uoregon.edu>; Wed, 28 Jul 2004 01:21:40 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.67])
	by gromit.rfc1035.com (8.12.10/8.12.10) with ESMTP id i6S8LbqJ014755;
	Wed, 28 Jul 2004 09:21:38 +0100 (BST)
To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
cc: Kenneth Porter <shiva@sewingwitch.com>, dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Light-weight DNS resolver 
In-Reply-To: Message from Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com> 
   of "Wed, 28 Jul 2004 12:23:15 +0530." <09cf01c4746f$8faedc90$40476c6b@sisodomain.com> 
Date: Wed, 28 Jul 2004 09:21:37 +0100
Message-ID: <14754.1091002897@gromit.rfc1035.com>
From: Jim Reid <jim@rfc1035.com>
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Jim Reid <jim@rfc1035.com>

>>>>> Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com> writes:

    >> Hi, I want to port a DNSv4/v6 client to an embedded system.
    >> The DNS client should have :- (1) A Resolver (2) Cache (3) API
    >> support like gethostbyname,getnamebyhost and getaddrinfo.

    >> This is what i call a light-weight DNS resolver.

    >> BIND is very huge for use in embedded systems and also resolver
    >> & nameserver daemon are inter-dependent.

    >> Can anyone help me?

Probably not based on the info you've provided. For instance, you've
not defined what you mean by "resolver". Is it a full service resolver
like you'd find in a name server or a stub resolver that just makes
one query? [I suspect it's the latter but your reference to cache
suggests the former.] You've also not given details of the OS and
hardware constraints. Or the intended operating environment: ie what
and how this lightweight resolver is expected to get used. So it's
hardly surprising you get few pointers. Not that there are more than a
handful of open source resolvers anyway. A google search will tell you
that you've already been told about the most common implementations.

Full service resolving is hard and complex. It'll get even harder once
DNSSEC gets deployed. This is not a task for any device that has
limited resources or a primitive OS: the typical embedded system in
other words. So it will probably be best to leave the hard work of
resolving and cache management to a local name server. ie Your
embedded system just makes regular DNS queries to some local name
server. This also saves you upgrading the firmware in these embedded
systems whenever the DNS protocol gets extended, say for a new
resource record or changes to DNSSEC semantics.

Bear in mind too that a client-side cache is usually a Bad Idea. It
adds complexity and leads to inconsistency: ie stale stuff lies in
this cache long after it expired from the DNS. Is the cost of a local
cache lookup worth it? You may be as well just to make a DNS query to
the local name server without interposing some lobotomised internal
cache.
.
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 Jul 28 23:15:55 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 XAA26830
	for <dnsop-archive@lists.ietf.org>; Wed, 28 Jul 2004 23:15: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 i6T2A6lj003862;
	Wed, 28 Jul 2004 19:10:06 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6T2A6l6003860;
	Wed, 28 Jul 2004 19:10:06 -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 i6T2A4nI003833
	for <dnsop@lists.uoregon.edu>; Wed, 28 Jul 2004 19:10:05 -0700 (PDT)
Received: by coconut.itojun.org (Postfix, from userid 1001)
	id D77D01C0BF; Thu, 29 Jul 2004 11:04:33 +0900 (JST)
To: miekg@atoom.net
Cc: pekkas@netcore.fi, namedroppers@ops.ietf.org, dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
In-Reply-To: Your message of "Tue, 27 Jul 2004 13:06:31 +0200"
	<20040727110631.GB14975@atoom.net>
References: <20040727110631.GB14975@atoom.net>
X-Mailer: Cue version 0.8 (040717-1035/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20040729020433.D77D01C0BF@coconut.itojun.org>
Date: Thu, 29 Jul 2004 11:04:33 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: itojun@itojun.org (Jun-ichiro itojun Hagino)

> [On 27 Jul, @11:49, Pekka wrote in "getaddrinfo/TTL and resolver a ..."]
> > Hi,
> > 
> > draft-gieben-resolver-application-interface-00.txt sketches what kind
> > of information the application and the resolver could have through an
> > interface.  This has been discussed in dnsext at least in Feb 2004.  
> > What has been the outcome?
> 
> nothing yet, we had a lot of discussion about it, but nothing
> materialized out of it.
> 
> Personally I think some other questions also need to be answered,
> like:
> 
> o what service does the DNS actually provide?
> 	(it's a naming service, but application seem to want to know 
> 	more and more about the resolution process. Esp. with DNSSEC).
> 
> o where do applications start and resolvers end?
> 	A seen from the text below, apps now want to know TTLs. Where
> 	does it stop? 
> 
> o Each "application" (IPSEC for instance) has different (security) needs,
>  	and has a different set of "local policy" rules. What kind of
> 	interface is needed to allow for an application to make it's
> 	own policy decisions?
> 
> Following this line of thinking we could come to the conclussion that
> an application wants to know the entire resolving chain, from the root
> down to the leave node.  But when your local resolver does caching
> this might now be available... so there you go....
> 
> > The reason why I got interested was because section 8.2 of
> > draft-ietf-dnsop-ipv6-dns-issues-08.txt (see below)  shows that the
> > application should be able to be aware of the TTL of the records,
> > easily, so that it could discard expired records from the memory if
> > it's built around in such a way that it would be feasible to do so.  
> > As it is, the applications typically query a name when they start and
> > use it forever, irregardless of the TTL.  (And if the
> > application-resolver interface needs work in any case....)
> > 
> > IMHO, it seem to be worth adding the TTL information to getaddrinfo()  
> > functions.

	I object to change getaddrinfo().  getaddrinfo() deployment is ongoing
	and i do not want two variants of getaddrinfo - one with TTL, one
	without TTL, depending on platforms.  it just leads to confusion
	with small benefit just for the sake of small set of users.
	if a user wants TTL info, she can use getrrsetbyname().

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  Thu Jul 29 10:14: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 KAA13760
	for <dnsop-archive@lists.ietf.org>; Thu, 29 Jul 2004 10:14: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 i6TCl0HY019534;
	Thu, 29 Jul 2004 05:47:00 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6TCl0ZT019531;
	Thu, 29 Jul 2004 05:47:00 -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 i6TCkxs9019512
	for <dnsop@lists.uoregon.edu>; Thu, 29 Jul 2004 05:46:59 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 28B6419BAAA; Thu, 29 Jul 2004 08:38:42 -0400 (EDT)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id BE0C619B984;
	Thu, 29 Jul 2004 08:38:41 -0400 (EDT)
Received: from [192.136.136.102] (mercury.arin.net [127.0.0.1])
	by mercury.arin.net (Postfix) with ESMTP id E2892CF394;
	Thu, 29 Jul 2004 08:46:57 -0400 (EDT)
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a06020401bd2e9c9247c1@[192.136.136.102]>
In-Reply-To: <20040729020433.D77D01C0BF@coconut.itojun.org>
References: <20040727110631.GB14975@atoom.net>
 <20040729020433.D77D01C0BF@coconut.itojun.org>
Date: Thu, 29 Jul 2004 08:39:25 -0400
To: itojun@itojun.org (Jun-ichiro itojun Hagino)
From: Edward Lewis <edlewis@arin.net>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
Cc: 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=-4.8 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>

I'm not sure who, but apparently someone wrote this to some mailing 
list at some time in the past.

>>  > The reason why I got interested was because section 8.2 of
>>  > draft-ietf-dnsop-ipv6-dns-issues-08.txt (see below)  shows that the
>>  > application should be able to be aware of the TTL of the records,
>>  > easily, so that it could discard expired records from the memory if
>>  > it's built around in such a way that it would be feasible to do so.

Please recall that the purpose of the TTL is for cache coherency, not 
a statement on the quality nor timeliness of the data in DNS. 
Similarly, the validity periods expressed in the signature records 
are not statements on the validity of the data, but the validity of 
the ancillary security data.

"Expired records" is a concept alien to DNS.  (A zone may be expired 
to a slave server.)

>>  > As it is, the applications typically query a name when they start and
>>  > use it forever, irregardless of the TTL.  (And if the
>>  > application-resolver interface needs work in any case....)

DNS is designed to be timeless service.  It's up to applications to 
be as dynamic as they want to be.  If applications assume incorrectly 
about the DNS, havoc will ensue.  Applications should not assume 
anything about the timers and clocks inside DNS.

OT: In my pre-DNS days, I once made my own simple lookup system.  The 
app looked up a name, got the address, and tried to complete the 
handshake of the transport layer.  If that failed, the app would then 
report back to the lookup system that the address was bad.  When the 
app wanted to connect again, it would lookup the name until a new 
address was registered.  If no address was received, it would set a 
timer and try again later.  This was mostly event driven, not 
timer-based - accomplishing what seems to be desired above without 
needing to pass timer information across the lookup service interface.

My point is - applications developers ought to rely on DNS at it's 
service's face value, not by inferring anything in the ancillary 
data.  If application developers try to read between the lines, we 
muddle the architecture of the Internet and will end up with a "house 
of cards."
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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  Thu Jul 29 12:57:07 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 MAA24647
	for <dnsop-archive@lists.ietf.org>; Thu, 29 Jul 2004 12:57:06 -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 i6TFcs3A028258;
	Thu, 29 Jul 2004 08:38:54 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6TFcsfd028255;
	Thu, 29 Jul 2004 08:38:54 -0700 (PDT)
Received: from fxodpr13.extra.daimlerchrysler.com (fxodpr13.extra.daimlerchrysler.com [129.9.82.74])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i6TFcrXr028165
	for <dnsop@lists.uoregon.edu>; Thu, 29 Jul 2004 08:38:53 -0700 (PDT)
Received: (from uucp@localhost)
	by fxodpr13.extra.daimlerchrysler.com (8.12.8/8.9.0) id i6TFcjBM012974
	for <dnsop@lists.uoregon.edu>; Thu, 29 Jul 2004 11:38:45 -0400 (EDT)
Received: from unknown(53.231.71.24) by fxodpr13.extra.daimlerchrysler.com via csmap (V6.0)
	id srcAAARBayvz; Thu, 29 Jul 04 11:38:45 -0400
Received: from odconpr2-hme0.oddc.chrysler.com ([127.0.0.1])
 by odconpr2-hme0.oddc.chrysler.com (Mail-Gear 2.0.0 bld 66) with SMTP id M2004072911384311673
 ; Thu, 29 Jul 2004 11:38:43 -0400
Received: from odmrspr2-hme0.oddc.chrysler.com ([53.231.2.113])
 by odconpr2-hme0.oddc.chrysler.com (SMSSMTP 4.0.0.59) with SMTP id M2004072911384303957
 ; Thu, 29 Jul 2004 11:38:43 -0400
Received: from shsecpr1-ce0.shdc.chrysler.com (shsecpr1-ce0.shdc.chrysler.com [53.231.128.176])
	by odmrspr2-hme0.oddc.chrysler.com (8.12.11/8.12.10/daimlerchrysler-relay-1.1-kcd) with SMTP id i6TFVlBh029408;
	Thu, 29 Jul 2004 11:32:23 -0400 (EDT)
Received: from wokcdts1.is.chrysler.com ([53.230.102.252])
 by shsecpr1-ce0.shdc.chrysler.com (SMSSMTP 4.0.0.59) with SMTP id M2004072911322300142
 ; Thu, 29 Jul 2004 11:32:23 -0400
Received: from daimlerchrysler.com (wokcdts1.is.chrysler.com [53.230.102.252])
	by wokcdts1.is.chrysler.com (8.11.7+Sun/8.9.1) with ESMTP id i6TFWMr11365;
	Thu, 29 Jul 2004 11:32:22 -0400 (EDT)
Message-ID: <41091886.1040205@daimlerchrysler.com>
Date: Thu, 29 Jul 2004 11:32:22 -0400
From: Kevin Darcy <kcd@daimlerchrysler.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20030701
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: namedroppers@ops.ietf.org, dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
References: <20040727110631.GB14975@atoom.net> <20040729020433.D77D01C0BF@coconut.itojun.org> <a06020401bd2e9c9247c1@[192.136.136.102]>
In-Reply-To: <a06020401bd2e9c9247c1@[192.136.136.102]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: Kevin Darcy <kcd@daimlerchrysler.com>
Content-Transfer-Encoding: 7bit

Edward Lewis wrote:

> I'm not sure who, but apparently someone wrote this to some mailing 
> list at some time in the past.
>
>>> > The reason why I got interested was because section 8.2 of
>>> > draft-ietf-dnsop-ipv6-dns-issues-08.txt (see below) shows that the
>>> > application should be able to be aware of the TTL of the records,
>>> > easily, so that it could discard expired records from the memory if
>>> > it's built around in such a way that it would be feasible to do so.
>>
>
> Please recall that the purpose of the TTL is for cache coherency, not 
> a statement on the quality nor timeliness of the data in DNS. 

I would argue that if an application is using the results of a previous 
DNS lookup which it has stored in memory, then that is "caching" by any 
meaningful definition of the term. And if an app is caching, we should 
provide a way for the app to do so in a coherent manner. This implies 
making the TTL visible. Whether this is in getaddrinfo() or some other 
API, I'm not qualified to comment.

Like others, I've had problems with apps that "lock on" to a particular 
IP address. Particularly in dynamically load-balanced scenarios.

- Kevin


.
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 Jul 29 13:23:54 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 NAA26431
	for <dnsop-archive@lists.ietf.org>; Thu, 29 Jul 2004 13:23:53 -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 i6TFwrk2022284;
	Thu, 29 Jul 2004 08:58:53 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6TFwrcx022283;
	Thu, 29 Jul 2004 08:58:53 -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 i6TFwqB3022257
	for <dnsop@lists.uoregon.edu>; Thu, 29 Jul 2004 08:58:52 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 329D319BAD8; Thu, 29 Jul 2004 11:50:33 -0400 (EDT)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id A700C19BAD0;
	Thu, 29 Jul 2004 11:50:32 -0400 (EDT)
Received: from [192.136.136.102] (mercury.arin.net [127.0.0.1])
	by mercury.arin.net (Postfix) with ESMTP id 44598CF394;
	Thu, 29 Jul 2004 11:58:51 -0400 (EDT)
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a06020408bd2ecd37ae37@[192.136.136.102]>
In-Reply-To: <41091886.1040205@daimlerchrysler.com>
References: <20040727110631.GB14975@atoom.net>
 <20040729020433.D77D01C0BF@coconut.itojun.org>
 <a06020401bd2e9c9247c1@[192.136.136.102]>
 <41091886.1040205@daimlerchrysler.com>
Date: Thu, 29 Jul 2004 11:58:50 -0400
To: Kevin Darcy <kcd@daimlerchrysler.com>
From: Edward Lewis <edlewis@arin.net>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
Cc: 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=-4.9 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 11:32 -0400 7/29/04, Kevin Darcy wrote:

>I would argue that if an application is using the results of a previous DNS
>lookup which it has stored in memory, then that is "caching" by any meaningful
>definition of the term. And if an app is caching, we should provide a way for
>the app to do so in a coherent manner. This implies making the TTL visible.
>Whether this is in getaddrinfo() or some other API, I'm not qualified to
>comment.

Yes, it is caching by the application and it is up to the application 
to decide how long it will internally cache the data.  (Will SSH 
close a connection after 8 hours because it feels the original lookup 
data is no longer fresh enough?)

The DNS TTL though is not a good measure of freshness - by that I 
mean freshness at the authoritative source.  E.g., on one run an SSH 
client might get an address via a cache that had to get a fresh 
authoritative answer.  In this case, the DNS TTL might be 10800.  On 
a later run, the same client may get the same address - but following 
an HTTP client lookup by an hour.  In this case, the TTL is now 7200.

What does that mean to the SSH client, other than the data was 
sitting in an intermediary for an hour?  It says nothing about the 
freshness of the data at the origin.  (Note that the client can't 
determine that it was sitting in the intermediary - there's no 
indication of how far a TTL has ticked down in a reply.  It might be 
that the source has lowered the TTL.  Also, even if the application 
can be made to decide that it wants fresher data - it can't force the 
cache to get it.  The app would have to do it's own query iteration.)

>Like others, I've had problems with apps that "lock on" to a particular IP
>address. Particularly in dynamically load-balanced scenarios.

I've seen that.  I attribute it to poor application design, not a 
limitation of the interface to DNS (or other lookup service).

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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  Thu Jul 29 19:04:13 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 TAA16086
	for <dnsop-archive@lists.ietf.org>; Thu, 29 Jul 2004 19:04:12 -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 i6TLhEAG025075;
	Thu, 29 Jul 2004 14:43:14 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6TLhDmm025071;
	Thu, 29 Jul 2004 14:43:13 -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 i6TLhBbe024884
	for <dnsop@lists.uoregon.edu>; Thu, 29 Jul 2004 14:43:12 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i6TLgsC27076;
	Fri, 30 Jul 2004 00:42:59 +0300
Date: Fri, 30 Jul 2004 00:42:54 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Edward Lewis <edlewis@arin.net>
cc: Kevin Darcy <kcd@daimlerchrysler.com>, <namedroppers@ops.ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
In-Reply-To: <a06020408bd2ecd37ae37@[192.136.136.102]>
Message-ID: <Pine.LNX.4.44.0407300030520.25726-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 Thu, 29 Jul 2004, Edward Lewis wrote:
> At 11:32 -0400 7/29/04, Kevin Darcy wrote:
> 
> >I would argue that if an application is using the results of a previous DNS
> >lookup which it has stored in memory, then that is "caching" by any meaningful
> >definition of the term. And if an app is caching, we should provide a way for
> >the app to do so in a coherent manner. This implies making the TTL visible.
> >Whether this is in getaddrinfo() or some other API, I'm not qualified to
> >comment.
> 
> Yes, it is caching by the application and it is up to the application 
> to decide how long it will internally cache the data.  (Will SSH 
> close a connection after 8 hours because it feels the original lookup 
> data is no longer fresh enough?)
> 
> The DNS TTL though is not a good measure of freshness - by that I 
> mean freshness at the authoritative source.  E.g., on one run an SSH 
> client might get an address via a cache that had to get a fresh 
> authoritative answer.  In this case, the DNS TTL might be 10800.  On 
> a later run, the same client may get the same address - but following 
> an HTTP client lookup by an hour.  In this case, the TTL is now 7200.
[...]

I don't think the "freshness" is the point here -- at least not for 
me.

Rather, it's "the minimum how long the DNS server asserts that this
address corresponding to the name I asked will be valid".

Rather than discarding the result after the TTL would expire, and
breaking connections (or whatever), the application could re-query the
record after TTL expires to see if it still points to the same
address(es).  And if the TTL it received now is signficantly larger
(e.g., because a cache returned a very low TTL), the new TTL would be
longer, leading to a longer time before the next query.

An interactive client-application like SSH is a bit bad example of 
this.

Instead, consider an SSH daemon which is configued to listen to the
hostname "server.example.net" (not a wildcard address).  The daemon
could run for a month or a year in one go, but the hostname might
change during that time.  It could be beneficial that the application 
could re-query the DNS for "server.example.net" at some intervals (TTL 
could be one indicator here), and change its bindings if the DNS 
changes.

Similarly, consider a mechanism like SCTP or HIP which ties multiple
addresses to a connection.  A hostname might map to 1..N addresses
when the connection is established; during the lifetime of the
connection, the hostname could change to point to an entirely
different set of addresses.  Depending on how the new addresses
corresponding to the end-points are discovered during the session,
this TTL information could be quite useful -- as a means to trigger
how often one should poll for new information (instead of an arbitrary
interval).

There are probably better examples as well..

-- 
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  Thu Jul 29 22:35:57 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 WAA26352
	for <dnsop-archive@lists.ietf.org>; Thu, 29 Jul 2004 22:35:57 -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 i6U1FhW9029382;
	Thu, 29 Jul 2004 18:15:43 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i6U1Fhbc029380;
	Thu, 29 Jul 2004 18:15:43 -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 i6U1FgJw029363
	for <dnsop@lists.uoregon.edu>; Thu, 29 Jul 2004 18:15:42 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 8214219B504; Thu, 29 Jul 2004 21:07:16 -0400 (EDT)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id D626F19B49C;
	Thu, 29 Jul 2004 21:07:15 -0400 (EDT)
Received: from [192.168.1.100] (mercury.arin.net [127.0.0.1])
	by mercury.arin.net (Postfix) with ESMTP id 724A9CF394;
	Thu, 29 Jul 2004 21:15:40 -0400 (EDT)
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a06020403bd2f4d764c4b@[192.168.1.100]>
In-Reply-To: <Pine.LNX.4.44.0407300030520.25726-100000@netcore.fi>
References: <Pine.LNX.4.44.0407300030520.25726-100000@netcore.fi>
Date: Thu, 29 Jul 2004 21:15:36 -0400
To: Pekka Savola <pekkas@netcore.fi>
From: Edward Lewis <edlewis@arin.net>
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
Cc: Edward Lewis <edlewis@arin.net>, <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.0 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 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. ;)

A DNS server makes no assurance of the accuracy, etc., of the data it 
serves.  The server makes no temporal statement of the data either. 
(DNSSEC only "protects" the transfer of data from where the 
administrator enters it to the resolver that last performs the check.)

Also, the servers are not the (ultimate) authority for the data. 
They are just the "publication" mechanism.  (That's when DNSSEC has 
something else sign the data, and has the authoritative servers load 
signed data.)

Statements like "DNS server asserts...will be valid" indicate 
expectations of what DNS does that are higher than reality.  DNS is 
just a plain old, vanilla look up service.

>Similarly, consider a mechanism like SCTP or HIP which ties multiple
>addresses to a connection.  A hostname might map to 1..N addresses
>when the connection is established; during the lifetime of the
>connection, the hostname could change to point to an entirely
>different set of addresses.  Depending on how the new addresses
>corresponding to the end-points are discovered during the session,
>this TTL information could be quite useful -- as a means to trigger
>how often one should poll for new information (instead of an arbitrary
>interval).

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.  That an 
application element needs to get new data from the DNS ought to be 
triggered by an event internal to the application (such as a sudden 
failure of one application element in hearing from a remote  element).

>There are probably better examples as well..

And this is another troubling statement to me.  The SIKED BOF said 
the same thing and we got grilled.  Unless we have a good taxonomy of 
how DNS is going to be fit under applications, it's hard to know that 
we are designing a "level above DNS" that is as level a playing field 
as the DNS interface.

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. 
 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."

Even if it seems tempting...

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.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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  Sat Jul 31 21:46: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 VAA28167
	for <dnsop-archive@lists.ietf.org>; Sat, 31 Jul 2004 21:46: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 i710KRXQ018057;
	Sat, 31 Jul 2004 17:20:27 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i710KRSX018056;
	Sat, 31 Jul 2004 17:20:27 -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 i710KOja018030
	for <dnsop@lists.uoregon.edu>; Sat, 31 Jul 2004 17:20:24 -0700 (PDT)
Received: by coconut.itojun.org (Postfix, from userid 1001)
	id 2854D1C0C4; Sun,  1 Aug 2004 09:14:19 +0900 (JST)
To: Erik.Nordmark@sun.com
Cc: miekg@atoom.net, pekkas@netcore.fi, namedroppers@ops.ietf.org,
        dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Re: getaddrinfo/TTL and resolver application-interface
In-Reply-To: Your message of "Thu, 29 Jul 2004 00:49:41 -0700 (PDT)"
	<Roam.SIMC.2.0.6.1091087381.20429.nordmark@bebop.france>
References: <Roam.SIMC.2.0.6.1091087381.20429.nordmark@bebop.france>
X-Mailer: Cue version 0.8 (040717-1035/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20040801001419.2854D1C0C4@coconut.itojun.org>
Date: Sun,  1 Aug 2004 09:14:19 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: itojun@itojun.org (Jun-ichiro itojun Hagino)

> On the other hand, introducing an new ai_ttl field at the end of struct
> addrinfo can be done without any effect on binaries (since the field offsets of
> the other fields do not change, and freeaddrinfo() will free the correct size
> structure). Applications which want to use ai_ttl would then do
> 
> 	call getaddrinfo...
> #ifdef _GETADDRINFO_AI_TTL
> 	ttl = ai->ai_tll;
> #else
> 	ttl = 30;	/* Or some other constant */
> #endif
> 
> While this is more painful than if we'd included ai_ttl from the start,
> it seems to be less painful than standardizing getrrsetbyname() to
> ensure portability of that interface across platforms.

	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?

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


