From owner-dnsop@cafax.se  Fri Aug  1 00:30:14 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26147
	for <dnsop-archive@lists.ietf.org>; Fri, 1 Aug 2003 00:30:13 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h713xM8W001762
	for <dnsop-outgoing@nic.cafax.se>; Fri, 1 Aug 2003 05:59:22 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h713xM7B001761
	for dnsop-outgoing; Fri, 1 Aug 2003 05:59:22 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h713xJ8W001756
	for <dnsop@cafax.se>; Fri, 1 Aug 2003 05:59:20 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308010344.MAA01087@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id MAA01087; Fri, 1 Aug 2003 12:44:00 +0900
Subject: Re: avoiding proxies
In-Reply-To: <C331E5A29B51A84E9755E834A3E619D10F9F7A@ftrdmel1.rd.francetelecom.fr>
 from BELOEIL Luc FTRD/DMI/CAE at "Jul 31, 2003 05:32:05 pm"
To: BELOEIL Luc FTRD/DMI/CAE <luc.beloeil@francetelecom.com>
Date: Fri, 1 Aug 2003 12:44:00 +0859 ()
CC: "Eric A. Hall" <ehall@ehsco.com>, dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Luc;

> > > On the Internet, the mechanism to relay requests to servers over
> > > multiple links is called routing.
> > 
> > Exactly, let's let routing do the job it is supposed to be providing
> > already anyway, rather than layering on even more mandatory services.
> > 
> 
> Ok I may understand what do you wanna say. 
> 1- we could use multicast to transport DNS requests. But multicast is
> not easy to deploy within access networks such as xDSL, RTC... (NBMA
> links)

I hope Eric recognizes that ring search with multicast is an
application layer attempt to poorly imitate a routing protocol.

> 2- we could use anycast
> 
> But it is not clear for me how we could use DNSSEC in such scheme. There
> is still and perhaps a bigger issue there if we need to distribute keys.
> (I do not argue that RA-based solution is better there ;+)

Read the draft on security considerations and never say autoconfigured
security.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  1 05:23:01 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03605
	for <dnsop-archive@lists.ietf.org>; Fri, 1 Aug 2003 05:22:59 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h718tW8W003079
	for <dnsop-outgoing@nic.cafax.se>; Fri, 1 Aug 2003 10:55:32 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h718tWPG003078
	for dnsop-outgoing; Fri, 1 Aug 2003 10:55:32 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h718tU8W003073
	for <dnsop@cafax.se>; Fri, 1 Aug 2003 10:55:30 +0200 (MEST)
Received: from FTRDMEL1.rd.francetelecom.fr ([10.193.117.152]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 1 Aug 2003 10:55:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: avoiding proxies
Date: Fri, 1 Aug 2003 10:55:23 +0200
Message-ID: <C331E5A29B51A84E9755E834A3E619D10F9F7B@ftrdmel1.rd.francetelecom.fr>
Thread-Topic: avoiding proxies
Thread-Index: AcNX5A/LUwmZW95cRemwx45dLMkZNAAJPIZA
From: "BELOEIL Luc FTRD/DMI/CAE" <luc.beloeil@francetelecom.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>
Cc: "Eric A. Hall" <ehall@ehsco.com>, <dnsop@cafax.se>
X-OriginalArrivalTime: 01 Aug 2003 08:55:25.0597 (UTC) FILETIME=[A61754D0:01C3580A]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nic.cafax.se id h718tV8W003074
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Masataka,

> -----Message d'origine-----
> De : Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]
> Envoye : vendredi 1 aout 2003 05:45
> > 2- we could use anycast
> > 
> > But it is not clear for me how we could use DNSSEC in such 
> scheme. There
> > is still and perhaps a bigger issue there if we need to 
> distribute keys.
> > (I do not argue that RA-based solution is better there ;+)
> 
> Read the draft on security considerations and never say autoconfigured
> security.
> 
> 							Masataka Ohta
> 

I've just read quickly you draft.

First point, 
I'm impressed that you dare say that you ask client to use no security.
(I hope I have missed nothing). Indeed we are not using any security
within current operational and commercial network for home residential
customers, and that works, this is a fact. I do know if we should
impose cryptography in all IP datagrams, but I feel that IETF want to
propose the option if needed.

Second point, 
I guess if Firewall will must be aware of anycast way of working,
because incoming datagrams may not have a source address = to anycast
destination address of outcoming datagrams. Did I miss something ?

Third point,
servers and client will must be able to manage anycast address in
different manner if UPd or TCP is used. Is it easy to implement ?

Luc

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  1 08:41:38 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07661
	for <dnsop-archive@lists.ietf.org>; Fri, 1 Aug 2003 08:41:37 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h71C9Z8W004107
	for <dnsop-outgoing@nic.cafax.se>; Fri, 1 Aug 2003 14:09:35 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h71C9ZVq004106
	for dnsop-outgoing; Fri, 1 Aug 2003 14:09:35 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h71C9X8W004101
	for <dnsop@cafax.se>; Fri, 1 Aug 2003 14:09:34 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308011158.UAA00543@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id UAA00543; Fri, 1 Aug 2003 20:58:33 +0900
Subject: Re: avoiding proxies
In-Reply-To: <C331E5A29B51A84E9755E834A3E619D10F9F7B@ftrdmel1.rd.francetelecom.fr>
 from BELOEIL Luc FTRD/DMI/CAE at "Aug 1, 2003 10:55:23 am"
To: BELOEIL Luc FTRD/DMI/CAE <luc.beloeil@francetelecom.com>
Date: Fri, 1 Aug 2003 20:58:33 +0859 ()
CC: "Eric A. Hall" <ehall@ehsco.com>, dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Luc;

> > Read the draft on security considerations and never say autoconfigured
> > security.

> I've just read quickly you draft.

Do read the draft, carefully and thoroughly.

> First point, 
> I'm impressed that you dare say that you ask client to use no security.

NO.

> (I hope I have missed nothing).

You have missed all.

> I do know if we should
> impose cryptography in all IP datagrams, but I feel that IETF want to
> propose the option if needed.

Yup.

> Second point, 
> I guess if Firewall will must be aware of anycast way of working,

No.

> because incoming datagrams may not have a source address = to anycast
> destination address of outcoming datagrams. Did I miss something ?

A site is free to have any policy on its firewalls.

The site may simply believe its ISP.

> Third point,
> servers and client will must be able to manage anycast address in
> different manner if UPd or TCP is used.

Wrong. Read the draft and RFC103[45].

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  1 22:06:15 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20108
	for <dnsop-archive@lists.ietf.org>; Fri, 1 Aug 2003 22:06:14 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h721Xp8W010145
	for <dnsop-outgoing@nic.cafax.se>; Sat, 2 Aug 2003 03:33:51 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h721XpgE010144
	for dnsop-outgoing; Sat, 2 Aug 2003 03:33:51 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h721Xk8W010139
	for <dnsop@cafax.se>; Sat, 2 Aug 2003 03:33:48 +0200 (MEST)
Received: from paulnb (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h721lHS23938;
	Sat, 2 Aug 2003 10:47:18 +0900 (KST)
Message-ID: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: "DNSOP WG" <dnsop@cafax.se>
Cc: <hinden@iprg.nokia.com>, <randy@psg.com>, <narten@us.ibm.com>,
        <mrw@windriver.com>, "David Meyer" <dmm@1-4-5.net>,
        "Rob Austein" <sra@hactrn.net>, "autonet" <autonet@ipv6.or.kr>,
        <hclee_shep@etri.re.kr>
Subject: Policy of IPv6 DNS Discovery
Date: Sat, 2 Aug 2003 10:32:42 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001F_01C358E1.6795C3E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-dnsop@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_001F_01C358E1.6795C3E0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: base64

SGVsbG8gYWxsLA0KDQpUaGFua3MgZm9yIHlvdXIgaW5zaWdodGZ1bCBzdWdnZXN0aW9ucyBhbmQg
Y29tbWVudHMuDQpGb3IgRE5TIERpc2NvdmVyeSwgd2UgaGF2ZSBiZWVuIGRpc2N1c3NpbmcgbXVj
aC4NCklNSE8sIGV2ZXJ5IHRlY2hub2xvZ3kgaGFzIGl0cyBvd24gYXBwbGljYXRpb24gZG9tYWlu
Lg0KVW50aWwgbm93LCBzZXZlcmFsIHByb3Bvc2l0aW9ucyBmb3IgRE5TIERpc2NvdmVyeSBoYXZl
IGJlZW4gc3VnZ2VzdGVkIGFuZCBkaXNjdXNzZWQuDQpBIHVuaXF1ZSBzb2x1dGlvbiBjYW4gbm90
IGNvdmVyIGV2ZXJ5IGVudmlyb25tZW50LCBJIHRoaW5rLg0KREhDUHY2LCBSQSwgQW55Y2FzdCBh
bmQgTXVsdGljYXN0IGFwcHJvYWNoZXMgaGF2ZSBpdHMgZG9tYWluLg0KSWYgZWFjaCBhcHBsaWNh
YmlsaXR5IGlzIHJlYXNvbmFibGUsIGl0IGlzIHZhbHVhYmxlIHRvIGRldmVsb3AgaXQgYW5kIGFk
b3B0IGl0Lg0KQXMgb25lIG9mIFJBIGNhbXAsIEkgdGhpbmssIFJBLWFwcHJvYWNoIGlzIHVzZWZ1
bCBpbiBzb21lIG9mIHdpcmVsZXNzIG5ldHdvcmtzLA0Kc3VjaCBhcyBITUlQdjYsIE1BTkVUIGNv
bm5lY3RlZCB0byB0aGUgSW50ZXJuZXQgYW5kIE5FTU8uDQpZb3UgY2FuIHJlZmVyIHRvIGVhY2gg
YXBwbGljYXRpb24gaW4gdGhlIGZvbGxvd2luZyBsaW5rczsNCg0KIC0gSE1JUHY2OiANCiAgIGh0
dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWplb25nLWhtaXB2Ni1kbnMt
b3B0aW1pemF0aW9uLTAxLnR4dA0KICAgaHR0cDovL3d3dy5hZGhvYy42YW50cy5uZXQvfnBhdWwv
cHVibGljYXRpb25zL2ludGVybmF0aW9uYWwtY29uZmVyZW5jZS92dGMyMDAzLWZhbGwtamFlaG9v
bi5wZGYNCg0KIC0gTUFORVQgYW5kIE5FTU86DQogICBodHRwOi8vd3d3LmFkaG9jLjZhbnRzLm5l
dC9+cGF1bC9wdWJsaWNhdGlvbnMvaW50ZXJuYXRpb25hbC1jb25mZXJlbmNlL3BpbXJjMjAwMy1q
YWVob29uLnBkZg0KDQpSQS1iYXNlZCBETlMgRGlzY292ZXJ5IGlzIGVmZmljaWVudCB3aGVuIGFk
ZHJlc3MgYXV0b2NvbmZpZ3VyYXRpb24gc2hvdWxkIGJlDQpwZXJmb3JtZWQgdGhyb3VnaCBSQSwg
YmVjYXVzZSBpdCBuZWVkcyBub3QgYWRkaXRpb25hbCBkaXNjb3ZlcnkuDQpGb3IgZXhhbXBsZSwg
aWYgTUFQIG9wdGlvbiBhbmQgRE5TIG9wdGlvbiBpbiBhbiBSQSBtZXNzYWdlIGFyZSBkZWxpdmVy
ZWQgaW4gSE1JUHY2LA0KdGhlcmUgaXMgbm8gZGVsYXkgdG8gZGlzY292ZXIgRE5TIGluZm9ybWF0
aW9uLiBUaGlzIHNjaGVtZSBsZWFkcyB0byB0aGUgb3B0aW1pemF0aW9uDQpvZiBETlMgbmFtZSBy
ZXNvbHV0aW9uIG93aW5nIHRvIHVzaW5nIHRoZSBsb2NhbCByZWN1cnNpdmUgRE5TIHNlcnZlciB3
aXRoaW4gdGhlIE1BUCBkb21haW4uDQoNCkluIE1BTkVUIGNvbm5lY3RlZCB0byB0aGUgSW50ZXJu
ZXQsIHRoZSBiaW5kaW5nIG9mIGdsb2JhbCBJUHY2IGFkZHJlc3MgaXMgbmVlZGVkDQp0byBjb21t
dW5pY2F0ZSB3aXRoIGFuIEludGVybmV0IG5vZGUuIFJBLWJhc2VkIGFwcHJvYWNoIGlzIHN1Z2dl
c3RlZCBhcyBmb2xsb3dzOw0KICBodHRwOi8vcGVvcGxlLm5va2lhLm5ldC9+Y2hhcmxpZXAvdHh0
L2FvZHZpZC9nbG9iYWx2Ni50eHQNCg0KSW4gdGhpcyBjYXNlLCB0aGUgYWRkcmVzcyBvZiByZWN1
cnNpdmUgRE5TIHNlcnZlciBpcyBuZWVkZWQgZm9yIHJlc29sdmluZyB0aGUgZ2xvYmFsIEROUyAN
Cm5hbWUuIEROUyBvcHRpb24gaXMgYWxzbyBpbmRpc3BlbnNpYmxlIHRvIHRoaXMgYXBwcm9hY2gu
DQoNCklmIHdlIGRvIG5vdCBhZG9wdCBSQS1iYXNlZCBETlMgRGlzY292ZXJ5LCB0aGVyZSB3aWxs
IGJlIGxpbWl0YXRpb24gaW4gc29tZSBkb21haW5zLg0KDQpCYXNpY2FsbHksIGluIG1vc3Qgb2Yg
dGhlIGN1cnJlbnQgIElQdjYgTEFOcywgTkQtYmFzZWQgc3RhdGVsZXNzIGFkZHJlc3MgYXV0b2Nv
bmZpZ3VyYXRpb24NCmlzIHVzZWQgZm9yIGFkZHJlc3MgYXV0b2NvbmZpZ3VyYXRpb24gcmF0aGVy
IHRoYW4gc3RhdGVmdWwgREhDUCBhcHByb2FjaC4NCkluIElQdjYgc3RhdGVsZXNzIGF1dG9jb25m
aWd1cmF0aW9uLCBETlMgZGlzY292ZXJ5IGlzIGEgYmlnIGxhY2sgaW4gdGhlIGJhc2ljIElQdjYg
bmV0d29ya2luZyBzZXJ2aWNlLiANCklmIEROUyBkaXNjb3ZlcnkgaXMgcHJvdmlkZWQgdmlhIFJB
IG1lc3NhZ2UsIEkgYmVsaWV2ZSwgbW9zdCBvZiBJUHY2IExBTnMgd2lsbCBkbyB3aXRob3V0IERI
Q1B2Ni4NCkFzIHlvdSBrbm93LCBpbiBtb3N0IG9mIElQdjQgTEFOcywgdGhyb3VnaCBESENQLCB3
ZSBnZXQgb25seSBJUCBhZGRyZXNzIGFuZCBETlMgaW5mb3JtYXRpb24sDQphbHRob3VnaCBiZWlu
ZyBhYmxlIHRvIGdldCBvdGhlciBpbXBvcnRhbnQgcGFyYW1ldGVycy4NClRoZXJlZm9yZSwgaWYg
TkQgcHJvdmlkZXMgSVB2NiBob3N0cyB3aXRoIEROUyBpbmZvcm1hdGlvbiBhcyB3ZWxsIGFzIElQ
djYgcHJlZml4LA0KdGhlIGhvc3RzIHdpbGwgbmVhcmx5IGhhdmUgbm8gaW5jb252ZW5pZW5jZSBp
biBiYXNpYyBJUHY2IG5ldHdvcmtpbmcuDQpJbiB0aGUgZW52aXJvbm1lbnQgd2hlcmUgdGhlcmUg
aXMgbmVlZCB0byBhdXRvY29uZmlndXJlIG1vcmUgb3RoZXIgcGFyYW1ldGVycywgDQpzdWNoIGFz
IE5UUCBzZXJ2ZXIgYW5kIFdlYi1wcm94eSwgREhDUHY2IGNhbiBiZSB1c2VkIHdlbGwuDQoNCklN
SE8sIHRoZSBkZXZlbG9wbWVudCBvZiBSQS1iYXNlZCBETlMgRGlzY292ZXJ5IGJlbG9uZ3MgdG8g
SVB2NiB3Zywgbm90IEROU09QIHdnLA0KYmVjYXVzZSBpdCBpcyB0aGUgZXh0ZW5zaW9uIG9mIElQ
djYgcHJvdG9jb2wsIG5vdCBETlMgcHJvdG9jb2wuDQpIb3dldmVyLCBpbiBteSBtZW1vcnksIFRo
b21hcyBOYXJ0ZW4sIEludGVybmV0IEFyZWEgRGlyZWN0b3IsIHNhaWQgdGhhdCBJUHY2IEROUyBE
aXNjb3ZlcnkNCnNob3VsZCBiZSBoYW5kbGVkIGluIEROU09QIHdnLg0KSWYgc28sIEkgdGhpbmss
IHRoZSBleHRlbnNpb24gb2YgSVB2NiBwcm90b2NvbCBmb3IgRE5TIERpc2NvdmVyeSBjYW4gYmUg
ZGlzY3Vzc2VkIGluIEROU09QIHdnLg0KDQpJbiBjb25jbHVzaW9uLCBJIGFtIHN1cmUsIElQdjYg
cHJvdG9jb2wgaXRzZWxmIG5lZWRzIE5ELWJhc2VkIEROUyBhdXRvY29uZmlndXJhdGlvbi4NCkxl
dCB0aGUgYXV0b2NvbmZpZ3VyYXRpb24gb2Ygb3RoZXIgcGFyYW1ldGVycyBleGNlcHQgRE5TIGlu
Zm9ybWF0aW9uIHByb2Nlc3NlZCBieSBESENQdjYuIA0KDQpJdCBzZWVtcyBiZSB0aW1lIGZvciBy
ZWxhdGVkIEFEcyBhbmQgQ2hhaXJzIHRvIG5lZ290aWF0ZSBhbmQgZGVjaWRlIHRoZSBwb2xpY3kg
Zm9yIEROUyBkaXNjb3ZlcnkuDQpBZnRlciB0aGF0LCB3ZSBlbmdpbmVlcnMgd2lsbCBiZSBhYmxl
IHRvIGRldmVsb3AgbW9yZSBwcmFjdGljYWwgc29sdXRpb24gbWVjaGFuaXNtcyBhY2NvcmRpbmcg
dG8gdGhlIGRpcmVjdGlvbi4NCg0KVGhhbmtzLg0KDQovSmFlaG9vbiBQYXVs

------=_NextPart_000_001F_01C358E1.6795C3E0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXdpbmRvd3MtMTI1MiI+DQo8TUVUQSBjb250ZW50PSJNU0hU
TUwgNi4wMC4yODAwLjExMDYiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hF
QUQ+DQo8Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPkhlbGxvIGFsbCw8L0RJVj4NCjxESVY+
PEZPTlQgZmFjZT0mIzQ0NDA0OyYjNDc1NDg7PjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+VGhh
bmtzIGZvciB5b3VyIGluc2lnaHRmdWwgc3VnZ2VzdGlvbnMgYW5kIGNvbW1lbnRzLjxCUj5Gb3Ig
RE5TIERpc2NvdmVyeSwgDQp3ZSBoYXZlIGJlZW4gZGlzY3Vzc2luZyBtdWNoLjxCUj5JTUhPLCBl
dmVyeSB0ZWNobm9sb2d5IGhhcyBpdHMgb3duIGFwcGxpY2F0aW9uIA0KZG9tYWluLjxCUj5VbnRp
bCBub3csIHNldmVyYWwgcHJvcG9zaXRpb25zIGZvciBETlMgRGlzY292ZXJ5IGhhdmUgYmVlbiBz
dWdnZXN0ZWQgDQphbmQgZGlzY3Vzc2VkLjxCUj5BIHVuaXF1ZSBzb2x1dGlvbiBjYW4gbm90IGNv
dmVyIGV2ZXJ5IGVudmlyb25tZW50LCBJIA0KdGhpbmsuPEJSPkRIQ1B2NiwgUkEsIEFueWNhc3Qg
YW5kIE11bHRpY2FzdCBhcHByb2FjaGVzIGhhdmUgaXRzIGRvbWFpbi48QlI+SWYgDQplYWNoIGFw
cGxpY2FiaWxpdHkgaXMgcmVhc29uYWJsZSwgaXQgaXMgdmFsdWFibGUgdG8gZGV2ZWxvcCBpdCBh
bmQgYWRvcHQgDQppdC48QlI+QXMgb25lIG9mIFJBIGNhbXAsIEkgdGhpbmssIFJBLWFwcHJvYWNo
IGlzIHVzZWZ1bCBpbiBzb21lIG9mIHdpcmVsZXNzIA0KbmV0d29ya3MsPEJSPnN1Y2ggYXMgSE1J
UHY2LCBNQU5FVCBjb25uZWN0ZWQgdG8gdGhlIEludGVybmV0IGFuZCBORU1PLjxCUj5Zb3UgDQpj
YW4gcmVmZXIgdG8gZWFjaCBhcHBsaWNhdGlvbiBpbiB0aGUgZm9sbG93aW5nIGxpbmtzOzwvRElW
Pg0KPERJVj48QlI+Jm5ic3A7LSBITUlQdjY6IDxCUj4mbmJzcDsmbmJzcDsgPEEgDQpocmVmPSJo
dHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qZW9uZy1obWlwdjYtZG5z
LW9wdGltaXphdGlvbi0wMS50eHQiPmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRz
L2RyYWZ0LWplb25nLWhtaXB2Ni1kbnMtb3B0aW1pemF0aW9uLTAxLnR4dDwvQT48QlI+Jm5ic3A7
Jm5ic3A7IA0KPEEgDQpocmVmPSJodHRwOi8vd3d3LmFkaG9jLjZhbnRzLm5ldC9+cGF1bC9wdWJs
aWNhdGlvbnMvaW50ZXJuYXRpb25hbC1jb25mZXJlbmNlL3Z0YzIwMDMtZmFsbC1qYWVob29uLnBk
ZiI+aHR0cDovL3d3dy5hZGhvYy42YW50cy5uZXQvfnBhdWwvcHVibGljYXRpb25zL2ludGVybmF0
aW9uYWwtY29uZmVyZW5jZS92dGMyMDAzLWZhbGwtamFlaG9vbi5wZGY8L0E+PC9ESVY+DQo8RElW
PiZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDstIE1BTkVUIGFuZCBORU1POjxCUj4mbmJzcDsmbmJz
cDsgPEEgDQpocmVmPSJodHRwOi8vd3d3LmFkaG9jLjZhbnRzLm5ldC9+cGF1bC9wdWJsaWNhdGlv
bnMvaW50ZXJuYXRpb25hbC1jb25mZXJlbmNlL3BpbXJjMjAwMy1qYWVob29uLnBkZiI+aHR0cDov
L3d3dy5hZGhvYy42YW50cy5uZXQvfnBhdWwvcHVibGljYXRpb25zL2ludGVybmF0aW9uYWwtY29u
ZmVyZW5jZS9waW1yYzIwMDMtamFlaG9vbi5wZGY8L0E+PC9ESVY+DQo8RElWPiZuYnNwOzwvRElW
Pg0KPERJVj5SQS1iYXNlZCBETlMgRGlzY292ZXJ5IGlzIGVmZmljaWVudCB3aGVuIGFkZHJlc3Mg
YXV0b2NvbmZpZ3VyYXRpb24gc2hvdWxkIA0KYmU8QlI+cGVyZm9ybWVkIHRocm91Z2ggUkEsIGJl
Y2F1c2UgaXQgbmVlZHMgbm90IGFkZGl0aW9uYWwgZGlzY292ZXJ5LjxCUj5Gb3IgDQpleGFtcGxl
LCBpZiBNQVAgb3B0aW9uIGFuZCBETlMgb3B0aW9uIGluIGFuIFJBIG1lc3NhZ2UgYXJlIGRlbGl2
ZXJlZCBpbiANCkhNSVB2Niw8QlI+dGhlcmUgaXMgbm8gZGVsYXkgdG8gZGlzY292ZXIgRE5TIGlu
Zm9ybWF0aW9uLiBUaGlzIHNjaGVtZSBsZWFkcyB0byANCnRoZSBvcHRpbWl6YXRpb248QlI+b2Yg
RE5TIG5hbWUgcmVzb2x1dGlvbiBvd2luZyB0byB1c2luZyB0aGUgbG9jYWwgcmVjdXJzaXZlIA0K
RE5TIHNlcnZlciB3aXRoaW4gdGhlIE1BUCBkb21haW4uPC9ESVY+DQo8RElWPjxGT05UIGZhY2U9
JiM0NDQwNDsmIzQ3NTQ4OyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj5JbiBNQU5F
VCBjb25uZWN0ZWQgdG8gdGhlIEludGVybmV0LCB0aGUgYmluZGluZyBvZiBnbG9iYWwgSVB2NiBh
ZGRyZXNzIGlzIA0KbmVlZGVkPEJSPnRvIGNvbW11bmljYXRlIHdpdGggYW4gSW50ZXJuZXQgbm9k
ZS4gUkEtYmFzZWQgYXBwcm9hY2ggaXMgc3VnZ2VzdGVkIA0KYXMgZm9sbG93czs8QlI+Jm5ic3A7
IDxBIA0KaHJlZj0iaHR0cDovL3Blb3BsZS5ub2tpYS5uZXQvfmNoYXJsaWVwL3R4dC9hb2R2aWQv
Z2xvYmFsdjYudHh0Ij5odHRwOi8vcGVvcGxlLm5va2lhLm5ldC9+Y2hhcmxpZXAvdHh0L2FvZHZp
ZC9nbG9iYWx2Ni50eHQ8L0E+PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5JbiB0aGlz
IGNhc2UsIHRoZSBhZGRyZXNzIG9mIHJlY3Vyc2l2ZSBETlMgc2VydmVyIGlzIG5lZWRlZCBmb3Ig
cmVzb2x2aW5nIA0KdGhlIGdsb2JhbCBETlMgPEJSPm5hbWUuIEROUyBvcHRpb24gaXMgYWxzbyBp
bmRpc3BlbnNpYmxlIHRvIHRoaXMgDQphcHByb2FjaC48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+
DQo8RElWPklmIHdlIGRvIG5vdCBhZG9wdCBSQS1iYXNlZCBETlMgRGlzY292ZXJ5LCB0aGVyZSB3
aWxsIGJlIGxpbWl0YXRpb24gaW4gc29tZSANCmRvbWFpbnMuPC9ESVY+DQo8RElWPiZuYnNwOzwv
RElWPg0KPERJVj5CYXNpY2FsbHksIGluIG1vc3Qgb2YgdGhlIGN1cnJlbnQmbmJzcDsgSVB2NiBM
QU5zLCBORC1iYXNlZCBzdGF0ZWxlc3MgDQphZGRyZXNzIGF1dG9jb25maWd1cmF0aW9uPEJSPmlz
IHVzZWQgZm9yIGFkZHJlc3MgYXV0b2NvbmZpZ3VyYXRpb24gcmF0aGVyIHRoYW4gDQpzdGF0ZWZ1
bCBESENQIGFwcHJvYWNoLjxCUj5JbiBJUHY2IHN0YXRlbGVzcyBhdXRvY29uZmlndXJhdGlvbiwg
RE5TIGRpc2NvdmVyeSBpcyANCmEgYmlnIGxhY2sgaW4gdGhlIGJhc2ljIElQdjYgbmV0d29ya2lu
ZyBzZXJ2aWNlLiA8QlI+SWYgRE5TIGRpc2NvdmVyeSBpcyANCnByb3ZpZGVkIHZpYSBSQSBtZXNz
YWdlLCBJIGJlbGlldmUsIG1vc3Qgb2YgSVB2NiBMQU5zIHdpbGwgZG8gd2l0aG91dCANCkRIQ1B2
Ni48QlI+QXMgeW91IGtub3csIGluIG1vc3Qgb2YgSVB2NCBMQU5zLCB0aHJvdWdoIERIQ1AsIHdl
IGdldCBvbmx5IElQIA0KYWRkcmVzcyBhbmQgRE5TIGluZm9ybWF0aW9uLDxCUj5hbHRob3VnaCBi
ZWluZyBhYmxlIHRvIGdldCBvdGhlciBpbXBvcnRhbnQgDQpwYXJhbWV0ZXJzLjxCUj5UaGVyZWZv
cmUsIGlmIE5EIHByb3ZpZGVzIElQdjYgaG9zdHMgd2l0aCBETlMgaW5mb3JtYXRpb24gYXMgd2Vs
bCANCmFzIElQdjYgcHJlZml4LDxCUj50aGUgaG9zdHMgd2lsbCBuZWFybHkgaGF2ZSBubyBpbmNv
bnZlbmllbmNlIGluIGJhc2ljIElQdjYgDQpuZXR3b3JraW5nLjxCUj5JbiB0aGUgZW52aXJvbm1l
bnQgd2hlcmUgdGhlcmUgaXMgbmVlZCB0byBhdXRvY29uZmlndXJlIG1vcmUgDQpvdGhlciBwYXJh
bWV0ZXJzLCA8QlI+c3VjaCBhcyBOVFAgc2VydmVyIGFuZCBXZWItcHJveHksIERIQ1B2NiBjYW4g
YmUgdXNlZCANCndlbGwuPC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5JTUhPLCB0aGUg
ZGV2ZWxvcG1lbnQgb2YgUkEtYmFzZWQgRE5TIERpc2NvdmVyeSBiZWxvbmdzIHRvIElQdjYgd2cs
IG5vdCANCkROU09QIHdnLDxCUj5iZWNhdXNlIGl0IGlzIHRoZSBleHRlbnNpb24gb2YgSVB2NiBw
cm90b2NvbCwgbm90IEROUyANCnByb3RvY29sLjxCUj5Ib3dldmVyLCBpbiBteSBtZW1vcnksIFRo
b21hcyBOYXJ0ZW4sIEludGVybmV0IEFyZWEgRGlyZWN0b3IsIHNhaWQgDQp0aGF0IElQdjYgRE5T
IERpc2NvdmVyeTxCUj5zaG91bGQgYmUgaGFuZGxlZCBpbiBETlNPUCB3Zy48QlI+SWYgc28sIEkg
dGhpbmssIHRoZSANCmV4dGVuc2lvbiBvZiBJUHY2IHByb3RvY29sIGZvciBETlMgRGlzY292ZXJ5
IGNhbiBiZSBkaXNjdXNzZWQgaW4gRE5TT1Agd2cuPC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0K
PERJVj5JbiBjb25jbHVzaW9uLCBJIGFtIHN1cmUsIElQdjYgcHJvdG9jb2wgaXRzZWxmIG5lZWRz
IE5ELWJhc2VkIEROUyANCmF1dG9jb25maWd1cmF0aW9uLjxCUj5MZXQgdGhlIGF1dG9jb25maWd1
cmF0aW9uIG9mIG90aGVyIHBhcmFtZXRlcnMgZXhjZXB0IEROUyANCmluZm9ybWF0aW9uIHByb2Nl
c3NlZCBieSBESENQdjYuIDwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+SXQgc2VlbXMg
YmUgdGltZSBmb3IgcmVsYXRlZCBBRHMgYW5kIENoYWlycyB0byBuZWdvdGlhdGUgYW5kIGRlY2lk
ZSB0aGUgDQpwb2xpY3kgZm9yIEROUyBkaXNjb3ZlcnkuPEJSPkFmdGVyIHRoYXQsIHdlIGVuZ2lu
ZWVycyB3aWxsIGJlIGFibGUgdG8gZGV2ZWxvcCANCm1vcmUgcHJhY3RpY2FsIHNvbHV0aW9uIG1l
Y2hhbmlzbXMgYWNjb3JkaW5nIHRvIHRoZSBkaXJlY3Rpb24uPC9ESVY+DQo8RElWPiZuYnNwOzwv
RElWPg0KPERJVj5UaGFua3MuPC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj4vSmFlaG9v
biBQYXVsPC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_001F_01C358E1.6795C3E0--

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 00:44:36 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22479
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 00:44:35 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h724GG8W010825
	for <dnsop-outgoing@nic.cafax.se>; Sat, 2 Aug 2003 06:16:16 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h724GG1w010824
	for dnsop-outgoing; Sat, 2 Aug 2003 06:16:16 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h724G88W010819
	for <dnsop@cafax.se>; Sat, 2 Aug 2003 06:16:15 +0200 (MEST)
Received: from paulnb (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h724TSS25133;
	Sat, 2 Aug 2003 13:29:28 +0900 (KST)
Message-ID: <005a01c358ac$a09822d0$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: "Bill Manning" <bmanning@ISI.EDU>
Cc: "DNSOP WG" <dnsop@cafax.se>
References: <200308020405.h7245Ns06115@boreas.isi.edu>
Subject: Re: Policy of IPv6 DNS Discovery
Date: Sat, 2 Aug 2003 13:14:53 +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.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by nic.cafax.se id h724GG8W010820
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Bill,

My mail is as follows;
Maybe, you can see mine, now.

/Jaehoon Paul

-----------------------------------------------------------------------------------------------
Hello all,

Thanks for your insightful suggestions and comments.
For DNS Discovery, we have been discussing much.
IMHO, every technology has its own application domain.
Until now, several propositions for DNS Discovery have been suggested and discussed.
A unique solution can not cover every environment, I think.
DHCPv6, RA, Anycast and Multicast approaches have their own domain.
If each applicability is reasonable, it is valuable to develop it and adopt it.
As one of RA camp, I think, RA-approach is useful in some of wireless networks,
such as HMIPv6, MANET connected to the Internet and NEMO.
You can refer to each application in the following links;

 - HMIPv6: 
   http://www.ietf.org/internet-drafts/draft-jeong-hmipv6-dns-optimization-01.txt
   http://www.adhoc.6ants.net/~paul/publications/international-conference/vtc2003-fall-jaehoon.pdf

 - MANET and NEMO:
   http://www.adhoc.6ants.net/~paul/publications/international-conference/pimrc2003-jaehoon.pdf

RA-based DNS Discovery is efficient when address autoconfiguration should be
performed through RA, because it needs not additional discovery.
For example, if MAP option and DNS option in an RA message are delivered in HMIPv6,
there is no delay to discover DNS information. This scheme leads to the optimization
of DNS name resolution owing to using the local recursive DNS server within the MAP domain.

In MANET connected to the Internet, the binding of global IPv6 address is needed
to communicate with an Internet node. RA-based approach is suggested as follows;
  http://people.nokia.net/~charliep/txt/aodvid/globalv6.txt

In this case, the address of recursive DNS server is needed for resolving the global DNS 
name. DNS option is also indispensible to this approach.

If we do not adopt RA-based DNS Discovery, there will be limitation in some domains.

Basically, in most of the current  IPv6 LANs, ND-based stateless address autoconfiguration
is used for address autoconfiguration rather than stateful DHCP approach.
In IPv6 stateless autoconfiguration, DNS discovery is a big lack in the basic IPv6 networking service. 
If DNS discovery is provided via RA message, I believe, most of IPv6 LANs will do without DHCPv6.
As you know, in most of IPv4 LANs, through DHCP, we get only IP address and DNS information,
although being able to get other important parameters.
Therefore, if ND provides IPv6 hosts with DNS information as well as IPv6 prefix,
the hosts will nearly have no inconvenience in basic IPv6 networking.
In the environment where there is need to autoconfigure more other parameters, 
such as NTP server and Web-proxy, DHCPv6 can be used well.

IMHO, the development of RA-based DNS Discovery belongs to IPv6 wg, not DNSOP wg,
because it is the extension of IPv6 protocol, not DNS protocol.
However, in my memory, Thomas Narten, Internet Area Director, said that IPv6 DNS Discovery
should be handled in DNSOP wg.
If so, I think, the extension of IPv6 protocol for DNS Discovery can be discussed in DNSOP wg.

In conclusion, I am sure, IPv6 protocol itself needs ND-based DNS autoconfiguration.
Let the autoconfiguration of other parameters except DNS information processed by DHCPv6. 

It seems be time for related ADs and Chairs to negotiate and decide the policy for DNS discovery.
After that, we engineers will be able to develop more practical solution mechanisms according to the direction.

Thanks.

/Jaehoon Paul


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

----- Original Message ----- 
From: "Bill Manning" <bmanning@ISI.EDU>
To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
Cc: "Bill Manning" <bmanning@ISI.EDU>
Sent: Saturday, August 02, 2003 1:05 PM
Subject: Re: Policy of IPv6 DNS Discovery


> 
> [Charset Windows-1252 unsupported, skipping...]
> 
> I think you were trying to say something, but it renders
> as a non-supported character set.  Sorry about that.
> 
> 
> --bill
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).
> 

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 12:34:53 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16747
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 12:34:51 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72G9v8W013774
	for <dnsop-outgoing@nic.cafax.se>; Sat, 2 Aug 2003 18:09:57 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h72G9v5w013773
	for dnsop-outgoing; Sat, 2 Aug 2003 18:09:57 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72G9t8W013768
	for <dnsop@cafax.se>; Sat, 2 Aug 2003 18:09:56 +0200 (MEST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h72G9hM12054;
	Sat, 2 Aug 2003 09:09:43 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200308021609.h72G9hM12054@boreas.isi.edu>
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <005a01c358ac$a09822d0$c470fe81@etri.re.kr> from Jaehoon Paul Jeong at "Aug 2, 3 01:14:53 pm"
To: paul@etri.re.kr (Jaehoon Paul Jeong)
Date: Sat, 2 Aug 2003 09:09:43 -0700 (PDT)
Cc: bmanning@ISI.EDU, dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

% Hi Bill,
% 
% My mail is as follows;
% Maybe, you can see mine, now.
% 
% /Jaehoon Paul
% 
% -----------------------------------------------------------------------------------------------
% Hello all,
% 
% Thanks for your insightful suggestions and comments.
% For DNS Discovery, we have been discussing much.
% IMHO, every technology has its own application domain.

	In the case of Internet, I beg to differ.

% Until now, several propositions for DNS Discovery have been suggested and discussed.
% A unique solution can not cover every environment, I think.
% DHCPv6, RA, Anycast and Multicast approaches have their own domain.

	DNS, as a unique solution, covers all the environments
	you have currently specified, so perhaps more thought it 
	needed.  In any case...
	If you take this approach, you must also indicate which
	method takes priority when "domains" overlap.
	This also means you must define all possible domains.
	DHCPv4, DHCPv6, RA, Anycast, Multicast, LLMNR, TBDS,...
	how many are there?


% In conclusion, I am sure, IPv6 protocol itself needs ND-based DNS autoconfiguration.
% Let the autoconfiguration of other parameters except DNS information processed by DHCPv6. 

	It remains unclear to me how ND-based DNS autoconfiguration
	will be able decern the DNS admins policy profile and use
	ND-based DNS autoconfiguration accordingly.


% /Jaehoon Paul
% 
% ----- Original Message ----- 
% From: "Bill Manning" <bmanning@ISI.EDU>
% To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
% Cc: "Bill Manning" <bmanning@ISI.EDU>
% Sent: Saturday, August 02, 2003 1:05 PM
% Subject: Re: Policy of IPv6 DNS Discovery
% 
% 
% > 
% > [Charset Windows-1252 unsupported, skipping...]
% > 
% > I think you were trying to say something, but it renders
% > as a non-supported character set.  Sorry about that.
% > 
% > --bill


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 13:32:21 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17434
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 13:32:19 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72HBV8W014084
	for <dnsop-outgoing@nic.cafax.se>; Sat, 2 Aug 2003 19:11:31 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h72HBVdn014083
	for dnsop-outgoing; Sat, 2 Aug 2003 19:11:31 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72HBU8W014078
	for <dnsop@cafax.se>; Sat, 2 Aug 2003 19:11:31 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 0001D190E
	for <dnsop@cafax.se>; Sat,  2 Aug 2003 13:11:28 -0400 (EDT)
Date: Sat, 02 Aug 2003 13:11:28 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030802171129.0001D190E@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Sat, 2 Aug 2003 10:32:42 +0900, Jaehoon Jeong wrote:
> 
> A unique solution can not cover every environment, I think.

Sorry, but that turns out not to be the case.  It's fairly obvious to
anyone who has taken the trouble to understand how DHCP works that
DHCPv6-lite would work in pretty much every environment we've been
discussing.  Apparently some people just don't like DHCP.

> It seems be time for related ADs and Chairs to negotiate and decide
> the policy for DNS discovery.  After that, we engineers will be able
> to develop more practical solution mechanisms according to the
> direction.

I'm not sure why you insist on a public repetition of an exchange that
you and I already had when you pestered me about this in private, but
whatever.

The reason why this topic was moved from the IPv6 WG to the DNSOP WG
was to force a real discussion of requirements before proposing
solutions.  In particular, we're required to answer the question which
the IPv6 WG declined to ask: given DHCPv6 (including DHCPv6-lite),
what real need is there for further work in this space?  This
discussion is finally taking place on the DNSOP mailing list, albiet
in fits and starts.  Discussion of new protocol extensions (such as
your draft) will be in scope (for some WG, probably not DNSOP) if and
only if this discussion concludes that there's a gap between real
requirements and existing protocols.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 15:25:22 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20028
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 15:25:20 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72J1K8W014663
	for <dnsop-outgoing@nic.cafax.se>; Sat, 2 Aug 2003 21:01:20 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h72J1KLO014662
	for dnsop-outgoing; Sat, 2 Aug 2003 21:01:20 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72J1I8W014657
	for <dnsop@cafax.se>; Sat, 2 Aug 2003 21:01:19 +0200 (MEST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA10967;
	Sat, 2 Aug 2003 12:01:17 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h72J1HR01261;
	Sat, 2 Aug 2003 12:01:17 -0700
X-mProtect: <200308021901> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (209.157.142.164, claiming to be "spruce.iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdAddE2i; Sat, 02 Aug 2003 12:01:14 PDT
Message-Id: <4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 02 Aug 2003 12:00:13 -0700
To: Rob Austein <sra+dnsop@hactrn.net>
From: Bob Hinden <hinden@iprg.nokia.com>
Subject: Re: Policy of IPv6 DNS Discovery
Cc: dnsop@cafax.se
In-Reply-To: <20030802171129.0001D190E@thrintun.hactrn.net>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
 <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-dnsop@cafax.se
Precedence: bulk

Rob,

>The reason why this topic was moved from the IPv6 WG to the DNSOP WG
>was to force a real discussion of requirements before proposing
>solutions.  In particular, we're required to answer the question which
>the IPv6 WG declined to ask: given DHCPv6 (including DHCPv6-lite),
>what real need is there for further work in this space?  This

I think the IPv6 w.g. did answer this question several times.  It concluded 
that it did want a solution in addition to DCHPv6.  For example from the 
minutes of the Salt Lake City IETF in December 2001:

    Deering took poll of room: How many people think w.g. should continue
    work on stateless DNS discovery? Consensus to continue work.

and again in the minutes of the Yokohama Japan Thursday, July 2002:

    Wasserman took poll for choices listed. Results were:

    1) Continue w/ existing proposal, Proposed Standard or Experimental:

    Consensus to standardize short term solution
    Consensus to continue work on current proposal.

    2) Accept DHCP in addition to current work

    Consensus to continue working on DHCPv6

    3) Requirements: Important to further develop requirements?

    Small consensus to not work on requirements

    4) Consider new short term solution:

    N/A

Also, a specific solution draft was accepted as a working group item.

This work was later removed from the IPv6 w.g. charter by the IESG and 
moved to this working group.

I would also note that at the Vienna meeting, a "hum" was taken in the 
DNSOP group and there was not a consensus that there should only be a 
DHCPv6 solution to this problem.

I conclude from this that there is a significant number of people who think 
that a solution is needed in addition to DHCPv6.

Regards,
Bob







#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 17:18:38 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22409
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 17:18:37 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72Kqb8W015411
	for <dnsop-outgoing@nic.cafax.se>; Sat, 2 Aug 2003 22:52:37 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h72Kqbre015410
	for dnsop-outgoing; Sat, 2 Aug 2003 22:52:37 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72Kqa8W015405
	for <dnsop@cafax.se>; Sat, 2 Aug 2003 22:52:36 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id EF43D18EA
	for <dnsop@cafax.se>; Sat,  2 Aug 2003 16:52:34 -0400 (EDT)
Date: Sat, 02 Aug 2003 16:52:34 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
	<20030802171129.0001D190E@thrintun.hactrn.net>
	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030802205235.EF43D18EA@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Sat, 02 Aug 2003 12:00:13 -0700, Bob Hinden wrote:
> 
> I think the IPv6 w.g. did answer this question several times.  It concluded 
> that it did want a solution in addition to DCHPv6.  For example from the 
> minutes of the Salt Lake City IETF in December 2001:
> 
>     Deering took poll of room: How many people think w.g. should continue
>     work on stateless DNS discovery? Consensus to continue work.

And there's at least part of the problem.  "Stateless DNS discovery"
is not the same thing as "a solution in addition to DHCPv6" unless
"stateless" is just a euphemism for "anything but DHCP".  DHCPv6-lite
is also "stateless" for every definition of "stateless" that applies
to, eg, the RA-based proposals.  This confusion persisted through the
entire discussion in the IPv6 WG, and at least some of the arguments
in favor of RA-based or ND-based solutions on this list still appear
to originate in this confusion.

> and again in the minutes of the Yokohama Japan Thursday, July 2002:

Same problem.

> I would also note that at the Vienna meeting, a "hum" was taken in the 
> DNSOP group and there was not a consensus that there should only be a 
> DHCPv6 solution to this problem.

Correct.  Please see the message to which I was responding, which
called for an immediate decision in favor of a non-DHCP-based
solution.  I do not think that the discussion is over yet, which is
why I do not think an immediate decision is appropriate.

> I conclude from this that there is a significant number of people
> who think that a solution is needed in addition to DHCPv6.

And a significant number of people are still waiting to hear reasons
more substantial than "I don't like DHCP" (or, even worse, "I don't
understand DHCP but I know that I don't like it").

If there are serious -technical- reasons for why DHCP-lite is a bad
solution, fine, put 'em on the table.

Real issues I've heard so far:

1) Pekka points out that the DHCPv6 spec is a pretty big chunk of text
   for an implementor to have to read just to do a little discovery
   frob.  The DHC WG is already aware of this problem and is already
   working on a doc to help: see draft-ietf-dhc-dhcpv6-stateless-00.
   So I think this issue is under control.

2) Alain points out that having every node in a building poll at once
   when the building's power comes on can ruin one's afternoon.   I'm
   not as concerned about this as Alain is, but Alain has already come
   up with a proposal for an optional extension that will address his
   concern.  So I think that this issue is also under control.

3) Ohta-san has resurfaced the well-known-anycast hack.  Issues with
   this are already on record in the IPv6 WG list archives, so I won't
   restate them here, but I will note that sites which chose to do
   this with unicast addresses out of their own address space (as
   opposed to well-known unicast or anycast addresses) are already
   free to do so, and, indeed, I've been told that many ISPs already
   do this for v4 -- pretty much by definition, nobody but the ops
   staff at those ISPs would know.  At a high level, though, the key
   point here is that this is not new technology, and sites which
   chose to use it can do so already without further protocol work.

Other than the above, what I've heard has been the same tired refrain
of "stateful address assignment is optional in IPv6, therefore we need
a DNS discovery solution which doesn't use DHCP", which just tells me
that the people singing this song still don't understand how the DHCP
Information-Request mechanism works.  See (1), above.

In summary, while it's possible that there's a credible case to be
made for why further protocol work is needed, I haven't seen it yet.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 17:44:07 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22676
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 17:44:05 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72LO58W015639
	for <dnsop-outgoing@nic.cafax.se>; Sat, 2 Aug 2003 23:24:06 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h72LO5BB015638
	for dnsop-outgoing; Sat, 2 Aug 2003 23:24:05 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72LO48W015633
	for <dnsop@cafax.se>; Sat, 2 Aug 2003 23:24:05 +0200 (MEST)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1)
  with ESMTP-TLS id 411314; Sat, 02 Aug 2003 16:23:58 -0500
Message-ID: <3F2C2BF0.10507@ehsco.com>
Date: Sat, 02 Aug 2003 16:24:00 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Rob Austein <sra+dnsop@hactrn.net>
CC: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>	<20030802171129.0001D190E@thrintun.hactrn.net>	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com> <20030802205235.EF43D18EA@thrintun.hactrn.net>
In-Reply-To: <20030802205235.EF43D18EA@thrintun.hactrn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 8/2/2003 3:52 PM Rob Austein wrote:

> Real issues I've heard so far:
> 
> 1) Pekka points out that the DHCPv6 spec is a pretty big chunk of text

> 2) Alain points out that having every node in a building poll at once

> 3) Ohta-san has resurfaced the well-known-anycast hack.  Issues with

> Other than the above, what I've heard has been the same tired refrain
> of "stateful address assignment is optional in IPv6, therefore we need

I don't know if you're bundling my complaint in the latter camp or not,
but if so that's an incorrect interpretation. My complaint is that the
mandatory requirement introduces unnecessary complexity to the default
scenario by interfering with the application-layer DNS service, imposes
non-intuitive management cycles onto the service ("oh yeah, my resolver
gets its config from this extraneous service that I forgot about because
I'm not using it for anything else"), and is wholly unnecessary when the
service is capable of handling it internally.

Separately, use of in-band dynamic discovery via multicast also allows
SRV-based discovery mechanisms to bootstrap further. Those systems also
operate outside of or run in parallel with DHCP.

FWIW, I run DHCP here and I would almost certainly use it for this too,
although my network is much better managed than most of the networks out
there today.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 18:34:40 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24324
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 18:34:39 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72MBS8W015932
	for <dnsop-outgoing@nic.cafax.se>; Sun, 3 Aug 2003 00:11:28 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h72MBSC4015931
	for dnsop-outgoing; Sun, 3 Aug 2003 00:11:28 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72MBR8W015925
	for <dnsop@cafax.se>; Sun, 3 Aug 2003 00:11:27 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 25E3C18E3
	for <dnsop@cafax.se>; Sat,  2 Aug 2003 18:11:26 -0400 (EDT)
Date: Sat, 02 Aug 2003 18:11:26 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <3F2C2BF0.10507@ehsco.com>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
	<20030802171129.0001D190E@thrintun.hactrn.net>
	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
	<20030802205235.EF43D18EA@thrintun.hactrn.net>
	<3F2C2BF0.10507@ehsco.com>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030802221126.25E3C18E3@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Sat, 02 Aug 2003 16:24:00 -0500, Eric A. Hall wrote:
> 
> I don't know if you're bundling my complaint in the latter camp or not,
> but if so that's an incorrect interpretation. My complaint is that the
> mandatory requirement introduces unnecessary complexity to the default
> scenario by interfering with the application-layer DNS service, imposes
> non-intuitive management cycles onto the service ("oh yeah, my resolver
> gets its config from this extraneous service that I forgot about because
> I'm not using it for anything else"), and is wholly unnecessary when the
> service is capable of handling it internally.
> 
> Separately, use of in-band dynamic discovery via multicast also allows
> SRV-based discovery mechanisms to bootstrap further. Those systems also
> operate outside of or run in parallel with DHCP.

No, sorry, I forgot about yours, and you're correct that it doesn't
quite fit into any of the pigeon holes in my previous message.

If I understand it correctly, the simple version of what you propose
(just using multicast to find recursive name servers, nothing else)
substitutes one multicast-based discovery protocol for another
multicast-based discovery protocol.  Since it's quite possible to
co-locate a DHCP-lite "server" inside the same "process" (or whatever
fate sharing unit a server host uses) as the recursive name server,
the fate sharing comparision comes out as a wash when one looks at it
closely.  So one's left arguing about relatively trivial engineering
details like packet formats and port numbers.

The SRV based stuff is a different ball of wax: in that one, you're
reinventing SLP instead of reinventing DHCP :).  While one could
certainly have a fun discussion along those lines, the ZEROCONF and
DNSEXT WGs have already spent a lot of time down the LLMNR rabbit
hole, and I'm reluctant to follow them down there.

In any case, either version of what you're talking about still looks
to me like a proposal for new protocol work.  We're still trying to
determine whether -any- new protocol work is needed, so this, like the
RA-based and ND-based proposals, isn't really in scope at the moment.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 20:04:43 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25427
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 20:04:42 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72Nct8W016363
	for <dnsop-outgoing@nic.cafax.se>; Sun, 3 Aug 2003 01:38:55 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h72NctxA016362
	for dnsop-outgoing; Sun, 3 Aug 2003 01:38:55 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h72Ncr8W016357
	for <dnsop@cafax.se>; Sun, 3 Aug 2003 01:38:54 +0200 (MEST)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1)
  with ESMTP-TLS id 411317; Sat, 02 Aug 2003 18:38:48 -0500
Message-ID: <3F2C4B8A.5000609@ehsco.com>
Date: Sat, 02 Aug 2003 18:38:50 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Rob Austein <sra+dnsop@hactrn.net>
CC: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>	<20030802171129.0001D190E@thrintun.hactrn.net>	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>	<20030802205235.EF43D18EA@thrintun.hactrn.net>	<3F2C2BF0.10507@ehsco.com> <20030802221126.25E3C18E3@thrintun.hactrn.net>
In-Reply-To: <20030802221126.25E3C18E3@thrintun.hactrn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 8/2/2003 5:11 PM Rob Austein wrote:

> If I understand it correctly, the simple version of what you propose
> (just using multicast to find recursive name servers, nothing else)
> substitutes one multicast-based discovery protocol for another
> multicast-based discovery protocol.  Since it's quite possible to
> co-locate a DHCP-lite "server" inside the same "process" (or whatever
> fate sharing unit a server host uses) as the recursive name server,
> the fate sharing comparision comes out as a wash when one looks at it
> closely.  So one's left arguing about relatively trivial engineering
> details like packet formats and port numbers.

There's also the operational overhead differences. You'll still have to
manage static pre-configured lists of servers, for example, while there
wouldn't be any such lists with the multicast DNS 'CONFIG' model. Since
any server that responded to the request would be a candidate, managing
the list would essentially boil down to adding and deleting servers (or
enabling and disabling recursion on those servers), and the new list of
servers would self-identifies on the next query seamlessly.

Granted, there would be some administration in terms of ensuring that
multicast filters were working properly, but this is less than the
requirements for DHCP.

> The SRV based stuff is a different ball of wax: in that one, you're
> reinventing SLP instead of reinventing DHCP :). 

I wasn't advocating any additional work for SRV. I was making the point
that SRV-based configurations only requires a working resolver, and that
the multicast CONFIG approach gets that minimal level of service working
*from inside DNS* as well. So again, for those services which use SRV,
using a DNS-based configuration service makes it simpler since everything
~needed would be in the resolver code, with no external services needed.

> In any case, either version of what you're talking about still looks
> to me like a proposal for new protocol work.

A new DNS opcode and some behavioral rules.

> We're still trying to
> determine whether -any- new protocol work is needed, so this, like the
> RA-based and ND-based proposals, isn't really in scope at the moment.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 20:34:23 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25714
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 20:34:21 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7306L8W016580
	for <dnsop-outgoing@nic.cafax.se>; Sun, 3 Aug 2003 02:06:22 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7306Lgg016579
	for dnsop-outgoing; Sun, 3 Aug 2003 02:06:21 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7306K8W016574
	for <dnsop@cafax.se>; Sun, 3 Aug 2003 02:06:21 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 94C1E18E3
	for <dnsop@cafax.se>; Sat,  2 Aug 2003 20:06:19 -0400 (EDT)
Date: Sat, 02 Aug 2003 20:06:19 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <3F2C4B8A.5000609@ehsco.com>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
	<20030802171129.0001D190E@thrintun.hactrn.net>
	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
	<20030802205235.EF43D18EA@thrintun.hactrn.net>
	<3F2C2BF0.10507@ehsco.com>
	<20030802221126.25E3C18E3@thrintun.hactrn.net>
	<3F2C4B8A.5000609@ehsco.com>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030803000619.94C1E18E3@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Sat, 02 Aug 2003 18:38:50 -0500, Eric A. Hall wrote:
> 
> There's also the operational overhead differences. You'll still have to
> manage static pre-configured lists of servers, for example, while there
> wouldn't be any such lists with the multicast DNS 'CONFIG' model. Since
> any server that responded to the request would be a candidate, managing
> the list would essentially boil down to adding and deleting servers (or
> enabling and disabling recursion on those servers), and the new list of
> servers would self-identifies on the next query seamlessly.

Nope.  A minimal DHCPv6-lite server co-located with a recursive name
server would just respond with its own address.  This is no more (and
no less) static configuration than in your model.

> Granted, there would be some administration in terms of ensuring that
> multicast filters were working properly, but this is less than the
> requirements for DHCP.

Nope.  It's exactly the same as with DHCP, just on a different port
number.  The only real difference is that with DHCP one also has the
alternative of using DHCP relays if site multicast isn't practical.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 20:34:51 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25731
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 20:34:50 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h730DT8W016614
	for <dnsop-outgoing@nic.cafax.se>; Sun, 3 Aug 2003 02:13:29 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h730DTjb016613
	for dnsop-outgoing; Sun, 3 Aug 2003 02:13:29 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h730DR8W016608
	for <dnsop@cafax.se>; Sun, 3 Aug 2003 02:13:27 +0200 (MEST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h730DCg07626;
	Sat, 2 Aug 2003 17:13:12 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200308030013.h730DCg07626@boreas.isi.edu>
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <20030802221126.25E3C18E3@thrintun.hactrn.net> from Rob Austein at "Aug 2, 3 06:11:26 pm"
To: sra+dnsop@hactrn.net (Rob Austein)
Date: Sat, 2 Aug 2003 17:13:12 -0700 (PDT)
Cc: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

% > Separately, use of in-band dynamic discovery via multicast also allows
% > SRV-based discovery mechanisms to bootstrap further. Those systems also
% > operate outside of or run in parallel with DHCP.
% 
% No, sorry, I forgot about yours, and you're correct that it doesn't
% quite fit into any of the pigeon holes in my previous message.
% 
% If I understand it correctly, the simple version of what you propose
% (just using multicast to find recursive name servers, nothing else)
% substitutes one multicast-based discovery protocol for another
% multicast-based discovery protocol.  Since it's quite possible to
% co-locate a DHCP-lite "server" inside the same "process" (or whatever
% fate sharing unit a server host uses) as the recursive name server,
% the fate sharing comparision comes out as a wash when one looks at it
% closely.  So one's left arguing about relatively trivial engineering
% details like packet formats and port numbers.
% 
% The SRV based stuff is a different ball of wax: in that one, you're
% reinventing SLP instead of reinventing DHCP :).  While one could
% certainly have a fun discussion along those lines, the ZEROCONF and
% DNSEXT WGs have already spent a lot of time down the LLMNR rabbit
% hole, and I'm reluctant to follow them down there.

	See the TBDS work that predates LLMNR (and is referenced by it)
	There are some interesting tweeks that should be done to the 
	protocol (a replacement for QUERY comes to mind...)

	when the early work was done, DHCP did not have all the hooks
	and SLP was too "heavy".   

% In any case, either version of what you're talking about still looks
% to me like a proposal for new protocol work.  We're still trying to
% determine whether -any- new protocol work is needed, so this, like the
% RA-based and ND-based proposals, isn't really in scope at the moment.

	Sorry about bringing up packing plant rejects... :)

% #----------------------------------------------------------------------
% # To unsubscribe, send a message to <dnsop-request@cafax.se>.
% 


-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 20:52:28 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25863
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 20:52:27 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h730Tr8W016736
	for <dnsop-outgoing@nic.cafax.se>; Sun, 3 Aug 2003 02:29:53 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h730Tr5K016735
	for dnsop-outgoing; Sun, 3 Aug 2003 02:29:53 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h730Tq8W016730
	for <dnsop@cafax.se>; Sun, 3 Aug 2003 02:29:52 +0200 (MEST)
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h730TmuG002891;
	Sat, 2 Aug 2003 17:29:49 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (sjc-vpn3-473.cisco.com [10.21.65.217])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ABF25028;
	Sat, 2 Aug 2003 20:29:46 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030802202137.05f32630@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 02 Aug 2003 20:29:42 -0400
To: "Eric A. Hall" <ehall@ehsco.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: Policy of IPv6 DNS Discovery
Cc: Rob Austein <sra+dnsop@hactrn.net>, dnsop@cafax.se
In-Reply-To: <3F2C4B8A.5000609@ehsco.com>
References: <20030802221126.25E3C18E3@thrintun.hactrn.net>
 <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
 <20030802171129.0001D190E@thrintun.hactrn.net>
 <4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
 <20030802205235.EF43D18EA@thrintun.hactrn.net>
 <3F2C2BF0.10507@ehsco.com>
 <20030802221126.25E3C18E3@thrintun.hactrn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-dnsop@cafax.se
Precedence: bulk

Eric,

I think there has been a difference of opinion in the past about your 
statement: "Granted, there would be some administration in terms of 
ensuring that multicast filters were working properly, but this is less 
than the requirements for DHCP."  My recollection is that similar 
multicast-based mechanisms have been rejected in the past because they 
require a multicast service, which has not been universally deployed to 
date.  Network admins do have successful experience with DHCP service 
deployment in IPv4 and the service deployment model in IPv6 would be 
essentially the same...

- Ralph

At 06:38 PM 8/2/2003 -0500, Eric A. Hall wrote:

>on 8/2/2003 5:11 PM Rob Austein wrote:
> > If I understand it correctly, the simple version of what you propose
> > (just using multicast to find recursive name servers, nothing else)
> > substitutes one multicast-based discovery protocol for another
> > multicast-based discovery protocol.  Since it's quite possible to
> > co-locate a DHCP-lite "server" inside the same "process" (or whatever
> > fate sharing unit a server host uses) as the recursive name server,
> > the fate sharing comparision comes out as a wash when one looks at it
> > closely.  So one's left arguing about relatively trivial engineering
> > details like packet formats and port numbers.
>
>There's also the operational overhead differences. You'll still have to
>manage static pre-configured lists of servers, for example, while there
>wouldn't be any such lists with the multicast DNS 'CONFIG' model. Since
>any server that responded to the request would be a candidate, managing
>the list would essentially boil down to adding and deleting servers (or
>enabling and disabling recursion on those servers), and the new list of
>servers would self-identifies on the next query seamlessly.
>
>Granted, there would be some administration in terms of ensuring that
>multicast filters were working properly, but this is less than the
>requirements for DHCP.
>
> > The SRV based stuff is a different ball of wax: in that one, you're
> > reinventing SLP instead of reinventing DHCP :).
>
>I wasn't advocating any additional work for SRV. I was making the point
>that SRV-based configurations only requires a working resolver, and that
>the multicast CONFIG approach gets that minimal level of service working
>*from inside DNS* as well. So again, for those services which use SRV,
>using a DNS-based configuration service makes it simpler since everything
>~needed would be in the resolver code, with no external services needed.
>
> > In any case, either version of what you're talking about still looks
> > to me like a proposal for new protocol work.
>
>A new DNS opcode and some behavioral rules.
>
> > We're still trying to
> > determine whether -any- new protocol work is needed, so this, like the
> > RA-based and ND-based proposals, isn't really in scope at the moment.
>
>--
>Eric A. Hall                                        http://www.ehsco.com/
>Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
>
>#----------------------------------------------------------------------
># To unsubscribe, send a message to <dnsop-request@cafax.se>.

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  2 21:34:10 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26496
	for <dnsop-archive@lists.ietf.org>; Sat, 2 Aug 2003 21:34:09 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7317g8W017016
	for <dnsop-outgoing@nic.cafax.se>; Sun, 3 Aug 2003 03:07:42 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7317gVG017015
	for dnsop-outgoing; Sun, 3 Aug 2003 03:07:42 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7317e8W017010
	for <dnsop@cafax.se>; Sun, 3 Aug 2003 03:07:41 +0200 (MEST)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1)
  with ESMTP-TLS id 411329; Sat, 02 Aug 2003 20:07:35 -0500
Message-ID: <3F2C6059.8040502@ehsco.com>
Date: Sat, 02 Aug 2003 20:07:37 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Rob Austein <sra+dnsop@hactrn.net>
CC: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>	<20030802171129.0001D190E@thrintun.hactrn.net>	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>	<20030802205235.EF43D18EA@thrintun.hactrn.net>	<3F2C2BF0.10507@ehsco.com>	<20030802221126.25E3C18E3@thrintun.hactrn.net>	<3F2C4B8A.5000609@ehsco.com> <20030803000619.94C1E18E3@thrintun.hactrn.net>
In-Reply-To: <20030803000619.94C1E18E3@thrintun.hactrn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 8/2/2003 7:06 PM Rob Austein wrote:

> At Sat, 02 Aug 2003 18:38:50 -0500, Eric A. Hall wrote:
> 
>>There's also the operational overhead differences. You'll still have to
>>manage static pre-configured lists of servers, for example, while there
>>wouldn't be any such lists with the multicast DNS 'CONFIG' model. Since
>>any server that responded to the request would be a candidate, managing
>>the list would essentially boil down to adding and deleting servers (or
>>enabling and disabling recursion on those servers), and the new list of
>>servers would self-identifies on the next query seamlessly.
> 
> Nope.  A minimal DHCPv6-lite server co-located with a recursive name
> server would just respond with its own address.  This is no more (and
> no less) static configuration than in your model.
> 
>>Granted, there would be some administration in terms of ensuring that
>>multicast filters were working properly, but this is less than the
>>requirements for DHCP.
> 
> Nope.  It's exactly the same as with DHCP, just on a different port
> number.  The only real difference is that with DHCP one also has the
> alternative of using DHCP relays if site multicast isn't practical.

I'll go refresh on dhcpv6-lite, but in the meantime if you'll guarantee
that manual maintenance of extra-service configuration data will never be
mandatory (my fear word) then I'll rescind my concerns.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sun Aug  3 13:44:26 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22769
	for <dnsop-archive@lists.ietf.org>; Sun, 3 Aug 2003 13:44:25 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h73HKF8W022506
	for <dnsop-outgoing@nic.cafax.se>; Sun, 3 Aug 2003 19:20:15 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h73HKFIv022505
	for dnsop-outgoing; Sun, 3 Aug 2003 19:20:15 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h73HKD8W022500
	for <dnsop@cafax.se>; Sun, 3 Aug 2003 19:20:14 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 8057018EE
	for <dnsop@cafax.se>; Sun,  3 Aug 2003 13:20:12 -0400 (EDT)
Date: Sun, 03 Aug 2003 13:20:12 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <3F2C6059.8040502@ehsco.com>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
	<20030802171129.0001D190E@thrintun.hactrn.net>
	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
	<20030802205235.EF43D18EA@thrintun.hactrn.net>
	<3F2C2BF0.10507@ehsco.com>
	<20030802221126.25E3C18E3@thrintun.hactrn.net>
	<3F2C4B8A.5000609@ehsco.com>
	<20030803000619.94C1E18E3@thrintun.hactrn.net>
	<3F2C6059.8040502@ehsco.com>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030803172012.8057018EE@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Sat, 02 Aug 2003 20:07:37 -0500, Eric A. Hall wrote:
> 
> I'll go refresh on dhcpv6-lite, but in the meantime if you'll guarantee
> that manual maintenance of extra-service configuration data will never be
> mandatory (my fear word) then I'll rescind my concerns.

It's clearly possible to use DHCPv6-lite for DNS discovery in a way
that does not require manual configuration, but read the draft and
decide for yourself.  Whether implementors and operators will chose to
support the no-manual-config co-located DHCPv6-lite server model is a
separate question, which might conceivably be the subject of a short
BCP doc if we reach consensus that this is important.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sun Aug  3 22:11:50 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA02655
	for <dnsop-archive@lists.ietf.org>; Sun, 3 Aug 2003 22:11:49 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h741mh8W025723
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 03:48:43 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h741mhgf025722
	for dnsop-outgoing; Mon, 4 Aug 2003 03:48:43 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h741mY8W025717
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 03:48:41 +0200 (MEST)
Received: from paulnb (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h74221S07064;
	Mon, 4 Aug 2003 11:02:02 +0900 (KST)
Message-ID: <002f01c35a2a$5bff4c50$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: "Rob Austein" <sra+dnsop@hactrn.net>
Cc: "DNSOP WG" <dnsop@cafax.se>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr> <20030802171129.0001D190E@thrintun.hactrn.net>
Subject: Re: Policy of IPv6 DNS Discovery
Date: Mon, 4 Aug 2003 10:47:24 +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.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by nic.cafax.se id h741mh8W025718
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 8bit


----- Original Message ----- 
From: "Rob Austein" <sra+dnsop@hactrn.net>
To: <dnsop@cafax.se>
Sent: Sunday, August 03, 2003 2:11 AM
Subject: Re: Policy of IPv6 DNS Discovery
> 
> I'm not sure why you insist on a public repetition of an exchange that
> you and I already had when you pestered me about this in private, but
> whatever.
> 

If I bothered you, I am sorry for that.
However, I wanted you, as DNSOP chair, join the discussion more actively.

> The reason why this topic was moved from the IPv6 WG to the DNSOP WG
> was to force a real discussion of requirements before proposing
> solutions.  In particular, we're required to answer the question which
> the IPv6 WG declined to ask: given DHCPv6 (including DHCPv6-lite),
> what real need is there for further work in this space?  This
> discussion is finally taking place on the DNSOP mailing list, albiet
> in fits and starts.  Discussion of new protocol extensions (such as
> your draft) will be in scope (for some WG, probably not DNSOP) if and
> only if this discussion concludes that there's a gap between real
> requirements and existing protocols.

I have two questions to ask you.
1. Do you mean that RA-based DNS Discovery is out of scope in DNSOP wg?
2. Do you think that DHCPv6-lite is necessary in the environment where DHCPv6 exists?

For the second question, IMHO, in such a case, DHCPv6-lite is unnecessary.
RA-based approach seeks to harmonize with DHCPv6.
Is this non-sense?

/Jaehoon Paul

> #----------------------------------------------------------------------
> # To unsubscribe, send a message to <dnsop-request@cafax.se>.
> 

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sun Aug  3 23:27:28 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA03405
	for <dnsop-archive@lists.ietf.org>; Sun, 3 Aug 2003 23:27:27 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7437o8W026112
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 05:07:50 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7437o9F026111
	for dnsop-outgoing; Mon, 4 Aug 2003 05:07:50 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7437n8W026106
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 05:07:49 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 67A0D18EE
	for <dnsop@cafax.se>; Sun,  3 Aug 2003 23:07:48 -0400 (EDT)
Date: Sun, 03 Aug 2003 23:07:48 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <002f01c35a2a$5bff4c50$c470fe81@etri.re.kr>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
	<20030802171129.0001D190E@thrintun.hactrn.net>
	<002f01c35a2a$5bff4c50$c470fe81@etri.re.kr>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030804030748.67A0D18EE@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Mon, 4 Aug 2003 10:47:24 +0900, Jaehoon Jeong wrote:
>
> 1. Do you mean that RA-based DNS Discovery is out of scope in DNSOP wg?

I have already answered this question, more than once:

  Discussion of new protocol extensions (such as your draft) will be in
  scope (for some WG, probably not DNSOP) if and only if the
  requirements discussion concludes that there's a gap between real
  requirements and existing protocols.

Serious question, not intended as sarcasm: is there some part of the
previous sentence which you do not understand?

> 2. Do you think that DHCPv6-lite is necessary in the environment where DHCPv6 exists?
>
> For the second question, IMHO, in such a case, DHCPv6-lite is unnecessary.
> RA-based approach seeks to harmonize with DHCPv6.

DHCPv6-lite is a subset of DHCPv6; therefore, by definition, if one
has DHCPv6, one also has DHCPv6-lite, and a DHCPv6-lite client doesn't
care whether the server(s) that answer it are DHCPv6 or DHCPv6-lite.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 00:40:57 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA04521
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 00:40:55 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h744JE8W026630
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 06:19:14 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h744JDRu026629
	for dnsop-outgoing; Mon, 4 Aug 2003 06:19:13 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h744JB8W026624
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 06:19:12 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308040402.NAA01187@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id NAA01187; Mon, 4 Aug 2003 13:02:27 +0900
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <20030802205235.EF43D18EA@thrintun.hactrn.net> from Rob Austein
 at "Aug 2, 2003 04:52:34 pm"
To: Rob Austein <sra+dnsop@hactrn.net>
Date: Mon, 4 Aug 2003 13:02:26 +0859 ()
CC: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Rob Austin;

> And there's at least part of the problem.  "Stateless DNS discovery"
> is not the same thing as "a solution in addition to DHCPv6" unless
> "stateless" is just a euphemism for "anything but DHCP".  DHCPv6-lite
> is also "stateless" for every definition of "stateless" that applies
> to, eg, the RA-based proposals.  This confusion persisted through the
> entire discussion in the IPv6 WG,

which is partly why I abandoned IPv6 WG not being a place
for serious protocol discussion long before.

> 3) Ohta-san has resurfaced the well-known-anycast hack.  Issues with
>    this are already on record in the IPv6 WG list archives, so I won't
>    restate them here,

I guess there should be a lot of confusions on "stateless" in addition
to poor understandings on "anycast", such as that anycast addresses
should not be a source address, and on "scope" such as that discussed
in my draft that the archives are not helpful.

If my guess is wrong, correct me with a few pointed references.

>    but I will note that sites which chose to do
>    this with unicast addresses out of their own address space (as
>    opposed to well-known unicast or anycast addresses) are already
>    free to do so, and, indeed, I've been told that many ISPs already
>    do this for v4 -- pretty much by definition, nobody but the ops
>    staff at those ISPs would know.  At a high level, though, the key
>    point here is that this is not new technology, and sites which
>    chose to use it can do so already without further protocol work.

Right. However, autocnfiguration is not a protocol but an operational
issue.

Site dependent anycast addresses can not remove operational effort
of DNS configuration by site administrators.

Global anycast addresses does remove it.

> In summary, while it's possible that there's a credible case to be
> made for why further protocol work is needed, I haven't seen it yet.

As we agree that

> to, eg, the RA-based proposals.  This confusion persisted through the
> entire discussion in the IPv6 WG,

isn't it obvious that removal of features related to "stateless
autoconfiguration", including entire ND, from IPv6 is the required
protocol work?

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 02:03:31 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA08878
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 02:03:30 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h745fT8W026993
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 07:41:29 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h745fTBC026992
	for dnsop-outgoing; Mon, 4 Aug 2003 07:41:29 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.114.50])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h745fL8W026987
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 07:41:27 +0200 (MEST)
Received: from paulnb (paul3.etri.re.kr [129.254.112.196])
	by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h745nuS08687;
	Mon, 4 Aug 2003 14:49:56 +0900 (KST)
Message-ID: <009d01c35a4a$32a8f840$c470fe81@etri.re.kr>
From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
To: "Rob Austein" <sra+dnsop@hactrn.net>
Cc: <dnsop@cafax.se>, <hinden@iprg.nokia.com>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr><20030802171129.0001D190E@thrintun.hactrn.net><002f01c35a2a$5bff4c50$c470fe81@etri.re.kr> <20030804030748.67A0D18EE@thrintun.hactrn.net>
Subject: Re: Policy of IPv6 DNS Discovery
Date: Mon, 4 Aug 2003 14:35:19 +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.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by nic.cafax.se id h745fS8W026988
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 8bit

Thanks for your prompt answers.

----- Original Message ----- 
From: "Rob Austein" <sra+dnsop@hactrn.net>
To: <dnsop@cafax.se>
Sent: Monday, August 04, 2003 12:07 PM
Subject: Re: Policy of IPv6 DNS Discovery


> 
> At Mon, 4 Aug 2003 10:47:24 +0900, Jaehoon Jeong wrote:
> >
> > 1. Do you mean that RA-based DNS Discovery is out of scope in DNSOP wg?
> 
> I have already answered this question, more than once:
> 
>   Discussion of new protocol extensions (such as your draft) will be in
>   scope (for some WG, probably not DNSOP) if and only if the
>   requirements discussion concludes that there's a gap between real
>   requirements and existing protocols.
> 
> Serious question, not intended as sarcasm: is there some part of the
> previous sentence which you do not understand?
> 

Now, I CAN unterstand your intention exactly.
Where can we discuss new protocol extensions if neither in IPv6 wg, nor in DNSOP wg?
This is a question for all DNSOP members except for you.

> > 2. Do you think that DHCPv6-lite is necessary in the environment where DHCPv6 exists?
> >
> > For the second question, IMHO, in such a case, DHCPv6-lite is unnecessary.
> > RA-based approach seeks to harmonize with DHCPv6.
> 
> DHCPv6-lite is a subset of DHCPv6; therefore, by definition, if one
> has DHCPv6, one also has DHCPv6-lite, and a DHCPv6-lite client doesn't
> care whether the server(s) that answer it are DHCPv6 or DHCPv6-lite.

If DHCPv6-lite is a subnet of DHCPv6, there may be no problem that RA-based DNS Discovery
coexists with DHCPv6 like in ND spec.
A significant number of people, including me, really want RA-based DNS Discovery.
I think, they know the usefulness and operation of DHCPv6.
At least my company has implemented DHCPv6 client/server fully.

I think, I did my best to appeal the necessity of RA-based DNS Discovery, 
although I could not express my opinions well enough because of the limitation of Non-English speaker.

If there is proper reason RA-based DNS Discovery SHOULD NOT coexist with DHCPv6,
I will also rescind my concerns about RA-based DNS Discovery.
Thanks.

/Jaehoon Paul


> #----------------------------------------------------------------------
> # To unsubscribe, send a message to <dnsop-request@cafax.se>.
> 

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 07:56:33 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA22736
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 07:56:31 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74BMU8W029070
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 13:22:30 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h74BMUMJ029069
	for dnsop-outgoing; Mon, 4 Aug 2003 13:22:30 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74BMO8W029064
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 13:22:24 +0200 (MEST)
Received: from cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 04 Aug 2003 04:26:35 -0700
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h74BMG7F017659;
	Mon, 4 Aug 2003 04:22:17 -0700 (PDT)
Received: from jschnizl-w2k.cisco.com (rtp-vpn2-100.cisco.com [10.82.240.100]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id EAA18968; Mon, 4 Aug 2003 04:22:15 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
X-Sender: jschnizl@wells.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 04 Aug 2003 07:22:13 -0400
To: "Jaehoon Paul Jeong" <paul@etri.re.kr>
From: John Schnizlein <jschnizl@cisco.com>
Subject: Re: Policy of IPv6 DNS Discovery
Cc: <dnsop@cafax.se>
In-Reply-To: <009d01c35a4a$32a8f840$c470fe81@etri.re.kr>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
 <20030802171129.0001D190E@thrintun.hactrn.net>
 <002f01c35a2a$5bff4c50$c470fe81@etri.re.kr>
 <20030804030748.67A0D18EE@thrintun.hactrn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-dnsop@cafax.se
Precedence: bulk

At 01:35 AM 8/4/2003, Jaehoon Paul Jeong wrote:

>Where can we discuss new protocol extensions if neither in IPv6 wg, nor in DNSOP wg?
>This is a question for all DNSOP members except for you.

The discussion of the question whether a protocol extension is
necessary for IPv6 hosts to locate DNS servers is underway here.
All the chair is requesting is that we understand first if there
is any need, before we discuss the nature of protocol extensions
that might fit that need.

>I think, I did my best to appeal the necessity of RA-based DNS Discovery, 
>although I could not express my opinions well enough because of the limitation of Non-English speaker.

Your interest is clear, and those of us who understand only English
appreciate your extra effort in making it clear in a language other
than your first.

>If there is proper reason RA-based DNS Discovery SHOULD NOT coexist 
>with DHCPv6, I will also rescind my concerns about RA-based DNS Discovery.

I think the reason is stated in RFC 1958: Architectural Principles of 
the Internet.:

   3.2 If there are several ways of doing the same thing, choose one.
   If a previous design, in the Internet context or elsewhere, has
   successfully solved the same problem, choose the same solution unless
   there is a good technical reason not to.  Duplication of the same
   protocol functionality should be avoided as far as possible, without
   of course using this argument to reject improvements.

While this does not deny that different solutions might be appropriate
for different operational situations, it does require that the nature of
the different situations, and the suitability of proposed solutions to 
those differences, should be identified. We have not seen the difference.

Since there is a protocol (DCHPv6) which can provide the necessary
information for hosts, and since the "heavy-weight" concerns attributed
to that protocol have been shown invalid (existence proof: DHPCv6-light),
justification for developing a new protocol (or extension of RA) must meet 
the burden identified in Architectural Principle 3.2

John

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 08:57:34 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA24212
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 08:57:33 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74CQ58W029516
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 14:26:05 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h74CQ5D5029515
	for dnsop-outgoing; Mon, 4 Aug 2003 14:26:05 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74CQ38W029510
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 14:26:03 +0200 (MEST)
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id NAA28343
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 13:26:03 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id NAA29501
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 13:26:02 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h74CQ2g13869
	for dnsop@cafax.se; Mon, 4 Aug 2003 13:26:02 +0100
Date: Mon, 4 Aug 2003 13:26:02 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
Message-ID: <20030804122602.GD13730@login.ecs.soton.ac.uk>
Mail-Followup-To: dnsop@cafax.se
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr> <20030802171129.0001D190E@thrintun.hactrn.net> <002f01c35a2a$5bff4c50$c470fe81@etri.re.kr> <20030804030748.67A0D18EE@thrintun.hactrn.net> <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
User-Agent: Mutt/1.4i
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Mon, Aug 04, 2003 at 07:22:13AM -0400, John Schnizlein wrote:
> 
> Since there is a protocol (DCHPv6) which can provide the necessary
> information for hosts, and since the "heavy-weight" concerns attributed
> to that protocol have been shown invalid (existence proof: DHPCv6-light),
> justification for developing a new protocol (or extension of RA) must meet 
> the burden identified in Architectural Principle 3.2

By that argument, we would not have IPv6 stateless autoconf at all?

Tim
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 09:27:31 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24890
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 09:27:30 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74CxG8W029684
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 14:59:16 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h74CxGOm029682
	for dnsop-outgoing; Mon, 4 Aug 2003 14:59:16 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74Cx98W029677
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 14:59:10 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308041245.VAA00366@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id VAA00366; Mon, 4 Aug 2003 21:45:30 +0900
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com> from John Schnizlein
 at "Aug 4, 2003 07:22:13 am"
To: John Schnizlein <jschnizl@cisco.com>
Date: Mon, 4 Aug 2003 21:45:29 +0859 ()
CC: Jaehoon Paul Jeong <paul@etri.re.kr>, dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

John;

> At 01:35 AM 8/4/2003, Jaehoon Paul Jeong wrote:

> >I think, I did my best to appeal the necessity of RA-based DNS Discovery, 
> >although I could not express my opinions well enough because of the limitation of Non-English speaker.
> 
> Your interest is clear,

And it is also clear that his case does not need RA-based DNS
discovery, as was pointed by two of us.

In mobile case, mobile hosts need constant DNS service. It is NOT
acceptable that the mobile hosts try to find DNS server at
foreign environment sometime successfully and sometimes not
that DNS service MUST be bundled and share fate with HA service,
which should be configured simultaneously.

> and those of us who understand only English
> appreciate your extra effort in making it clear in a language other
> than your first.

He should also appreciate my extra effort.

> Since there is a protocol (DCHPv6) which can provide the necessary
> information for hosts, and since the "heavy-weight" concerns attributed
> to that protocol have been shown invalid (existence proof: DHPCv6-light),
> justification for developing a new protocol (or extension of RA) must meet 
> the burden identified in Architectural Principle 3.2

ND performs functionality already provided by ARP, DHCP and routing
protocols that it should disapper.

For example, DHCP collocated on routers is the mechanism to provide
address prefixes for autoconfiguration of addresses.

						Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 09:45:00 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25666
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 09:44:59 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74DGM8W029786
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 15:16:22 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h74DGMtR029785
	for dnsop-outgoing; Mon, 4 Aug 2003 15:16:22 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74DGK8W029780
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 15:16:21 +0200 (MEST)
Received: from cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 04 Aug 2003 06:16:21 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h74DGHLH014295;
	Mon, 4 Aug 2003 06:16:18 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (sjc-vpn3-38.cisco.com [10.21.64.38])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ABF71264;
	Mon, 4 Aug 2003 09:16:16 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030804090815.04339b00@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 04 Aug 2003 09:16:13 -0400
To: Tim Chown <tjc@ecs.soton.ac.uk>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: Policy of IPv6 DNS Discovery
Cc: dnsop@cafax.se
In-Reply-To: <20030804122602.GD13730@login.ecs.soton.ac.uk>
References: <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
 <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
 <20030802171129.0001D190E@thrintun.hactrn.net>
 <002f01c35a2a$5bff4c50$c470fe81@etri.re.kr>
 <20030804030748.67A0D18EE@thrintun.hactrn.net>
 <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-dnsop@cafax.se
Precedence: bulk

Tim,

Do you think Architectural Principle 3.2 is being misinterpreted in
this discussion (regarding DNS configuration), or should AP3.2 be amended,
or should we deprecate IPv6 stateless autoconfiguration?

I ask in all seriousness, because IMHO the IETF as a whole may not be
keeping AP3.2 as firmly in mind as it should...

I'm also a little leery of lurching off into a philosophical black hole on
the dnsop mailing list, so any declaration of "out of scope" will be heeded.
Perhaps discussion of AP3.2 might move to the problem-statement mailing list?

- Ralph

At 01:26 PM 8/4/2003 +0100, Tim Chown wrote:
>On Mon, Aug 04, 2003 at 07:22:13AM -0400, John Schnizlein wrote:
> >
> > Since there is a protocol (DCHPv6) which can provide the necessary
> > information for hosts, and since the "heavy-weight" concerns attributed
> > to that protocol have been shown invalid (existence proof: DHPCv6-light),
> > justification for developing a new protocol (or extension of RA) must meet
> > the burden identified in Architectural Principle 3.2
>
>By that argument, we would not have IPv6 stateless autoconf at all?
>
>Tim
>#----------------------------------------------------------------------
># To unsubscribe, send a message to <dnsop-request@cafax.se>.

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 10:07:50 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA26714
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 10:07:48 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74DaN8W029976
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 15:36:23 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h74DaNim029975
	for dnsop-outgoing; Mon, 4 Aug 2003 15:36:23 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74DaM8W029970
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 15:36:22 +0200 (MEST)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h74DaJtp004169;
	Mon, 4 Aug 2003 06:36:20 -0700 (PDT)
Received: from jschnizl-w2k.cisco.com (rtp-vpn2-100.cisco.com [10.82.240.100]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id GAA03087; Mon, 4 Aug 2003 06:36:18 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030804092340.0204b560@wells.cisco.com>
X-Sender: jschnizl@wells.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 04 Aug 2003 09:36:17 -0400
To: Tim Chown <tjc@ecs.soton.ac.uk>
From: John Schnizlein <jschnizl@cisco.com>
Subject: Re: Policy of IPv6 DNS Discovery
Cc: dnsop@cafax.se
In-Reply-To: <20030804122602.GD13730@login.ecs.soton.ac.uk>
References: <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
 <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
 <20030802171129.0001D190E@thrintun.hactrn.net>
 <002f01c35a2a$5bff4c50$c470fe81@etri.re.kr>
 <20030804030748.67A0D18EE@thrintun.hactrn.net>
 <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-dnsop@cafax.se
Precedence: bulk

At 08:26 AM 8/4/2003, Tim Chown wrote:
>On Mon, Aug 04, 2003 at 07:22:13AM -0400, John Schnizlein wrote:
>> 
>> Since there is a protocol (DCHPv6) which can provide the necessary
>> information for hosts, and since the "heavy-weight" concerns attributed
>> to that protocol have been shown invalid (existence proof: DHPCv6-light),
>> justification for developing a new protocol (or extension of RA) must meet 
>> the burden identified in Architectural Principle 3.2
>
>By that argument, we would not have IPv6 stateless autoconf at all?

Not necessarily by that argument, but this is neither the time nor
place to revisit that question. We can assume for now that there were
sufficient reasons to justify stateless auto-config of host addresses.

Notice that the existence proof to which I refer is stateless also.
Just because the DHCPv6 protocol is used, does not make the result
state-full. Remember that the DHCP server can provide site-specific
information in a stateless way even if it is not managing (state-fully)
the addresses of the hosts. As an additional simplifying feature,
providing (stateless) information about the address of DNS servers
uses the same protocol where addresses are (state-fully) managed 
by a DHCP server. Host configuration can either include or exclude 
host address configuration, depending on the site's decision.

John

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 16:47:55 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11610
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 16:47:54 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74KAk8W002646
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 22:10:46 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h74KAkCj002645
	for dnsop-outgoing; Mon, 4 Aug 2003 22:10:46 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74KAi8W002640
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 22:10:45 +0200 (MEST)
Received: from esunmail ([129.147.156.34])
	by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h74KAhea008735
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 14:10:43 -0600 (MDT)
Received: from xpa-fe1 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTP id <0HJ4003XP2PU2B@edgemail1.Central.Sun.COM> for dnsop@cafax.se;
 Mon, 04 Aug 2003 14:10:43 -0600 (MDT)
Received: from sun.com ([129.146.12.17])
 by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPSA id <0HJ400BLA2PT8Z@mail.sun.net> for dnsop@cafax.se; Mon,
 04 Aug 2003 14:10:42 -0600 (MDT)
Date: Mon, 04 Aug 2003 13:10:41 -0700
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: Policy of IPv6 DNS Discovery
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: dnsop@cafax.se
Message-id: <3F2EBDC1.4040206@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920
 Netscape/7.0
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
 <20030802171129.0001D190E@thrintun.hactrn.net>
 <002f01c35a2a$5bff4c50$c470fe81@etri.re.kr>
 <20030804030748.67A0D18EE@thrintun.hactrn.net>
 <4.3.2.7.2.20030804070642.020893d8@wells.cisco.com>
 <20030804122602.GD13730@login.ecs.soton.ac.uk>
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7BIT



Tim Chown wrote:

>On Mon, Aug 04, 2003 at 07:22:13AM -0400, John Schnizlein wrote:
>  
>
>>Since there is a protocol (DCHPv6) which can provide the necessary
>>information for hosts, and since the "heavy-weight" concerns attributed
>>to that protocol have been shown invalid (existence proof: DHPCv6-light),
>>justification for developing a new protocol (or extension of RA) must meet 
>>the burden identified in Architectural Principle 3.2
>>    
>>
>
>By that argument, we would not have IPv6 stateless autoconf at all?
>
>Tim
>
No, because DHCPv6-lite keeps no state, so it is fitted
to hand out information without keeping track of who it sent them to.
Works just fine for DNS server, NTP,.... discovery, but
is a little cumbersome for address management...

Note: for those of us who really do not like stateless autoconf,
we could still replace it with DHCPv6-lite where the returned address
would be the concatenation of the prefix and the modified EUI64....
This would not require the DHCPv6-lite server to keep any state,
it could be easily implemented in the routers, ,will serve as access 
control,
allow for prefixes other than /64, simplify having multiple prefixes
on the same link and make the management of reverse DNS so much simpler...
Just 1/2 kidding. ;-)

    - Alain.

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 17:01:36 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA12039
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 17:01:36 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74KX58W002780
	for <dnsop-outgoing@nic.cafax.se>; Mon, 4 Aug 2003 22:33:05 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h74KX4Ae002779
	for dnsop-outgoing; Mon, 4 Aug 2003 22:33:04 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from psg.com (psg.com [147.28.0.62])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h74KX38W002774
	for <dnsop@cafax.se>; Mon, 4 Aug 2003 22:33:04 +0200 (MEST)
Received: from [127.0.0.1] (helo=roam.psg.com)
	by psg.com with esmtp (Exim 4.20)
	id 19jm0t-0007cX-1O; Mon, 04 Aug 2003 20:33:03 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.20)
	id 19jlth-000Lv3-VM; Mon, 04 Aug 2003 13:25:38 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 4 Aug 2003 13:25:37 -0700
To: Rob Austein <sra+dnsop@hactrn.net>
Cc: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
	<20030802171129.0001D190E@thrintun.hactrn.net>
Message-Id: <E19jlth-000Lv3-VM@roam.psg.com>
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The reason why this topic was moved from the IPv6 WG to the DNSOP WG
> was to force a real discussion of requirements before proposing
> solutions.  In particular, we're required to answer the question which
> the IPv6 WG declined to ask: given DHCPv6 (including DHCPv6-lite),
> what real need is there for further work in this space?  This
> discussion is finally taking place on the DNSOP mailing list, albiet
> in fits and starts.  Discussion of new protocol extensions (such as
> your draft) will be in scope (for some WG, probably not DNSOP) if and
> only if this discussion concludes that there's a gap between real
> requirements and existing protocols.

<ad hat>

this is indeed what i thought was/is happening

randy

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug  4 21:53:04 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA17785
	for <dnsop-archive@lists.ietf.org>; Mon, 4 Aug 2003 21:53:04 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h751Jx8W004350
	for <dnsop-outgoing@nic.cafax.se>; Tue, 5 Aug 2003 03:20:00 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h751JxTr004349
	for dnsop-outgoing; Tue, 5 Aug 2003 03:19:59 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h751Jp8W004344
	for <dnsop@cafax.se>; Tue, 5 Aug 2003 03:19:52 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308050110.KAA07138@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id KAA07138; Tue, 5 Aug 2003 10:10:14 +0900
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <3F2EBDC1.4040206@sun.com> from Alain Durand at "Aug 4, 2003 01:10:41
 pm"
To: Alain Durand <Alain.Durand@Sun.COM>
Date: Tue, 5 Aug 2003 10:10:12 +0859 ()
CC: Tim Chown <tjc@ecs.soton.ac.uk>, dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Alain;

> Note: for those of us who really do not like stateless autoconf,

The problem of stateless autoconf is that it is not define at all,
while the resulting protocols have duplicated functionalities to
existing ones.

Though it is so easy to overlook AP3.2, those who carefully observe
it are rewarded a lot for ease of design, operation and deployment.

> we could still replace it with DHCPv6-lite where the returned address
> would be the concatenation of the prefix and the modified EUI64....
> This would not require the DHCPv6-lite server to keep any state,
> it could be easily implemented in the routers,

That's what I have already pointed out.

> will serve as access 
> control,
> allow for prefixes other than /64, simplify having multiple prefixes
> on the same link and make the management of reverse DNS so much simpler...

In addition, with DHCP autoconfiguration, it is also possible to use
arbitrary value for the lower 64 bits of addresses at the descretion
of site administrators.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Tue Aug  5 04:01:14 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA04666
	for <dnsop-archive@lists.ietf.org>; Tue, 5 Aug 2003 04:01:12 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h757SX8W007430
	for <dnsop-outgoing@nic.cafax.se>; Tue, 5 Aug 2003 09:28:33 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h757SXr1007429
	for dnsop-outgoing; Tue, 5 Aug 2003 09:28:33 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h757SR8W007424
	for <dnsop@cafax.se>; Tue, 5 Aug 2003 09:28:27 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h757Rpl25982;
	Tue, 5 Aug 2003 10:27:51 +0300
Date: Tue, 5 Aug 2003 10:27:50 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: John Schnizlein <jschnizl@cisco.com>, Jaehoon Paul Jeong <paul@etri.re.kr>,
        <dnsop@cafax.se>
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <200308041245.VAA00366@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0308051017030.25140-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Mon, 4 Aug 2003, Masataka Ohta wrote:
> > At 01:35 AM 8/4/2003, Jaehoon Paul Jeong wrote:
> 
> > >I think, I did my best to appeal the necessity of RA-based DNS Discovery, 
> > >although I could not express my opinions well enough because of the limitation of Non-English speaker.
> > 
> > Your interest is clear,
> 
> And it is also clear that his case does not need RA-based DNS
> discovery, as was pointed by two of us.
> 
> In mobile case, mobile hosts need constant DNS service. It is NOT
> acceptable that the mobile hosts try to find DNS server at
> foreign environment sometime successfully and sometimes not
> that DNS service MUST be bundled and share fate with HA service,
> which should be configured simultaneously.
[...]

There are two cases here:

 1) "mobile hosts which use Mobile IP"

 In this case, what you say may rather close to the mark.  However, note 
that if a mechanism to find DNS service is commonplace, hosts would have 
more success in finding it -- and the point of not getting it would be 
moot.  

 Moreover, the DNS service located at the home network could be the "last 
resort" service, to be used when no other DNS servers are found in foreign 
network(s).  Depending on where your home agents are (e.g. across the 
globe, 300 ms RTT away), being able to optimize to use the closer DNS 
servers would be desirable, I think.

 2) "mobile hosts without Mobile IP"

A case of this is e.g. a laptop which just plugs in networks here and
there (e.g. IETF meetings) and is not concerned on connection survability,
i.e. doesn't really have a home agent or home network (in Mobile IP
terms).  Such hosts typically require nothing else of the foreign networks
they use than DNS resolution.  They already have (in most cases!)
sufficient clock (for DNSSEC, if used), don't want DNS search path to
point to some local operator's domain because they don't care about it,
etc.

Seems like there may be some cases where DHCP-less operation could indeed 
be useful.

However, if implementing DHCP-lite or such was simple and straightforward 
enough, requiring very little effort, that just *MIGHT* be the way to go 
-- because it will have to be implemented *anyway* to cater for the needs 
of the other cases where configuring more than just the DNS server is 
needed.

I haven't really made up my mind whether DHCP-lite fulfills those
criteria.

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Tue Aug  5 06:39:17 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA06897
	for <dnsop-archive@lists.ietf.org>; Tue, 5 Aug 2003 06:39:17 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h75A0L8W008175
	for <dnsop-outgoing@nic.cafax.se>; Tue, 5 Aug 2003 12:00:21 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h75A0LUi008174
	for dnsop-outgoing; Tue, 5 Aug 2003 12:00:21 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h75A0E8W008168
	for <dnsop@cafax.se>; Tue, 5 Aug 2003 12:00:15 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308050834.RAA11131@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id RAA11131; Tue, 5 Aug 2003 17:34:43 +0900
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <Pine.LNX.4.44.0308051017030.25140-100000@netcore.fi> from Pekka
 Savola at "Aug 5, 2003 10:27:50 am"
To: Pekka Savola <pekkas@netcore.fi>
Date: Tue, 5 Aug 2003 17:34:42 +0859 ()
CC: John Schnizlein <jschnizl@cisco.com>, Jaehoon Paul Jeong <paul@etri.re.kr>,
        dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Pekka;

> > And it is also clear that his case does not need RA-based DNS
> > discovery, as was pointed by two of us.

> There are two cases here:

No.

>  1) "mobile hosts which use Mobile IP"

>  2) "mobile hosts without Mobile IP"

Don't try to misdirect the discussion.

Jaehoon Paul Jeong said:

> As one of RA camp, I think, RA-approach is useful in some of wireless networks,
> such as HMIPv6, MANET connected to the Internet and NEMO.

That is the assumption here.

Worse, most of your reasonings are wrong and rest of them are too
weak that any standardized way of DNS autoconfiguration is fine
for your requirement.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Tue Aug  5 07:01:35 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07155
	for <dnsop-archive@lists.ietf.org>; Tue, 5 Aug 2003 07:01:34 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h75AUM8W008354
	for <dnsop-outgoing@nic.cafax.se>; Tue, 5 Aug 2003 12:30:22 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h75AULxi008353
	for dnsop-outgoing; Tue, 5 Aug 2003 12:30:21 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from elektron.atoom.net (vhe-530008.sshn.net [195.169.222.38])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h75AUL8W008348
	for <dnsop@cafax.se>; Tue, 5 Aug 2003 12:30:21 +0200 (MEST)
Received: from elektron.atoom.net (localhost [127.0.0.1])
	by elektron.atoom.net (8.12.9/8.12.9/Debian-5) with ESMTP id h75AUA43021112
	for <dnsop@cafax.se>; Tue, 5 Aug 2003 12:30:11 +0200
Received: from localhost (roy@localhost)
	by elektron.atoom.net (8.12.9/8.12.9/Debian-5) with ESMTP id h75AU9ed021108
	for <dnsop@cafax.se>; Tue, 5 Aug 2003 12:30:09 +0200
X-Authentication-Warning: elektron.atoom.net: roy owned process doing -bs
Date: Tue, 5 Aug 2003 12:30:06 +0200 (CEST)
From: Roy Arends <roy@logmess.com>
X-X-Sender: roy@elektron.atoom.net
To: dnsop@cafax.se
Subject: TLD nameserver time survey.
Message-ID: <Pine.LNX.4.56.0308051055450.2490@elektron.atoom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-0.5 required=5.0
	tests=USER_AGENT_PINE,X_AUTH_WARNING
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Virus-Scanned: by amavisd-new
Sender: owner-dnsop@cafax.se
Precedence: bulk

Hello,

I've done a small survey wrt tld nameserver set. Results are below.

Comments are sollicited.

Thanks, regards

Roy

----

Introduction.

   Securing the DNS system has a common requirement. The set of systems,
   including stub resolvers, recursive resolvers and authoritative servers
   need to agree on time when DNS protocols such as TSIG, SIG(0)  and
   DNSSEC are involved. In the scope of those protocols, time is a
   factor in the defense against replay attacks.

   Time may be less a factor for authoritative nameservers regardless
   whether DNSSEC is involved, since it is recommended that signing DNS
   data for DNSSEC is done offline, i.e. an authoritative nameserver does
   not need to be in sync for purposes of answering a query. Note that a
   secured zonetransfer (TSIG/SIG(0) + IXFR/AXFR) requires the servers
   to be in sync.

   A recursive nameserver needs to be in sync to verify DNSSEC data.
   Recursive nameservers were not part of this survey, though some servers
   in this survey happen to offer recursion.

Time Survey.

   As an indication, clocks at authoritative nameservers responsible for
   the top level domains (TLDs) were compared against 'actual time'.

   As input for this exercise, the NSDNAME value in authoritative name
   server resource records (NS) in the Root Zone (SOA:2003073101) were
   resolved for their addresses. A unique pair of name and address is
   regarded as a single nameserver for this survey. These nameservers were
   queried [1] for their clock value. Not every server responded, which
   does not imply that a name server was not running.

   A received clock value is then subtracted by the 'actual time'. This
   actual time is the mean of recorded time 'on send' and 'on receive'.
   The recorded time has been synchronized through NTP with a set of
   stratum 1 time servers connected to GPS receivers.

   There is a 'response timeout' of 2 seconds which implies that there may
   be a 2 second fault. Values outside this fault window can be considered
   "out of sync".

   To give an indication of where a server set for a domain exist in time,
   the 'range' is shown for a domain.

   Say the TLD example has 5 nameservers, with the following offset:

        ns1.example   -50 seconds
        ns2.example   -12 seconds
        ns3.example     1 seconds
        ns4.example    77 seconds
        ns3.example   150 seconds

   Then 'range' for TLD 'example' is 200 (i.e. -50 to 150).

   Only domains with a range larger then 4 seconds are mentioned below.

   Note that a single nameserver may serve multiple zones. If this single
   nameserver is N seconds out of sync, all zones served by this server
   will be at least N seconds out of sync.

   Domain   Range  Domain   Range  Domain   Range  Domain   Range

   VU.      6      EDU.     7      GOV.     7      KH.      7
   NAME.    7      ORG.     7      SB.      8      JM.      11
   SG.      11     SO.      13     GF.      15     AO.      17
   BG.      17     BM.      17     CV.      17     CZ.      17
   EE.      17     HR.      17     IS.      17     LV.      17
   MY.      17     NG.      17     NL.      17     PT.      17
   RU.      17     SI.      17     SK.      17     ST.      17
   YU.      17     SE.      18     UA.      19     IL.      35
   AU.      39     PL.      39     VI.      51     HK.      61
   TR.      61     PN.      77     SY.      86     MN.      93
   NR.      102    KW.      118    NP.      120    MA.      125
   SC.      135    FM.      142    CU.      159    DJ.      162
   BZ.      163    HU.      164    BB.      165    LU.      167
   UZ.      178    NE.      185    MZ.      208    LY.      212
   AD.      231    EG.      281    GM.      281    IT.      299
   ET.      316    GT.      337    TT.      339    GE.      389
   HN.      413    ES.      459    AR.      470    UY.      470
   GG.      472    JE.      472    LT.      492    GH.      507
   LK.      514    BH.      533    QA.      613    KY.      634
   KR.      642    EC.      667    TN.      715    MO.      717
   CL.      728    DK.      762    RO.      767    VN.      788
   IQ.      824    IN.      826    AI.      908    GQ.      960
   CN.      962    MT.      976    KZ.      979    AN.      1041
   KM.      1077   JO.      1109   BN.      1143   KE.      1254
   TH.      1271   MD.      1338   AW.      1669   CA.      1677
   NU.      1824   PRO.     1980   ML.      2231   MR.      2349
   CY.      2449   TW.      2482   MG.      2928   PR.      3066
   MQ.      3312   BO.      3523   YE.      3555   DZ.      3669
   SD.      3767   IE.      3989   MIL.     3989   INT.     4381
   MUSEUM.  4475   TD.      4957   MH.      5608   TG.      5913
   GR.      5955   AL.      7217   CC.      7725   DM.      7725
   SN.      7871   BY.      8949   BI.      11563  CD.      11563
   CG.      11563  RW.      11563  IR.      12879  PK.      13242
   PY.      14491  BJ.      17872  LB.      25200  OM.      28715
   DO.      29051  MW.      29189  VE.      29574  CR.      42495
   PA.      42495  NI.      43387  SV.      43819  WS.      46440
   GP.      49643  SL.      54184  UG.      56973  NF.      60523
   HM.      84227  CX.      87640

   [1] The methodology, tools, raw data and more in-depth analysis are not
   made public here yet to allow operators to sync their nameservers. It
   is however trivial and no secret to many, to determine a servers
   timestamp.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Tue Aug  5 16:22:57 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27423
	for <dnsop-archive@lists.ietf.org>; Tue, 5 Aug 2003 16:22:56 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h75JnD8W011542
	for <dnsop-outgoing@nic.cafax.se>; Tue, 5 Aug 2003 21:49:13 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h75JnDHV011541
	for dnsop-outgoing; Tue, 5 Aug 2003 21:49:13 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h75JnC8W011536
	for <dnsop@cafax.se>; Tue, 5 Aug 2003 21:49:12 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 0659C18FB
	for <dnsop@cafax.se>; Tue,  5 Aug 2003 15:49:10 -0400 (EDT)
Date: Tue, 05 Aug 2003 15:49:10 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Keeping the DNS discovery discussion focused and civil
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030805194911.0659C18FB@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

<hat wg-co-chair=on personality-simulator-sensitivity-level=new-age>

A few observations and requests regarding the recent discussion.

1) Regardless of what we might wish, we are starting from where we are
   today, not from where we might have been had various decisions been
   made differently at some point in the past. This is not the IPv6
   WG, and we are not here to revise or debate stateless address
   autoconfiguration, neighbor discovery, etc.  The only exception to
   this that I can see is that we might reasonably conclude that the
   "O" bit in the Router Advertisement ICMPv6 message is not relevant
   to DNS discovery, in the sense that we might conclude that DNS
   discovery should be performed in the same way regardless of the
   setting of the "O" bit.

2) Several of our participants are making a serious attempt to
   communicate with each other past nontrivial language and cultural
   barriers.  Misunderstandings are very easy under such
   circumstances, and all of us (particularly those of us whose native
   language happens to be English) need to be careful both not to read
   too much into the phrasing and tone of others' messages and also to
   be sensitive to how tone and phrasing in our own postings might be
   read.  Limiting postings to subjects which are within the proper
   scope of the discussion should help, since it will at least limit
   the range of subjects on which we can have these misunderstandings.

</hat>
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 01:51:35 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09865
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 01:51:33 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h765JG8W015288
	for <dnsop-outgoing@nic.cafax.se>; Wed, 6 Aug 2003 07:19:16 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h765JGuK015287
	for dnsop-outgoing; Wed, 6 Aug 2003 07:19:16 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h765JD8W015282
	for <dnsop@cafax.se>; Wed, 6 Aug 2003 07:19:14 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308060511.OAA01338@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id OAA01338; Wed, 6 Aug 2003 14:11:02 +0900
Subject: Re: Keeping the DNS discovery discussion focused and civil
In-Reply-To: <20030805194911.0659C18FB@thrintun.hactrn.net> from Rob Austein
 at "Aug 5, 2003 03:49:10 pm"
To: Rob Austein <sra+dnsop@hactrn.net>
Date: Wed, 6 Aug 2003 14:11:01 +0859 ()
CC: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Rob Austin;

> A few observations and requests regarding the recent discussion.
> 
> 1) Regardless of what we might wish, we are starting from where we are
>    today,

that IPv6 is not deployed in the real world, partly because the
protocol suite is not complete pursuing unclear goals some of
which are impossible.

An attempt to obscure the incompleteness is to delegate some
of the work from IPv6 WG to other WGs, only to export the internal
chaos.

>    not from where we might have been had various decisions been
>    made differently at some point in the past.

Haven't we, IETF, changed a past decision to use OSI?

>    This is not the IPv6
>    WG, and we are not here to revise or debate stateless address
>    autoconfiguration, neighbor discovery, etc.

First, we should analyze the problem to its source, which is
what we are doing now.

Then, perhaps, we must define what "autoconfiguration" means,
even though we are not the IPv6 WG.

And then, we can solve some of the problem by ourselves and
recommend others to solve the rest.

> 2) Several of our participants are making a serious attempt to
>    communicate with each other past nontrivial language and cultural
>    barriers.

As we often say "read the draft", it is our culture to regard
draft reading the prerequisite to participate the discussion.

However, it is not even a cultural issue but a very basic
requirement by definition to regard reading mails, at
least recent ones of the thread, the prerequisite to
participate the mailing list discussion.

Still, I'm less demanding than you never expect people
have wide knowledge of archive content of other WGs.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 15:48:06 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02157
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 15:48:04 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76J7o8W020017
	for <dnsop-outgoing@nic.cafax.se>; Wed, 6 Aug 2003 21:07:50 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h76J7oQC020016
	for dnsop-outgoing; Wed, 6 Aug 2003 21:07:50 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76J7n8W020011
	for <dnsop@cafax.se>; Wed, 6 Aug 2003 21:07:49 +0200 (MEST)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1)
  with ESMTP-TLS id 414016; Wed, 06 Aug 2003 14:07:44 -0500
Message-ID: <3F315201.7000908@ehsco.com>
Date: Wed, 06 Aug 2003 14:07:45 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Rob Austein <sra+dnsop@hactrn.net>
CC: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>	<20030802171129.0001D190E@thrintun.hactrn.net>	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>	<20030802205235.EF43D18EA@thrintun.hactrn.net>	<3F2C2BF0.10507@ehsco.com> <20030802221126.25E3C18E3@thrintun.hactrn.net>
In-Reply-To: <20030802221126.25E3C18E3@thrintun.hactrn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 8/2/2003 5:11 PM Rob Austein wrote:

> If I understand it correctly, the simple version of what you propose
> (just using multicast to find recursive name servers, nothing else)
> substitutes one multicast-based discovery protocol for another
> multicast-based discovery protocol.  Since it's quite possible to
> co-locate a DHCP-lite "server" inside the same "process" (or whatever
> fate sharing unit a server host uses) as the recursive name server,
> the fate sharing comparision comes out as a wash when one looks at it
> closely.  So one's left arguing about relatively trivial engineering
> details like packet formats and port numbers.

Are you referring to draft-ietf-dhc-dhcpv6-stateless-00.txt or something
else? That draft makes no mention of multicast whatsoever, and the
reference context of link-local is a unicast address.

> In any case, either version of what you're talking about still looks
> to me like a proposal for new protocol work.  We're still trying to
> determine whether -any- new protocol work is needed, so this, like the

Some amount of work will need to be done no matter what. At the very
least, a set of behavioral rules will need to be codified.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 15:52:41 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02293
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 15:52:41 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76JOJ8W020125
	for <dnsop-outgoing@nic.cafax.se>; Wed, 6 Aug 2003 21:24:19 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h76JOIPg020124
	for dnsop-outgoing; Wed, 6 Aug 2003 21:24:18 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76JOH8W020119
	for <dnsop@cafax.se>; Wed, 6 Aug 2003 21:24:18 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id A650B1909
	for <dnsop@cafax.se>; Wed,  6 Aug 2003 15:24:16 -0400 (EDT)
Date: Wed, 06 Aug 2003 15:24:16 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <3F315201.7000908@ehsco.com>
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>
	<20030802171129.0001D190E@thrintun.hactrn.net>
	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>
	<20030802205235.EF43D18EA@thrintun.hactrn.net>
	<3F2C2BF0.10507@ehsco.com>
	<20030802221126.25E3C18E3@thrintun.hactrn.net>
	<3F315201.7000908@ehsco.com>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030806192416.A650B1909@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Wed, 06 Aug 2003 14:07:45 -0500, Eric A. Hall wrote:
> 
> Are you referring to draft-ietf-dhc-dhcpv6-stateless-00.txt or something
> else? That draft makes no mention of multicast whatsoever, and the
> reference context of link-local is a unicast address.

draft-ietf-dhc-dhcpv6-stateless-00.txt is primarily a guide to the
relevant portions of the DHCPv6 spec, and includes a bunch of
normative references.  Try RFC 3315 section 1.2.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 17:16:55 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05310
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 17:16:54 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76Kf08W020595
	for <dnsop-outgoing@nic.cafax.se>; Wed, 6 Aug 2003 22:41:00 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h76Kf0LD020594
	for dnsop-outgoing; Wed, 6 Aug 2003 22:41:00 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76Kex8W020589
	for <dnsop@cafax.se>; Wed, 6 Aug 2003 22:41:00 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 8A91018FB
	for <dnsop@cafax.se>; Wed,  6 Aug 2003 16:40:58 -0400 (EDT)
Date: Wed, 06 Aug 2003 16:40:58 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: the well-known address approach
In-Reply-To: <200308060511.OAA01338@necom830.hpcl.titech.ac.jp>
References: <20030805194911.0659C18FB@thrintun.hactrn.net>
	<200308060511.OAA01338@necom830.hpcl.titech.ac.jp>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030806204058.8A91018FB@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Wed, 6 Aug 2003 14:11:01 +0859, Masataka Ohta wrote:
> 
> Still, I'm less demanding than you never expect people
> have wide knowledge of archive content of other WGs.

That's a fair criticism.  I've been reluctant to attempt to summarize
the IPv6 WG's discussion of the well-known-address proposal, in part
because I was hardly a neutral party in that debate and thus would
prefer to let others form their own conclusions.  However, since
you're correct that it's unfair to say that one has to understand that
whole debate to participate in this WG's discussion of requirements,
I'll try to summarize what I remember, with the understanding that
this is just my view.  For those who have the interest and patience to
dig through the IPv6 WG archives, the relevant stuff probably starts
in April of 2002 and runs (on and off) through October 2002.

Ignoring irrelevant issues (eg, the IPv6 Site-Local swamp), I still
have concerns with the well-known address approach:

- How does this interact with LLMNR?  Eg, how is a node supposed to
  know whether it should be doing LLMNR or not?  (NB: I'm no fan of
  LLMNR, but it's out there and people are using it.)

- There are layering and administrative issues.  This approach puts
  the DNS configuration information into the routing system.  It's not
  immediately obvious that the local routing system and the local
  recursive name servers are necessarily controlled by the same
  administrators, so there are issues with how updates get into the
  routing system, with how (and whether) the routing system reflects
  recursive name servers that die or move, and so forth.

- There are also fate sharing and coupling issues.  Using well-known
  addresses hides the binding between the addresses and the particular
  recursive name servers in question, which may matter if one or more
  of the recursive name servers starts flaking out.  In the "normal"
  (not well-known-address) case, a resolver can keep track of which of
  the recursive name servers it's using is performing, and might
  conceivably inititate some form of recovery action (eg, probing for
  a new set of recursive name servers) if something bad happens.  In
  the well-known-address case, none of that is likely to work well.

There may have been other issues, but those are the ones I remember.

Summarizing: I think this approach is a step towards the smart
network/dumb host model beloved by telcos, and is a step away from the
smart host/dumb network model that's traditional for Internet
applications (this is, of course, an oversimplification, the truth is
and always has been more complicated, but it's close enough for this
summary).  So this approach might well make sense in certain kinds of
networks, but not in others, and thus it's not obvious to me that this
is the right general solution.

Hope this helps.  Folks who disagree are of course welcome to respond,
with the understanding that the goal here is still the quest to
understand the requirements for DNS discovery here in the DNSOP WG,
not recounting the history of a particular draft.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 17:46:40 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06114
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 17:46:39 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76LBW8W020796
	for <dnsop-outgoing@nic.cafax.se>; Wed, 6 Aug 2003 23:11:32 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h76LBWx5020795
	for dnsop-outgoing; Wed, 6 Aug 2003 23:11:32 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76LBV8W020790
	for <dnsop@cafax.se>; Wed, 6 Aug 2003 23:11:31 +0200 (MEST)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1)
  with ESMTP-TLS id 414022; Wed, 06 Aug 2003 16:11:27 -0500
Message-ID: <3F316EFF.1090709@ehsco.com>
Date: Wed, 06 Aug 2003 16:11:27 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Rob Austein <sra+dnsop@hactrn.net>
CC: dnsop@cafax.se
Subject: Re: Policy of IPv6 DNS Discovery
References: <002301c35895$f9b5abb0$c470fe81@etri.re.kr>	<20030802171129.0001D190E@thrintun.hactrn.net>	<4.3.2.7.2.20030802110556.032a81d8@mailhost.iprg.nokia.com>	<20030802205235.EF43D18EA@thrintun.hactrn.net>	<3F2C2BF0.10507@ehsco.com>	<20030802221126.25E3C18E3@thrintun.hactrn.net>	<3F315201.7000908@ehsco.com> <20030806192416.A650B1909@thrintun.hactrn.net>
In-Reply-To: <20030806192416.A650B1909@thrintun.hactrn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 8/6/2003 2:24 PM Rob Austein wrote:

> Try RFC 3315 section 1.2.

Okay, that and various other sections helped.

As I see it there are a few issues that would need to be described, and
which would effectively equate to protocol work. This includes your
proposal that servers should return a single-item list of just themselves
(or not, if you want to do something else), client algorithms for sorting
the responses (eg, weighted according to the search lists, in comparison
to the host's known domain), recovery options (which do not seem to be
described), and possibly IPv4 support which was listed as a desirable
feature (and would be desirable for the networks I work with, too).

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 19:33:22 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10118
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 19:33:22 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76N3m8W021582
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 01:03:48 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h76N3mev021581
	for dnsop-outgoing; Thu, 7 Aug 2003 01:03:48 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sa.vix.com (sa.vix.com [204.152.187.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h76N3l8W021576
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 01:03:47 +0200 (MEST)
Received: by sa.vix.com (Postfix, from userid 716)
	id D1D3413976; Wed,  6 Aug 2003 23:03:41 +0000 (GMT)
To: dnsop@cafax.se
Subject: Re: the well-known address approach
References: <20030806204058.8A91018FB@thrintun.hactrn.net>
From: Paul Vixie <vixie@vix.com>
Date: 06 Aug 2003 23:03:41 +0000
In-Reply-To: <20030806204058.8A91018FB@thrintun.hactrn.net>
Message-ID: <g3ekzy75iq.fsf@sa.vix.com>
Lines: 14
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@cafax.se
Precedence: bulk

sra+dnsop@hactrn.net (Rob Austein) writes:

> Ignoring irrelevant issues (eg, the IPv6 Site-Local swamp), I still
> have concerns with the well-known address approach:
> ...

I agree with Rob's objections to this approach.  Asking for a well known
address for DNS begs questions like, why do we need to use IRDP or DHCP to
tell a host its default router -- we can just designate the all-zeroes
address in any given subnet for "default route service".  And so on.  This
way lies madness, and we need a layer of indirection where policy can be
localized.
-- 
Paul Vixie
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 20:29:32 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11355
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 20:29:31 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7700m8W022071
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 02:00:48 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7700mUV022070
	for dnsop-outgoing; Thu, 7 Aug 2003 02:00:48 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7700k8W022065
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 02:00:47 +0200 (MEST)
Received: from esunmail ([129.147.156.34])
	by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h7700jL0010480
	for <dnsop@cafax.se>; Wed, 6 Aug 2003 18:00:46 -0600 (MDT)
Received: from xpa-fe1 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTP id <0HJ8001OI2P9FY@edgemail1.Central.Sun.COM> for dnsop@cafax.se;
 Wed, 06 Aug 2003 18:00:45 -0600 (MDT)
Received: from sun.com ([129.146.12.17])
 by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPSA id <0HJ80020T2P3PT@mail.sun.net> for dnsop@cafax.se; Wed,
 06 Aug 2003 18:00:39 -0600 (MDT)
Date: Wed, 06 Aug 2003 17:00:38 -0700
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: the well-known address approach
To: Rob Austein <sra+dnsop@hactrn.net>
Cc: dnsop@cafax.se
Message-id: <3F3196A6.10003@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920
 Netscape/7.0
References: <20030805194911.0659C18FB@thrintun.hactrn.net>
 <200308060511.OAA01338@necom830.hpcl.titech.ac.jp>
 <20030806204058.8A91018FB@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Being the last author of the well known address document
in the v6 wg, I feel I can answer for the sake of clarification.
I do not intend to reopen the discussion, so I will try to limit
myself to this post only.

See inline.

Rob Austein wrote:

>- How does this interact with LLMNR?  Eg, how is a node supposed to
>  know whether it should be doing LLMNR or not?  (NB: I'm no fan of
>  LLMNR, but it's out there and people are using it.)
>
This is an orthogonal issue. Any DNS discovery mechanism will
have to face this. Beside, this is an LLMNR issue.

>- There are layering and administrative issues.  This approach puts
>  the DNS configuration information into the routing system.  It's not
>  immediately obvious that the local routing system and the local
>  recursive name servers are necessarily controlled by the same
>  administrators, so there are issues with how updates get into the
>  routing system, with how (and whether) the routing system reflects
>  recursive name servers that die or move, and so forth.
>
This is the same issue with DHCP-lite or RA. The routing folks
have to put some configuration in their routers, and this configuration
is derived from what the DNS folks tells them.

>- There are also fate sharing and coupling issues.  Using well-known
>  addresses hides the binding between the addresses and the particular
>  recursive name servers in question, which may matter if one or more
>  of the recursive name servers starts flaking out.  In the "normal"
>  (not well-known-address) case, a resolver can keep track of which of
>  the recursive name servers it's using is performing, and might
>  conceivably inititate some form of recovery action (eg, probing for
>  a new set of recursive name servers) if something bad happens.  In
>  the well-known-address case, none of that is likely to work well.
>  
>
Fate sharing is not specific to the well know address.
With RA or DHCP-lite, there is also fate sharing on the local router
between the routing process and the RA/DHCP-lite one.

The loss of strong binding with the DNS server is anl issue.
With the well known address, you somehow lose track of who
you're talking to, especially if that address is an anycast one.
Note that the latest draft was especially not using the term anycast
and was reserving 3 addresses, so you could somehow mitigate
the issue by placing 3 servers with 3 different addresses. That way
the DNS client/stub resolver could try another server if the current
one started to behave badly.

Generally speaking, sevral people were uncomfortable
with the idea of overloading IP addresses with service semantic.
For example, it is common practice in IPv4 to use x.x.x.1/24 or y.y.y.254/24
for the local router on the link, but there is no protocol that makes
this assumption. People were reluctant to make this step in IPv6.

    - Alain.

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug  6 22:15:06 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13963
	for <dnsop-archive@lists.ietf.org>; Wed, 6 Aug 2003 22:15:05 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h771gU8W023540
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 03:42:30 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h771gUlC023539
	for dnsop-outgoing; Thu, 7 Aug 2003 03:42:30 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from stoneport.math.uic.edu (stoneport.math.uic.edu [131.193.178.160])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with SMTP id h771gN8W023534
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 03:42:29 +0200 (MEST)
Received: (qmail 15607 invoked by uid 1016); 7 Aug 2003 01:42:43 -0000
Date: 7 Aug 2003 01:42:43 -0000
Message-ID: <20030807014243.15606.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: dnsop@cafax.se
Subject: Re: the well-known address approach
References: <20030806204058.8A91018FB@thrintun.hactrn.net> <g3ekzy75iq.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-dnsop@cafax.se
Precedence: bulk

Paul Vixie writes:
> we can just designate the all-zeroes address in any given subnet for
> "default route service".  And so on.  This way lies madness

Taking away layers of indirection isn't always a good idea, but it's
inherently self-limiting. Madness lies in the opposite direction, where
people keep adding unnecessary layers of indirection. Examples:

   * ``Instead of specifying port 25 for SMTP, let's use SRV to declare
     site-specific SMTP ports!''
   * ``Instead of specifying IP addresses in NS records, let's specify
     host names, which will be resolved recursively!''
   * ``Instead of specifying a universal character set, let's have every
     piece of text tagged with its character set!''

There's no limit to the amount of ``configurability'' bloat that people
can---and do---add to their designs.

If there's a real advantage to indirection in the router address, DNS
cache address, etc., then someone should be able to state exactly what
that advantage is. So far, all I've seen are religious comments about
how this is ``madness,'' ``not the way the Internet works,'' etc.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 02:03:38 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22913
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 02:03:36 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h775TD8W024742
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 07:29:13 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h775TCgL024741
	for dnsop-outgoing; Thu, 7 Aug 2003 07:29:12 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h775T58W024730
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 07:29:06 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308070513.OAA05697@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id OAA05697; Thu, 7 Aug 2003 14:12:47 +0859
Subject: [OT] stateless vs universal  (was: Re: the well-known address approach)
In-Reply-To: <20030807014243.15606.qmail@cr.yp.to> from "D. J. Bernstein" at
 "Aug 7, 2003 01:42:43 am"
To: "D. J. Bernstein" <djb@cr.yp.to>
Date: Thu, 7 Aug 2003 14:12:46 +0859 ()
CC: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

D. J. Bernstein;

This message is of topic, except that ND and Unicode share similar
chaos.

>    * ``Instead of specifying a universal character set, let's have every
>      piece of text tagged with its character set!''

Right.

However...

> Taking away layers of indirection isn't always a good idea, but it's
> inherently self-limiting. Madness lies in the opposite direction, where
> people keep adding unnecessary layers of indirection. Examples:

The fundamental cause of the chaos is to invent terminology, such
as "stateless autoconfiguration" or "universal character set",
without defining its meaning.

>    * ``Instead of specifying a universal character set, let's have every
>      piece of text tagged with its character set!''

In Unicode case, there is no definition on "a universal character
set".

As a result, extra tagging, such as a language tag, is added,
as an imprecise alternative of script tagging, if you want to
use Unicode in universal, international, environment.

As we gain more experience, it becomes more and more obvious that
ISO 2022, which was denied because it were not universal, is the
mechanism for "universal character set", just as DHCP, which
was denied because it were not stateless, is the mechanism for
"stateless autoconfiguration".

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 02:38:59 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02334
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 02:38:58 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7769C8W025038
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 08:09:12 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7769CxV025037
	for dnsop-outgoing; Thu, 7 Aug 2003 08:09:12 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h776998W025031
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 08:09:10 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308070557.OAA06014@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id OAA06014; Thu, 7 Aug 2003 14:56:58 +0859
Subject: Re: the well-known address approach
In-Reply-To: <20030806204058.8A91018FB@thrintun.hactrn.net> from Rob Austein
 at "Aug 6, 2003 04:40:58 pm"
To: Rob Austein <sra+dnsop@hactrn.net>
Date: Thu, 7 Aug 2003 14:56:58 +0859 ()
CC: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Rob Austin;

> I'll try to summarize what I remember, with the understanding that
> this is just my view.

Thank you.

> Ignoring irrelevant issues (eg, the IPv6 Site-Local swamp),

That is a reason good enough to avoid reading the archives by myself.

> I still have concerns with the well-known address approach:

Most, if not all, of the concerns is seemingly addressed by Alain
that I add my own comments.

> - How does this interact with LLMNR?  Eg, how is a node supposed to
>   know whether it should be doing LLMNR or not?  (NB: I'm no fan of
>   LLMNR, but it's out there and people are using it.)

LLMNR was another swamp, but is filled up by DNSOP. So, the LLMNR
document has made it clear how the interaction between LLMNR and
configured DNS servers, hasn't it?

However, I sill am not so sure what the precise requirement of
LLMNR is, so that some of it may be overridden by DNS
autoconfiguration, but it is not anycast-specific and is a
problem of LLMNR.

> - There are layering and administrative issues.  This approach puts
>   the DNS configuration information into the routing system.  It's not
>   immediately obvious that the local routing system and the local
>   recursive name servers are necessarily controlled by the same
>   administrators,

In anycast proposal, it is not assumed that the local routing
system and the local (or external) recursive name servers are
necessarily controlled by the same administrators.

An example is ISP controlled name servers exemplified in
my draft. But, the point should have been sunken in the
swamp of scope.

Router configuration is required to limit the scope of local
(or external) recursive name servers, which is common to all
the proposals here.

> - There are also fate sharing and coupling issues.  Using well-known
>   addresses hides the binding between the addresses and the particular
>   recursive name servers in question, which may matter if one or more
>   of the recursive name servers starts flaking out. 

>   In the "normal"
>   (not well-known-address) case, a resolver can keep track of which of
>   the recursive name servers it's using is performing, and might
>   conceivably inititate some form of recovery action (eg, probing for
>   a new set of recursive name servers) if something bad happens.  In
>   the well-known-address case, none of that is likely to work well.

Then, autoconfigured case, where hosts blindly believe anything
configured even if something bad happens, is not "normal".

Or, if one insists that a host can be autoconfigured with multiple
sets of resolvers, a host can be preconfigured with multiple sets
of anycast addresses.

> There may have been other issues, but those are the ones I remember.

So far, it is a summary of the archives and is not necessarily
your opinion, I presume.

> Summarizing: I think this approach is a step towards the smart

OK, you think, now.

> network/dumb host model beloved by telcos, and is a step away from the
> smart host/dumb network model that's traditional for Internet
> applications (this is, of course, an oversimplification, the truth is
> and always has been more complicated, but it's close enough for this
> summary).

If a set of global addresses are tied to a global servers, yes,
which is the case of current root servers.

However, anycast allows for local control of root servers and
default recursive servers, even if addresses of them have
a global scope.

So, just say, anycast.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 02:46:06 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02533
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 02:46:06 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h776LN8W025113
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 08:21:23 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h776LNtt025112
	for dnsop-outgoing; Thu, 7 Aug 2003 08:21:23 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h776LM8W025107
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 08:21:22 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h776LDc20123;
	Thu, 7 Aug 2003 09:21:13 +0300
Date: Thu, 7 Aug 2003 09:21:13 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Alain Durand <Alain.Durand@Sun.COM>
cc: Rob Austein <sra+dnsop@hactrn.net>, <dnsop@cafax.se>
Subject: Re: the well-known address approach
In-Reply-To: <3F3196A6.10003@sun.com>
Message-ID: <Pine.LNX.4.44.0308070919120.19597-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Wed, 6 Aug 2003, Alain Durand wrote:
[...]
> Generally speaking, sevral people were uncomfortable
> with the idea of overloading IP addresses with service semantic.
> For example, it is common practice in IPv4 to use x.x.x.1/24 or y.y.y.254/24
> for the local router on the link, but there is no protocol that makes
> this assumption. People were reluctant to make this step in IPv6.

There is such an address -- the subnet-router anycast address.  However, 
I'm not so sure it works in all the cases, e.g. RFC2461 Redirects, or that 
it even should..

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 02:46:06 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02532
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 02:46:06 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h776OH8W025162
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 08:24:17 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h776OHZd025161
	for dnsop-outgoing; Thu, 7 Aug 2003 08:24:17 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h776OG8W025155
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 08:24:16 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h776NRG20129;
	Thu, 7 Aug 2003 09:23:27 +0300
Date: Thu, 7 Aug 2003 09:23:27 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: John Schnizlein <jschnizl@cisco.com>, Jaehoon Paul Jeong <paul@etri.re.kr>,
        <dnsop@cafax.se>
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <200308050834.RAA11131@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0308070922000.19597-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Tue, 5 Aug 2003, Masataka Ohta wrote:
> >  1) "mobile hosts which use Mobile IP"
> 
> >  2) "mobile hosts without Mobile IP"
> 
> Don't try to misdirect the discussion.
> 
> Jaehoon Paul Jeong said:
> 
> > As one of RA camp, I think, RA-approach is useful in some of wireless networks,
> > such as HMIPv6, MANET connected to the Internet and NEMO.
> 
> That is the assumption here.

I'm not restricting myself to Jaehoon's assumptions about applicability of 
RA-approaches.  I'm just pointing out that when one says "mobile node", it 
can mean at least a couple of different things.
 
> Worse, most of your reasonings are wrong and rest of them are too
> weak that any standardized way of DNS autoconfiguration is fine
> for your requirement.

Please elaborate.

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 08:32:49 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09977
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 08:32:48 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77C2G8W027083
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 14:02:16 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h77C2GOp027082
	for dnsop-outgoing; Thu, 7 Aug 2003 14:02:16 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77C2F8W027077
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 14:02:15 +0200 (MEST)
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h77C2Cpp021530
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 05:02:13 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.215])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ABI42868;
	Thu, 7 Aug 2003 08:02:10 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030807060857.04196320@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 07 Aug 2003 08:02:08 -0400
To: dnsop@cafax.se
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: the well-known address approach
In-Reply-To: <20030806204058.8A91018FB@thrintun.hactrn.net>
References: <200308060511.OAA01338@necom830.hpcl.titech.ac.jp>
 <20030805194911.0659C18FB@thrintun.hactrn.net>
 <200308060511.OAA01338@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-dnsop@cafax.se
Precedence: bulk

I believe there is also a scaling issue.  If the well-known address 
mechanism is truly limited to unicast (and not anycast) addressing, an 
enterprise can only deploy as many recursive name servers as there are 
reserved, well-known addresses.

Another potential issue is that deployment of hosts using the well-known 
addresses will force network operators to support DNS service at those 
well-known addresses, even if some other service architecture would be 
better suited to that network's requirements.

- Ralph

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 08:32:51 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09993
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 08:32:50 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77BxO8W027063
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 13:59:24 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h77BxOfC027062
	for dnsop-outgoing; Thu, 7 Aug 2003 13:59:24 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77BxL8W027057
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 13:59:22 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308071145.UAA10376@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id UAA10376; Thu, 7 Aug 2003 20:44:46 +0859
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <Pine.LNX.4.44.0308070922000.19597-100000@netcore.fi> from Pekka
 Savola at "Aug 7, 2003 09:23:27 am"
To: Pekka Savola <pekkas@netcore.fi>
Date: Thu, 7 Aug 2003 20:44:45 +0859 ()
CC: John Schnizlein <jschnizl@cisco.com>, Jaehoon Paul Jeong <paul@etri.re.kr>,
        dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Pekka Savola;

> > > There are two cases here:

> > >  1) "mobile hosts which use Mobile IP"
> > 
> > >  2) "mobile hosts without Mobile IP"
> > 
> > Don't try to misdirect the discussion.

> > > As one of RA camp, I think, RA-approach is useful in some of wireless networks,
> > > such as HMIPv6, MANET connected to the Internet and NEMO.
> > 
> > That is the assumption here.

> I'm not restricting myself to Jaehoon's assumptions

Here, you are restricted by the context with which we are discussing,
if you want to contribute to the discussion.

> I'm just pointing out that when one says "mobile node", it 
> can mean at least a couple of different things.

Do it elsewhere, not here.

Here, in this thread at least, we already have an established
terminology, defined by Jaehoon Paul Jeong, on mobility.

Note also that the definition is well established in IETF that
you should find somewhere outside of IETF.

> > Worse, most of your reasonings are wrong and rest of them are too
> > weak that any standardized way of DNS autoconfiguration is fine
> > for your requirement.
> 
> Please elaborate.

Read recent mails of this WG to find the elaboration.

						Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 09:26:27 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11527
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 09:26:25 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77CsT8W027462
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 14:54:29 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h77CsT0h027461
	for dnsop-outgoing; Thu, 7 Aug 2003 14:54:29 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77CsS8W027448
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 14:54:28 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h77CsIG23957;
	Thu, 7 Aug 2003 15:54:18 +0300
Date: Thu, 7 Aug 2003 15:54:18 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Ralph Droms <rdroms@cisco.com>
cc: dnsop@cafax.se
Subject: Re: the well-known address approach
In-Reply-To: <4.3.2.7.2.20030807060857.04196320@funnel.cisco.com>
Message-ID: <Pine.LNX.4.44.0308071548360.23883-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Thu, 7 Aug 2003, Ralph Droms wrote:
> I believe there is also a scaling issue.  If the well-known address 
> mechanism is truly limited to unicast (and not anycast) addressing, an 
> enterprise can only deploy as many recursive name servers as there are 
> reserved, well-known addresses.

It depends on what you mean by "anycast" here.

If well-known addresses are shared-unicast addresses (by the terminology 
of draft-ietf-ipngwg-ipv6-anycast-analysis-02.txt), it might go easier.

You could just deploy the same (service) address in a lot of different
nodes, and just propagate host routes to those service addresses in the
internal routing; so, there could be more servers, but based on one node's
temporal view of the topology, it could only see N (e.g. three) at the
time and the place.
 
> Another potential issue is that deployment of hosts using the well-known 
> addresses will force network operators to support DNS service at those 
> well-known addresses, even if some other service architecture would be 
> better suited to that network's requirements.

Agreed, this may be an issue.  However, just as well you could redirect 
all of those to a box (even a router) which could proxy those requests to 
some otherwise configured DNS servers.

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 12:24:13 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21123
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 12:24:12 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77FaY8W028733
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 17:36:34 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h77FaYCj028732
	for dnsop-outgoing; Thu, 7 Aug 2003 17:36:34 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77FaX8W028727
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 17:36:33 +0200 (MEST)
Received: from cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 07 Aug 2003 08:41:31 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h77FaULH008562
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 08:36:31 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.215])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ABI62084;
	Thu, 7 Aug 2003 11:36:28 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030807113039.0448a5a0@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 07 Aug 2003 11:36:26 -0400
To: dnsop@cafax.se
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: the well-known address approach
In-Reply-To: <Pine.LNX.4.44.0308071548360.23883-100000@netcore.fi>
References: <4.3.2.7.2.20030807060857.04196320@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-dnsop@cafax.se
Precedence: bulk

I really did mean to talk about unicast as opposed to any kind of anycast,
because the most recent published description of a scheme for using
well-known addresses to access DNS service
<draft-ietf-ipv6-dns-discovery-07.txt> specifies unicast.  If I remember
correctly, the earlier discussion about well-known addresses progressed from
specifying anycast to unicast because of concerns that "just propagate host
routes to those service addresses in the internal routing" might prove to be
complicated in practice.

- Ralph

At 03:54 PM 8/7/2003 +0300, Pekka Savola wrote:
>On Thu, 7 Aug 2003, Ralph Droms wrote:
> > I believe there is also a scaling issue.  If the well-known address
> > mechanism is truly limited to unicast (and not anycast) addressing, an
> > enterprise can only deploy as many recursive name servers as there are
> > reserved, well-known addresses.
>
>It depends on what you mean by "anycast" here.
>
>If well-known addresses are shared-unicast addresses (by the terminology
>of draft-ietf-ipngwg-ipv6-anycast-analysis-02.txt), it might go easier.
>
>You could just deploy the same (service) address in a lot of different
>nodes, and just propagate host routes to those service addresses in the
>internal routing; so, there could be more servers, but based on one node's
>temporal view of the topology, it could only see N (e.g. three) at the
>time and the place.
>
> > Another potential issue is that deployment of hosts using the well-known
> > addresses will force network operators to support DNS service at those
> > well-known addresses, even if some other service architecture would be
> > better suited to that network's requirements.
>
>Agreed, this may be an issue.  However, just as well you could redirect
>all of those to a box (even a router) which could proxy those requests to
>some otherwise configured DNS servers.
>
>--
>Pekka Savola                 "You each name yourselves king, yet the
>Netcore Oy                    kingdom bleeds."
>Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug  7 16:41:43 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01821
	for <dnsop-archive@lists.ietf.org>; Thu, 7 Aug 2003 16:41:42 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77K9N8W000863
	for <dnsop-outgoing@nic.cafax.se>; Thu, 7 Aug 2003 22:09:23 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h77K9NuG000862
	for dnsop-outgoing; Thu, 7 Aug 2003 22:09:23 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h77K9K8W000857
	for <dnsop@cafax.se>; Thu, 7 Aug 2003 22:09:21 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308071956.EAA01972@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id EAA01972; Fri, 8 Aug 2003 04:55:50 +0859
Subject: Re: the well-known address approach
In-Reply-To: <4.3.2.7.2.20030807113039.0448a5a0@funnel.cisco.com> from Ralph
 Droms at "Aug 7, 2003 11:36:26 am"
To: Ralph Droms <rdroms@cisco.com>
Date: Fri, 8 Aug 2003 04:55:49 +0859 ()
CC: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Ralph;

> I really did mean to talk about unicast as opposed to any kind of anycast,
> because the most recent published description of a scheme for using
> well-known addresses to access DNS service
> <draft-ietf-ipv6-dns-discovery-07.txt> specifies unicast.

See

	draft-ohta-preconfigured-dns-00.txt

> If I remember
> correctly, the earlier discussion about well-known addresses progressed from
> specifying anycast to unicast because of concerns that "just propagate host
> routes to those service addresses in the internal routing" might prove to be
> complicated in practice.

Routers just propagate routes with no configuration that there is no
complication.

> Another potential issue is that deployment of hosts using the well-known
> addresses will force network operators to support DNS service at those
> well-known addresses, even if some other service architecture would be
> better suited to that network's requirements.

As the DNS is the name service, it is an issue of those who want
to provide alternatives. See, for example, LLMNR draft of this WG.
Another approach could be to use DHCP to override the default.

						Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 08:22:11 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08929
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 08:22:10 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78Bif8W006718
	for <dnsop-outgoing@nic.cafax.se>; Fri, 8 Aug 2003 13:44:41 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h78Bifpd006717
	for dnsop-outgoing; Fri, 8 Aug 2003 13:44:41 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78Bid8W006712
	for <dnsop@cafax.se>; Fri, 8 Aug 2003 13:44:40 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h78Bhpm03827;
	Fri, 8 Aug 2003 14:43:51 +0300
Date: Fri, 8 Aug 2003 14:43:50 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Ralph Droms <rdroms@cisco.com>
cc: dnsop@cafax.se
Subject: Re: the well-known address approach
In-Reply-To: <4.3.2.7.2.20030807113039.0448a5a0@funnel.cisco.com>
Message-ID: <Pine.LNX.4.44.0308081438500.2900-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Thu, 7 Aug 2003, Ralph Droms wrote:
> I really did mean to talk about unicast as opposed to any kind of anycast,
> because the most recent published description of a scheme for using
> well-known addresses to access DNS service
> <draft-ietf-ipv6-dns-discovery-07.txt> specifies unicast.  If I remember
> correctly, the earlier discussion about well-known addresses progressed from
> specifying anycast to unicast because of concerns that "just propagate host
> routes to those service addresses in the internal routing" might prove to be
> complicated in practice.

The argument I've heard a lot is one of architectural purity, as the 
address architecture states (for example):

--8<--
2.6 Anycast Addresses
                                                                                                                         
   An IPv6 anycast address is an address that is assigned to more than
   one interface (typically belonging to different nodes), with the
   property that a packet sent to an anycast address is routed to the
   "nearest" interface having that address, according to the routing
   protocols' measure of distance.
                                                                                                                         
   Anycast addresses are allocated from the unicast address space, using
   any of the defined unicast address formats.  Thus, anycast addresses
   are syntactically indistinguishable from unicast addresses.  When a
   unicast address is assigned to more than one interface, thus turning
   it into an anycast address, the nodes to which the address is
   assigned must be explicitly configured to know that it is an anycast
   address.

[...]
--8<--

I.e. that any address which is allocated in more than one interface turns 
into an anycast address... and there can be _no_ "nearest-unicast" 
addresses at all.

Needless to say I disagree with this model... :-)

> At 03:54 PM 8/7/2003 +0300, Pekka Savola wrote:
> >On Thu, 7 Aug 2003, Ralph Droms wrote:
> > > I believe there is also a scaling issue.  If the well-known address
> > > mechanism is truly limited to unicast (and not anycast) addressing, an
> > > enterprise can only deploy as many recursive name servers as there are
> > > reserved, well-known addresses.
> >
> >It depends on what you mean by "anycast" here.
> >
> >If well-known addresses are shared-unicast addresses (by the terminology
> >of draft-ietf-ipngwg-ipv6-anycast-analysis-02.txt), it might go easier.
> >
> >You could just deploy the same (service) address in a lot of different
> >nodes, and just propagate host routes to those service addresses in the
> >internal routing; so, there could be more servers, but based on one node's
> >temporal view of the topology, it could only see N (e.g. three) at the
> >time and the place.
> >
> > > Another potential issue is that deployment of hosts using the well-known
> > > addresses will force network operators to support DNS service at those
> > > well-known addresses, even if some other service architecture would be
> > > better suited to that network's requirements.
> >
> >Agreed, this may be an issue.  However, just as well you could redirect
> >all of those to a box (even a router) which could proxy those requests to
> >some otherwise configured DNS servers.
> >
> >--
> >Pekka Savola                 "You each name yourselves king, yet the
> >Netcore Oy                    kingdom bleeds."
> >Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> 
> #----------------------------------------------------------------------
> # To unsubscribe, send a message to <dnsop-request@cafax.se>.
> 

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 16:16:12 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24217
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 16:16:10 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78Jax8W009238
	for <dnsop-outgoing@nic.cafax.se>; Fri, 8 Aug 2003 21:36:59 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h78Jaxj3009237
	for dnsop-outgoing; Fri, 8 Aug 2003 21:36:59 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78Jav8W009232
	for <dnsop@cafax.se>; Fri, 8 Aug 2003 21:36:57 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 237A618E0
	for <dnsop@cafax.se>; Fri,  8 Aug 2003 15:36:56 -0400 (EDT)
Date: Fri, 08 Aug 2003 15:36:56 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: scope
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030808193656.237A618E0@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

Messieurs Ohta and Vixie got me thinking about scoping and fault
isolation in the approaches we've been discussing.  No, this is not
about IPv6 site-local and I will thank y'all not to bring that up :).

Ohta-san is correct that every single one of the approaches we've
discussed has some kind of scoping constraint which, ultimately, is
decided by some human action or inaction.  Router configuration of
routes to well-known addresses, router configuration of RA, router
configuration of multicast, DHCP relay configuration, doesn't matter.
All of these mechanisms have some kind of scoping control with a
default that may need to be changed by a human.

One place where these approaches differ in interesting ways, however,
is in the default behavior.  This is particularly interesting when
trying to understand the failure modes of each of these approaches
if they're implemented or administered badly.

- RA/ND-based: if RA/ND isn't configured, discovery doesn't happen.

- Multicast-query based (DHCP, DHCP-lite, LLMNR-like, whatever): if
  router multicast (or DHCP relay) isn't configured, may work anyway
  on the local link, but otherwise discovery doesn't happen.

- Well-known address based: discovery propagates upstream following
  the default route until it finds something or hits the edge of the
  default free routing zone.  Discovery does not work if neither
  well-known address nor default route is configured.

Assuming that one buys this analysis, this says that the well-known
address approach is significantly different, in ways that are both
good and bad.  Good, because it means that dumb edge networks may just
inherit the necessary data from the larger networks to which they're
attached (although one might have security issues, eg, trust
boundaries for use of the AD bit).  Bad, because this has the
potential to turn into a bug amplifier.  Think, for example, about a
hypothetical firewall product that blocks inbound recursive responses:
this doesn't hurt the outside world so long as the well-known address
points to something inside the firewall, but what happens if the
well-known address route gets hosed?  Oops.

One hopes that no ISP would ever be silly enough to advertise or
accept routes for these well-known addresess in the default free zone.

Bottom line is that thinking about fault isolation gives me another
reason for discomfort with the well-known address approach.  YMMV.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 17:42:36 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27206
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 17:42:35 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78L7C8W009744
	for <dnsop-outgoing@nic.cafax.se>; Fri, 8 Aug 2003 23:07:12 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h78L7CYi009743
	for dnsop-outgoing; Fri, 8 Aug 2003 23:07:12 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from stoneport.math.uic.edu (stoneport.math.uic.edu [131.193.178.160])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with SMTP id h78L7A8W009738
	for <dnsop@cafax.se>; Fri, 8 Aug 2003 23:07:10 +0200 (MEST)
Received: (qmail 17649 invoked by uid 1016); 8 Aug 2003 21:07:29 -0000
Date: 8 Aug 2003 21:07:29 -0000
Message-ID: <20030808210729.17648.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: dnsop@cafax.se
Subject: Re: scope
References: <20030808193656.237A618E0@thrintun.hactrn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-dnsop@cafax.se
Precedence: bulk

Rob Austein writes:
> Think, for example, about a hypothetical firewall product that blocks
> inbound recursive responses: this doesn't hurt the outside world so
> long as the well-known address points to something inside the firewall,
> but what happens if the well-known address route gets hosed?  Oops.

The administrator who sets up that firewall, but neglects to set up DNS
service inside it, will find that his clients can't browse the web. This
is exactly the behavior I'd expect.

Why do you say ``Oops''? What's the big deal?

Do you also worry when people set up DNS caches that are firewalled away
from the root servers? Do you realize that the DNS root server addresses
are ``well-known addresses''?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 18:29:59 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29556
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 18:29:57 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78M1U8W010101
	for <dnsop-outgoing@nic.cafax.se>; Sat, 9 Aug 2003 00:01:30 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h78M1UDX010100
	for dnsop-outgoing; Sat, 9 Aug 2003 00:01:30 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from goose.ehsco.com (goose.ehsco.com [207.65.203.98])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78M1T8W010095
	for <dnsop@cafax.se>; Sat, 9 Aug 2003 00:01:29 +0200 (MEST)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1)
  with ESMTP-TLS id 414297; Fri, 08 Aug 2003 17:01:25 -0500
Message-ID: <3F341DAF.6080209@ehsco.com>
Date: Fri, 08 Aug 2003 17:01:19 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Rob Austein <sra+dnsop@hactrn.net>
CC: dnsop@cafax.se
Subject: Re: scope
References: <20030808193656.237A618E0@thrintun.hactrn.net>
In-Reply-To: <20030808193656.237A618E0@thrintun.hactrn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 8/8/2003 2:36 PM Rob Austein wrote:

> Ohta-san is correct that every single one of the approaches we've
> discussed has some kind of scoping constraint which, ultimately, is

This is what I was trying to point out as well.

> - RA/ND-based: if RA/ND isn't configured, discovery doesn't happen.
> 
> - Multicast-query based (DHCP, DHCP-lite, LLMNR-like, whatever): if
>   router multicast (or DHCP relay) isn't configured, may work anyway
>   on the local link, but otherwise discovery doesn't happen.
> 
> - Well-known address based: discovery propagates upstream following
>   the default route until it finds something or hits the edge of the
>   default free routing zone.  Discovery does not work if neither
>   well-known address nor default route is configured.

That's pretty mcuh right, except for a clarification to the well-known
address problem, which is that in the default (unmanaged) scenario,
locally-generated queries will follow the default routes, and will get
passed to whoever actually owns the address space in question.

There are actually two impositions here: First is that the use of an
address-based mechanism needs to have non-delegated, non-used address
space explicitly reserved for it by ICANN or whoever. Organizations don't
necessarily have to use that address space, but something needs to be
reserved for use in the default model, and it must not be part of RFC1918
space or any actual space. Second is that the use of locally-preferred
addresses actually cranks up the administrative costs greatly, since
admins not only have to configure the routing service to accomodate the
local addresses, but also needs to configure the nodes to use that address
space. None of the other requirements have any need for the admins to
manage the leaf-nodes whatsoever, and this is not a trivial artifact.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 18:50:09 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29877
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 18:50:08 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78MI78W010221
	for <dnsop-outgoing@nic.cafax.se>; Sat, 9 Aug 2003 00:18:07 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h78MI7rQ010220
	for dnsop-outgoing; Sat, 9 Aug 2003 00:18:07 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78MI68W010215
	for <dnsop@cafax.se>; Sat, 9 Aug 2003 00:18:06 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 1DDA418F2
	for <dnsop@cafax.se>; Fri,  8 Aug 2003 18:18:05 -0400 (EDT)
Date: Fri, 08 Aug 2003 18:18:05 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: scope
In-Reply-To: <20030808210729.17648.qmail@cr.yp.to>
References: <20030808193656.237A618E0@thrintun.hactrn.net>
	<20030808210729.17648.qmail@cr.yp.to>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030808221805.1DDA418F2@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At 8 Aug 2003 21:07:29 -0000, Daniel J. Bernstein wrote:
> 
> The administrator who sets up that firewall, but neglects to set up DNS
> service inside it, will find that his clients can't browse the web. This
> is exactly the behavior I'd expect.

Yes, if they screw this up for all of the well-known addresses.   What
if they only screw up one of them?

> Why do you say ``Oops''? What's the big deal?
> 
> Do you also worry when people set up DNS caches that are firewalled away
> from the root servers? Do you realize that the DNS root server addresses
> are ``well-known addresses''?

In reverse order, yes, I do realize that the root server addresses are
well-known, and that's part of what worries me.  Studies of traffic
observed at those servers suggest that a significant fraction of the
total root server query load is the result of bad packet filtering
that lets queries get out but blocks some or all responses.

Discovery based on well-known addresses is a bit different because the
packets (probably) stop at the edge of the default free zone, but the
potential for bug amplification is similar.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 19:50:43 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01181
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 19:50:41 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78NJP8W010583
	for <dnsop-outgoing@nic.cafax.se>; Sat, 9 Aug 2003 01:19:25 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h78NJPiL010582
	for dnsop-outgoing; Sat, 9 Aug 2003 01:19:25 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h78NJH8W010575
	for <dnsop@cafax.se>; Sat, 9 Aug 2003 01:19:18 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308082309.IAA01057@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA01057; Sat, 9 Aug 2003 08:08:49 +0859
Subject: Re: the well-known address approach
In-Reply-To: <Pine.LNX.4.44.0308081438500.2900-100000@netcore.fi> from Pekka
 Savola at "Aug 8, 2003 02:43:50 pm"
To: Pekka Savola <pekkas@netcore.fi>
Date: Sat, 9 Aug 2003 08:08:48 +0859 ()
CC: Ralph Droms <rdroms@cisco.com>, dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Pekka Savola;

> The argument I've heard a lot is one of architectural purity, as the 
> address architecture states (for example):

The proper interpretation of the address architecture RFC
is that IPv6 WG does not know anything about address (not only
anycast one) architecture.

The RFC says:

> An IPv6 unicast address refers to a single interface.

> When a unicast address is assigned to more than one interface,

without defining "assign".

The confusion, seemingly, is a result of an attempot to purposelessly
distinguish a subnet and a link.

Purposeful requirements are that a subnet, which is identical to
a link, may have multiple address prefixes and that a link may
be divided into virtual links such as VLAN, which is purely
an L2 issue.

> 2.6 Anycast Addresses

>    An IPv6 anycast address is an address that is assigned to more than
>    one interface (typically belonging to different nodes),

>    are syntactically indistinguishable from unicast addresses.  When a
>    unicast address is assigned to more than one interface, thus turning
>    it into an anycast address,

If a host (or a router or a node or whatever) have a unicast address
assigned to an interface, the host must receive a packet to the address,
even if the packet is received on another interface. In addition,
if a host have a unicast address assigned to an interface, the host
may send a packet from the address, even if the packet is sent from
another interface.

That is, all the unicast addresses of a multi-interface host are
assigned to more than one interface and are anycast ones.

> Needless to say I disagree with this model... :-)

Yup.

						Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 21:09:38 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02498
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 21:09:38 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h790dF8W011034
	for <dnsop-outgoing@nic.cafax.se>; Sat, 9 Aug 2003 02:39:15 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h790dEL4011033
	for dnsop-outgoing; Sat, 9 Aug 2003 02:39:14 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from mail.kahlerlarson.org (h-68-165-167-86.MCLNVA23.covad.net [68.165.167.86])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h790dD8W011028
	for <dnsop@cafax.se>; Sat, 9 Aug 2003 02:39:14 +0200 (MEST)
Received: from whirlwind (whirlwind.kahlerlarson.org [192.168.0.128])
	by mail.kahlerlarson.org (Postfix) with SMTP
	id 49DC0101064; Fri,  8 Aug 2003 20:39:12 -0400 (EDT)
Message-ID: <03b701c35e0e$a7338370$8000a8c0@whirlwind>
From: "Matt Larson" <mlarson@verisign.com>
To: "Rob Austein" <sra+dnsop@hactrn.net>, <dnsop@cafax.se>
References: <20030808193656.237A618E0@thrintun.hactrn.net><20030808210729.17648.qmail@cr.yp.to> <20030808221805.1DDA418F2@thrintun.hactrn.net>
Subject: Re: scope
Date: Fri, 8 Aug 2003 20:39:12 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

> In reverse order, yes, I do realize that the root server addresses are
> well-known, and that's part of what worries me.  Studies of traffic
> observed at those servers suggest that a significant fraction of the
> total root server query load is the result of bad packet filtering
> that lets queries get out but blocks some or all responses.

You can say that again.  IWFs (Idiots With Firewalls) account for a
tremendous volume of repeat queries to the roots.  It's more common than you
might think.  Those same boxes are probably the ones that inform their
administrators that the blocked responses are in fact attacks, many of which
get dutifully reported.

Matt

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug  8 21:21:06 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03134
	for <dnsop-archive@lists.ietf.org>; Fri, 8 Aug 2003 21:21:05 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h790nE8W011087
	for <dnsop-outgoing@nic.cafax.se>; Sat, 9 Aug 2003 02:49:14 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h790nD2I011086
	for dnsop-outgoing; Sat, 9 Aug 2003 02:49:13 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h790nB8W011081
	for <dnsop@cafax.se>; Sat, 9 Aug 2003 02:49:12 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308090038.JAA01595@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA01595; Sat, 9 Aug 2003 09:38:27 +0900
Subject: Re: scope
In-Reply-To: <20030808193656.237A618E0@thrintun.hactrn.net> from Rob Austein
 at "Aug 8, 2003 03:36:56 pm"
To: Rob Austein <sra+dnsop@hactrn.net>
Date: Sat, 9 Aug 2003 09:38:27 +0859 ()
CC: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Rob Austin;

> One place where these approaches differ in interesting ways, however,
> is in the default behavior.

> Assuming that one buys this analysis, this says that the well-known
> address approach is significantly different,

Other hop-by-hop-relaying (multicast does not qualify) approaches
may also be modified to let routers, by default, relay information
from all interfaces to all the other interfaces, if they are
protected from loops and have some preference metric to
multiple sources of the information.

But, the simplest way is to just rely on routing protocols.

> Good, because it means that dumb edge networks may just
> inherit the necessary data from the larger networks to which they're
> attached (although one might have security issues, eg, trust
> boundaries for use of the AD bit).

Considering that the requirement is, perhaps, maybe, hopefully, to
reduce configuration effort of host and site adminisgtrators
as much as possible, it is good.

> Bad, because this has the
> potential to turn into a bug amplifier.  Think, for example, about a
> hypothetical firewall product that blocks inbound recursive responses:
> this doesn't hurt the outside world so long as the well-known address
> points to something inside the firewall, but what happens if the
> well-known address route gets hosed?  Oops.

> Bottom line is that thinking about fault isolation gives me another
> reason for discomfort with the well-known address approach.  YMMV.

You are merely claiming that implementations of relaying entities
may be buggy, applicable to all the approaches (including multicast
one, this time).

In addition, it should also be claimed that manual configuration of
relaying entities may be wrong that the number of configured
entities should be small.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  9 14:17:41 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02887
	for <dnsop-archive@lists.ietf.org>; Sat, 9 Aug 2003 14:17:39 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h79HhH8W015735
	for <dnsop-outgoing@nic.cafax.se>; Sat, 9 Aug 2003 19:43:17 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h79HhHSq015734
	for dnsop-outgoing; Sat, 9 Aug 2003 19:43:17 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h79HhA8W015729
	for <dnsop@cafax.se>; Sat, 9 Aug 2003 19:43:11 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h79Hgqi17013;
	Sat, 9 Aug 2003 20:42:52 +0300
Date: Sat, 9 Aug 2003 20:42:52 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: John Schnizlein <jschnizl@cisco.com>, <dnsop@cafax.se>
Subject: Re: Policy of IPv6 DNS Discovery
In-Reply-To: <200308071145.UAA10376@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0308092035410.16647-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Thu, 7 Aug 2003, Masataka Ohta wrote:
> > > > As one of RA camp, I think, RA-approach is useful in some of wireless networks,
> > > > such as HMIPv6, MANET connected to the Internet and NEMO.
> > > 
> > > That is the assumption here.
> 
> > I'm not restricting myself to Jaehoon's assumptions
> 
> Here, you are restricted by the context with which we are discussing,
> if you want to contribute to the discussion.

What prevents me from expanding the scope of that discussion?  That's what 
discussion is about.

Granted, perhaps it would have been clearer if I had changed the subject 
line when originally posting, but most supposedly read the whole emails, 
not just the subject line.

> > I'm just pointing out that when one says "mobile node", it 
> > can mean at least a couple of different things.
> 
> Do it elsewhere, not here.
> 
> Here, in this thread at least, we already have an established
> terminology, defined by Jaehoon Paul Jeong, on mobility.

See above.

> > > Worse, most of your reasonings are wrong and rest of them are too
> > > weak that any standardized way of DNS autoconfiguration is fine
> > > for your requirement.
> > 
> > Please elaborate.
> 
> Read recent mails of this WG to find the elaboration.

They do not provide elaboration of this specific context so it is not
apparent which mails you're referring to. Please spell it out.

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sat Aug  9 14:17:42 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02903
	for <dnsop-archive@lists.ietf.org>; Sat, 9 Aug 2003 14:17:42 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h79HlU8W015776
	for <dnsop-outgoing@nic.cafax.se>; Sat, 9 Aug 2003 19:47:31 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h79HlUv2015775
	for dnsop-outgoing; Sat, 9 Aug 2003 19:47:30 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h79HlT8W015770
	for <dnsop@cafax.se>; Sat, 9 Aug 2003 19:47:29 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h79HlCf17022;
	Sat, 9 Aug 2003 20:47:13 +0300
Date: Sat, 9 Aug 2003 20:47:12 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Rob Austein <sra+dnsop@hactrn.net>
cc: dnsop@cafax.se
Subject: Re: scope
In-Reply-To: <20030808221805.1DDA418F2@thrintun.hactrn.net>
Message-ID: <Pine.LNX.4.44.0308092043260.16647-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Fri, 8 Aug 2003, Rob Austein wrote:
[...]
> Discovery based on well-known addresses is a bit different because the
> packets (probably) stop at the edge of the default free zone, but the
> potential for bug amplification is similar.

Note that couldn't a similar argument be applied to 6to4 relays using the
anycast address?  That all the parties should provide some support for it?  
Of course, the service is of a more fundamental type, but still..

We might be much better off if we recommended that such anycast addresses
should not be propagated at peering links (for example).  That way, the
fallback would be quicker (to using no DNS servers at all, most probably).  
Instead of going around the world like 6to4, this could be an incentive
for the ISP's to deploy such a service.  However, the time it might take
to ensure global availability of such a service could also be rather long.

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sun Aug 10 02:44:06 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29993
	for <dnsop-archive@lists.ietf.org>; Sun, 10 Aug 2003 02:44:05 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7A64d8W019386
	for <dnsop-outgoing@nic.cafax.se>; Sun, 10 Aug 2003 08:04:39 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7A64d8o019385
	for dnsop-outgoing; Sun, 10 Aug 2003 08:04:39 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from stoneport.math.uic.edu (stoneport.math.uic.edu [131.193.178.160])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with SMTP id h7A64b8W019380
	for <dnsop@cafax.se>; Sun, 10 Aug 2003 08:04:38 +0200 (MEST)
Received: (qmail 10657 invoked by uid 1016); 10 Aug 2003 06:04:56 -0000
Date: 10 Aug 2003 06:04:56 -0000
Message-ID: <20030810060456.10656.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: dnsop@cafax.se
Subject: Re: scope
References: <20030808193656.237A618E0@thrintun.hactrn.net> <20030808210729.17648.qmail@cr.yp.to> <20030808221805.1DDA418F2@thrintun.hactrn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-dnsop@cafax.se
Precedence: bulk

Rob Austein writes:
> a significant fraction of the total root server query load
> is the result of bad packet filtering

Think about the numbers for a moment.

The screwups you're talking about, added up over the _entire Internet_,
are on the scale of thousands of packets per second. Split the same
screwup level across all of the Internet's ISPs and the load becomes
unnoticeable.

Furthermore, even the most extreme DNS loads are miniscule compared to
HTTP load. Root-server load is special, because it has a serious (and
unnecessary) centralization problem; ISP-cache load isn't, and doesn't.
Do you think ISPs say to themselves ``Wow, our expenses are totally out
of control; it must be because of all those customers dropping responses
from our DNS caches''?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sun Aug 10 08:44:21 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05119
	for <dnsop-archive@lists.ietf.org>; Sun, 10 Aug 2003 08:44:21 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7AC9F8W020497
	for <dnsop-outgoing@nic.cafax.se>; Sun, 10 Aug 2003 14:09:15 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7AC9FRF020496
	for dnsop-outgoing; Sun, 10 Aug 2003 14:09:15 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7AC9C8W020491
	for <dnsop@cafax.se>; Sun, 10 Aug 2003 14:09:13 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308101157.UAA07437@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id UAA07437; Sun, 10 Aug 2003 20:57:27 +0900
Subject: Re: scope
In-Reply-To: <20030810060456.10656.qmail@cr.yp.to> from "D. J. Bernstein" at
 "Aug 10, 2003 06:04:56 am"
To: "D. J. Bernstein" <djb@cr.yp.to>
Date: Sun, 10 Aug 2003 20:57:26 +0859 ()
CC: dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

djb;

> > a significant fraction of the total root server query load
> > is the result of bad packet filtering
> 
> Think about the numbers for a moment.

Before that, I think we should think about a DHCP configured name
server located beyond a firewall, which is no different from
an anycast name server located beyond a firewall.

> The screwups you're talking about, added up over the _entire Internet_,
> are on the scale of thousands of packets per second. Split the same
> screwup level across all of the Internet's ISPs and the load becomes
> unnoticeable.

And, that's why anycast is the way to go both for root servers
and autoconfigured recursive servers.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Sun Aug 10 08:44:47 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05146
	for <dnsop-archive@lists.ietf.org>; Sun, 10 Aug 2003 08:44:46 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7AC9T8W020505
	for <dnsop-outgoing@nic.cafax.se>; Sun, 10 Aug 2003 14:09:29 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7AC9TVg020504
	for dnsop-outgoing; Sun, 10 Aug 2003 14:09:29 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7AC9Q8W020499
	for <dnsop@cafax.se>; Sun, 10 Aug 2003 14:09:27 +0200 (MEST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200308101159.UAA07447@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id UAA07447; Sun, 10 Aug 2003 20:59:34 +0900
Subject: Re: scope
In-Reply-To: <3F341DAF.6080209@ehsco.com> from "Eric A. Hall" at "Aug 8, 2003
 05:01:19 pm"
To: "Eric A. Hall" <ehall@ehsco.com>
Date: Sun, 10 Aug 2003 20:59:32 +0859 ()
CC: Rob Austein <sra+dnsop@hactrn.net>, dnsop@cafax.se
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-dnsop@cafax.se
Precedence: bulk

Eric A. Hall;

> That's pretty mcuh right, except for a clarification to the well-known
> address problem, which is that in the default (unmanaged) scenario,
> locally-generated queries will follow the default routes,

That is an inappropriate assumption.

For scalable multihoming, there should be no default routes even
within sites.

							Masataka Ohta
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug 11 06:59:12 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12729
	for <dnsop-archive@lists.ietf.org>; Mon, 11 Aug 2003 06:59:11 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7BAFq8W027380
	for <dnsop-outgoing@nic.cafax.se>; Mon, 11 Aug 2003 12:15:52 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7BAFq5K027379
	for dnsop-outgoing; Mon, 11 Aug 2003 12:15:52 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7BAFo8W027374
	for <dnsop@cafax.se>; Mon, 11 Aug 2003 12:15:50 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h7BAFh315330;
	Mon, 11 Aug 2003 13:15:43 +0300
Date: Mon, 11 Aug 2003 13:15:42 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@cafax.se
cc: yasuhiro@jprs.co.jp, <jinmei@isl.rdc.toshiba.co.jp>
Subject: comments about morishita-dnsop-misbehavior-against-aaaa-00
Message-ID: <Pine.LNX.4.44.0308111248400.13622-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

Hi,

A few comments on:

       Common Misbehavior against DNS Queries for IPv6 Addresses
         draft-morishita-dnsop-misbehavior-against-aaaa-00.txt

In short, I think this is a very well written and a very useful document.  
I was surprised why it wasn't on the DNSOP agenda in Vienna.

In any case, down to the comments..

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

4.1 Return NXDOMAIN
                                                                                                  
   This type of server returns a response with the RCODE being 3
   (NXDOMAIN) to a query for a AAAA RR, indicating it does not have any
   RRs of any type for the queried name.  In fact, such a server
   apparently returns NXDOMAIN to all queries except those for an A RR.

and:

4.3 Ignore Queries for AAAA
[...]
   Again, these servers apparently ignore all queries except those for
   an A RR.

==> is this really the case?  Do these servers *also* ignore or return an 
error to queries for NS, MX, SOA, and other resource records (and the text 
was slightly inaccurate), or does it really, really break everything 
except A records (whoops, maybe add a few words of clarification to 
underline that).

4.2 Return NOTIMP
                                                                                                  
   Other authoritative servers return a response with the RCODE being 4
   (NOTIMP), indicating the servers do not support the requested type of
   query.

[...]

  Using SERVFAIL or FORMERR would cause the same effect, though the
   authors have not seen such implementations yet.
                                                                                                  
==> I recall faintly that e.g. bind 4.9 series prior to patching some
years ago returned SERVFAIL?  Maybe also have a look at: 
http://www.wcug.wwu.edu/lists/ngtrans/200110/msg00123.html


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

In the following sections, this
   memo describes some typical cases of the misbehavior, the rationale,
   and (bad) effects of them.

==> "them" is an ambiguous referral.  Does it refer to the both 
misbehaviour and the rationale?  Based on the memo, it looks like it 
should only refer to the misbehaviour, because the document doesn't 
generally look at the (bad) effects of the _rationale_ (why the DNS 
queries are mishandled, which is typically just due to bugs or whatnot).



editorial
---------

This memo describes details of the known cases and
   discusses the effect.

==> s/effect/effects of these cases/ (seems to end a bit abruptly?)

   Many DNS clients (resolvers) that support IPv6 first search for AAAA
   RRs (Resource Records) of a target host name, and then for A RRs of
   the same name.

s/RRs (Resource Records)/Resource Records (RRs)/

Thus, if a DNS server which is responsible for the
   name is not compliant to the specifications

==> s/to/with/ (I've seen both but I think that with is better)?

 In some cases, for example, a web browser fails to connect
   to a web server otherwise it could.

==> s/otherwise it/it otherwise/ ?

The examples are for informational purposes
   only, and the authors do not intend accusation against any
   implementations or zone administrators described in this memo.

==> s/intend accusation against/intend to accuse/

4.4 Return a Broken Response
                                                                                                  
   Some other type of authoritative servers return broken responses to
   AAAA queries.

==> s/type/types/ ?

Full Copyright Statement

==> add the IPR boilerplate section before this?

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


#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug 11 07:36:35 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13258
	for <dnsop-archive@lists.ietf.org>; Mon, 11 Aug 2003 07:36:34 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7BB1Z8W027597
	for <dnsop-outgoing@nic.cafax.se>; Mon, 11 Aug 2003 13:01:35 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7BB1YHQ027596
	for dnsop-outgoing; Mon, 11 Aug 2003 13:01:34 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7BB1X8W027591
	for <dnsop@cafax.se>; Mon, 11 Aug 2003 13:01:33 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h7BB1Wi15821
	for <dnsop@cafax.se>; Mon, 11 Aug 2003 14:01:33 +0300
Date: Mon, 11 Aug 2003 14:01:32 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: dnsop@cafax.se
Subject: comments on ipv6-transport-guidelines-00
Message-ID: <Pine.LNX.4.44.0308111327580.13622-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

Hi,

A few comments on the new DNS IPv6 transport guidelines document.

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

==> first as there are no references to the prior work, or any mention of 
it, I think it would be both appropriate and useful to add an 
"Acknowledgements" section which could begin with a paragraph dedicated to 
summarizing how this document came to be.

   In order to preserve name space continuity, the following administrative
   policies are RECOMMENDED:
      - every recursive DNS server SHOULD be either IPv4-only or dual
      stack,
      - every single DNS zone SHOULD be served by at least one IPv4
      reachable DNS server.
                                                                                                  
   This rules out IPv6-only DNS servers performing full recursion and
   DNS zones served only by IPv6-only DNS servers.

==> as was noted in my comment in a related subject in v6ops earlier (just 
rehashing here with a different audience), this is not entirely accurate, 
especially with all the interpretations of "recursive DNS server".  That 
is, it would be entirely OK to have an IPv6-only resolver point to a few 
IPv6-only DNS servers which would be configured to recurse from some other 
servers (ad infinitum) until a dual-stack recursive DNS resolver is found.

Some might say that such a dummy DNS resolver is not really recursive but
a forwarder but I might disagree..

So, I think we need to both clarify the terminology and decide what 
exactly we want to recommend or allow.  (Note, if someone deploys 
IPv6-only networks with "first-hop DNS resolvers", being able to deploy 
IPv6-only recursive servers might be beneficial.)

==> the other thing to clarify might be "dual stack".  Again, if one 
wanted to be entirely accurate, the question is about whether the DNS 
server software is programmed (and enabled) for the both IP versions while 
the node is dual-stack.  I'm not sure how important this clarification is.

   In order to enforce the second point, the zone validation process
   SHOULD ensure that there is at least one IPv4 address record
   available for the name servers of any child delegations within the
   zone.


==> what is this "zone validation process"?  where is it defined?  where 
is it done (dns regisrars, dns software etc.)?

5. Security considerations
                                                                                                  
   Being a critical piece of the Internet infrastructure, the DNS is a
   potential value target and thus should be protected.  Great care
   should be taken not to weaken the security of DNS while introducing
   IPv6 operation.
                                                                                                  
   The RECOMMENDED guidelines are compatible with the operation of
   DNSsec and do not introduce any new security issues.

==> add something like below after the first paragraph:

   Keeping the DNS name space from fragmenting is a critical thing for the 
   availability and the operation of the Internet; this memo addresses 
   this issue by clear and simple operational guidelines.


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

Abstract
                                                                                                  
   This memo provides guidelines and best common practice to operate DNS
   in a mixed world of IPv4 and IPv6 transport.

==> the abstract should be longer, and include e.g. the summary of those 
guidelines (if possible).

==> note: is the goal for this Informational or BCP?  If Info, reword to 
remove reference to BCP [sic].

   Today there are only a few DNS "zones" on the public Internet that
   are  available over IPv6 transport, and they can mostly be regarded
   as "experimental". However, as soon as there is a root name server
   available over IPv6 transport it is reasonable to expect that it will
   become more common to have zones served by IPv6 servers over time.

==> The " as soon as there is a root name server available over IPv6
transport" is unrelated and irrelevant in this context, for the whole
purpose of this document, please remove!  (transport!=data; one could add
IPv6 glue in root, gtld's or cctld's before those are available over IPv6)

   The RECOMMENDED approach to maintain name space continuity is to use
   administrative policies.

==> the curious reader now (before looking down a bit) begins to wonder, 
"OK, _what_ administrative policies??".  Fix: s/policies./policies, as 
described in the next section./ :-)




editorial
---------

Internet Engineering Task Force                     Alain Durand
INTERNET-DRAFT                             SUN Microsystems,inc.
June, 17, 2003                                       Johan Ihren

==> s/Alain/A./, s/Johan/J./

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [2119].

==> should avoid references in the I-D boilerplate.

Abstract
                                                                                                  
   This memo provides guidelines and best common practice to operate DNS
   in a mixed world of IPv4 and IPv6 transport.

==> spell out DNS?
==> s/best common practice/Best Current Practice/ ?
==> "IPv4 and IPv6 _transport_" could be clarified.  It's OK for those 
who're used to the terminology but begs questions like "transport for 
what?  transport over what?"  (same in terminology)

2. Introduction to the problem of name space fragmentation:
     following the referral chain

==> s/problem/Problem/ etc. for section titles etc.

   The caching resolver that tries to lookup a name starts out at the
 
==> s/lookup/look up/

If somewhere down the chain of
   referrals it is referred to a nameserver that is only accessible over
   a type of transport that is unavailable, a traditional nameserver is
   unable to finish the task.

==> s/a type of transport that is unavailable/an unavailable type of transport/

   When the Internet moves from IPv4 to a mixture of IPv4 and IPv6 it is
   only a matter of time until this starts to happen and the complete
   DNS hierarchy starts to fragment into a graph where authoritative
   nameservers for certain nodes are only accessible over a certain
   transport. What is feared is that a node using only a particular
   version of IP, querying information about another node using the same
   version of IP can not do it because, somewhere in the chain of
   servers accessed during the resolution process, one or more of them
   will only be accessible with the other version of IP.

==> This paragraph only includes two (2!) long sentences, especially the 
latter.  It might be a bit more user-friendly broken down to shorter 
ones.. :-)

   However, the second situation will not arise in a foreseeable time.
   Instead, it is expected that the transition will be from IPv4 only to
   a mixture of IPv4 and IPv6, with DNS data of theoretically three
   categories depending on whether it is available only over IPv4
   transport, only over IPv6 or both.
                                                                                                  
   The latter is the best situation, and a major question is how to
   ensure that it as quickly as possible becomes the norm. [...]

==> the "latter" is a big ambiguous referral, perhaps just say "Having DNS 
data available on both transports is the best situation, ..." ?

3. Policy based avoidance of name space fragmentation.
                                                                                                  
==> s/ion./ion/ (similar for section header for section 4)

  DNSsec and do not introduce any new security issues.
                                                                                                  
==>s/DNSsec/DNSSEC/ ?

7. References

==> rename to "Normative References".

8. Full Copyright Statement

==> add the standard IPR boilerplate section prior to this one



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



#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug 11 14:46:42 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27836
	for <dnsop-archive@lists.ietf.org>; Mon, 11 Aug 2003 14:46:41 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7BI648W000299
	for <dnsop-outgoing@nic.cafax.se>; Mon, 11 Aug 2003 20:06:04 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7BI64fP000298
	for dnsop-outgoing; Mon, 11 Aug 2003 20:06:04 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7BI5v8W000287
	for <dnsop@cafax.se>; Mon, 11 Aug 2003 20:06:03 +0200 (MEST)
Received: from esunmail ([129.147.156.34])
	by brmea-mail-4.sun.com (8.12.9/8.12.9) with ESMTP id h7BI5jm5001009
	for <dnsop@cafax.se>; Mon, 11 Aug 2003 12:05:46 -0600 (MDT)
Received: from xpa-fe2 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTP id <0HJG006VGVLLEE@edgemail1.Central.Sun.COM> for dnsop@cafax.se;
 Mon, 11 Aug 2003 12:05:45 -0600 (MDT)
Received: from sun.com ([129.146.12.17])
 by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPSA id <0HJG00B77VLKPF@mail.sun.net> for dnsop@cafax.se; Mon,
 11 Aug 2003 12:05:45 -0600 (MDT)
Date: Mon, 11 Aug 2003 11:05:44 -0700
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: comments on ipv6-transport-guidelines-00
To: Pekka Savola <pekkas@netcore.fi>
Cc: dnsop@cafax.se
Message-id: <3F37DAF8.40706@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920
 Netscape/7.0
References: <Pine.LNX.4.44.0308111327580.13622-100000@netcore.fi>
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Pekka,

Thank you for your detailed review. I'll incorporate fixes in a new rev.
Comments inline.]

    - Alain.

>   In order to preserve name space continuity, the following administrative
>   policies are RECOMMENDED:
>      - every recursive DNS server SHOULD be either IPv4-only or dual
>      stack,
>      - every single DNS zone SHOULD be served by at least one IPv4
>      reachable DNS server.
>                                                                                                  
>   This rules out IPv6-only DNS servers performing full recursion and
>   DNS zones served only by IPv6-only DNS servers.
>
>==> as was noted in my comment in a related subject in v6ops earlier (just 
>rehashing here with a different audience), this is not entirely accurate, 
>especially with all the interpretations of "recursive DNS server".  That 
>is, it would be entirely OK to have an IPv6-only resolver point to a few 
>IPv6-only DNS servers which would be configured to recurse from some other 
>servers (ad infinitum) until a dual-stack recursive DNS resolver is found.
>
>Some might say that such a dummy DNS resolver is not really recursive but
>a forwarder but I might disagree..
>
>So, I think we need to both clarify the terminology and decide what 
>exactly we want to recommend or allow.  (Note, if someone deploys 
>IPv6-only networks with "first-hop DNS resolvers", being able to deploy 
>IPv6-only recursive servers might be beneficial.)
>
The problem is that DNS terminology is not very well defined anywhere.
So, I suggest to add a sentence specifically talking about forwarders
to clarify the point.

>==> the other thing to clarify might be "dual stack".  Again, if one 
>wanted to be entirely accurate, the question is about whether the DNS 
>server software is programmed (and enabled) for the both IP versions while 
>the node is dual-stack.  I'm not sure how important this clarification is.
>
>   In order to enforce the second point, the zone validation process
>   SHOULD ensure that there is at least one IPv4 address record
>   available for the name servers of any child delegations within the
>   zone.
>
We could be pedantic and say:
"the server software has to be dual stack, configured to listen for IPv6
traffic, on a dual stack host where IPv6 is turned on, an a network
annoncing and routing Ipv6 packets to the big Internet...."
I think that "dual stack" is a nice shortcut that everybody understand.

>==> what is this "zone validation process"?  where is it defined?  where 
>is it done (dns regisrars, dns software etc.)?
>
This happens in several places, software are developped for this.
Before delegating a zone, numberof registrars insist on some
kind of a zone check. I'm not sure there is much value in
explaining this process in details.

>5. Security considerations
>                                                                                                  
>   Being a critical piece of the Internet infrastructure, the DNS is a
>   potential value target and thus should be protected.  Great care
>   should be taken not to weaken the security of DNS while introducing
>   IPv6 operation.
>                                                                                                  
>   The RECOMMENDED guidelines are compatible with the operation of
>   DNSsec and do not introduce any new security issues.
>
>==> add something like below after the first paragraph:
>
>   Keeping the DNS name space from fragmenting is a critical thing for the 
>   availability and the operation of the Internet; this memo addresses 
>   this issue by clear and simple operational guidelines.
>

Ok.

>semi-editorial
>--------------
>
>Abstract
>                                                                                                  
>   This memo provides guidelines and best common practice to operate DNS
>   in a mixed world of IPv4 and IPv6 transport.
>
>==> the abstract should be longer, and include e.g. the summary of those 
>guidelines (if possible).
>
>==> note: is the goal for this Informational or BCP?  If Info, reword to 
>remove reference to BCP [sic].
>
BCP is the target for this document.

>   Today there are only a few DNS "zones" on the public Internet that
>   are  available over IPv6 transport, and they can mostly be regarded
>   as "experimental". However, as soon as there is a root name server
>   available over IPv6 transport it is reasonable to expect that it will
>   become more common to have zones served by IPv6 servers over time.
>
>==> The " as soon as there is a root name server available over IPv6
>transport" is unrelated and irrelevant in this context, for the whole
>purpose of this document, please remove!  (transport!=data; one could add
>IPv6 glue in root, gtld's or cctld's before those are available over IPv6)
>
Ok



>
>   The RECOMMENDED approach to maintain name space continuity is to use
>   administrative policies.
>
>==> the curious reader now (before looking down a bit) begins to wonder, 
>"OK, _what_ administrative policies??".  Fix: s/policies./policies, as 
>described in the next section./ :-)
>

ok

>  
>


#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug 11 17:15:27 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06727
	for <dnsop-archive@lists.ietf.org>; Mon, 11 Aug 2003 17:15:27 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7BKSk8W001538
	for <dnsop-outgoing@nic.cafax.se>; Mon, 11 Aug 2003 22:28:46 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7BKSkoS001537
	for dnsop-outgoing; Mon, 11 Aug 2003 22:28:46 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from stoneport.math.uic.edu (stoneport.math.uic.edu [131.193.178.160])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with SMTP id h7BKSe8W001530
	for <dnsop@cafax.se>; Mon, 11 Aug 2003 22:28:45 +0200 (MEST)
Received: (qmail 12709 invoked by uid 1016); 11 Aug 2003 20:28:58 -0000
Date: 11 Aug 2003 20:28:58 -0000
Message-ID: <20030811202858.12708.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: dnsop@cafax.se
Subject: Re: comments on ipv6-transport-guidelines-00
References: <Pine.LNX.4.44.0308111327580.13622-100000@netcore.fi> <3F37DAF8.40706@sun.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-dnsop@cafax.se
Precedence: bulk

Alain Durand writes:
> We could be pedantic and say:
> "the server software has to be dual stack, configured to listen for IPv6
> traffic, on a dual stack host where IPv6 is turned on, an a network
> annoncing and routing Ipv6 packets to the big Internet...."
> I think that "dual stack" is a nice shortcut that everybody understand.

No.

Many computers are running ``dual stack'' operating systems, but very
few computers are ``routing IPv6 packets to the big Internet,'' This is
a huge difference. You can't simply gloss over it in a protocol spec.

See http://cr.yp.to/djbdns/ipv6mess.html for further discussion.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Tue Aug 12 05:25:43 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06085
	for <dnsop-archive@lists.ietf.org>; Tue, 12 Aug 2003 05:25:42 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7C8kk8W006431
	for <dnsop-outgoing@nic.cafax.se>; Tue, 12 Aug 2003 10:46:46 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7C8kkc6006430
	for dnsop-outgoing; Tue, 12 Aug 2003 10:46:46 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7C8ki8W006425
	for <dnsop@cafax.se>; Tue, 12 Aug 2003 10:46:45 +0200 (MEST)
Received: from ocean.jinmei.org (shuttle.wide.toshiba.co.jp [3ffe:501:100f::35])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id C52F51525D; Tue, 12 Aug 2003 17:46:38 +0900 (JST)
Date: Tue, 12 Aug 2003 17:46:39 +0900
Message-ID: <y7vfzk7mff4.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: Pekka Savola <pekkas@netcore.fi>
Cc: dnsop@cafax.se, yasuhiro@jprs.co.jp
Subject: Re: comments about morishita-dnsop-misbehavior-against-aaaa-00
In-Reply-To: <Pine.LNX.4.44.0308111248400.13622-100000@netcore.fi>
References: <Pine.LNX.4.44.0308111248400.13622-100000@netcore.fi>
User-Agent: Wanderlust/2.10.0 (Venus) 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@cafax.se
Precedence: bulk

>>>>> On Mon, 11 Aug 2003 13:15:42 +0300 (EEST), 
>>>>> Pekka Savola <pekkas@netcore.fi> said:

> A few comments on:

>        Common Misbehavior against DNS Queries for IPv6 Addresses
>          draft-morishita-dnsop-misbehavior-against-aaaa-00.txt

> In short, I think this is a very well written and a very useful document.  
> I was surprised why it wasn't on the DNSOP agenda in Vienna.

Thanks for the careful reading and the comments.  This is the first
response to the draft as far as I know:-)

> substantial
> -----------

> 4.1 Return NXDOMAIN
                                                                                                  
>    This type of server returns a response with the RCODE being 3
>    (NXDOMAIN) to a query for a AAAA RR, indicating it does not have any
>    RRs of any type for the queried name.  In fact, such a server
>    apparently returns NXDOMAIN to all queries except those for an A RR.

> and:

> 4.3 Ignore Queries for AAAA
> [...]
>    Again, these servers apparently ignore all queries except those for
>    an A RR.

> ==> is this really the case?  Do these servers *also* ignore or return an 
> error to queries for NS, MX, SOA, and other resource records (and the text 
> was slightly inaccurate), or does it really, really break everything 
> except A records (whoops, maybe add a few words of clarification to 
> underline that).

This is the case at least about the examples described in the draft.
You can even check the behavior described in Section 4.3 by yourself
(I just retried and confirmed that it is still the case).

> 4.2 Return NOTIMP
                                                                                                  
>    Other authoritative servers return a response with the RCODE being 4
>    (NOTIMP), indicating the servers do not support the requested type of
>    query.

> [...]

>   Using SERVFAIL or FORMERR would cause the same effect, though the
>    authors have not seen such implementations yet.
                                                                                                  
> ==> I recall faintly that e.g. bind 4.9 series prior to patching some
> years ago returned SERVFAIL?  Maybe also have a look at: 
> http://www.wcug.wwu.edu/lists/ngtrans/200110/msg00123.html

Hmm, I've looked at the ngtrans message, and the latest version of the
internet-draft discussed there, but I could not find a concrete
example.  Could you be more specific please?

Regarding BIND 4.9, I don't have an environment to check the behavior
at least at this moment.  If anyone else could confirm the
information, it would be helpful.

As for editorial comments, we'll take them into account when we ever
have a chance to revise the draft.  (At the moment, I, for one, do not
see the need.)  But in any event, we appreciate all the comments.

Thanks,

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug 13 03:12:13 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10959
	for <dnsop-archive@lists.ietf.org>; Wed, 13 Aug 2003 03:12:13 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D6aE8W014178
	for <dnsop-outgoing@nic.cafax.se>; Wed, 13 Aug 2003 08:36:14 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7D6aEKx014177
	for dnsop-outgoing; Wed, 13 Aug 2003 08:36:14 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D6aC8W014172
	for <dnsop@cafax.se>; Wed, 13 Aug 2003 08:36:13 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h7D6a8f06900;
	Wed, 13 Aug 2003 09:36:08 +0300
Date: Wed, 13 Aug 2003 09:36:07 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Alain Durand <Alain.Durand@Sun.COM>
cc: dnsop@cafax.se
Subject: Re: comments on ipv6-transport-guidelines-00
In-Reply-To: <3F37DAF8.40706@sun.com>
Message-ID: <Pine.LNX.4.44.0308130921090.5778-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-dnsop@cafax.se
Precedence: bulk

Responding to two issues only, on "dual-stack" use and on "zone validation 
process".

On Mon, 11 Aug 2003, Alain Durand wrote:
> >==> the other thing to clarify might be "dual stack".  Again, if one 
> >wanted to be entirely accurate, the question is about whether the DNS 
> >server software is programmed (and enabled) for the both IP versions while 
> >the node is dual-stack.  I'm not sure how important this clarification is.
> >
> >   In order to enforce the second point, the zone validation process
> >   SHOULD ensure that there is at least one IPv4 address record
> >   available for the name servers of any child delegations within the
> >   zone.
> >
> We could be pedantic and say:
> "the server software has to be dual stack, configured to listen for IPv6
> traffic, on a dual stack host where IPv6 is turned on, an a network
> annoncing and routing Ipv6 packets to the big Internet...."
> I think that "dual stack" is a nice shortcut that everybody understand.

I agree that we definitely need a short-cut in this text.  But still, I
think we need to define it in the very beginning in the terminology
section.  Using something else than "dual-stack" has both drawbacks and
advantages.

IMHO, using dual-stack in the text would probably be all right assuming we
coined up what exactly we mean (and how it may differ from other
interpretations) by dual-stack in this context in the terminology.

So, having some other term could be simpler as it doesn't already have
connotations (dual-stack _can_ be interpreted to mean just a system which
implements dual-stack, period) in people's minds, but if we can't figure
out anything fancy, DS is probably ok with above reservations.
 
> >==> what is this "zone validation process"?  where is it defined?  where 
> >is it done (dns regisrars, dns software etc.)?
> 
> This happens in several places, software are developped for this.

Yes, I've seen the reports from such software.

> Before delegating a zone, numberof registrars insist on some
> kind of a zone check. I'm not sure there is much value in
> explaining this process in details.

OK, I think we have to be clear here that the DNS specification does not 
mandate such zone validation checks, and this is (just) a sometimes (or 
even "often", not sure) done additional sanity check.

For example, rephrase:

   In order to enforce the second point, the zone validation process
   SHOULD ensure that there is at least one IPv4 address record
   available for the name servers of any child delegations within the
   zone.

to:

   In order to help enforcing the second point, the optional operational 
   zone validation processes SHOULD ensure that there is at least one IPv4
   address record available for the name servers of any child delegations 
   within the zone.
 
-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug 13 03:37:15 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11362
	for <dnsop-archive@lists.ietf.org>; Wed, 13 Aug 2003 03:37:14 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D7AK8W014345
	for <dnsop-outgoing@nic.cafax.se>; Wed, 13 Aug 2003 09:10:20 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7D7AKEE014344
	for dnsop-outgoing; Wed, 13 Aug 2003 09:10:20 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D7AD8W014339
	for <dnsop@cafax.se>; Wed, 13 Aug 2003 09:10:15 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h7D79uK07285;
	Wed, 13 Aug 2003 10:09:57 +0300
Date: Wed, 13 Aug 2003 10:09:56 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
cc: dnsop@cafax.se, <yasuhiro@jprs.co.jp>
Subject: Re: comments about morishita-dnsop-misbehavior-against-aaaa-00
In-Reply-To: <y7vfzk7mff4.wl@ocean.jinmei.org>
Message-ID: <Pine.LNX.4.44.0308130939150.5778-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Tue, 12 Aug 2003, JINMEI Tatuya / [ISO-2022-JP] $B?@L@C#:H(B wrote:
> > substantial
> > -----------
> 
> > 4.1 Return NXDOMAIN
>                                                                                                   
> >    This type of server returns a response with the RCODE being 3
> >    (NXDOMAIN) to a query for a AAAA RR, indicating it does not have any
> >    RRs of any type for the queried name.  In fact, such a server
> >    apparently returns NXDOMAIN to all queries except those for an A RR.
> 
> > and:
> 
> > 4.3 Ignore Queries for AAAA
> > [...]
> >    Again, these servers apparently ignore all queries except those for
> >    an A RR.
> 
> > ==> is this really the case?  Do these servers *also* ignore or return an 
> > error to queries for NS, MX, SOA, and other resource records (and the text 
> > was slightly inaccurate), or does it really, really break everything 
> > except A records (whoops, maybe add a few words of clarification to 
> > underline that).
> 
> This is the case at least about the examples described in the draft.
> You can even check the behavior described in Section 4.3 by yourself
> (I just retried and confirmed that it is still the case).

So it seems, perhaps some stronger words are in order if revising the 
draft.

> > 4.2 Return NOTIMP
>                                                                                                   
> >    Other authoritative servers return a response with the RCODE being 4
> >    (NOTIMP), indicating the servers do not support the requested type of
> >    query.
> 
> > [...]
> 
> >   Using SERVFAIL or FORMERR would cause the same effect, though the
> >    authors have not seen such implementations yet.
>                                                                                                   
> > ==> I recall faintly that e.g. bind 4.9 series prior to patching some
> > years ago returned SERVFAIL?  Maybe also have a look at: 
> > http://www.wcug.wwu.edu/lists/ngtrans/200110/msg00123.html
> 
> Hmm, I've looked at the ngtrans message, and the latest version of the
> internet-draft discussed there, but I could not find a concrete
> example.  Could you be more specific please?

Unfortunately, I do not know more details than that.. :-/
 
> Regarding BIND 4.9, I don't have an environment to check the behavior
> at least at this moment.  If anyone else could confirm the
> information, it would be helpful.

I tried to look this up, but failed; in any case, I believe the code would 
be some 6-7 years old at least.  We'll see if someone else brings this up.

In doing so, I googled across this one:

http://mailman.isi.edu/pipermail/6bone/2002-October/006531.html

which brings some statistics to the play, which may be interesting.

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug 13 04:24:21 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12219
	for <dnsop-archive@lists.ietf.org>; Wed, 13 Aug 2003 04:24:19 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D7t38W014641
	for <dnsop-outgoing@nic.cafax.se>; Wed, 13 Aug 2003 09:55:03 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7D7t3Qh014640
	for dnsop-outgoing; Wed, 13 Aug 2003 09:55:03 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D7t18W014635
	for <dnsop@cafax.se>; Wed, 13 Aug 2003 09:55:02 +0200 (MEST)
Received: from ocean.jinmei.org (shuttle.wide.toshiba.co.jp [3ffe:501:100f::35])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 7CFFD1525D; Wed, 13 Aug 2003 16:54:59 +0900 (JST)
Date: Wed, 13 Aug 2003 16:54:58 +0900
Message-ID: <y7v1xvqm1pp.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: Pekka Savola <pekkas@netcore.fi>
Cc: dnsop@cafax.se, <yasuhiro@jprs.co.jp>
Subject: Re: comments about morishita-dnsop-misbehavior-against-aaaa-00
In-Reply-To: <Pine.LNX.4.44.0308130939150.5778-100000@netcore.fi>
References: <y7vfzk7mff4.wl@ocean.jinmei.org>
	 <Pine.LNX.4.44.0308130939150.5778-100000@netcore.fi>
User-Agent: Wanderlust/2.10.0 (Venus) 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@cafax.se
Precedence: bulk

>>>>> On Wed, 13 Aug 2003 10:09:56 +0300 (EEST), 
>>>>> Pekka Savola <pekkas@netcore.fi> said:

>> > 4.3 Ignore Queries for AAAA
>> > [...]
>> >    Again, these servers apparently ignore all queries except those for
>> >    an A RR.
>> 
>> > ==> is this really the case?  Do these servers *also* ignore or return an 
>> > error to queries for NS, MX, SOA, and other resource records (and the text 
>> > was slightly inaccurate), or does it really, really break everything 
>> > except A records (whoops, maybe add a few words of clarification to 
>> > underline that).
>> 
>> This is the case at least about the examples described in the draft.
>> You can even check the behavior described in Section 4.3 by yourself
>> (I just retried and confirmed that it is still the case).

> So it seems, perhaps some stronger words are in order if revising the 
> draft.

Hmm, perhaps I misunderstood your original question.  Did you
actually ask if we checked the problematic server ignored all the
65535 (2^16 - 1) RR types?  If so, the answer is no.  We only tested
against AAAA, MX, SOA, and NS (perhaps A6 or some other types).  Also,
for the "ignore" case, the checking side cannot be sure if the
authoritative server really ignores the query or some intermediate
node drops the query or the response.  That's why we used the word
"apparently" in the draft.

And, you seem to require the authors to be more concrete (for example,
"we tried to send queries for AAAA, MX, SOA, NS, ...and XX, and waited
for yy seconds.  We did not get any responses.")

Not sure if the "redundant but perfectly accurate" wording is the best
way, but I'll keep this in mind for the next revision (if any).

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Wed Aug 13 04:43:50 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12668
	for <dnsop-archive@lists.ietf.org>; Wed, 13 Aug 2003 04:43:48 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D8I08W014771
	for <dnsop-outgoing@nic.cafax.se>; Wed, 13 Aug 2003 10:18:00 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7D8I0Y0014770
	for dnsop-outgoing; Wed, 13 Aug 2003 10:18:00 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7D8Hv8W014765
	for <dnsop@cafax.se>; Wed, 13 Aug 2003 10:17:58 +0200 (MEST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h7D8Hpb07916;
	Wed, 13 Aug 2003 11:17:51 +0300
Date: Wed, 13 Aug 2003 11:17:50 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
cc: dnsop@cafax.se, <yasuhiro@jprs.co.jp>
Subject: Re: comments about morishita-dnsop-misbehavior-against-aaaa-00
In-Reply-To: <y7v1xvqm1pp.wl@ocean.jinmei.org>
Message-ID: <Pine.LNX.4.44.0308131112120.7442-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Wed, 13 Aug 2003, JINMEI Tatuya / [ISO-2022-JP] $B?@L@C#:H(B wrote:
> >> > 4.3 Ignore Queries for AAAA
> >> > [...]
> >> >    Again, these servers apparently ignore all queries except those for
> >> >    an A RR.
> >> 
> >> > ==> is this really the case?  Do these servers *also* ignore or return an 
> >> > error to queries for NS, MX, SOA, and other resource records (and the text 
> >> > was slightly inaccurate), or does it really, really break everything 
> >> > except A records (whoops, maybe add a few words of clarification to 
> >> > underline that).
> >> 
> >> This is the case at least about the examples described in the draft.
> >> You can even check the behavior described in Section 4.3 by yourself
> >> (I just retried and confirmed that it is still the case).
> 
> > So it seems, perhaps some stronger words are in order if revising the 
> > draft.
> 
> Hmm, perhaps I misunderstood your original question.  Did you
> actually ask if we checked the problematic server ignored all the
> 65535 (2^16 - 1) RR types?  If so, the answer is no. 

No, my question was as you first interpreted.

>  We only tested
> against AAAA, MX, SOA, and NS (perhaps A6 or some other types).  Also,
> for the "ignore" case, the checking side cannot be sure if the
> authoritative server really ignores the query or some intermediate
> node drops the query or the response.  That's why we used the word
> "apparently" in the draft.

Right.
 
> And, you seem to require the authors to be more concrete (for example,
> "we tried to send queries for AAAA, MX, SOA, NS, ...and XX, and waited
> for yy seconds.  We did not get any responses.")
> 
> Not sure if the "redundant but perfectly accurate" wording is the best
> way, but I'll keep this in mind for the next revision (if any).

As the title of the section is "Ignore Queries for AAAA", it may be best
to be even more explicit on what was tested and what was not.  My
immediate reaction was "OK, these broken boxes have implemented very basic
RR support, but no "fancy" new features like AAAA", but the reality was
different, and they *only* seem to implement A records.  I think this was
already stated that only A RR's get responses, but to be double sure, it
would not hurt to really, really spell it out :-) -- that the issues are
not specific to AAAA records.

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

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug 25 04:06:00 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01323
	for <dnsop-archive@lists.ietf.org>; Mon, 25 Aug 2003 04:05:59 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7P7Qn8W023497
	for <dnsop-outgoing@nic.cafax.se>; Mon, 25 Aug 2003 09:26:49 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7P7QnZ4023496
	for dnsop-outgoing; Mon, 25 Aug 2003 09:26:49 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from postman.ripe.net (postman.ripe.net [193.0.0.199])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7P7Qm8W023491
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 09:26:48 +0200 (MEST)
Received: by postman.ripe.net (Postfix, from userid 8)
	id 87E4F4E16C; Mon, 25 Aug 2003 09:26:48 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP id 1B8E44E0B5
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 09:26:48 +0200 (CEST)
Received: from x50.ripe.net (x50.ripe.net [193.0.1.50])
	by birch.ripe.net (8.12.9/8.11.6) with SMTP id h7P7QlWt010356
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 09:26:47 +0200
Date: Mon, 25 Aug 2003 09:26:47 +0200
From: "Olaf M. Kolkman" <olaf@ripe.net>
To: dnsop@cafax.se
Subject: draft-kolkman-dnssec-operational-practices-00.txt
Message-Id: <20030825092647.236f76e0.olaf@ripe.net>
Organization: RIPE NCC
X-Mailer: Sylpheed version 0.9.0 (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Status: N 0.493601
X-RIPE-Signature: b9f0ffd9317c8bb2f6b5c41faa83f864
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit



Colleagues,

draft-kolkman-dnssec-operational-practices-00.txt is now in the I-D
repository.


To give you an idea about content the abstract and index are copied
below.


Does the working group want to accept this document as a working group
item?


-- Olaf



---------------------------------| Olaf M. Kolkman
---------------------------------| RIPE NCC




Abstract

   This Internet-Draft is intended as a place holder for considerations
   and operational practices for DNSSEC key-management.  It is intended
   to be 'long-lived' and result in documentation of best(?) current
   practices.


Table of Contents

   1.    Introduction . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.    Time in DNSSEC . . . . . . . . . . . . . . . . . . . . . . .  3
   2.1   Time definitions . . . . . . . . . . . . . . . . . . . . . .  3
   2.2   Time considerations  . . . . . . . . . . . . . . . . . . . .  4
   3.    Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   3.1   Using Key-Signing and Zone-Signing Keys. . . . . . . . . . .  6
   3.1.1 Motivations for the KSK and ZSK functions  . . . . . . . . .  6
   3.2   Key security considerations  . . . . . . . . . . . . . . . .  6
   3.3   Key rollovers  . . . . . . . . . . . . . . . . . . . . . . .  7
   3.3.1 Zone-signing key rollovers . . . . . . . . . . . . . . . . .  7
   3.3.2 Key-signing key rollovers  . . . . . . . . . . . . . . . . . 10
   4.    Planning for emergency key rollover. . . . . . . . . . . . . 11
   4.1   KSK compromise . . . . . . . . . . . . . . . . . . . . . . . 12
   4.2   ZSK compromise . . . . . . . . . . . . . . . . . . . . . . . 12
   4.3   Compromises of keys configured at the resolver level . . . . 12
   5.    Parental policies. . . . . . . . . . . . . . . . . . . . . . 13
   6.    Initial key exchanges and parental policies
         considerations.  . . . . . . . . . . . . . . . . . . . . . . 13
   6.1   Storing keys so hashes can be regenerated  . . . . . . . . . 13
   6.2   Self signed keys during upload or not? . . . . . . . . . . . 13
   6.3   Security lameness checks.  . . . . . . . . . . . . . . . . . 13
   6.4   SIG DS validity period.  . . . . . . . . . . . . . . . . . . 13
   7.    Resolver key configuration.  . . . . . . . . . . . . . . . . 13
   8.    Security considerations  . . . . . . . . . . . . . . . . . . 13
   9.    Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . 13
         Normative References . . . . . . . . . . . . . . . . . . . . 14
         Informative References . . . . . . . . . . . . . . . . . . . 14
         Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 15
   A.    Terminology  . . . . . . . . . . . . . . . . . . . . . . . . 15
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug 25 14:10:58 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06049
	for <dnsop-archive@lists.ietf.org>; Mon, 25 Aug 2003 14:10:57 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7PHWN8W001184
	for <dnsop-outgoing@nic.cafax.se>; Mon, 25 Aug 2003 19:32:23 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7PHWNbZ001183
	for dnsop-outgoing; Mon, 25 Aug 2003 19:32:23 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from postmark.nist.gov (pushme.nist.gov [129.6.16.92])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7PHWL8W001178
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 19:32:22 +0200 (MEST)
Received: from barnacle (barnacle.antd.nist.gov [129.6.55.185])
	by postmark.nist.gov (8.12.5/8.12.5) with SMTP id h7PHVk15027594
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 13:31:46 -0400 (EDT)
Message-ID: <025501c36b2e$c364d9e0$b9370681@barnacle>
From: "Scott Rose" <scottr@nist.gov>
To: <dnsop@cafax.se>
References: <20030825092647.236f76e0.olaf@ripe.net>
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt
Date: Mon, 25 Aug 2003 13:31:48 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

An opinion on section 3.2 (Security Key Considerations):  It is the wrong
place for a discourse on key strengh, but a reference would be good for
further info for someone interested.  Otherwise, it might be good to give
some rough rules to follow such as "the larger the zone, the larger the key"
and "larger the zone, zone key rollovers should be more frequent".

I think this may help neophyte admins get a basic understanding.

Scott


----- Original Message ----- 
From: "Olaf M. Kolkman" <olaf@ripe.net>
To: <dnsop@cafax.se>
Sent: Monday, August 25, 2003 3:26 AM
Subject: draft-kolkman-dnssec-operational-practices-00.txt


>
>
> Colleagues,
>
> draft-kolkman-dnssec-operational-practices-00.txt is now in the I-D
> repository.
>
>
> To give you an idea about content the abstract and index are copied
> below.
>
>
> Does the working group want to accept this document as a working group
> item?
>
>
> -- Olaf
>
>
>
> ---------------------------------| Olaf M. Kolkman
> ---------------------------------| RIPE NCC
>
>
>
>
> Abstract
>
>    This Internet-Draft is intended as a place holder for considerations
>    and operational practices for DNSSEC key-management.  It is intended
>    to be 'long-lived' and result in documentation of best(?) current
>    practices.
>
>
> Table of Contents
>
>    1.    Introduction . . . . . . . . . . . . . . . . . . . . . . . .  3
>    2.    Time in DNSSEC . . . . . . . . . . . . . . . . . . . . . . .  3
>    2.1   Time definitions . . . . . . . . . . . . . . . . . . . . . .  3
>    2.2   Time considerations  . . . . . . . . . . . . . . . . . . . .  4
>    3.    Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
>    3.1   Using Key-Signing and Zone-Signing Keys. . . . . . . . . . .  6
>    3.1.1 Motivations for the KSK and ZSK functions  . . . . . . . . .  6
>    3.2   Key security considerations  . . . . . . . . . . . . . . . .  6
>    3.3   Key rollovers  . . . . . . . . . . . . . . . . . . . . . . .  7
>    3.3.1 Zone-signing key rollovers . . . . . . . . . . . . . . . . .  7
>    3.3.2 Key-signing key rollovers  . . . . . . . . . . . . . . . . . 10
>    4.    Planning for emergency key rollover. . . . . . . . . . . . . 11
>    4.1   KSK compromise . . . . . . . . . . . . . . . . . . . . . . . 12
>    4.2   ZSK compromise . . . . . . . . . . . . . . . . . . . . . . . 12
>    4.3   Compromises of keys configured at the resolver level . . . . 12
>    5.    Parental policies. . . . . . . . . . . . . . . . . . . . . . 13
>    6.    Initial key exchanges and parental policies
>          considerations.  . . . . . . . . . . . . . . . . . . . . . . 13
>    6.1   Storing keys so hashes can be regenerated  . . . . . . . . . 13
>    6.2   Self signed keys during upload or not? . . . . . . . . . . . 13
>    6.3   Security lameness checks.  . . . . . . . . . . . . . . . . . 13
>    6.4   SIG DS validity period.  . . . . . . . . . . . . . . . . . . 13
>    7.    Resolver key configuration.  . . . . . . . . . . . . . . . . 13
>    8.    Security considerations  . . . . . . . . . . . . . . . . . . 13
>    9.    Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . 13
>          Normative References . . . . . . . . . . . . . . . . . . . . 14
>          Informative References . . . . . . . . . . . . . . . . . . . 14
>          Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 15
>    A.    Terminology  . . . . . . . . . . . . . . . . . . . . . . . . 15
> #----------------------------------------------------------------------
> # To unsubscribe, send a message to <dnsop-request@cafax.se>.

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Mon Aug 25 18:30:11 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20768
	for <dnsop-archive@lists.ietf.org>; Mon, 25 Aug 2003 18:30:10 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7PLpX8W003417
	for <dnsop-outgoing@nic.cafax.se>; Mon, 25 Aug 2003 23:51:33 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7PLpX80003416
	for dnsop-outgoing; Mon, 25 Aug 2003 23:51:33 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from noxmail.sandelman.ottawa.on.ca (oetest.freeswan.org [205.150.200.166])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7PLpV8W003411
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 23:51:31 +0200 (MEST)
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca [205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h7PLpId03964
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 17:51:23 -0400 (EDT)
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h7PLpHRB025335
	for <dnsop@cafax.se>; Mon, 25 Aug 2003 17:51:17 -0400
To: dnsop@cafax.se
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt 
In-reply-to: Your message of "Mon, 25 Aug 2003 09:26:47 +0200."
             <20030825092647.236f76e0.olaf@ripe.net> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 25 Aug 2003 17:51:16 -0400
Message-ID: <25334.1061848276@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-dnsop@cafax.se
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Olaf" == Olaf M Kolkman <olaf@ripe.net> writes:
    Olaf> draft-kolkman-dnssec-operational-practices-00.txt is now in the I-D
    Olaf> repository.

    Olaf> Does the working group want to accept this document as a working
    Olaf> group item?

  Yes, I think it should.

  I still would like to introduce some kind of term, like "dieletric constant
of DNSSEC" or some such to explain "propogation" of SIGs through caches :-)

  Some initial comments/thoughts:

>   o  "Key publication period"
>
>         The period for which the public part of the key is published in
>         the DNS.  The public part of the key can be published in the
>         DNS while it has not yet been used to sign data As soon as a
>         public key is published a brute force attack can be attempted
>         to recover the private key.  Publishing the public key in
>         advance (and not signing any data with it) does not guard
>         against this attack.

  One interesting "defense" against this would be to publish multiple
keys. Some of them could be total garbage. Since there is no signed data,
you'd have to brute force all them to figure out which one signed the data.

  But, in any case, if you believe that the key can be brute forced during
any low multiple of the "key publication period", then the period is probably
too short, or the keys too small.

re: 3.3.1.1 A double signature zone-signing key rollover

I don't think that at SOA#1, you have to resign with key 10. Maybe you
  have to sign the DNSKEY11, but that's it.
Also, I think that when you remove KEY10, that you wind up at SOA#2 as well.

>   Note that in this example we assumed that the zone did not get
>   modified during the rollover.  New data can be introduced in the zone
>   as long as it is signed with both keys.

  Is it strictly necessary to sign with a new key?

  At SOA#1, the trusted path is via KEY11. Since the new record, and
the DNSSIG record on the new data can't have been cached yet (since they
don't exist yet!), so signing with the old key is kind of irrelevant, I
think.

>3.3.1.2 Pre-publish keyset rollover
>
>   This section shows how to perform a ZSK key without the need to sign
>   all the data in ones zone twice.  We recommend this method because it
>   has certain advantages in the case of key compromises.  A small
>   "HOWTO" for this kind of rollover can be found in Appendix B.

  It would be good to explain this.
  The major advantage is that it costs only 1 DNSKEY record, vs
O(size-of-zone) DNSSIG records.

>4.1 KSK compromise
>
>   When the KSK has been compromised the parent must be notified as soon
>   as possible and in a secure means.  The keyset of the zone SHOULD

  I believe that we should have a BCP for this part.
  What does it mean to securely notify the parent -- this is a human
protocol, not necessarily just a network one.

]      Out and about in Ottawa.    hmmm... beer.                |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian/notebook using, kernel hacking, security guy");  [

  
  




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat

iQCVAwUBP0qE04qHRg3pndX9AQGEtQQA8Ko/3w6HpVWWB8P5yapGNlqvf3Pj1zqD
tUgZHU7NipO3G/cFFSYPwXswcHUPhljB4U6Txusx/ar5OrPXH0eawOSmAW85gO9r
qz3v7082WPxvM/o4QA4hpX9daYhTIJKg4yHBuEoDxeLZ3ZHJu5wvU4CIFt02IWmR
UlcqAf2VNkM=
=6g4n
-----END PGP SIGNATURE-----
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug 28 18:03:06 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22823
	for <dnsop-archive@lists.ietf.org>; Thu, 28 Aug 2003 18:03:03 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SLVc6K022967
	for <dnsop-outgoing@nic.cafax.se>; Thu, 28 Aug 2003 23:31:38 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7SLVcq1022966
	for dnsop-outgoing; Thu, 28 Aug 2003 23:31:38 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from elektron.atoom.net (vhe-530008.sshn.net [195.169.222.38])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SA346K011103
	for <dnsop@cafax.se>; Thu, 28 Aug 2003 12:03:04 +0200 (MEST)
Received: from elektron.atoom.net (localhost [127.0.0.1])
	by elektron.atoom.net (8.12.9/8.12.9/Debian-5) with ESMTP id h7SA2tJJ015640
	for <dnsop@cafax.se>; Thu, 28 Aug 2003 12:02:55 +0200
Received: (from miekg@localhost)
	by elektron.atoom.net (8.12.9/8.12.9/Debian-5) id h7SA2tm0015638
	for dnsop@cafax.se; Thu, 28 Aug 2003 12:02:55 +0200
Date: Thu, 28 Aug 2003 12:02:55 +0200
From: Miek Gieben <miekg@atoom.net>
To: dnsop@cafax.se
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt
Message-ID: <20030828100255.GD14869@atoom.net>
Mail-Followup-To: dnsop@cafax.se
References: <20030825092647.236f76e0.olaf@ripe.net> <025501c36b2e$c364d9e0$b9370681@barnacle>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <025501c36b2e$c364d9e0$b9370681@barnacle>
User-Agent: Vim/Mutt/Linux
X-Home: www.miek.nl
X-Spam-Status: No, hits=-2.0 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,
	      USER_AGENT
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Virus-Scanned: by amavisd-new
Sender: owner-dnsop@cafax.se
Precedence: bulk

[On 25 Aug, @19:31, Scott wrote in "Re: draft-kolkman-dnssec-opera ..."]
> An opinion on section 3.2 (Security Key Considerations):  It is the wrong
> place for a discourse on key strengh, but a reference would be good for
> further info for someone interested.  Otherwise, it might be good to give
> some rough rules to follow such as "the larger the zone, the larger the key"
> and "larger the zone, zone key rollovers should be more frequent".

thanks, I've added this. I think it is good to make such a non technical
statement about key sizes.

References to documents regarding key sizes is still a good idea, but I don't
want to specify exact sizes in this draft. 

I do however have a document at home which has a table: year <-> key length. You
can just look up the year and then find a key length. This runs up until the
year 2025 (or something). Maybe that should be added as an reference...

grtz Miek
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug 28 18:03:07 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22825
	for <dnsop-archive@lists.ietf.org>; Thu, 28 Aug 2003 18:03:03 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SLa26K023364
	for <dnsop-outgoing@nic.cafax.se>; Thu, 28 Aug 2003 23:36:02 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7SLa2bv023363
	for dnsop-outgoing; Thu, 28 Aug 2003 23:36:02 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from coconut.itojun.org (coconut.itojun.org [219.101.47.130])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7RNhY6K003865
	for <dnsop@cafax.se>; Thu, 28 Aug 2003 01:43:40 +0200 (MEST)
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP
	id 030058F; Thu, 28 Aug 2003 08:43:29 +0900 (JST)
To: ipng@sunroof.eng.sun.com, dnsop@cafax.se
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: RFC2553 API: getnameinfo: ambiguous result due to malicious PTR setting
From: itojun@iijlab.net
Date: Thu, 28 Aug 2003 08:43:28 +0900
Message-Id: <20030827234329.030058F@coconut.itojun.org>
Sender: owner-dnsop@cafax.se
Precedence: bulk

	getnameinfo(3) handles both numeric and FQDN notation of the address,
	which is very good.  i'm happy about this API.  however, i have certain
	worry so i'd mumble here.

	when (malicious) PTR record like below is configured, there's no
	way for the user of getnameinfo(3) to detect if (a) there was no
	PTR record and therefore getnameinfo is returneing a numeric notation,
	or (b) there was a malicious PTR record.

1.0.0.127.in-addr.arpa.	IN PTR	10.1.1.1

	char addr[NI_MAXHOST];
	struct sockaddr *sa;	/* AF_INET, 127.0.0.1 */
	getnameinfo(sa, salen, addr, sizeof(addr), NULL, 0, 0)

	then "addr" will contain 10.1.1.1, which looks like a numeric IPv4
	address.  therefore programmers would think like (a) - there was no
	PTR record and "sa" contains 10.1.1.1.

	if we want to be proactive (to protect normal applications), we could
	reject such PTR responses.  however, if we reject those, we will be
	hiding certain data on the DNS (i.e. DNS diagnostic tool written with
	getnameinfo(3) will not be able to access raw DNS data).

	one way to solve this issue is to use NI_NAMEREQD flag, which is
	cumbersome.

	char addr[NI_MAXHOST];
	struct sockaddr *sa;	/* AF_INET, 127.0.0.1 */
	if (!getnameinfo(sa, salen, addr, sizeof(addr), NULL, 0, NI_NAMEREQD))
		/* PTR record is there */
	else
		getnameinfo(sa, salen, addr, sizeof(addr), NULL, 0, 0)
		/* it is numeric */

	any solutions, comments, whatever, is welcome.

itojun
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug 28 18:48:34 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22824
	for <dnsop-archive@lists.ietf.org>; Thu, 28 Aug 2003 18:03:03 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SLVZ6K022951
	for <dnsop-outgoing@nic.cafax.se>; Thu, 28 Aug 2003 23:31:35 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7SLVZxr022950
	for dnsop-outgoing; Thu, 28 Aug 2003 23:31:35 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from elektron.atoom.net (vhe-530008.sshn.net [195.169.222.38])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SAbk6K011491
	for <dnsop@cafax.se>; Thu, 28 Aug 2003 12:37:48 +0200 (MEST)
Received: from elektron.atoom.net (localhost [127.0.0.1])
	by elektron.atoom.net (8.12.9/8.12.9/Debian-5) with ESMTP id h7SAbiJJ016166
	for <dnsop@cafax.se>; Thu, 28 Aug 2003 12:37:44 +0200
Received: (from miekg@localhost)
	by elektron.atoom.net (8.12.9/8.12.9/Debian-5) id h7SAbi7u016164
	for dnsop@cafax.se; Thu, 28 Aug 2003 12:37:44 +0200
Date: Thu, 28 Aug 2003 12:37:44 +0200
From: Miek Gieben <miekg@atoom.net>
To: dnsop@cafax.se
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt
Message-ID: <20030828103743.GA15697@atoom.net>
Mail-Followup-To: dnsop@cafax.se
References: <20030825092647.236f76e0.olaf@ripe.net> <25334.1061848276@marajade.sandelman.ottawa.on.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25334.1061848276@marajade.sandelman.ottawa.on.ca>
User-Agent: Vim/Mutt/Linux
X-Home: www.miek.nl
X-Spam-Status: No, hits=-2.3 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Virus-Scanned: by amavisd-new
Sender: owner-dnsop@cafax.se
Precedence: bulk

[On 25 Aug, @23:51, Michael wrote in "Re: draft-kolkman-dnssec-opera ..."]
>   I still would like to introduce some kind of term, like "dieletric constant
> of DNSSEC" or some such to explain "propogation" of SIGs through caches :-)

Well, we already have the "singing zone rollover" :-)

>   Some initial comments/thoughts:
> 
> >   o  "Key publication period"
> >
> >         The period for which the public part of the key is published in
> >         the DNS.  The public part of the key can be published in the
> >         DNS while it has not yet been used to sign data As soon as a
> >         public key is published a brute force attack can be attempted
> >         to recover the private key.  Publishing the public key in
> >         advance (and not signing any data with it) does not guard
> >         against this attack.
> 
>   One interesting "defense" against this would be to publish multiple
> keys. Some of them could be total garbage. Since there is no signed data,
> you'd have to brute force all them to figure out which one signed the data.
> 
>   But, in any case, if you believe that the key can be brute forced during
> any low multiple of the "key publication period", then the period is probably
> too short, or the keys too small.

yes, but I'm not sure is something of this wording should be put in, although I
like the idea of "garbage keys".

> 
> re: 3.3.1.1 A double signature zone-signing key rollover
> 
> I don't think that at SOA#1, you have to resign with key 10. Maybe you
>   have to sign the DNSKEY11, but that's it.

the idea is to go from key10 to key11, both ZSKs. The thing is that caches
which do have key 10 but not any data can stil get data from the zone which
is signed with key 10.

after key 10 is timed out, the cache will pick up the keyset with keys
10 and 11. So now key 11 is in play. 

> Also, I think that when you remove KEY10, that you wind up at SOA#2 as well.

When this has happened key 10 can be discarded from the zonefile. So this
is what actually happens. Or are you saying, to go from SOA#0 to SOA#2 simple
discard key 10? But as I tried to explain above will not work. 

> >   Note that in this example we assumed that the zone did not get
> >   modified during the rollover.  New data can be introduced in the zone
> >   as long as it is signed with both keys.
> 
>   Is it strictly necessary to sign with a new key?
> 
>   At SOA#1, the trusted path is via KEY11. Since the new record, and
> the DNSSIG record on the new data can't have been cached yet (since they
> don't exist yet!), so signing with the old key is kind of irrelevant, I
> think.

it's all about old data which is signed with the old key. We wanted to 
specify some sort of transition from key 10 to key 11.

> 
> >3.3.1.2 Pre-publish keyset rollover
> >
> >   This section shows how to perform a ZSK key without the need to sign
> >   all the data in ones zone twice.  We recommend this method because it
> >   has certain advantages in the case of key compromises.  A small
> >   "HOWTO" for this kind of rollover can be found in Appendix B.
> 
>   It would be good to explain this.

Maybe adding something like this would help?:

If the old key gets compromised the new key is already distributed in the DNS. A
zone administrator is than able to quickly switch to the new key and remove the
compromised key from the zone.

>   The major advantage is that it costs only 1 DNSKEY record, vs
> O(size-of-zone) DNSSIG records.

yes, true, took me a moment to parse this, but you mean that you don't need
to have a double signed zone (which could be really big). 

> >4.1 KSK compromise
> >
> >   When the KSK has been compromised the parent must be notified as soon
> >   as possible and in a secure means.  The keyset of the zone SHOULD
> 
>   I believe that we should have a BCP for this part.

a seperate one? Or be just more verbose in this one?

>   What does it mean to securely notify the parent -- this is a human
> protocol, not necessarily just a network one.

I have no idea what is means, it probably means don't use the DNS.... :)

thanks for your comments,

grtz Miek
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug 28 19:38:51 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00378
	for <dnsop-archive@lists.ietf.org>; Thu, 28 Aug 2003 19:38:50 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SNHc6K024699
	for <dnsop-outgoing@nic.cafax.se>; Fri, 29 Aug 2003 01:17:38 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7SNHbRq024698
	for dnsop-outgoing; Fri, 29 Aug 2003 01:17:37 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from sith.maoz.com (sith.maoz.com [205.167.76.10])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SNHa6K024693
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 01:17:36 +0200 (MEST)
Received: (from dmm@localhost)
	by sith.maoz.com (8.12.9/8.12.9) id h7SNHZov013149;
	Thu, 28 Aug 2003 16:17:35 -0700
Date: Thu, 28 Aug 2003 16:17:35 -0700
From: David Meyer <dmm@1-4-5.net>
To: Rob Austein <sra+dnsop@hactrn.net>
Cc: dnsop@cafax.se
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt
Message-ID: <20030828161735.A13146@1-4-5.net>
References: <20030825092647.236f76e0.olaf@ripe.net> <20030828231251.901E718DC@thrintun.hactrn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030828231251.901E718DC@thrintun.hactrn.net>; from sra+dnsop@hactrn.net on Thu, Aug 28, 2003 at 07:12:50PM -0400
X-public-key: http://www.maoz.com/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-dnsop@cafax.se
Precedence: bulk

>> > Does the working group want to accept this document as a working group
>> > item?
>> 
>> Sure sounds to me like something this WG ought to be doing.

Agree, and thanks for speaking up Rob (hat on or off).

Dave

[in the immortal works John Aaron, "try SCE to AUX"]
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug 28 19:39:21 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00444
	for <dnsop-archive@lists.ietf.org>; Thu, 28 Aug 2003 19:39:21 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SNCs6K024641
	for <dnsop-outgoing@nic.cafax.se>; Fri, 29 Aug 2003 01:12:54 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7SNCsAn024640
	for dnsop-outgoing; Fri, 29 Aug 2003 01:12:54 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SNCq6K024633
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 01:12:53 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 901E718DC
	for <dnsop@cafax.se>; Thu, 28 Aug 2003 19:12:51 -0400 (EDT)
Date: Thu, 28 Aug 2003 19:12:50 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt
In-Reply-To: <20030825092647.236f76e0.olaf@ripe.net>
References: <20030825092647.236f76e0.olaf@ripe.net>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030828231251.901E718DC@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

At Mon, 25 Aug 2003 09:26:47 +0200, Olaf Kolkman wrote:
> 
> Does the working group want to accept this document as a working group
> item?

Sure sounds to me like something this WG ought to be doing.

<hat wg-co-chair=on>

  Any objections?

</hat>
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Thu Aug 28 20:07:22 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02332
	for <dnsop-archive@lists.ietf.org>; Thu, 28 Aug 2003 20:07:21 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SNif6K024903
	for <dnsop-outgoing@nic.cafax.se>; Fri, 29 Aug 2003 01:44:41 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7SNifI1024902
	for dnsop-outgoing; Fri, 29 Aug 2003 01:44:41 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from thrintun.hactrn.net (dsl092-066-067.bos1.dsl.speakeasy.net [66.92.66.67])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7SNie6K024897
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 01:44:40 +0200 (MEST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 00CB018D2
	for <dnsop@cafax.se>; Thu, 28 Aug 2003 19:44:39 -0400 (EDT)
Date: Thu, 28 Aug 2003 19:44:39 -0400
From: Rob Austein <sra+dnsop@hactrn.net>
To: dnsop@cafax.se
Subject: Re: RFC2553 API: getnameinfo: ambiguous result due to malicious PTR setting
In-Reply-To: <20030827234329.030058F@coconut.itojun.org>
References: <20030827234329.030058F@coconut.itojun.org>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030828234440.00CB018D2@thrintun.hactrn.net>
Sender: owner-dnsop@cafax.se
Precedence: bulk

[ipng mailing list cc dropped due to posting restrictions, don't ask]

I suppose you might add another flag bit to control whether or not
getnameinfo() rejects the form of PTR RR you're worried about.
Interfering with DNS diagnostic code doesn't particularly worry me,
since DNS diagnostic tools probably don't use this API anyway.  But
once your API starts down the path of trying to figure out what a
"bad" PTR RR looks like, forever will it dominate your destiny.

The real problem here is that the getnameinfo() API has two very
different ways of generating results that indistinguishable to the
caller.  There really ought to be another return value which tells you
how getnameinfo() ended up generating the text string.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug 29 08:10:57 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16245
	for <dnsop-archive@lists.ietf.org>; Fri, 29 Aug 2003 08:10:56 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TBTH6K000783
	for <dnsop-outgoing@nic.cafax.se>; Fri, 29 Aug 2003 13:29:17 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7TBTHZg000782
	for dnsop-outgoing; Fri, 29 Aug 2003 13:29:17 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from postmark.nist.gov (pushme.nist.gov [129.6.16.92])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TBTG6K000777
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 13:29:16 +0200 (MEST)
Received: from barnacle (barnacle.antd.nist.gov [129.6.55.185])
	by postmark.nist.gov (8.12.5/8.12.5) with SMTP id h7TBT9LR009641
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 07:29:10 -0400 (EDT)
Message-ID: <008001c36e20$c4afcbd0$b9370681@barnacle>
From: "Scott Rose" <scottr@nist.gov>
To: <dnsop@cafax.se>
References: <20030825092647.236f76e0.olaf@ripe.net> <20030828231251.901E718DC@thrintun.hactrn.net>
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt
Date: Fri, 29 Aug 2003 07:29:10 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

None from me.  I would like to see this a WG document.

Scott

----- Original Message ----- 
From: "Rob Austein" <sra+dnsop@hactrn.net>
To: <dnsop@cafax.se>
Sent: Thursday, August 28, 2003 7:12 PM
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt


> At Mon, 25 Aug 2003 09:26:47 +0200, Olaf Kolkman wrote:
> > 
> > Does the working group want to accept this document as a working group
> > item?
> 
> Sure sounds to me like something this WG ought to be doing.
> 
> <hat wg-co-chair=on>
> 
>   Any objections?
> 
> </hat>
> #----------------------------------------------------------------------
> # To unsubscribe, send a message to <dnsop-request@cafax.se>.
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug 29 09:13:24 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21225
	for <dnsop-archive@lists.ietf.org>; Fri, 29 Aug 2003 09:13:22 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TCi26K001508
	for <dnsop-outgoing@nic.cafax.se>; Fri, 29 Aug 2003 14:44:02 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7TCi1ed001507
	for dnsop-outgoing; Fri, 29 Aug 2003 14:44:01 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from postmark.nist.gov (pushme.nist.gov [129.6.16.92])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TChw6K001502
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 14:43:59 +0200 (MEST)
Received: from barnacle (barnacle.antd.nist.gov [129.6.55.185])
	by postmark.nist.gov (8.12.5/8.12.5) with SMTP id h7TChZLR007010;
	Fri, 29 Aug 2003 08:43:35 -0400 (EDT)
Message-ID: <00c301c36e2b$2a491eb0$b9370681@barnacle>
From: "Scott Rose" <scottr@nist.gov>
To: "Miek Gieben" <miekg@atoom.net>
Cc: <dnsop@cafax.se>
References: <20030825092647.236f76e0.olaf@ripe.net> <025501c36b2e$c364d9e0$b9370681@barnacle> <20030828100255.GD14869@atoom.net>
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt
Date: Fri, 29 Aug 2003 08:43:36 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

The key length <-> year sounds like a good reference doc.  I'm sure the hard
core security folk will want to consider other factors too (size of
plaintext, etc.) but admins that do not have the time to study up on
cryptography will want a handy guide.  That and the other rules I talked
about should give admins new to DNSSEC a place to start.

Scott

----- Original Message ----- 
From: "Miek Gieben" <miekg@atoom.net>
To: <dnsop@cafax.se>
Sent: Thursday, August 28, 2003 6:02 AM
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt


> [On 25 Aug, @19:31, Scott wrote in "Re: draft-kolkman-dnssec-opera ..."]
> > An opinion on section 3.2 (Security Key Considerations):  It is the
wrong
> > place for a discourse on key strengh, but a reference would be good for
> > further info for someone interested.  Otherwise, it might be good to
give
> > some rough rules to follow such as "the larger the zone, the larger the
key"
> > and "larger the zone, zone key rollovers should be more frequent".
>
> thanks, I've added this. I think it is good to make such a non technical
> statement about key sizes.
>
> References to documents regarding key sizes is still a good idea, but I
don't
> want to specify exact sizes in this draft.
>
> I do however have a document at home which has a table: year <-> key
length. You
> can just look up the year and then find a key length. This runs up until
the
> year 2025 (or something). Maybe that should be added as an reference...
>
> grtz Miek
> #----------------------------------------------------------------------
> # To unsubscribe, send a message to <dnsop-request@cafax.se>.

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug 29 12:23:11 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09448
	for <dnsop-archive@lists.ietf.org>; Fri, 29 Aug 2003 12:23:10 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TFoH6K003569
	for <dnsop-outgoing@nic.cafax.se>; Fri, 29 Aug 2003 17:50:17 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7TFoHET003568
	for dnsop-outgoing; Fri, 29 Aug 2003 17:50:17 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TFoD6K003563
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 17:50:14 +0200 (MEST)
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca [205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h7TFo5d04448
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Fri, 29 Aug 2003 11:50:11 -0400 (EDT)
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h7TFo2Zw028289;
	Fri, 29 Aug 2003 11:50:02 -0400
To: Miek Gieben <miekg@atoom.net>
cc: dnsop@cafax.se
Subject: Re: draft-kolkman-dnssec-operational-practices-00.txt 
In-reply-to: Your message of "Thu, 28 Aug 2003 12:37:44 +0200."
             <20030828103743.GA15697@atoom.net> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 29 Aug 2003 11:50:02 -0400
Message-ID: <28287.1062172202@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-dnsop@cafax.se
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Miek" == Miek Gieben <miekg@atoom.net> writes:
    >> But, in any case, if you believe that the key can be brute forced
    >> during any low multiple of the "key publication period", then the
    >> period is probably too short, or the keys too small.
                              ^long

  Sorry.

    Miek> yes, but I'm not sure is something of this wording should be put
    Miek> in, although I like the idea of "garbage keys".

  If you are very paranoid.

    >> It would be good to explain this.

    Miek> Maybe adding something like this would help?:

    Miek> If the old key gets compromised the new key is already distributed
    Miek> in the DNS. A zone administrator is than able to quickly switch to
    Miek> the new key and remove the compromised key from the zone.

  Yes.

    >> The major advantage is that it costs only 1 DNSKEY record, vs
    >> O(size-of-zone) DNSSIG records.

    Miek> yes, true, took me a moment to parse this, but you mean that you
    Miek> don't need to have a double signed zone (which could be really
    Miek> big).

  Yes, that's the point.
  It means that nearly all large zones would want to pre-publish the next
key.

    >> I believe that we should have a BCP for this part.

    Miek> a seperate one? Or be just more verbose in this one?

    >> What does it mean to securely notify the parent -- this is a human
    >> protocol, not necessarily just a network one.

    Miek> I have no idea what is means, it probably means don't use the
    Miek> DNS.... :)

  A seperate BCP on the human protocol for indicating a compromise of a key
via out-of-band protocol.

]      Out and about in Ottawa.    hmmm... beer.                |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian/notebook using, kernel hacking, security guy");  [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat

iQCVAwUBP092KYqHRg3pndX9AQGQzQQAmYojTr+FM6BBPL0LJyELbf7lZe+s8N/A
awBuXbAM2DkyRdg/grJzG682yJOEQ2gEVPXWX3SmH7Ii2PJOaHXtTKw4neWsFlKI
GOGT1le7u10F13AYuSuRF08irfOYjNvHbqaEW7YkH9vSYvgaFD7KfiBQ4YUR1Qje
LzHyEK3pYEk=
=L5bq
-----END PGP SIGNATURE-----
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


From owner-dnsop@cafax.se  Fri Aug 29 17:10:56 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05440
	for <dnsop-archive@lists.ietf.org>; Fri, 29 Aug 2003 17:10:55 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TKYi6K006791
	for <dnsop-outgoing@nic.cafax.se>; Fri, 29 Aug 2003 22:34:44 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h7TKYhrx006790
	for dnsop-outgoing; Fri, 29 Aug 2003 22:34:43 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from tpamail2.bdi.gte.com (tpamail2.bdi.gte.com [192.76.82.136])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h7TKYW6K006785
	for <dnsop@cafax.se>; Fri, 29 Aug 2003 22:34:32 +0200 (MEST)
Received: from smtptpa.interwan.gte.com ([138.83.66.45])
	by tpamail2.bdi.gte.com (8.12.9/8.12.5) with ESMTP id h7TKYTkL022683;
	Fri, 29 Aug 2003 16:34:30 -0400 (EDT)
Received: from USFLTTPSTCMMS01.ent.verizon.com (TPAMMS01B.interwan.gte.com [138.83.67.209])
	by smtptpa.interwan.gte.com (8.12.9/8.12.5) with ESMTP id h7TKYSDU022784;
	Fri, 29 Aug 2003 16:34:28 -0400 (EDT)
Received: from 138.83.66.45 by USFLTTPSTCMMS01.ent.verizon.com with
 ESMTP (SMTP Relay); Fri, 29 Aug 2003 16:34:23 -0400
Received: from ustxdfwh06.its.verizon.com (it.verizon.com
 [113.128.189.26]) by smtptpa.interwan.gte.com (8.12.9/8.12.5) with
 ESMTP id h7TKYMOv022702; Fri, 29 Aug 2003 16:34:23 -0400 (EDT)
Received: from mail pickup service by ustxdfwh06.its.verizon.com with
 Microsoft SMTPSVC; Fri, 29 Aug 2003 15:24:47 -0500
thread-index: AcNs9atBdopbnOL4RWWHDzPwxqekBg==
Received: from smtpirv.interwan.gte.com ([138.83.34.67]) by
 ustxdfwh06.its.verizon.com with Microsoft SMTPSVC(5.0.2195.5329); Wed,
 27 Aug 2003 18:48:08 -0500
Received: from USTXIRVHQWMMS02.ent.verizon.com (
 IRVMMS02B.interwan.gte.com [138.83.34.109]) by smtpirv.interwan.gte.com
 (8.12.9/8.12.5) with ESMTP id h7RNm8VI012963 for
 <Min.Xie@ap.bdi.gte.com>; Wed, 27 Aug 2003 18:48:08 -0500 (CDT)
Received: from 192.76.80.129 by USTXIRVHQWMMS02.ent.verizon.com with
 ESMTP (SMTP Relay (MMS v5.5.3)); Wed, 27 Aug 2003 18:48:02 -0500
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34]
 ) by irvmail.bdi.gte.com (8.12.9/8.12.5) with ESMTP id h7RNlVsq015006
 for <Min.Xie@ap.bdi.gte.com>; Wed, 27 Aug 2003 18:47:31 -0500 (CDT)
Content-Class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Received: from engmail1mpk.Eng.Sun.COM ([129.146.11.21]) by
 brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h7RNiFvG018886; Wed,
 27 Aug 2003 17:44:15 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM
 [129.146.168.88]) by engmail1mpk.Eng.Sun.COM (
 8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h7RNi8VB016908; Wed, 27
 Aug 2003 16:44:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by
 sunroof.eng.sun.com (8.12.10.Beta3+Sun/8.12.10.Beta3) with ESMTP id
 h7RNkcU3019756; Wed, 27 Aug 2003 16:46:38 -0700 (PDT)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (
 8.12.10.Beta3+Sun/8.12.10.Beta3/Submit) id h7RNkbnq019755; Wed, 27 Aug
 2003 16:46:37 -0700 (PDT)
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19]) by
 sunroof.eng.sun.com (8.12.10.Beta3+Sun/8.12.10.Beta3) with ESMTP id
 h7RNkXU3019748 for <ipng@sunroof.eng.sun.com>; Wed, 27 Aug 2003 16:46:
 33 -0700 (PDT)
Received: from brmea-mail-1.sun.com (brmea-mail-1.Central.Sun.COM
 [129.147.5.31]) by engmail2sun.Eng.Sun.COM (8.12.9+Sun/8.12.9/ENSMAIL,
 v2.2) with ESMTP id h7RNhbUu018259 for <ipng@sunroof.eng.sun.com>; Wed,
 27 Aug 2003 16:43:37 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [219.101.47.130])
 by brmea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h7RNhVNM016650
 for <ipng@sunroof.eng.sun.com>; Wed, 27 Aug 2003 17:43:31 -0600 (MDT)
Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org
 (Postfix) with ESMTP id 030058F; Thu, 28 Aug 2003 08:43:29 +0900 (JST)
To: ipng@sunroof.eng.sun.com, dnsop@cafax.se
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: RFC2553 API: getnameinfo: ambiguous result due to malicious PTR
 setting
From: itojun@iijlab.net
Date: Thu, 28 Aug 2003 08:43:28 +0900
Message-ID: <20030827234329.030058F@coconut.itojun.org>
MIME-Version: 1.0
X-WSS-ID: 13539CB81430267-01-01
X-OriginalArrivalTime: 27 Aug 2003 23:48:09.0028 (UTC)
 FILETIME=[AB1FC840:01C36CF5]
X-WSS-ID: 13516745990722-01-01
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

	getnameinfo(3) handles both numeric and FQDN notation of the address,
	which is very good.  i'm happy about this API.  however, i have certain
	worry so i'd mumble here.

	when (malicious) PTR record like below is configured, there's no
	way for the user of getnameinfo(3) to detect if (a) there was no
	PTR record and therefore getnameinfo is returneing a numeric notation,
	or (b) there was a malicious PTR record.

1.0.0.127.in-addr.arpa.	IN PTR	10.1.1.1

	char addr[NI_MAXHOST];
	struct sockaddr *sa;	/* AF_INET, 127.0.0.1 */
	getnameinfo(sa, salen, addr, sizeof(addr), NULL, 0, 0)

	then "addr" will contain 10.1.1.1, which looks like a numeric IPv4
	address.  therefore programmers would think like (a) - there was no
	PTR record and "sa" contains 10.1.1.1.

	if we want to be proactive (to protect normal applications), we could
	reject such PTR responses.  however, if we reject those, we will be
	hiding certain data on the DNS (i.e. DNS diagnostic tool written with
	getnameinfo(3) will not be able to access raw DNS data).

	one way to solve this issue is to use NI_NAMEREQD flag, which is
	cumbersome.

	char addr[NI_MAXHOST];
	struct sockaddr *sa;	/* AF_INET, 127.0.0.1 */
	if (!getnameinfo(sa, salen, addr, sizeof(addr), NULL, 0, NI_NAMEREQD))
		/* PTR record is there */
	else
		getnameinfo(sa, salen, addr, sizeof(addr), NULL, 0, 0)
		/* it is numeric */

	any solutions, comments, whatever, is welcome.

itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to majordomo@sunroof.eng.sun.com
--------------------------------------------------------------------


#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.


