
From Ted.Lemon@nominum.com  Sun Feb  2 06:42:50 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FBA61A00D9 for <dnsop@ietfa.amsl.com>; Sun,  2 Feb 2014 06:42:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v6ipdlDnELSg for <dnsop@ietfa.amsl.com>; Sun,  2 Feb 2014 06:42:48 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 895C01A00DC for <dnsop@ietf.org>; Sun,  2 Feb 2014 06:42:48 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUu5ZZPKJpbnXCOzAodjzLvDdBsj2RvYc@postini.com; Sun, 02 Feb 2014 06:42:44 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2486B1B8318 for <dnsop@ietf.org>; Sun,  2 Feb 2014 06:42:44 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D7A0E190052; Sun,  2 Feb 2014 06:42:43 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 2 Feb 2014 06:42:43 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140130004530.C660CE086E0@rock.dv.isc.org>
Date: Sun, 2 Feb 2014 09:42:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <92B69F15-5DF0-46BC-8D77-02FE15AC24F8@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, Ralf Weber <dns@fl1ger.de>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Feb 2014 14:42:50 -0000

On Jan 29, 2014, at 7:45 PM, Mark Andrews <marka@isc.org> wrote:
> The squatted tld's used by software .onion, .bit etc could be
> migrated to a new namespaces.  Just issue new software that looks
> / recognises in the new namespace first then in the old one for X
> years.  After X years stop looking in / recognising the old namespace.
> Set X to about 10 years and there will be very little old code left
> when you turn off support for the namespace.  Set and compile in
> the drop dead date.

Ten years is a long time, and even if the schedule you recommend is =
practical, the conflict will still cause problems in the short term, =
which is what actually matters.   The IETF could choose to simply punt =
on this and let ICANN deal with it however they want, but there's some =
degree of consensus that we ought to document these issues, and that's =
why this draft is up for consideration.

The point is not to say "squatting on TLDs is ok" or "special-use TLDs =
for these uses is the right architecture," but rather to say =
"special-use TLDs for these uses exist; here is what they are; here is =
where to go to learn more about them."

In my mind, the criteria for deciding whether to document them are (a) =
whether there is some serious effort out there somewhere to use them _on =
the internet_, (b) that someone proposes to document the use in the IETF =
under RFC 6761, and (c) that we think there is sufficient interest in =
the usage being documented that it's reasonable to think that, were the =
TLD in question to be assigned in the DNS, significant problems would =
ensue.

(c) is a judgment call, (b) is a prerequisite for RFC 6761 to apply (the =
IETF does not have change control for the namespace, but is an =
appropriate venue for documenting uses of it), and (a) is a requirement =
because if (a) doesn't apply, it's simply not the IETF's problem.

It's certainly reasonable to say that we ought to make architectural =
recommendations to proponents of these special-use TLDs, but we can't =
actually stop them from using them.   It's somewhat analogous to the =
situation with TXT records.

So if we punt on this and refuse to document these special use TLDs =
under 6761, it doesn't actually solve the problem, or make anything =
better.

And although several heavy hitters in the DNS working groups do =
apparently feel strongly that special use TLDs are a bad architectural =
choice, there is no consensus in the IETF for this position (yes, I am =
saying that with my AD hat on).

The IESG would prefer to see these proposals worked on by DNSOP, because =
that will likely improve the documents.   Part of that improvement might =
be some recommendation for sunsetting, although I am skeptical that that =
will gain consensus.

But we've been down the "this is a bad idea, let's not document it" path =
before, and it leads to worse outcomes than documenting it.   So I'd =
really love it if we could see some discussion of how to make the =
document better, rather than simple rejection of the proposal.


From bortzmeyer@nic.fr  Mon Feb  3 07:20:32 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822731A016C for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 07:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UktlpXpGjfGV for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 07:20:30 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 753FE1A0160 for <dnsop@ietf.org>; Mon,  3 Feb 2014 07:20:30 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 152B92801BB; Mon,  3 Feb 2014 16:20:29 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 0F683280041; Mon,  3 Feb 2014 16:20:29 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 0CFED960001; Mon,  3 Feb 2014 16:19:59 +0100 (CET)
Date: Mon, 3 Feb 2014 16:19:59 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mark Andrews <marka@isc.org>
Message-ID: <20140203151958.GA1673@nic.fr>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20140130004530.C660CE086E0@rock.dv.isc.org>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, Ralf Weber <dns@fl1ger.de>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 15:20:32 -0000

On Thu, Jan 30, 2014 at 11:45:30AM +1100,
 Mark Andrews <marka@isc.org> wrote 
 a message of 74 lines which said:

> The squatted tld's used by software .onion, .bit etc could be
> migrated to a new namespaces.

:-)

"squatted" is not a bad word here. In the physical world, squatters
are often people who do not have the money to rent a home, because
some rich people put the price of the housing too high. Here, you will
have trouble convincing the users of Tor or Namecoin that it is right
to pay 185Â 000 $ for a TLD and that, if they cannot afford it, they
have to stay in the slums.

[End of political rant, sorry]

From paul.hoffman@vpnc.org  Mon Feb  3 08:15:16 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68061A0035 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 08:15:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t3zn11dwoVfO for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 08:15:15 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 921B81A002B for <dnsop@ietf.org>; Mon,  3 Feb 2014 08:15:15 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s13FtBjC099724 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 3 Feb 2014 08:55:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140203151958.GA1673@nic.fr>
Date: Mon, 3 Feb 2014 08:15:10 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 16:15:17 -0000

On Feb 3, 2014, at 7:19 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:

> On Thu, Jan 30, 2014 at 11:45:30AM +1100,
> Mark Andrews <marka@isc.org> wrote=20
> a message of 74 lines which said:
>=20
>> The squatted tld's used by software .onion, .bit etc could be
>> migrated to a new namespaces.
>=20
> :-)
>=20
> "squatted" is not a bad word here. In the physical world, squatters
> are often people who do not have the money to rent a home, because
> some rich people put the price of the housing too high. Here, you will
> have trouble convincing the users of Tor or Namecoin that it is right
> to pay 185 000 $ for a TLD and that, if they cannot afford it, they
> have to stay in the slums.
>=20
> [End of political rant, sorry]

Your political rant is, however, off-base. Assume for the moment that =
the Tor folks had registered oniontld.fr for a relatively small amount =
of money. It could have all of the attributes of .onion: you could =
hard-wire it into local resolvers, some requests for it would leak to =
the DNS and therefore possibly be trackable, and so on. For the purposes =
given in draft-grothoff-iesg-special-use-p2p-names, unsquatted FQDNs =
would work just as well as squatted TLDs.

--Paul Hoffman=

From jabley@hopcount.ca  Mon Feb  3 12:35:19 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D301A01FB for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 12:35:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60UjNBWA7Z9O for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 12:35:17 -0800 (PST)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 686FB1A0162 for <dnsop@ietf.org>; Mon,  3 Feb 2014 12:35:17 -0800 (PST)
Received: by mail-qa0-f53.google.com with SMTP id cm18so10667757qab.26 for <dnsop@ietf.org>; Mon, 03 Feb 2014 12:35:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=pGQ7SmfhrL/GE7x/F9NAlfpuhUR8+/qyDroJLyr9a9w=; b=BOXjPFMLCD8Inax0OJLoXdLgJX+Jf9j34yuwfY5uiTH7htz2+jkKVGhWH3anVaYpw4 gz8fcH5fiHAF5qlazgqVuPkcQDVkEPBdTwuIkyZ9N6TQ6h8TvPx/p81cnep9CqY4F8fs ZI7enzWqQrMBsUSjCBYB6IMsw4/jh+YyiVhSQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=pGQ7SmfhrL/GE7x/F9NAlfpuhUR8+/qyDroJLyr9a9w=; b=OjikrMozZGZYghKqondRgSpbmg+rJi9JOZg3XuAARfs/ytL9t58VUDpKSVB4NM1Gs9 kce9ukzr5X8fegJBCWOgb5MG30TR1kONs5BEwKKxPHjW0r75sJ6Wqu3yPyJ1tr8Qdsuj VI+nJTxE89+2J0JxS5Uu3e+Z8tCvUqvbtmj4V4Hx+LWTUmGnEZuLzzRAJVQ0a4XkgDKH Y1gBrz9rMFO9MS/K/BHY/RJpD7MBdODJAi4npiclv9GPl4RoR9mRg1Pk/gs5ImgEw3ip LCfQmh8A2P952QLd9F3fNJDFZKVatHgphaSR6Zx8ukbyt4DRCBxXcQQTXw+IJtexBk+G ohXg==
X-Gm-Message-State: ALoCoQkIHDlezz2Uqg6w3DaO09Mc+D1rXajkRO27KvfNPCs9C/9DqxlkVDaLGn5frQZyMsaJD8My
X-Received: by 10.229.46.70 with SMTP id i6mr23848328qcf.10.1391459716519; Mon, 03 Feb 2014 12:35:16 -0800 (PST)
Received: from [172.16.28.85] (nat-08-mht.dyndns.com. [216.146.45.247]) by mx.google.com with ESMTPSA id u4sm59778572qai.21.2014.02.03.12.35.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 12:35:15 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_AC167ED6-0581-42F3-8493-3BA4D57046A0"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org>
Date: Mon, 3 Feb 2014 15:35:13 -0500
Message-Id: <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 20:35:19 -0000

--Apple-Mail=_AC167ED6-0581-42F3-8493-3BA4D57046A0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-02-03, at 11:15, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Feb 3, 2014, at 7:19 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:
>=20
>> "squatted" is not a bad word here. In the physical world, squatters
>> are often people who do not have the money to rent a home, because
>> some rich people put the price of the housing too high. Here, you =
will
>> have trouble convincing the users of Tor or Namecoin that it is right
>> to pay 185 000 $ for a TLD and that, if they cannot afford it, they
>> have to stay in the slums.
>>=20
>> [End of political rant, sorry]
>=20
> Your political rant is, however, off-base. Assume for the moment that =
the Tor folks had registered oniontld.fr for a relatively small amount =
of money. It could have all of the attributes of .onion: you could =
hard-wire it into local resolvers, some requests for it would leak to =
the DNS and therefore possibly be trackable, and so on. For the purposes =
given in draft-grothoff-iesg-special-use-p2p-names, unsquatted FQDNs =
would work just as well as squatted TLDs.

I made that point somewhat earlier (but my example was onion.eff.org or =
something).

The reasonable response to my instance of that observation was that =
there's a significant deployed base of users already making use of =
.onion [1], and we don't have a time machine that we're aware of [2] to =
allow that to be fixed.

Despite the enduring (and endearing, perhaps) optimism that the new gTLD =
programme would eventually bear fruit, I don't think it's unreasonable =
to think that in 2002 [3] a new gTLD wasn't really a practical option to =
choose not to take.

So squatting doesn't sound right to me.


Joe

[1] https://metrics.torproject.org
[2] =
http://www.huffingtonpost.co.uk/2012/07/02/stephen-hawking-time-travel_n_1=
643488.html
[3] http://en.wikipedia.org/wiki/Tor_(anonymity_network)#History


--Apple-Mail=_AC167ED6-0581-42F3-8493-3BA4D57046A0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLv/YEACgkQNI8MvYZSOiwyEQCgpDCFkB7czvUHkPDscZRVXoo+
RmkAoIgoMwCUe4NUWLAS8C4e2xJcz+zH
=7ADM
-----END PGP SIGNATURE-----

--Apple-Mail=_AC167ED6-0581-42F3-8493-3BA4D57046A0--

From marka@isc.org  Mon Feb  3 13:23:52 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A6C1A0225 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 13:23:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.436
X-Spam-Level: 
X-Spam-Status: No, score=-7.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpOeYZR_q74A for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 13:23:50 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id EAE661A01FB for <dnsop@ietf.org>; Mon,  3 Feb 2014 13:23:48 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 50D6D2383D4; Mon,  3 Feb 2014 21:23:35 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 40A7F160446; Mon,  3 Feb 2014 21:35:53 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 0B8B51602EA; Mon,  3 Feb 2014 21:35:53 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 1259EE44493; Tue,  4 Feb 2014 08:23:33 +1100 (EST)
To: Joe Abley <jabley@hopcount.ca>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca>
In-reply-to: Your message of "Mon, 03 Feb 2014 15:35:13 -0500." <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca>
Date: Tue, 04 Feb 2014 08:23:33 +1100
Message-Id: <20140203212333.1259EE44493@rock.dv.isc.org>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 21:23:52 -0000

In message <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca>, Joe Abley writes:
>
> On 2014-02-03, at 11:15, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>
> > On Feb 3, 2014, at 7:19 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
> wrote:
> >
> >> "squatted" is not a bad word here. In the physical world, squatters
> >> are often people who do not have the money to rent a home, because
> >> some rich people put the price of the housing too high. Here, you will
> >> have trouble convincing the users of Tor or Namecoin that it is right
> >> to pay 185 000 $ for a TLD and that, if they cannot afford it, they
> >> have to stay in the slums.
> >>
> >> [End of political rant, sorry]
> >
> > Your political rant is, however, off-base. Assume for the moment that
> > the Tor folks had registered oniontld.fr for a relatively small amount of
> > money. It could have all of the attributes of .onion: you could hard-wire
> > it into local resolvers, some requests for it would leak to the DNS and
> > therefore possibly be trackable, and so on. For the purposes given in
> > draft-grothoff-iesg-special-use-p2p-names, unsquatted FQDNs would work
> > just as well as squatted TLDs.
>
> I made that point somewhat earlier (but my example was onion.eff.org or
> something).
>
> The reasonable response to my instance of that observation was that
> there's a significant deployed base of users already making use of .onion
> [1], and we don't have a time machine that we're aware of [2] to allow
> that to be fixed.
>
> Despite the enduring (and endearing, perhaps) optimism that the new gTLD
> programme would eventually bear fruit, I don't think it's unreasonable to
> think that in 2002 [3] a new gTLD wasn't really a practical option to
> choose not to take.
>
> So squatting doesn't sound right to me.

They choose to use a TLD.  There were plenty of people saying "Do
NOT use a TLD for your private namespace, use a namespace you own"
in 2002 whether it was for a protocol or a internal network.

For $20 a year or less they could have registered a name in just
about any TLD and avoided the issue.

> Joe
> 
> [1] https://metrics.torproject.org
> [2] =
> http://www.huffingtonpost.co.uk/2012/07/02/stephen-hawking-time-travel_n_1=
> 643488.html
> [3] http://en.wikipedia.org/wiki/Tor_(anonymity_network)#History
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From Ted.Lemon@nominum.com  Mon Feb  3 13:56:41 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5921A019F for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 13:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFFsaFJH2T89 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 13:56:40 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id A498B1A015D for <dnsop@ietf.org>; Mon,  3 Feb 2014 13:56:40 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUvAQmJpS+wwkZdpz1mojHWGAcibTLLQx@postini.com; Mon, 03 Feb 2014 13:56:40 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6CF761B82FF for <dnsop@ietf.org>; Mon,  3 Feb 2014 13:56:40 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 4FAB1190043; Mon,  3 Feb 2014 13:56:40 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Feb 2014 13:56:40 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140203212333.1259EE44493@rock.dv.isc.org>
Date: Mon, 3 Feb 2014 16:56:38 -0500
Content-Transfer-Encoding: 7bit
Message-ID: <CB7515C9-0120-4B42-B0D3-E30FF6638555@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 21:56:41 -0000

On Feb 3, 2014, at 4:23 PM, Mark Andrews <marka@isc.org> wrote:
> They choose to use a TLD.  There were plenty of people saying "Do
> NOT use a TLD for your private namespace, use a namespace you own"
> in 2002 whether it was for a protocol or a internal network.

This is a useless discussion.   Recriminations do not change the past.


From ajs@anvilwalrusden.com  Mon Feb  3 14:15:11 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 701651A01EE for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 14:15:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkDADWLd9U6j for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 14:15:10 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB201A0218 for <dnsop@ietf.org>; Mon,  3 Feb 2014 14:15:09 -0800 (PST)
Received: from mx1.yitter.info (nat-01-mht.dyndns.com [216.146.45.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id A12D18A031 for <dnsop@ietf.org>; Mon,  3 Feb 2014 22:15:08 +0000 (UTC)
Date: Mon, 3 Feb 2014 17:15:06 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140203221506.GO13520@mx1.yitter.info>
References: <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CB7515C9-0120-4B42-B0D3-E30FF6638555@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CB7515C9-0120-4B42-B0D3-E30FF6638555@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 22:15:11 -0000

On Mon, Feb 03, 2014 at 04:56:38PM -0500, Ted Lemon wrote:
> This is a useless discussion.   Recriminations do not change the past.

True, but effectively what you're saying is that this special-use
registry could be used by anyone who's prepared to [squat|use a TLD
without registering it] in the right ways to get around the ICANN
allocation procedures.  I think that's spelled "moral hazard" in
economics.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jonne.soininen@broadcom.com  Mon Feb  3 13:54:46 2014
Return-Path: <jonne.soininen@broadcom.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5BC81A019F for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 13:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXQijdmDapk3 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 13:54:44 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.116]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6941A015D for <dnsop@ietf.org>; Mon,  3 Feb 2014 13:54:44 -0800 (PST)
Received: from [193.109.254.147:61850] by server-12.bemta-14.messagelabs.com id 50/1F-17220-32010F25; Mon, 03 Feb 2014 21:54:43 +0000
X-Env-Sender: jonne.soininen@broadcom.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1391464482!1741932!1
X-Originating-IP: [213.174.82.10]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3505 invoked from network); 3 Feb 2014 21:54:42 -0000
Received: from renexfe01.roe2.renesasmobile.com (HELO renexfe01.roe2.renesasmobile.com) (213.174.82.10) by server-16.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 3 Feb 2014 21:54:42 -0000
Received: from RENEXMB01.roe2.renesasmobile.com ([fe80::e58a:2b9f:54fe:ff5]) by renexfe01.roe2.renesasmobile.com ([fe80::ec94:bbb3:68e:a94a%18]) with mapi id 14.03.0174.001; Mon, 3 Feb 2014 23:54:42 +0200
From: <jonne.soininen@broadcom.com>
To: <marka@isc.org>, <jabley@hopcount.ca>
Thread-Topic: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
Thread-Index: AQHPISqKpqmZs4RLaEKxwrcTU52+xA==
Date: Mon, 3 Feb 2014 21:54:41 +0000
Message-ID: <CF15D98C.197C0B%jonne.soininen@renesasmobile.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org>
In-Reply-To: <20140203212333.1259EE44493@rock.dv.isc.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.22.172]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C3D25FD9E31F5046B72324E72493AAAF@renesasmobile.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 03 Feb 2014 14:34:31 -0800
Cc: dnsop@ietf.org, paul.hoffman@vpnc.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 21:54:47 -0000

Hi everybody,

(just for full closure - I'm the IETF technical liaison to the ICANN
board, but taking that hat off here)


On 2/3/14 11:23 PM, "Mark Andrews" <marka@isc.org> wrote:

>
>In message <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca>, Joe Abley
>writes:
>>
>> On 2014-02-03, at 11:15, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>>
>> > On Feb 3, 2014, at 7:19 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
>> wrote:
>> >
>> >> "squatted" is not a bad word here. In the physical world, squatters
>> >> are often people who do not have the money to rent a home, because
>> >> some rich people put the price of the housing too high. Here, you
>>will
>> >> have trouble convincing the users of Tor or Namecoin that it is right
>> >> to pay 185 000 $ for a TLD and that, if they cannot afford it, they
>> >> have to stay in the slums.
>> >>
>> >> [End of political rant, sorry]
>> >
>> > Your political rant is, however, off-base. Assume for the moment that
>> > the Tor folks had registered oniontld.fr for a relatively small
>>amount of
>> > money. It could have all of the attributes of .onion: you could
>>hard-wire
>> > it into local resolvers, some requests for it would leak to the DNS
>>and
>> > therefore possibly be trackable, and so on. For the purposes given in
>> > draft-grothoff-iesg-special-use-p2p-names, unsquatted FQDNs would work
>> > just as well as squatted TLDs.
>>
>> I made that point somewhat earlier (but my example was onion.eff.org or
>> something).
>>
>> The reasonable response to my instance of that observation was that
>> there's a significant deployed base of users already making use of
>>.onion
>> [1], and we don't have a time machine that we're aware of [2] to allow
>> that to be fixed.
>>
>> Despite the enduring (and endearing, perhaps) optimism that the new gTLD
>> programme would eventually bear fruit, I don't think it's unreasonable
>>to
>> think that in 2002 [3] a new gTLD wasn't really a practical option to
>> choose not to take.
>>
>> So squatting doesn't sound right to me.
>
>They choose to use a TLD.  There were plenty of people saying "Do
>NOT use a TLD for your private namespace, use a namespace you own"
>in 2002 whether it was for a protocol or a internal network.
>
>For $20 a year or less they could have registered a name in just
>about any TLD and avoided the issue.

I think we have to distinguish here between the "new squatters" and the
"old squatters" and the reasons for "squatting". For instance in corp and
home, the installed base seems to be quite large. It comes from equipment
and hardware that might not be easily replaceable and not really under a
single organization's control. You cannot change that and ignoring it
might cause harm for the Internet.

The new technologies (gnu/onion/...) seem to be different. First of all,
they don't use DNS but something else. Therefore, there should be no
collisions. It seems more that delegating them to the DNS would harm those
technologies rather than DNS or Internet getting harmed. The only
relationship to the DNS seems to be that they happen to have a structure
that is similar to the FQDN.

Anyways, I have been following this discussion now for a while. It seems
to me that the discussion is not really converging. I would blame it at
least partly on RFC6761. Though, RFC6761 isn't that old, it was written in
a time before the new gTLD round was ongoing.

Rather than discussing the individual strings, maybe we should consider to
discuss the principles under which TLDs can be reserved for special use
and consider a re-spin or an update to RFC6761.

Cheers,

Jonne.

>
>> Joe
>>=20
>> [1] https://metrics.torproject.org
>> [2] =3D
>>=20
>>http://www.huffingtonpost.co.uk/2012/07/02/stephen-hawking-time-travel_n_
>>1=3D
>> 643488.html
>> [3] http://en.wikipedia.org/wiki/Tor_(anonymity_network)#History
>--=20
>Mark Andrews, ISC
>1 Seymour St., Dundas Valley, NSW 2117, Australia
>PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop


From ggm@algebras.org  Mon Feb  3 14:56:25 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF5A41A0273 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 14:56:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.957
X-Spam-Level: 
X-Spam-Status: No, score=-0.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWO2ZMXz0pLi for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 14:56:22 -0800 (PST)
Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by ietfa.amsl.com (Postfix) with ESMTP id 672971A0268 for <dnsop@ietf.org>; Mon,  3 Feb 2014 14:56:22 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id un15so7695917pbc.10 for <dnsop@ietf.org>; Mon, 03 Feb 2014 14:56:22 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:cc:content-type; bh=Bgvm+4kkvIyKJr8Z7rTs3BHQFK+v5C4szhxyUO0bPBY=; b=dY9l+gQoQQwT0QnwwdKvEdhjv7oychNYuzpiwnrto+618JpomkiXvotGWxllPVgHc2 WG7Lam++1I1osAcXro22U5QpQ636LUvU2cGxJDacUq7dNSB4BCLv/+FcsdkSlJnHyZAR Jkc/eAajAsCOOWjoKNEDQsxisaalsUFIrYvUw8Dx0ihoNs8u9m/zxTP2eDxrpfzSeljg yc8DYq+t44bKDpi6GzD8VOAQxwFzBCM8QYBAjGRSchYm+3ueQTNnJ/uwDxzMADRLZvuv +G0TSO6ULCM5MSmZq8bkxycI9mowvSGPB5xGpIw36YFItgr+NKVH3Q6DbiiTLaQ+mVIW eamg==
X-Gm-Message-State: ALoCoQkLYFBnlwEAtVQEB6l1ffPFxISxpLq6wip/ItBaeuFoflBDafp5g5vAFsmFjxj5V1lu3Npc
MIME-Version: 1.0
X-Received: by 10.68.231.35 with SMTP id td3mr39748584pbc.137.1391468182301; Mon, 03 Feb 2014 14:56:22 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Mon, 3 Feb 2014 14:56:22 -0800 (PST)
X-Originating-IP: [2001:44b8:2136:8e00:8cae:7195:4e13:8720]
In-Reply-To: <CF15D98C.197C0B%jonne.soininen@renesasmobile.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com>
Date: Tue, 4 Feb 2014 08:56:22 +1000
Message-ID: <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b33d592b906e304f1886e17
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 22:56:25 -0000

--047d7b33d592b906e304f1886e17
Content-Type: text/plain; charset=ISO-8859-1

I am not personally convinced by "there are too many people committed"
arguments. I never have been, and I think the chilling effect of this has
been seen time and again.

There has always been "too many people" doing things. Claiming the dead
hand of history prevents us from changing course or deploying new things is
just wrong.

1 create onion.something.else and mark .onion as suitable for future use
under gTLD, if not now
2 release new TOR code and declare sunset period
3 wait for sunset period
4 stop blocking release of .onion

We don't expect people to use rlogin or rsh any more. Protocols move on.


On Tue, Feb 4, 2014 at 7:54 AM, <jonne.soininen@broadcom.com> wrote:

> Hi everybody,
>
> (just for full closure - I'm the IETF technical liaison to the ICANN
> board, but taking that hat off here)
>
>
> On 2/3/14 11:23 PM, "Mark Andrews" <marka@isc.org> wrote:
>
> >
> >In message <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca>, Joe Abley
> >writes:
> >>
> >> On 2014-02-03, at 11:15, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> >>
> >> > On Feb 3, 2014, at 7:19 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
> >> wrote:
> >> >
> >> >> "squatted" is not a bad word here. In the physical world, squatters
> >> >> are often people who do not have the money to rent a home, because
> >> >> some rich people put the price of the housing too high. Here, you
> >>will
> >> >> have trouble convincing the users of Tor or Namecoin that it is right
> >> >> to pay 185 000 $ for a TLD and that, if they cannot afford it, they
> >> >> have to stay in the slums.
> >> >>
> >> >> [End of political rant, sorry]
> >> >
> >> > Your political rant is, however, off-base. Assume for the moment that
> >> > the Tor folks had registered oniontld.fr for a relatively small
> >>amount of
> >> > money. It could have all of the attributes of .onion: you could
> >>hard-wire
> >> > it into local resolvers, some requests for it would leak to the DNS
> >>and
> >> > therefore possibly be trackable, and so on. For the purposes given in
> >> > draft-grothoff-iesg-special-use-p2p-names, unsquatted FQDNs would work
> >> > just as well as squatted TLDs.
> >>
> >> I made that point somewhat earlier (but my example was onion.eff.org or
> >> something).
> >>
> >> The reasonable response to my instance of that observation was that
> >> there's a significant deployed base of users already making use of
> >>.onion
> >> [1], and we don't have a time machine that we're aware of [2] to allow
> >> that to be fixed.
> >>
> >> Despite the enduring (and endearing, perhaps) optimism that the new gTLD
> >> programme would eventually bear fruit, I don't think it's unreasonable
> >>to
> >> think that in 2002 [3] a new gTLD wasn't really a practical option to
> >> choose not to take.
> >>
> >> So squatting doesn't sound right to me.
> >
> >They choose to use a TLD.  There were plenty of people saying "Do
> >NOT use a TLD for your private namespace, use a namespace you own"
> >in 2002 whether it was for a protocol or a internal network.
> >
> >For $20 a year or less they could have registered a name in just
> >about any TLD and avoided the issue.
>
> I think we have to distinguish here between the "new squatters" and the
> "old squatters" and the reasons for "squatting". For instance in corp and
> home, the installed base seems to be quite large. It comes from equipment
> and hardware that might not be easily replaceable and not really under a
> single organization's control. You cannot change that and ignoring it
> might cause harm for the Internet.
>
> The new technologies (gnu/onion/...) seem to be different. First of all,
> they don't use DNS but something else. Therefore, there should be no
> collisions. It seems more that delegating them to the DNS would harm those
> technologies rather than DNS or Internet getting harmed. The only
> relationship to the DNS seems to be that they happen to have a structure
> that is similar to the FQDN.
>
> Anyways, I have been following this discussion now for a while. It seems
> to me that the discussion is not really converging. I would blame it at
> least partly on RFC6761. Though, RFC6761 isn't that old, it was written in
> a time before the new gTLD round was ongoing.
>
> Rather than discussing the individual strings, maybe we should consider to
> discuss the principles under which TLDs can be reserved for special use
> and consider a re-spin or an update to RFC6761.
>
> Cheers,
>
> Jonne.
>
> >
> >> Joe
> >>
> >> [1] https://metrics.torproject.org
> >> [2] =
> >>
> >>
> http://www.huffingtonpost.co.uk/2012/07/02/stephen-hawking-time-travel_n_
> >>1=
> >> 643488.html
> >> [3] http://en.wikipedia.org/wiki/Tor_(anonymity_network)#History
> >--
> >Mark Andrews, ISC
> >1 Seymour St., Dundas Valley, NSW 2117, Australia
> >PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >_______________________________________________
> >DNSOP mailing list
> >DNSOP@ietf.org
> >https://www.ietf.org/mailman/listinfo/dnsop
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--047d7b33d592b906e304f1886e17
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am not personally convinced by &quot;there are too many =
people committed&quot; arguments. I never have been, and I think the chilli=
ng effect of this has been seen time and again.<div><br></div><div>There ha=
s always been &quot;too many people&quot; doing things. Claiming the dead h=
and of history prevents us from changing course or deploying new things is =
just wrong.</div>
<div><br></div><div>1 create onion.something.else and mark .onion as suitab=
le for future use under gTLD, if not now</div><div>2 release new TOR code a=
nd declare sunset period</div><div>3 wait for sunset period</div><div>4 sto=
p blocking release of .onion</div>
<div><br></div><div>We don&#39;t expect people to use rlogin or rsh any mor=
e. Protocols move on.</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Tue, Feb 4, 2014 at 7:54 AM,  <span dir=3D"ltr">&lt;=
<a href=3D"mailto:jonne.soininen@broadcom.com" target=3D"_blank">jonne.soin=
inen@broadcom.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi everybody,<br>
<br>
(just for full closure - I&#39;m the IETF technical liaison to the ICANN<br=
>
board, but taking that hat off here)<br>
<div><div class=3D"h5"><br>
<br>
On 2/3/14 11:23 PM, &quot;Mark Andrews&quot; &lt;<a href=3D"mailto:marka@is=
c.org">marka@isc.org</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt;In message &lt;<a href=3D"mailto:ACF06352-98E5-4368-A8C9-5AB50783C2D3@h=
opcount.ca">ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca</a>&gt;, Joe A=
bley<br>
&gt;writes:<br>
&gt;&gt;<br>
&gt;&gt; On 2014-02-03, at 11:15, Paul Hoffman &lt;<a href=3D"mailto:paul.h=
offman@vpnc.org">paul.hoffman@vpnc.org</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; &gt; On Feb 3, 2014, at 7:19 AM, Stephane Bortzmeyer &lt;<a href=
=3D"mailto:bortzmeyer@nic.fr">bortzmeyer@nic.fr</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &quot;squatted&quot; is not a bad word here. In the physi=
cal world, squatters<br>
&gt;&gt; &gt;&gt; are often people who do not have the money to rent a home=
, because<br>
&gt;&gt; &gt;&gt; some rich people put the price of the housing too high. H=
ere, you<br>
&gt;&gt;will<br>
&gt;&gt; &gt;&gt; have trouble convincing the users of Tor or Namecoin that=
 it is right<br>
&gt;&gt; &gt;&gt; to pay 185 000 $ for a TLD and that, if they cannot affor=
d it, they<br>
&gt;&gt; &gt;&gt; have to stay in the slums.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; [End of political rant, sorry]<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Your political rant is, however, off-base. Assume for the mom=
ent that<br>
&gt;&gt; &gt; the Tor folks had registered <a href=3D"http://oniontld.fr" t=
arget=3D"_blank">oniontld.fr</a> for a relatively small<br>
&gt;&gt;amount of<br>
&gt;&gt; &gt; money. It could have all of the attributes of .onion: you cou=
ld<br>
&gt;&gt;hard-wire<br>
&gt;&gt; &gt; it into local resolvers, some requests for it would leak to t=
he DNS<br>
&gt;&gt;and<br>
&gt;&gt; &gt; therefore possibly be trackable, and so on. For the purposes =
given in<br>
&gt;&gt; &gt; draft-grothoff-iesg-special-use-p2p-names, unsquatted FQDNs w=
ould work<br>
&gt;&gt; &gt; just as well as squatted TLDs.<br>
&gt;&gt;<br>
&gt;&gt; I made that point somewhat earlier (but my example was <a href=3D"=
http://onion.eff.org" target=3D"_blank">onion.eff.org</a> or<br>
&gt;&gt; something).<br>
&gt;&gt;<br>
&gt;&gt; The reasonable response to my instance of that observation was tha=
t<br>
&gt;&gt; there&#39;s a significant deployed base of users already making us=
e of<br>
&gt;&gt;.onion<br>
&gt;&gt; [1], and we don&#39;t have a time machine that we&#39;re aware of =
[2] to allow<br>
&gt;&gt; that to be fixed.<br>
&gt;&gt;<br>
&gt;&gt; Despite the enduring (and endearing, perhaps) optimism that the ne=
w gTLD<br>
&gt;&gt; programme would eventually bear fruit, I don&#39;t think it&#39;s =
unreasonable<br>
&gt;&gt;to<br>
&gt;&gt; think that in 2002 [3] a new gTLD wasn&#39;t really a practical op=
tion to<br>
&gt;&gt; choose not to take.<br>
&gt;&gt;<br>
&gt;&gt; So squatting doesn&#39;t sound right to me.<br>
&gt;<br>
&gt;They choose to use a TLD. =A0There were plenty of people saying &quot;D=
o<br>
&gt;NOT use a TLD for your private namespace, use a namespace you own&quot;=
<br>
&gt;in 2002 whether it was for a protocol or a internal network.<br>
&gt;<br>
&gt;For $20 a year or less they could have registered a name in just<br>
&gt;about any TLD and avoided the issue.<br>
<br>
</div></div>I think we have to distinguish here between the &quot;new squat=
ters&quot; and the<br>
&quot;old squatters&quot; and the reasons for &quot;squatting&quot;. For in=
stance in corp and<br>
home, the installed base seems to be quite large. It comes from equipment<b=
r>
and hardware that might not be easily replaceable and not really under a<br=
>
single organization&#39;s control. You cannot change that and ignoring it<b=
r>
might cause harm for the Internet.<br>
<br>
The new technologies (gnu/onion/...) seem to be different. First of all,<br=
>
they don&#39;t use DNS but something else. Therefore, there should be no<br=
>
collisions. It seems more that delegating them to the DNS would harm those<=
br>
technologies rather than DNS or Internet getting harmed. The only<br>
relationship to the DNS seems to be that they happen to have a structure<br=
>
that is similar to the FQDN.<br>
<br>
Anyways, I have been following this discussion now for a while. It seems<br=
>
to me that the discussion is not really converging. I would blame it at<br>
least partly on RFC6761. Though, RFC6761 isn&#39;t that old, it was written=
 in<br>
a time before the new gTLD round was ongoing.<br>
<br>
Rather than discussing the individual strings, maybe we should consider to<=
br>
discuss the principles under which TLDs can be reserved for special use<br>
and consider a re-spin or an update to RFC6761.<br>
<br>
Cheers,<br>
<br>
Jonne.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt;<br>
&gt;&gt; Joe<br>
&gt;&gt;<br>
&gt;&gt; [1] <a href=3D"https://metrics.torproject.org" target=3D"_blank">h=
ttps://metrics.torproject.org</a><br>
&gt;&gt; [2] =3D<br>
&gt;&gt;<br>
&gt;&gt;<a href=3D"http://www.huffingtonpost.co.uk/2012/07/02/stephen-hawki=
ng-time-travel_n_" target=3D"_blank">http://www.huffingtonpost.co.uk/2012/0=
7/02/stephen-hawking-time-travel_n_</a><br>
&gt;&gt;1=3D<br>
&gt;&gt; 643488.html<br>
&gt;&gt; [3] <a href=3D"http://en.wikipedia.org/wiki/Tor_(anonymity_network=
)#History" target=3D"_blank">http://en.wikipedia.org/wiki/Tor_(anonymity_ne=
twork)#History</a><br>
&gt;--<br>
&gt;Mark Andrews, ISC<br>
&gt;1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
&gt;PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+=
61 2 9871 4742</a> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 INTERNET: <a href=3D"mai=
lto:marka@isc.org">marka@isc.org</a><br>
&gt;_______________________________________________<br>
&gt;DNSOP mailing list<br>
&gt;<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/dnsop</a><br>
<br>
_______________________________________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dnsop</a><br>
</div></div></blockquote></div><br></div>

--047d7b33d592b906e304f1886e17--

From Ted.Lemon@nominum.com  Mon Feb  3 15:17:51 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E678B1A0267 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 15:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id or0Jng_mQ5Wh for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 15:17:50 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2007E1A0265 for <dnsop@ietf.org>; Mon,  3 Feb 2014 15:17:49 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUvAjntvEguz3P/lIw/KB1G0ADHypvCI5@postini.com; Mon, 03 Feb 2014 15:17:50 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BBB6F1B82FC for <dnsop@ietf.org>; Mon,  3 Feb 2014 15:17:49 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 9496A190052; Mon,  3 Feb 2014 15:17:49 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Feb 2014 15:17:49 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com>
Date: Mon, 3 Feb 2014 18:17:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 23:17:52 -0000

On Feb 3, 2014, at 5:56 PM, George Michaelson <ggm@algebras.org> wrote:
> We don't expect people to use rlogin or rsh any more. Protocols move =
on.

RSH was horrifically broken.   .onion makes a few IETFers feel a little =
dirty.   It's not the same situation.


From ggm@algebras.org  Mon Feb  3 15:27:11 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A139C1A0291 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 15:27:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsVg_vCB8TTv for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 15:27:09 -0800 (PST)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id BA1A51A0268 for <dnsop@ietf.org>; Mon,  3 Feb 2014 15:27:09 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id ld10so7759101pab.10 for <dnsop@ietf.org>; Mon, 03 Feb 2014 15:27:09 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3t8AaiFwr/nPMZlWJHg8/I4gcq5Cq70kIs0eeZXR2CA=; b=AUSk3IuGzXyhndPBP+5XobVyalhpudeQEjeER54/YojT4qlmrcynfIA3as2BzPwrmJ O77SzIbH1Amuoa8Pz9rFcfIxCr70xBFqKIUNOufWz+IEy4V51pS4NgEQxLy8f5Yhxvv7 rPsY+/nlWy3/+Rsk81QuwFJuYfrj1X2jnP/TB7ZlCnSH2pY/pxY5TTI6FvRv8j1Fz8OZ gbSEg8Or2gYFdsehSfhguRDWs0/rBYUv86lFSrFp16pyfyQpuEDB+4ZzG7ybVY5DlCaS rO1xktjGiBe3xa93wcLD95SVmgrAnPKqv72nK0ql7HidA+kTyMe6poKzehs0+CfhA3LJ zJdg==
X-Gm-Message-State: ALoCoQla89Cnb1M4CgBP49Bq5z+8eh/ugo7OX8WSYnjlg1/tjkcONHqp5C0+wSzPHKeYwgVBRe2r
MIME-Version: 1.0
X-Received: by 10.66.124.230 with SMTP id ml6mr36089765pab.29.1391470029659; Mon, 03 Feb 2014 15:27:09 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Mon, 3 Feb 2014 15:27:09 -0800 (PST)
X-Originating-IP: [2001:44b8:2136:8e00:8cae:7195:4e13:8720]
In-Reply-To: <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com>
Date: Tue, 4 Feb 2014 09:27:09 +1000
Message-ID: <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11343f4ed576e704f188dca2
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 23:27:11 -0000

--001a11343f4ed576e704f188dca2
Content-Type: text/plain; charset=ISO-8859-1

Its a scaling question. Please don't sidetrack into distaste, its the
question of preventing progress by saying "too many" when in fact, its
tractable, and its software.

.onion is an eminently tractable problem. Arguing otherwise is to argue the
current .onion codebase dependency cannot move, therefore any future CVE
against TOR cannot be fixed, therefore further code development on TOR is
fruitless, therefore lets all stop coding. Breathing even.

This IETF mantra of "too many to change" is wrong. We need to stop invoking
the dead weight of the past over future events.

--001a11343f4ed576e704f188dca2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">Its a scaling question. Please =
don&#39;t sidetrack into distaste, its the question of preventing progress =
by saying &quot;too many&quot; when in fact, its tractable, and its softwar=
e.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">.onion is a=
n eminently tractable problem. Arguing otherwise is to argue the current .o=
nion codebase dependency cannot move, therefore any future CVE against TOR =
cannot be fixed, therefore further code development on TOR is fruitless, th=
erefore lets all stop coding. Breathing even.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">This IETF m=
antra of &quot;too many to change&quot; is wrong. We need to stop invoking =
the dead weight of the past over future events.</div></div>

--001a11343f4ed576e704f188dca2--

From johnl@iecc.com  Mon Feb  3 16:01:37 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7081A026A for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 16:01:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkdgLlDCWHJ0 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 16:01:36 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id B28801A02A5 for <dnsop@ietf.org>; Mon,  3 Feb 2014 16:01:35 -0800 (PST)
Received: (qmail 83872 invoked from network); 4 Feb 2014 00:01:33 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Feb 2014 00:01:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f02ddd.xn--3zv.k1402; i=johnl@user.iecc.com; bh=fqXlZze7D5Z5CAZ3PyqgKl3gbPxghQ+CpcjQvmm/b38=; b=kZcOF6bwIY8vhH7gfmnc7H4BzXqMFFHy02mLa2L2ZbhkUZgxUoFujRUOZHs/eWFFJnGl8OXpz/lzGBo1L8DA++ydQHP9i1b00nipUoRQhDBBXZWcdet48Tj4cBH7brCBnf5omQN2lzlt3ZU3wn5g5Sx1WJkltTtIpUgoPxpZ2FnriaAYwNwFeKDqABdteddjvkZhgNXMXqrcrAaQgoYuk6Qd4yvlQoGMlflbJPiYVfXYoEiNQ78h+dZ3uC3QkD1N
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f02ddd.xn--3zv.k1402; bh=fqXlZze7D5Z5CAZ3PyqgKl3gbPxghQ+CpcjQvmm/b38=; b=bNS2X0XBlmfvYRPRQyEuIXLP2kfVRcwig6UwXb/pjEAuoJuzB6o95lg9yfz3FYlkFhlJjtmCGlhfJKjcGASxeHr+tXPORwDwOm9Y/EtDYhTotOl/cQxBXR6BC7VQ5QzkAJ5eNeSFxDK1VYNImFZzRfyu1pEvAWX+MStaGK6lhvVQBRBrQRZZsqiiLCtLo6NoyDrwWPh5pn0/qsaX4BmNK1Ohem3cs905DjaKR0q9w8whJa8N0KYi1tyd8T2cc7tm
Date: 4 Feb 2014 00:01:10 -0000
Message-ID: <20140204000110.16894.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20140203221506.GO13520@mx1.yitter.info>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: ajs@anvilwalrusden.com
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 00:01:37 -0000

>> This is a useless discussion.   Recriminations do not change the past.
>
>True, but effectively what you're saying is that this special-use
>registry could be used by anyone who's prepared to [squat|use a TLD
>without registering it] in the right ways to get around the ICANN
>allocation procedures.  I think that's spelled "moral hazard" in
>economics.

Not really, because what you get by squatting on a TLD is nothing like
what you get if you rent it from ICANN.  Squats are all local
(mis-)use, with names only leaking onto the public Internet by
accident. 

It also seems implicit in this document that the plan is only to add
names to the registry if there is existing evidence that they're
significantly squatted, by which time it's too late anyway.

R's,
John

From ajs@anvilwalrusden.com  Mon Feb  3 16:11:41 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9107B1A02A3 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 16:11:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOJVszUwO1s5 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 16:11:40 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 8BACF1A026A for <dnsop@ietf.org>; Mon,  3 Feb 2014 16:11:40 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 14D568A031 for <dnsop@ietf.org>; Tue,  4 Feb 2014 00:11:40 +0000 (UTC)
Date: Mon, 3 Feb 2014 19:11:37 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140204001137.GA53095@mx1.yitter.info>
References: <20140203221506.GO13520@mx1.yitter.info> <20140204000110.16894.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140204000110.16894.qmail@joyce.lan>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 00:11:41 -0000

On Tue, Feb 04, 2014 at 12:01:10AM -0000, John Levine wrote:
> Not really, because what you get by squatting on a TLD is nothing like
> what you get if you rent it from ICANN.  Squats are all local
> (mis-)use, with names only leaking onto the public Internet by
> accident. 

That actually depends on what you're doing with the name.  In the case
of the names discussed in the chapin draft, that is true.  It's less
true in all cases.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Ted.Lemon@nominum.com  Mon Feb  3 17:09:05 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F251A02CF for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:09:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fggU6d9PVZb2 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:09:01 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 683AD1A02DC for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:09:01 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUvA9raUlGh9nhVEUlzCnn1zEE348HUC+@postini.com; Mon, 03 Feb 2014 17:09:01 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0A7F61B82FC for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:09:01 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id E605D190052; Mon,  3 Feb 2014 17:09:00 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Feb 2014 17:09:00 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com>
Date: Mon, 3 Feb 2014 20:08:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 01:09:05 -0000

On Feb 3, 2014, at 6:27 PM, George Michaelson <ggm@algebras.org> wrote:
> .onion is an eminently tractable problem. Arguing otherwise is to =
argue the current .onion codebase dependency cannot move, therefore any =
future CVE against TOR cannot be fixed, therefore further code =
development on TOR is fruitless, therefore lets all stop coding. =
Breathing even.\

What I'm saying is that it's an obnoxious thing to do, and there's no =
good reason to do it.   We really ought to have a good reason to demand =
that an organization over which we exert no control at all make a =
significant and incompatible change to their deployed code purely on the =
basis that some of us don't like what they did.   We need a better =
reason than that, and thus far none has been stated.


From ggm@algebras.org  Mon Feb  3 17:19:08 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5741A02DE for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z8UKanIiD3zO for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:18:59 -0800 (PST)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF2C1A02D0 for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:18:59 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id ld10so7824568pab.38 for <dnsop@ietf.org>; Mon, 03 Feb 2014 17:18:59 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=37U7B3DDlN7MUm1p+DatlaQlvNbJ2SRkX1F7D0VEENI=; b=Oabv2cE3yCEw7YTCf5HF+qXKaoIYUI6zkiooQn4j2BSDbiWVO58e6LyytWz44gaP+d UxdwZpdMUPWKFH1okwsDO6ar7HPZ3xWZ1rGPITmmT3E3ybACQ8NxEqTqJlqxY5KxNQC9 ursHpA7V6kjprrPTCh1WVLNrOJIxljP2rXs3+58c9WZkQ/WSMbgF5ePeNSFpO4CVipP7 yGzpGYbNxwgPXE4z77BTeKw6CV7htc3cUbmVIhHXYW8xEyViKlBQAzbWsMLr0M9a2vvU aGd0/Y74bNzZSaX0esX8upNw4jqFl+Nb8FjDbC6lJDZ5P/+6sXUPKwH1jk8fvP6J7T8X BP7Q==
X-Gm-Message-State: ALoCoQkMYxiZRyJwVMJgnF3NHeKWpZ00aR9muIlksCMP9nM1VlI6X2Wqutn68/NHb8K/9Jxi4ri7
MIME-Version: 1.0
X-Received: by 10.68.231.35 with SMTP id td3mr40352443pbc.137.1391476739450; Mon, 03 Feb 2014 17:18:59 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Mon, 3 Feb 2014 17:18:59 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:302e:dba0:2280:4927]
In-Reply-To: <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com>
Date: Tue, 4 Feb 2014 11:18:59 +1000
Message-ID: <CAKr6gn2BFxuy28Wo0ZB88W0-rq8PuDO+ZTjob+Dgp7MvSw2yWQ@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7b33d592c4c3a204f18a6cd4
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 01:19:08 -0000

--047d7b33d592c4c3a204f18a6cd4
Content-Type: text/plain; charset=ISO-8859-1

ok. I see where you are. I can be there, somewhat. Thats not a bad position
Ted.

So my sense of this is "you were advised not to do this, and you didn't
respect the process" for some value of "you"

What I don't like about that is a schoolmarm/punitive voice. But it has the
qualities. Tragedies of the commons don't just take one form, and having
s/w develop a dependency on name/locator properties with high visibility,
without considering the commons, is (in my opinion) a tragedy.

I'm not inherently arguing for ICANN process, or even the DNS. I think a
mature sense of the locator/id separation qualities of any endeavour, and
the arguments around naming, lead you to caution in seizing names in any
space.

IETF is constantly advised by w3c people (mark nottingham?) to be mindful
of the URI/URL concept, and not to over-egg stipulations on what is
meaningful in that space. And I think by and large, thats right.

So is what the TOR people did usurping .onion respectful of process? What
do you do, when process isn't respected?

-G



On Tue, Feb 4, 2014 at 11:08 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 3, 2014, at 6:27 PM, George Michaelson <ggm@algebras.org> wrote:
> > .onion is an eminently tractable problem. Arguing otherwise is to argue
> the current .onion codebase dependency cannot move, therefore any future
> CVE against TOR cannot be fixed, therefore further code development on TOR
> is fruitless, therefore lets all stop coding. Breathing even.\
>
> What I'm saying is that it's an obnoxious thing to do, and there's no good
> reason to do it.   We really ought to have a good reason to demand that an
> organization over which we exert no control at all make a significant and
> incompatible change to their deployed code purely on the basis that some of
> us don't like what they did.   We need a better reason than that, and thus
> far none has been stated.
>
>

--047d7b33d592c4c3a204f18a6cd4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">ok. I see where you are. I can be there, somewhat. Thats n=
ot a bad position Ted.<div><br></div><div>So my sense of this is &quot;you =
were advised not to do this, and you didn&#39;t respect the process&quot; f=
or some value of &quot;you&quot;</div>
<div><br></div><div>What I don&#39;t like about that is a schoolmarm/puniti=
ve voice. But it has the qualities. Tragedies of the commons don&#39;t just=
 take one form, and having s/w develop a dependency on name/locator propert=
ies with high visibility, without considering the commons, is (in my opinio=
n) a tragedy.</div>
<div><br></div><div>I&#39;m not inherently arguing for ICANN process, or ev=
en the DNS. I think a mature sense of the locator/id separation qualities o=
f any endeavour, and the arguments around naming, lead you to caution in se=
izing names in any space.</div>
<div><br></div><div>IETF is constantly advised by w3c people (mark nottingh=
am?) to be mindful of the URI/URL concept, and not to over-egg stipulations=
 on what is meaningful in that space. And I think by and large, thats right=
.</div>
<div><br>So is what the TOR people did usurping .onion respectful of proces=
s? What do you do, when process isn&#39;t respected?</div><div><br></div><d=
iv>-G</div><div><br></div></div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">
On Tue, Feb 4, 2014 at 11:08 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D=
"mailto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Feb 3, 2014, at 6:27 PM, George Michaelson &lt;<a href=3D"mailto:ggm@alg=
ebras.org">ggm@algebras.org</a>&gt; wrote:<br>
&gt; .onion is an eminently tractable problem. Arguing otherwise is to argu=
e the current .onion codebase dependency cannot move, therefore any future =
CVE against TOR cannot be fixed, therefore further code development on TOR =
is fruitless, therefore lets all stop coding. Breathing even.\<br>

<br>
What I&#39;m saying is that it&#39;s an obnoxious thing to do, and there&#3=
9;s no good reason to do it. =A0 We really ought to have a good reason to d=
emand that an organization over which we exert no control at all make a sig=
nificant and incompatible change to their deployed code purely on the basis=
 that some of us don&#39;t like what they did. =A0 We need a better reason =
than that, and thus far none has been stated.<br>

<br>
</blockquote></div><br></div>

--047d7b33d592c4c3a204f18a6cd4--

From ajs@anvilwalrusden.com  Mon Feb  3 17:21:52 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4391A02D7 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DsNzZm2iHYJD for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:21:51 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 128321A02DC for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:21:51 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B2FD68A031 for <dnsop@ietf.org>; Tue,  4 Feb 2014 01:21:50 +0000 (UTC)
Date: Mon, 3 Feb 2014 20:21:48 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140204012148.GE16180@mx1.yitter.info>
References: <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 01:21:52 -0000

On Mon, Feb 03, 2014 at 08:08:59PM -0500, Ted Lemon wrote:
> 
> purely on the basis that some of us don't like what they did.  We
> need a better reason than that, and thus far none has been stated.

In the particular case of .onion, I'm not sure I agree none has been
stated.  But let me try again:

    If you want to use a name in DNS protocol slots, then you need a DNS
    name.  You didn't get a DNS name, and instead you used a label
    that wasn't under your control.  That's been against the rules in the
    DNS since forever.  Now you want to short-circuit the allocation
    mechanism.  But we have an allocation mechanism for this.  In the
    normal case, you apply to ICANN.  In an unusual case where the
    protocol depends on this, then you can use this special-use
    registry.  So you need to show that your protocol needs to depend
    on this special-use label, and then we can register it under the
    special use mechanism.  Otherwise go to ICANN.

What we ought to be arguing about, in effect, is precisely why this
needs a special-names registration.  Now, _maybe_ there is an argument
that this is a DNS-looking series of labels but it never goes into the
DNS namespace (that's what I've heard once).  In that case, there
might be an argument.  ("Put this in the default local zones, always
NXDOMAIN, because we want to protect the DNS.")  Maybe the argument is
instead that sometimes these names are handed to DNS resolvers and are
supposed to resolve.  In _that_ case, it seems to me that the "this is
a DNS name" consideration is also pretty high.  I'm unsure we've had
clear and consistent arguments about this for each of the cases.

In the chapin draft, the argument is different, and it appears to be
purely a local-resolution-only one -- that is, always "protection of
the DNS" because of de facto resolution and security decisions
deployed on the Net.  I haven't read it closely enough to decide
whether this is true for every label in the list.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Ted.Lemon@nominum.com  Mon Feb  3 17:27:37 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E9B1A02D8 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsXVtd5pHoY7 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:27:35 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id AEB451A02D2 for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:27:35 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUvBCB5WkftF/IM56ng8XTLpMn6MgE+7C@postini.com; Mon, 03 Feb 2014 17:27:35 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 8E2991B82F7 for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:27:35 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 876C9190052; Mon,  3 Feb 2014 17:27:35 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Feb 2014 17:27:35 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAKr6gn2BFxuy28Wo0ZB88W0-rq8PuDO+ZTjob+Dgp7MvSw2yWQ@mail.gmail.com>
Date: Mon, 3 Feb 2014 20:27:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <3B2A573E-F030-4508-B8DF-87EBB77F878C@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <CAKr6gn2BFxuy28Wo0ZB88W0-rq8PuDO+ZTjob+Dgp7MvSw2yWQ@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 01:27:37 -0000

On Feb 3, 2014, at 8:18 PM, George Michaelson <ggm@algebras.org> wrote:
> So is what the TOR people did usurping .onion respectful of process? =
What do you do, when process isn't respected?

Until recently there wasn't a process, and they seem to have tried to =
follow the process that now exists, in a pretty reasonable timeframe.   =
You can definitely ask them for more documentation.   If your ask is =
reasonable, and seems beneficial, there's a decent chance they'll do it. =
  But if your ask is unreasonable, you'll get ignored, and rightly so.   =
I think asking them to change .onion without a solid reason (not "you =
didn't follow process") is in the latter category.


From Ted.Lemon@nominum.com  Mon Feb  3 17:32:08 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9721A02D8 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFWMjuZ8tZBJ for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:32:07 -0800 (PST)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 55CAF1A02D2 for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:32:07 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUvBDF+QVabgeRFhvSK1mdobr+zTMFFHT@postini.com; Mon, 03 Feb 2014 17:32:07 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id DC1AB1B82F7 for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:32:06 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D18EA190052; Mon,  3 Feb 2014 17:32:06 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Feb 2014 17:32:06 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140204012148.GE16180@mx1.yitter.info>
Date: Mon, 3 Feb 2014 20:32:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <1397C673-86CD-40A1-9055-17B3B74FAC80@nominum.com>
References: <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 01:32:08 -0000

On Feb 3, 2014, at 8:21 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
>    If you want to use a name in DNS protocol slots, then you need a =
DNS
>    name.  You didn't get a DNS name, and instead you used a label
>    that wasn't under your control.

This is the "you didn't follow process" argument.   But they couldn't =
have followed process=97there was no realistic process for allocating a =
special-use TLD before 6761 was published.   So this amounts to an =
emotional appeal, which isn't much of a justification for the change you =
are demanding of them.

I absolutely get why you are saying this.   It's a pretty good emotional =
appeal.   But we shouldn't act on it, because that's all it is.   We =
have a process, and they are following it.   We should see it through.


From jonne.soininen@broadcom.com  Mon Feb  3 17:45:19 2014
Return-Path: <jonne.soininen@broadcom.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 203001A02F6 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:45:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lts2xtt1RDVz for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:45:14 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.109]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB1C1A02F3 for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:45:14 -0800 (PST)
Received: from [193.109.254.147:28996] by server-5.bemta-14.messagelabs.com id FE/B4-16688-92640F25; Tue, 04 Feb 2014 01:45:13 +0000
X-Env-Sender: jonne.soininen@broadcom.com
X-Msg-Ref: server-10.tower-27.messagelabs.com!1391478312!1773254!1
X-Originating-IP: [213.174.82.10]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10553 invoked from network); 4 Feb 2014 01:45:13 -0000
Received: from renexfe01.roe2.renesasmobile.com (HELO renexfe01.roe2.renesasmobile.com) (213.174.82.10) by server-10.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 4 Feb 2014 01:45:13 -0000
Received: from RENEXMB01.roe2.renesasmobile.com ([fe80::e58a:2b9f:54fe:ff5]) by renexfe01.roe2.renesasmobile.com ([fe80::ec94:bbb3:68e:a94a%18]) with mapi id 14.03.0174.001; Tue, 4 Feb 2014 03:45:12 +0200
From: <jonne.soininen@broadcom.com>
To: <ajs@anvilwalrusden.com>, <dnsop@ietf.org>
Thread-Topic: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
Thread-Index: AQHPIUeNwYLSV6MX4ki2zpkW9UfcIZqkUumA
Date: Tue, 4 Feb 2014 01:45:11 +0000
Message-ID: <CF160FB8.1983E7%jonne.soininen@renesasmobile.com>
References: <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info>
In-Reply-To: <20140204012148.GE16180@mx1.yitter.info>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.22.172]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9E06B2050B99F249A1ED13C9F92FABC2@renesasmobile.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 01:45:19 -0000

Hi Andrew,


On 2/4/14 3:21 AM, "Andrew Sullivan" <ajs@anvilwalrusden.com> wrote:

>On Mon, Feb 03, 2014 at 08:08:59PM -0500, Ted Lemon wrote:
>>=20
>> purely on the basis that some of us don't like what they did.  We
>> need a better reason than that, and thus far none has been stated.
>
>In the particular case of .onion, I'm not sure I agree none has been
>stated.  But let me try again:
>
>    If you want to use a name in DNS protocol slots, then you need a DNS
>    name.  You didn't get a DNS name, and instead you used a label
>    that wasn't under your control.  That's been against the rules in the
>    DNS since forever.  Now you want to short-circuit the allocation
>    mechanism.  But we have an allocation mechanism for this.  In the
>    normal case, you apply to ICANN.  In an unusual case where the
>    protocol depends on this, then you can use this special-use
>    registry.  So you need to show that your protocol needs to depend
>    on this special-use label, and then we can register it under the
>    special use mechanism.  Otherwise go to ICANN.

In addition, I would say that perhaps the current rules are targeted
towards DNS (or extensions of DNS as mDNS could be considered). These new
protocols are something else. They are not DNS and not even specified in
the IETF. They have taken a design choice where they look like DNS and
therefore, may clash with the DNS namespace. The aspect of reserve these
or you'll break the Internet (in some definition of break) isn't really
valid. It is more that you interfere with the functionality of these
protocols, which is a different magnitude of a problem. Perhaps, it is a
different problem all together.

>
>What we ought to be arguing about, in effect, is precisely why this
>needs a special-names registration.  Now, _maybe_ there is an argument
>that this is a DNS-looking series of labels but it never goes into the
>DNS namespace (that's what I've heard once).  In that case, there
>might be an argument.  ("Put this in the default local zones, always
>NXDOMAIN, because we want to protect the DNS.")  Maybe the argument is
>instead that sometimes these names are handed to DNS resolvers and are
>supposed to resolve.  In _that_ case, it seems to me that the "this is
>a DNS name" consideration is also pretty high.  I'm unsure we've had
>clear and consistent arguments about this for each of the cases.

Right. From there comes the question that if this is a way to work around
the process we have in the Internet now - you want a TLD you go to ICANN.
Regardless of what people think of that process, this is the process we
have created already a long time ago and it has been operational since the
beginning of ICANN. There is no other process to get TLDs.
=20
>
>In the chapin draft, the argument is different, and it appears to be
>purely a local-resolution-only one -- that is, always "protection of
>the DNS" because of de facto resolution and security decisions
>deployed on the Net.  I haven't read it closely enough to decide
>whether this is true for every label in the list.

Completely agree. The Chapin draft is trying to protect the Internet by
reserving names that for various reasons have collisions in the Internet.
It would be nice to remove these collisions, but it seems to be currently
impossible. So, this is a way to deal with a real problem in the Internet
we have today and avoid that these names would be delegated and cause
breakage in the Internet.

I also believe these two cases should be considered very separately.

Cheers,

Jonne.
>
>Best,
>
>A
>
>--=20
>Andrew Sullivan
>ajs@anvilwalrusden.com
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop


From ajs@anvilwalrusden.com  Mon Feb  3 17:50:33 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 657851A0341 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:50:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eD7ASGmE25Uv for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 17:50:29 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 716241A02F5 for <dnsop@ietf.org>; Mon,  3 Feb 2014 17:50:29 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id C87588A031 for <dnsop@ietf.org>; Tue,  4 Feb 2014 01:50:28 +0000 (UTC)
Date: Mon, 3 Feb 2014 20:50:27 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140204015026.GC53095@mx1.yitter.info>
References: <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info> <1397C673-86CD-40A1-9055-17B3B74FAC80@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1397C673-86CD-40A1-9055-17B3B74FAC80@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 01:50:33 -0000

On Mon, Feb 03, 2014 at 08:32:04PM -0500, Ted Lemon wrote:

> This is the "you didn't follow process" argument.  But they couldn't
> have followed processâ€”there was no realistic process for allocating
> a special-use TLD before 6761 was published.  So this amounts to an
> emotional appeal, which isn't much of a justification for the change
> you are demanding of them.

The DNS works -- has _always worked_ -- on the principle that you
register your names if you want to use them on the Internet.  This is
just as true of top level names as of anything else.  It is true that
when .onion (to stick to our example) was adopted, there wasn't a
mechanism other than going to ICANN to get a TLD.  (There certainly
was a mechanism via the ICANN route at the time.)  I'm not sure how to
interpret this part of your argument except, "If the mechanism for
what you want to do doesn't exist or is too inconvenient, just do
whatever you want."  That has interesting implications for the IANA
function.

Moreover, 6761 is _perfectly clear_ that you're supposed to show that
your use actually requires a TLD.  I still don't see why .onion.arpa
would've been a bad choice.  Failing to answer that question really
_would_ be not following the process.

Finally, mine at least is not just an emotional argument; see above,
variations of which I have repeated.  Indeed, whether you intend it or
not, your mails appear to me to be rather emotionally charged and
dismissive of any pointy question or suggestion that the interests of
the rest of the DNS (including the root management regime) need to be
taken into consideration as well.  It seems to me that you could read
with a more generous application of the principle of charity.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From johnl@iecc.com  Mon Feb  3 22:39:35 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE2FE1A0373 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 22:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAVzDoof5VQm for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 22:39:34 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDE81A0371 for <dnsop@ietf.org>; Mon,  3 Feb 2014 22:39:34 -0800 (PST)
Received: (qmail 33453 invoked from network); 4 Feb 2014 06:39:33 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Feb 2014 06:39:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f08b25.xn--3zv.k1402; i=johnl@user.iecc.com; bh=X7bnBTmokpDeTn2VolD357FKIUCiFe6eAJ1DXnMtAXc=; b=ICXgrTCF8kCcd8b5VD9ooOMSWFjsdeQCgVsM8zy5LRhNjhrwL7EeJanC9RPJQF9AVfyDUcHwsCKZf/xMZItRahu7YihVa5HXGGg6rxIO2Uua1Bqhyl4OLPpCFEkgXCTdaBC/gm22LWIBOqnu3wh0KB0kj0Oysj6yO50qu0UIuNF95BYhkGO3EqHpYNQr3s3ljkD2tuXgwVbBdz1b1yck0ganSNYXeH0YfgYcjp5CifNpjlDnqP5dkXdfm73gzCwe
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f08b25.xn--3zv.k1402; bh=X7bnBTmokpDeTn2VolD357FKIUCiFe6eAJ1DXnMtAXc=; b=jSYvIm9HhinxEMQXA3aO0ogeiOyR+FXNX3MN3nstTqlBq5ZCcYRHqChHqkBlx1sSZb5e4S04tsEz0GEmoSswYiC4qcXaFC0tVcR0AYodJrYdrgPgkASerKqD+bfHYeI2I5M/SViSFhr3etYgR2k5qRZ3D+W47AO7KG6rKl9PWP9/eIPkVCQwQPlxL68+VI+5NFO6Z0mlMFErvWZtI+tkZ0U7CQx/4cbGmQ3LHEi/ig10YaSfJWRLbsTANfR6344J
Date: 4 Feb 2014 06:39:11 -0000
Message-ID: <20140204063911.55905.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20140204001137.GA53095@mx1.yitter.info>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: ajs@anvilwalrusden.com
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 06:39:36 -0000

>> Not really, because what you get by squatting on a TLD is nothing like
>> what you get if you rent it from ICANN.  Squats are all local
>> (mis-)use, with names only leaking onto the public Internet by
>> accident. 

>That actually depends on what you're doing with the name.  In the case
>of the names discussed in the chapin draft, that is true.  It's less
>true in all cases.

I think that all we're talking about here is reserving domain names
and saying that they should never resolve on the global Internet.

If the IETF finds good technical reasons to reserve some other name
for some other reason, e.g., peer to peer exchange of crypto
credentials or something, so what?  It's one less name for ICANN to
sell but I don't see why that would be our problem.

I suppose the situation with .onion is slightly different, but in
concept it's not all that different from .arpa.  It's a domain that
people are using for special technical purposes, so it's not available
for normal delegation.  The only ICANN delegated name that's the least
bit interesting is .TEL, an attempt to create an online directory
using NAPTR that is a failure, so they're unlikely to do any more.

R's,
John

PS: Because I am not a good person, you can reply to me at
jl@m.183.57.64.in-addr.arpa.  Or, of course, johnl@taughannock.tel.


From paf@frobbit.se  Mon Feb  3 22:43:43 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8891A0374 for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 22:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.786
X-Spam-Level: 
X-Spam-Status: No, score=-1.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fo3ac4yjrdEj for <dnsop@ietfa.amsl.com>; Mon,  3 Feb 2014 22:43:41 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3E01A0372 for <dnsop@ietf.org>; Mon,  3 Feb 2014 22:43:40 -0800 (PST)
Received: from ix-2.local (s83-179-7-188.cust.tele2.se [83.179.7.188]) by mail.frobbit.se (Postfix) with ESMTPSA id A817D20046; Tue,  4 Feb 2014 07:43:39 +0100 (CET)
Message-ID: <52F08C18.90602@frobbit.se>
Date: Tue, 04 Feb 2014 07:43:36 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, dnsop@ietf.org
References: <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info>
In-Reply-To: <20140204012148.GE16180@mx1.yitter.info>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bb0rBtt34ad1htPKpupqCDrDD9QvF9GAW"
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 06:43:43 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bb0rBtt34ad1htPKpupqCDrDD9QvF9GAW
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-04 02:21, Andrew Sullivan wrote:
> On Mon, Feb 03, 2014 at 08:08:59PM -0500, Ted Lemon wrote:
>> >=20
>> > purely on the basis that some of us don't like what they did.  We
>> > need a better reason than that, and thus far none has been stated.
> In the particular case of .onion, I'm not sure I agree none has been
> stated.  But let me try again:
>=20
>     If you want to use a name in DNS protocol slots, then you need a DN=
S
>     name.  You didn't get a DNS name, and instead you used a label
>     that wasn't under your control.

I would like to express the situation slightly different, or rather,
this what you describe is one situation. Another situation which I think
is more complicated is when a name is needed that looks like a domain
name, but is never to be used in DNS. The only thing you need is a
string that is not used as a domain name.

So we have (at least):

1. Strings that are used in DNS, allocated as they where intended to be
allocated

2. Strings that are to be used in DNS, with special roots

3. Strings that are to be used in DNS, but only in local environments
(search path, .local etc)

4. Strings that looks like domain names but are never to be used in DNS,
but still needs to be globally unique

5. Strings that looks like domain names but are never to be used in DNS,
that does not need to be globally unique

We know about 1. We say no to 2. We know about 3. What is new is 4 and 5.=


   Patrik



--bb0rBtt34ad1htPKpupqCDrDD9QvF9GAW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS8IwbrMabGguI180RAkW2AJ44kpucKHzKfNGb2dTKdnhARjQ2tgCfdDxS
6FE5fMVOyvaFl6fRJYLYJO4=
=Excm
-----END PGP SIGNATURE-----

--bb0rBtt34ad1htPKpupqCDrDD9QvF9GAW--

From jim@rfc1035.com  Tue Feb  4 00:22:59 2014
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0EF1A039B for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:22:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81Q2hjDkGVMb for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:22:56 -0800 (PST)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) by ietfa.amsl.com (Postfix) with ESMTP id B9E421A018E for <dnsop@ietf.org>; Tue,  4 Feb 2014 00:22:56 -0800 (PST)
Received: from [158.38.10.162] (unknown [158.38.10.162]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 93AD32420FA3; Tue,  4 Feb 2014 08:22:55 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20140204012148.GE16180@mx1.yitter.info>
Date: Tue, 4 Feb 2014 08:22:54 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBEC374F-F6B9-4BEC-B3B5-5A8E4045ED66@rfc1035.com>
References: <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1510)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 08:22:59 -0000

On 4 Feb 2014, at 01:21, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

>    If you want to use a name in DNS protocol slots, then you need a =
DNS
>    name.  You didn't get a DNS name, and instead you used a label
>    that wasn't under your control.  That's been against the rules in =
the
>    DNS since forever.  Now you want to short-circuit the allocation
>    mechanism.  But we have an allocation mechanism for this.  In the
>    normal case, you apply to ICANN.  In an unusual case where the
>    protocol depends on this, then you can use this special-use
>    registry.  So you need to show that your protocol needs to depend
>    on this special-use label, and then we can register it under the
>    special use mechanism.  Otherwise go to ICANN.

+100.

I hope everyone here can agree on the above and we get back to =
discussing the actual draft.


From bortzmeyer@nic.fr  Tue Feb  4 00:41:18 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B584F1A03A4 for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level: 
X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vZuOsMK1Lju for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:41:16 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 79ECD1A039E for <dnsop@ietf.org>; Tue,  4 Feb 2014 00:41:16 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9CD0B28052C; Tue,  4 Feb 2014 09:41:15 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 973AA280526; Tue,  4 Feb 2014 09:41:15 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 94BD6960002; Tue,  4 Feb 2014 09:40:45 +0100 (CET)
Date: Tue, 4 Feb 2014 09:40:45 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mark Andrews <marka@isc.org>
Message-ID: <20140204084045.GA17756@nic.fr>
References: <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20140203212333.1259EE44493@rock.dv.isc.org>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 08:41:18 -0000

On Tue, Feb 04, 2014 at 08:23:33AM +1100,
 Mark Andrews <marka@isc.org> wrote 
 a message of 62 lines which said:

> There were plenty of people saying "Do NOT use a TLD for your
> private namespace, use a namespace you own" in 2002 whether it was
> for a protocol or a internal network.

Hmmm, the experience of many developers is that, no, it is not easy to
get advice from the IETF. Some did not even bother but those who did
were often turned down immediately. 

Let's play an experiment. In 2014, Joe Developer has a bright idea of
using cryptographic keys as domain names (yes, I know, there is
already the zkeys of GNUnet), he is going to write code to implement
it and wants a suffix for that, to be sure his domain names won't
collide with the ICANN root. Knowing nothing about Internet
governance, not having 185Â 000 US $ and a zillion lawyers at his
disposal to request a TLD, not being Apple, with the ability to squatt
a TLD and deploy it massively, he sends an email to dnsop or
namedroppers asking about advice. What happens?

1) (Most likely) He gets no reply at all because nobody knows him and
he never appeared in an IETF meeting

2) He gets a few messages saying "that's a bad idea, don't do that,
for reasons explained in [insert a long list of RFC]"

3) He gets a ton of messages saying it is a stupid idea and he is
endangering the security and stability of the Internet

4) He gets a sensible advice, based on a careful study of his
proposal, and given by people who forgives him for making a few
mistakes such as not being able to know what is the difference between
IETF and ICANN

In the first three cases, what will he do? He will follow the usual
Internet/free software method, implement and distribute and we'll see
what happens. And then it will be too late to change what's in his
code.


From bortzmeyer@nic.fr  Tue Feb  4 00:43:31 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323CA1A039C for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level: 
X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r5gaGA_XJ0CE for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:43:30 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1771A01D7 for <dnsop@ietf.org>; Tue,  4 Feb 2014 00:43:30 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 90D3228052C; Tue,  4 Feb 2014 09:43:29 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 8BE9B280526; Tue,  4 Feb 2014 09:43:29 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 8A6D2960001; Tue,  4 Feb 2014 09:42:59 +0100 (CET)
Date: Tue, 4 Feb 2014 09:42:59 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: jonne.soininen@broadcom.com
Message-ID: <20140204084259.GB17756@nic.fr>
References: <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CF15D98C.197C0B%jonne.soininen@renesasmobile.com>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 08:43:31 -0000

On Mon, Feb 03, 2014 at 09:54:41PM +0000,
 jonne.soininen@broadcom.com <jonne.soininen@broadcom.com> wrote 
 a message of 112 lines which said:

> maybe we should consider to discuss the principles under which TLDs
> can be reserved for special use and consider a re-spin or an update
> to RFC6761.

So, RFC 6761 was written just to allow Apple to register .local and,
once it is done, we close the door to new registrations?


From bortzmeyer@nic.fr  Tue Feb  4 00:52:06 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E9CD1A03BF for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level: 
X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eXwzySYnqLRP for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 00:52:05 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id F07281A039E for <dnsop@ietf.org>; Tue,  4 Feb 2014 00:52:04 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 72F5E280547; Tue,  4 Feb 2014 09:52:04 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 6E77E28052C; Tue,  4 Feb 2014 09:52:04 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 6BBA3960002; Tue,  4 Feb 2014 09:51:34 +0100 (CET)
Date: Tue, 4 Feb 2014 09:51:34 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: jonne.soininen@broadcom.com
Message-ID: <20140204085134.GC17756@nic.fr>
References: <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info> <CF160FB8.1983E7%jonne.soininen@renesasmobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CF160FB8.1983E7%jonne.soininen@renesasmobile.com>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 08:52:06 -0000

On Tue, Feb 04, 2014 at 01:45:11AM +0000,
 jonne.soininen@broadcom.com <jonne.soininen@broadcom.com> wrote 
 a message of 88 lines which said:

> They are not DNS and not even specified in the IETF. They have taken
> a design choice where they look like DNS

No, that's not a correct description. These proposals use domain names
(not things that "look like" domain names). Domain names are *older*
than the DNS (see RFC 810 and many others). They can be resolved by
several protocols (DNS, Bonjour, /etc/hosts, LDAP, whatever). It is
perfectly sensible to use domain names for new protocols.

> you want a TLD you go to ICANN.  Regardless of what people think of
> that process, this is the process we have created already a long
> time ago

If "we" is the US governement, the sentence is true. Otherwise, no, I
had no part in the ICANN creation. I remember a discussion with Stuart
Cheshire where he explained that IETF, not ICANN, created the entire
name space, since it created the rules, and therefore has rights above
those of ICANN.




From ajs@anvilwalrusden.com  Tue Feb  4 02:30:00 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7665E1A03D9 for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 02:30:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tsiq7rtbP5rQ for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 02:29:58 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA581A02BC for <dnsop@ietf.org>; Tue,  4 Feb 2014 02:29:58 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 8F5928A031 for <dnsop@ietf.org>; Tue,  4 Feb 2014 10:29:57 +0000 (UTC)
Date: Tue, 4 Feb 2014 05:29:56 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140204102956.GB16366@mx1.yitter.info>
References: <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info> <CF160FB8.1983E7%jonne.soininen@renesasmobile.com> <20140204085134.GC17756@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140204085134.GC17756@nic.fr>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 10:30:00 -0000

On Tue, Feb 04, 2014 at 09:51:34AM +0100, Stephane Bortzmeyer wrote:
> had no part in the ICANN creation. I remember a discussion with Stuart
> Cheshire where he explained that IETF, not ICANN, created the entire
> name space, since it created the rules, and therefore has rights above
> those of ICANN.

With respect, while that is one view of the history, it is surely not
the only one, and it seems to me it is one that is not shared by all
the actors in this space.  Most importantly, it involves a false
dichotomy between "ICANN" and "IETF": neither organization existed at
the time the DNS name space was created, so it's hard to credit the
idea that either of them created the name space.

I do not think we want to turn over the rock labelled, "Who owns the
DNS name space?"  Under that rock live all manner of creatures from
layer 9 and above.  We have two allocation procedures: regular
allocation via IANA procedures (which happen to be defined right now
in ICANN) and RFC 6761.  One of those procedures is the one we can
exercise, and I still believe the only question is whether any
particular registration attempt works under RFC 6761.  I agree with
Ted Lemon that the question of what happened in the past is not
exactly relevant.  What _is_ relevant in my view is how these names
need to be used in support of the protocols they're supposed to be
supporting.  This is exactly the same question I had since I first
read the grothoff draft; see my earlier review.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jabley@hopcount.ca  Tue Feb  4 06:41:21 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B571A0100 for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 06:41:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KG04B8TSsxmB for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 06:41:19 -0800 (PST)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9169B1A0126 for <dnsop@ietf.org>; Tue,  4 Feb 2014 06:41:19 -0800 (PST)
Received: by mail-qc0-f171.google.com with SMTP id n7so13579012qcx.2 for <dnsop@ietf.org>; Tue, 04 Feb 2014 06:41:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=FMuSCH8HnOPEFphaTL9CELb5TuJUptCorwjfCdlPYH8=; b=hAViRxK162TEvmuHBjA/oEbpA7oGCDmuIXVw6+T5aMm0hZqyU/pXKCdVNKmkCgQEqJ hsEommM9FCUPWEGmNfk7Atcr5wwDkrV3nAK7MuIf3s/yKz8JmSCkeW+66FXe91CHPgqO 7VG7Aux7FUqS/L5Tm1moR3IixYuICvoLiRdgY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=FMuSCH8HnOPEFphaTL9CELb5TuJUptCorwjfCdlPYH8=; b=JftOKfnJmnjdaE4OyJuJQnkQ36bBxmiJsQkkYIyI0Y4FBTDmFSxPD3JF766vI81X3D p1lcGEFUM9bxmbEiCi1a2hHCNBBtHxwj/WtIqLkCSmMytLrMpo0KpAVIpCsERyAIcXf8 0fFKtyjCA9ED91VNvc/DyACE7E1RSllJE3KZO9XgbBjZGij62wlV6m8/QdmlhSyANfwI sUfLnuJmnrmY0XOAbqYCPBPcZtxA1oZ4xspQsz9BhhB/DUI6t/aJ8YS4lyS9vUTDqbqO DdS2DhFveDAqH+AbVXNVgox8VJNXMCXUeWFEYFT4LU20/rnvhIgZEDcB5Fo36gkErvXb B5NQ==
X-Gm-Message-State: ALoCoQnHNPCNB5DBl6QDmVbqYPxaQ4yzhMINgR+XI7NQQi08n3eoRVm21flXPUHyENcI258tBAmg
X-Received: by 10.140.30.66 with SMTP id c60mr62457123qgc.13.1391524879101; Tue, 04 Feb 2014 06:41:19 -0800 (PST)
Received: from [172.16.29.101] (nat-08-mht.dyndns.com. [216.146.45.247]) by mx.google.com with ESMTPSA id d7sm67392936qad.10.2014.02.04.06.41.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 06:41:18 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_35485591-FDAF-404B-A563-8ABC0F9A4986"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20140204063911.55905.qmail@joyce.lan>
Date: Tue, 4 Feb 2014 09:41:16 -0500
Message-Id: <AACA56B2-52E6-416A-9CAF-CB7A7BE1ECC8@hopcount.ca>
References: <20140204063911.55905.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 14:41:21 -0000

--Apple-Mail=_35485591-FDAF-404B-A563-8ABC0F9A4986
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-02-04, at 01:39, John Levine <johnl@taugh.com> wrote:

> I suppose the situation with .onion is slightly different, but in
> concept it's not all that different from .arpa.

I think it's quite different.

ARPA is really no different from any other TLD. There's a registry, =
there are rules you need to follow to get a delegation, but it's a zone =
in the DNS just like COM and ORG.

ONION is a namespace convention outside the DNS. There's no registry, =
it's not a zone, and there is no possibility of getting a delegation.

ONION is like LOCAL. Neither are like ARPA (or any other TLD).


Joe


--Apple-Mail=_35485591-FDAF-404B-A563-8ABC0F9A4986
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLw/AwACgkQNI8MvYZSOizANwCeISzbm2KwLY/nO1YZQPMpo5mw
TPsAnAh0q0x4L+mbIU6DSvZ/cRzzmtvs
=/gSU
-----END PGP SIGNATURE-----

--Apple-Mail=_35485591-FDAF-404B-A563-8ABC0F9A4986--

From paul@redbarn.org  Tue Feb  4 07:00:27 2014
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9EA1A00E4 for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FrPgAu2Y-V0z for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:00:26 -0800 (PST)
Received: from ss.vix.su (ss.vix.su [IPv6:2001:559:8000:cb::2]) by ietfa.amsl.com (Postfix) with ESMTP id 927291A00EC for <dnsop@ietf.org>; Tue,  4 Feb 2014 07:00:26 -0800 (PST)
Received: from [IPv6:2001:559:8000:cb:d944:c465:c117:44ce] (unknown [IPv6:2001:559:8000:cb:d944:c465:c117:44ce]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ss.vix.su (Postfix) with ESMTPSA id 8E5A9EBCD0; Tue,  4 Feb 2014 15:00:25 +0000 (UTC) (envelope-from paul@redbarn.org)
Message-ID: <52F1008A.4030502@redbarn.org>
Date: Tue, 04 Feb 2014 07:00:26 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.9 (Windows/20140128)
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
References: <20140204063911.55905.qmail@joyce.lan> <AACA56B2-52E6-416A-9CAF-CB7A7BE1ECC8@hopcount.ca>
In-Reply-To: <AACA56B2-52E6-416A-9CAF-CB7A7BE1ECC8@hopcount.ca>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, John Levine <johnl@taugh.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 15:00:27 -0000

Joe Abley wrote:
> ...
>
> ONION is like LOCAL. Neither are like ARPA (or any other TLD).

How like LOCAL is ONION? ICANN knows it can't sell .LOCAL, but does
ICANN know it can't sell .ONION ?


From jabley@hopcount.ca  Tue Feb  4 07:15:14 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2BD1A0160 for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5zysfr65EoL for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:15:13 -0800 (PST)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id CBE761A011C for <dnsop@ietf.org>; Tue,  4 Feb 2014 07:15:12 -0800 (PST)
Received: by mail-qa0-f48.google.com with SMTP id f11so12321406qae.7 for <dnsop@ietf.org>; Tue, 04 Feb 2014 07:15:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=I5qM3oucfn9+VX5KY1aIS3BcWTzAI4NL3kSx54doWmk=; b=F9uAhUx2PEzdWJgAFK3fBvedXzQ/tQVYEoXN+SqwLZjQNWb9d6seJQsGKlTcydJ69+ cnAg27JHPAVWdRPoTgEb0fEAoyIz4yp5i5LmUfIRLrPxsJ6fuG1cZaR8c4J/UrqIHJcu 8wtuvv1TtzBqyfHr0SmWb8PY3HW8SOMK2ShCA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=I5qM3oucfn9+VX5KY1aIS3BcWTzAI4NL3kSx54doWmk=; b=c/ChbtfngwmceWBnlFO9clxWw2qEeUU9kllrPiauvYXkcTQX7RiBfxLv7RvRRlWLkT 9T5h/CQCUb5Uq6cmd3a75LfzO6bwXN5bLj225TsNCw3t5HSFceGXchPb9h/XHbFZa90s EGj3APxryfihDPPwkIiBq1m0F0r46hWOxqvsgBYVNGsj15lwMzutKxfhH8941APBHRP6 niMkb0MYjgrrqZ2BvZTSh1+Ku8J1lARXV1ev1wtuCOlgIpuZ1SNnltCKrPsmMtPWSwZx IuiOUP+CTxRUig1XneJ1Gmo9r2mmCTr6hChH6FGbQnR4GnvtAFsjJ2AH+vxtcfDKligW SKlg==
X-Gm-Message-State: ALoCoQlMk1mxr02j5bU5oQxz+HR3fGbvp9sxs91Qm6u7gkFSmelRhYuzdra81CAWjE/kppuZngv1
X-Received: by 10.140.88.180 with SMTP id t49mr63445062qgd.97.1391526912222; Tue, 04 Feb 2014 07:15:12 -0800 (PST)
Received: from [172.16.29.101] (nat-08-mht.dyndns.com. [216.146.45.247]) by mx.google.com with ESMTPSA id f10sm67643429qar.12.2014.02.04.07.15.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 07:15:11 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_12835AD0-C13F-4CBE-A6F5-69A649566AB5"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <52F1008A.4030502@redbarn.org>
Date: Tue, 4 Feb 2014 10:15:05 -0500
Message-Id: <8BCC9B33-8369-49BE-90DD-7E1861CA670E@hopcount.ca>
References: <20140204063911.55905.qmail@joyce.lan> <AACA56B2-52E6-416A-9CAF-CB7A7BE1ECC8@hopcount.ca> <52F1008A.4030502@redbarn.org>
To: Paul Vixie <paul@redbarn.org>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, John Levine <johnl@taugh.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 15:15:14 -0000

--Apple-Mail=_12835AD0-C13F-4CBE-A6F5-69A649566AB5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-02-04, at 10:00, Paul Vixie <paul@redbarn.org> wrote:

> Joe Abley wrote:
>> ...
>>=20
>> ONION is like LOCAL. Neither are like ARPA (or any other TLD).
>=20
> How like LOCAL is ONION?

Neither is a zone in the DNS or a domain in the DNS namespace, and both =
refer to names for which a protocol other than DNS should be used for =
resolution.

(I realise the protocol for LOCAL is DNS-like, but it's not DNS, right?)

> ICANN knows it can't sell .LOCAL, but does
> ICANN know it can't sell .ONION ?

I was never quite sure what ICANN knew, even when I worked for ICANN.

I'm not arguing against the IETF protecting the world from conflicting =
ONION namespaces in the same way that they did with LOCAL, which would =
have the effect that ICANN would not sell ONION. I agree that if ICANN =
sold ONION to someone, the result would be messy.

However, I don't think ambiguity in the discussion about the namespaces =
we're talking about or the failure modes we're hoping to avoid helps us =
narrow in on anything resembling consensus.


Joe

--Apple-Mail=_12835AD0-C13F-4CBE-A6F5-69A649566AB5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLxA/kACgkQNI8MvYZSOiyfrACgxTXH5l593sF8oRswV2pnGwy2
QcQAn0WmzCoHvH5vJvlziqEmZtejSX+l
=9LEs
-----END PGP SIGNATURE-----

--Apple-Mail=_12835AD0-C13F-4CBE-A6F5-69A649566AB5--

From fergdawgster@mykolab.com  Tue Feb  4 07:17:32 2014
Return-Path: <fergdawgster@mykolab.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968381A010A for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-cu9Qv1GnrY for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:17:30 -0800 (PST)
Received: from mx05.mykolab.com (mx01.mykolab.com [95.128.36.1]) by ietfa.amsl.com (Postfix) with ESMTP id 249E81A016B for <dnsop@ietf.org>; Tue,  4 Feb 2014 07:17:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at kolabsys.net
Sender: fergdawgster@mykolab.com
Message-ID: <52F10481.4000700@mykolab.com>
Date: Tue, 04 Feb 2014 07:17:21 -0800
From: Paul Ferguson <fergdawgster@mykolab.com>
Organization: Clowns R. Mofos
To: Paul Vixie <paul@redbarn.org>
References: <20140204063911.55905.qmail@joyce.lan> <AACA56B2-52E6-416A-9CAF-CB7A7BE1ECC8@hopcount.ca> <52F1008A.4030502@redbarn.org>
In-Reply-To: <52F1008A.4030502@redbarn.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, John Levine <johnl@taugh.com>, Joe Abley <jabley@hopcount.ca>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: fergdawgster@mykolab.com
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 15:17:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2/4/2014 7:00 AM, Paul Vixie wrote:

> 
> Joe Abley wrote:
>>> ...
>>> 
>>> ONION is like LOCAL. Neither are like ARPA (or any other TLD).
> How like LOCAL is ONION? ICANN knows it can't sell .LOCAL, but
> does ICANN know it can't sell .ONION ?

I think I see where Vixie is going with this, and I concur. I don't
see the difference either, and simply because .onion started being
used before a contrarian policy was in place should not be reason
enough to dispense with it's use.

$.02,

- - ferg


- -- 
Paul Ferguson
VP Threat Intelligence, IID
PGP Public Key ID: 0x54DC85B2

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlLxBIEACgkQKJasdVTchbKLwQEAhXCQ/3EcUjZRtjyFkD+WirA4
0N+jWQlKEIdY43ZlQuIA/2XGqEJxRPhQxF0nMPK/brMnliaD14d0jgr0BY6U6EHC
=VrNq
-----END PGP SIGNATURE-----

From suzworldwide@gmail.com  Tue Feb  4 07:43:11 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23D601A012A for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:43:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKhQTi8f031n for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 07:43:09 -0800 (PST)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 899041A011C for <dnsop@ietf.org>; Tue,  4 Feb 2014 07:43:09 -0800 (PST)
Received: by mail-ig0-f182.google.com with SMTP id uy17so8248050igb.3 for <dnsop@ietf.org>; Tue, 04 Feb 2014 07:43:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=e9k6LiRWhcoOWVIaI7707i7qot7q/qnACRXQUsS9+LU=; b=pxe4EeaD37lOrzx/UA1c/lJlwUfyieiqWq6a+McRUg5nTE88sZDXZJtyhVY3lHUVmk QgXPEqZRuaZDPt+8SD4sGnU2LT14ykyvMWBGBamhJeoH/7AOjZA/yABemr5BBlt9HxUm 2OVTanLmJ0ZvVomJuRmzdcmPw1KKUVV4bC7CwJpBrA/d15XnKH2x4hiYdwdWiRGJac3/ mlqyE51BGwTgo2Zuxpg7D8nK3kDF0gpWznEVvQM1KrH9WCeFoalbvA6TenRk5P60pLJo quxGvupFvPJlWaMViCTAo5RkFnl1z/jYyF5xGNAmw51150wAzhOg1sb1KEUaf+NAY5ba /UWA==
X-Received: by 10.43.137.5 with SMTP id im5mr1856227icc.55.1391528589150; Tue, 04 Feb 2014 07:43:09 -0800 (PST)
Received: from [172.19.131.154] ([12.130.127.94]) by mx.google.com with ESMTPSA id y9sm41011585igl.0.2014.02.04.07.43.05 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 07:43:08 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20140204102956.GB16366@mx1.yitter.info>
Date: Tue, 4 Feb 2014 10:42:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E480A769-2241-4891-BFE8-7BA075E7D563@gmail.com>
References: <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info> <CF160FB8.1983E7%jonne.soininen@renesasmobile.com> <20140204085134.GC17756@nic.fr> <20140204102956.GB16366@mx1.yitter.info>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1510)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 15:43:11 -0000

Dear Colleagues,

On Feb 4, 2014, at 5:29 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
> I do not think we want to turn over the rock labelled, "Who owns the
> DNS name space?"  Under that rock live all manner of creatures from
> layer 9 and above.  We have two allocation procedures: regular
> allocation via IANA procedures (which happen to be defined right now
> in ICANN) and RFC 6761.  One of those procedures is the one we can
> exercise, and I still believe the only question is whether any
> particular registration attempt works under RFC 6761.=20

In this spirit, I'd like to suggest that we assume for the sake of the =
current discussion that any apparent problem between ICANN and the IETF =
over the public DNS namespace can be resolved sensibly, so it's =
unnecessary to speculate on what ICANN knows, or what applicants for =
names under ICANN's process will or won't do, or whose process has =
precedence.

I think our job here has to be to discuss these drafts on their merits-- =
the operational impact of adding these names to the special use =
registry, or not, including guidance to implementors (if we converge on =
any) and precedents for other protocol and software developers in the =
future.

It also seems to me that if we come up with refinements or modifications =
to RFC 6761, we can write those up and share them with the community in =
the usual way.


best,
Suzanne









From johnl@iecc.com  Tue Feb  4 15:41:02 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2946C1A0169 for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 15:41:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0TUziGVSBjm for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 15:41:01 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id ADFEC1A0163 for <dnsop@ietf.org>; Tue,  4 Feb 2014 15:41:00 -0800 (PST)
Received: (qmail 48733 invoked from network); 4 Feb 2014 23:40:59 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Feb 2014 23:40:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f17a8b.xn--3zv.k1402; i=johnl@user.iecc.com; bh=XkyzmzP67Ixbc0bwPk25JRn+HYx9HN+trNgn28Qxq7U=; b=SfWT0jXMwUorLIQdutLEpF/UMcINH1WMCv1wT/2m2mCO8EHrvFgvdtnqKcCda5gP1xFLayDi5bTNt7RG1HEFrEvuDfaJ/+j1+69fvyRoauu1ohKuvgBAfderuLvwY11qtl0I1JnIZKKiTJctmxJGUm5dL8LSEcDvD+JqbJgR2+PljBAx4I4yLwk8SMlnDiwsS0fb6B9WYB38kxfYNs900s/704qnAYo8yoWjNF5NdmJexre+ldAQmlrHH6kuvUW7
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f17a8b.xn--3zv.k1402; bh=XkyzmzP67Ixbc0bwPk25JRn+HYx9HN+trNgn28Qxq7U=; b=FhMR+gZ4rUAnGHeMIG4Vb9dLluK0tyy7RUO3t9qvxNHd0HiXp3nVGNkWBZDeknmpB0+SeLHix3eix71RVTJD0QJ9/Di8oZGAdnmN1LdJanGlvV+SnkrMub5J7vY93npaJXHvHV4Fi6iwcbmH0FGlLKRhcT+ZBHAD6J35K1oxixueLZzugBAPI27C+dHBLgnzk4iWETdmswt72wQFgYUerQx8llIRlwqYJFQs47NqOM+3nP7YmMoELGGq6JwUEvTw
Date: 4 Feb 2014 23:40:37 -0000
Message-ID: <20140204234037.57613.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20140204084045.GA17756@nic.fr>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 23:41:02 -0000

>Let's play an experiment. In 2014, Joe Developer has a bright idea of
>using cryptographic keys as domain names

Yup, that would be .bit.  Everything you say is true.

R's,
John

From johnl@iecc.com  Tue Feb  4 16:53:58 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E30F61A01BD for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 16:53:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yafyxw_gfAUA for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 16:53:57 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE731A01BB for <dnsop@ietf.org>; Tue,  4 Feb 2014 16:53:57 -0800 (PST)
Received: (qmail 60908 invoked from network); 5 Feb 2014 00:53:56 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 5 Feb 2014 00:53:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f18ba4.xn--yuvv84g.k1402; i=johnl@user.iecc.com; bh=LjJnFrVqzCpHJ1L3RwHqweHHu1uIpPAgQfO7cyRvhuE=; b=LsiPKPBYjyRMKITdCytYdWR8+mwn3KSG2pI5nRetx8+rdiUZdcVrCzbQcKzSne1lQ1VTmNyLQS+ABGgVxpXFBdWa/IryT9Ged+MYPccb1a6sadAW2VDGY7i30zRMmsajB1d4JTU23TQgGQCDLWRPA6vkOmT/7I7K38+axh7CK93+36hTfRHmDM/vPPLPheEjmRNsvItGt0uiY6bCgf1y6UDbzbjVYlsC2tuLPXAxnbYgjsblXEykj5sJGgIzKDlV
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52f18ba4.xn--yuvv84g.k1402; bh=LjJnFrVqzCpHJ1L3RwHqweHHu1uIpPAgQfO7cyRvhuE=; b=B1qHR0PXZ3qbrUGWHh1NmmBHzrWhWODhbO4/jC336ypRYRtO8uQV2APICKtopUd9G74Ttl/zTd1HSGtXWlxWK9VfKuHXsPK8PFdh76deOIdPvRdlOE/cEJXPqaNqZVtsFe8i+RnL3D33wg83fFB5WUa/nJXYvaYqkhSWPP0bPL0JXOULdAfZRbu3uZG8sW+BaD2IagbdeJPUsg15Ay7u7FPGdLsK3F6UfXMiQ2Lfay8XvJ6kM2/NVUwlVWru1Sjl
Date: 5 Feb 2014 00:53:34 -0000
Message-ID: <20140205005334.57929.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <8BCC9B33-8369-49BE-90DD-7E1861CA670E@hopcount.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: jabley@hopcount.ca
Subject: Re: [DNSOP] possibly quite a lot of additional special names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 00:53:59 -0000

>> How like LOCAL is ONION?
>
>Neither is a zone in the DNS or a domain in the DNS namespace, and both refer to names for which a
>protocol other than DNS should be used for resolution.
>
>(I realise the protocol for LOCAL is DNS-like, but it's not DNS, right?)

The protocol for .ONION is DNS-like, too.  If you're running Tor, its
SOCKS proxy handles the domain names, using the normal SOCKS5
protocol, with .ONION and .EXIT treated as special cases.  The client
software, typically a web browser, doesn't know it's any different
from any other SOCKS proxy.

It seems to me that we can make a meaningful distinction between
domain names that are delegated from the global root using the normal
DNS protocol and allow arbitrary RRs (give or take) which is ICANN's
department, and domain names that are handled in other ways which is
the IETF's.  The only ICANN domain that isn't technically totally
ordinary is .TEL, which was supposed to be a directory using NAPTR to
map names to phone numbers.  It is quietly slouching toward genericity
with rather a lot of names parked by speculators, so I doubt we'll see
any more of those from ICANN.

I realize that the received wisdom is that any variation from the
standard protocol is awful and must be eliminated with extreme
prejudice, but that horse left the barn a long time ago, and enough
people have seen it running around and looking healthy that we have a
credibility problem.

What does cause problems is name collisions, but we can deal with them
more effectively with registries than by trying to stamp out pseudo-TLDs
named .ONION and .BIT and who knows what else.

R's,
John, formerly aka johnl@ima.uucp, currently johnl@taughannock.tel.

PS: Andrew asked whether .onion.arpa would have worked technically as
well as .onion.  Sure.  But so what?

From joelja@bogus.com  Tue Feb  4 17:06:16 2014
Return-Path: <joelja@bogus.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE16E1A01A5 for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 17:06:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8OeZ1JdqHse for <dnsop@ietfa.amsl.com>; Tue,  4 Feb 2014 17:06:15 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 321B41A0196 for <dnsop@ietf.org>; Tue,  4 Feb 2014 17:06:15 -0800 (PST)
Received: from mb-aye.lan (50-0-150-57.dsl.static.sonic.net [50.0.150.57]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s1516CUh015406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 5 Feb 2014 01:06:12 GMT (envelope-from joelja@bogus.com)
Message-ID: <52F18E83.4070701@bogus.com>
Date: Tue, 04 Feb 2014 17:06:11 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, jonne.soininen@broadcom.com
References: <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <20140204084259.GB17756@nic.fr>
In-Reply-To: <20140204084259.GB17756@nic.fr>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7oVqlqKaiP4aCCGC1aINtvQgNP4xPiRe6"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Wed, 05 Feb 2014 01:06:13 +0000 (UTC)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 01:06:16 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7oVqlqKaiP4aCCGC1aINtvQgNP4xPiRe6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2/4/14, 12:42 AM, Stephane Bortzmeyer wrote:
> On Mon, Feb 03, 2014 at 09:54:41PM +0000,
>  jonne.soininen@broadcom.com <jonne.soininen@broadcom.com> wrote=20
>  a message of 112 lines which said:
>=20
>> maybe we should consider to discuss the principles under which TLDs
>> can be reserved for special use and consider a re-spin or an update
>> to RFC6761.
>=20
> So, RFC 6761 was written just to allow Apple to register .local and,
> once it is done, we close the door to new registrations?

That in and of itself would be a bit of a moral hazard. it's plausible
that this one case is simply more clear cut (certainly in the minds of
the authors) then others.

I don't believe that we did this (6761) so that we could treat this as a
one-off event.

it's my personal opinion that application specific namespaces should be
treated differently in some way, if resolver libraries are being asked
to make a decision on the basis of .tld how to handle a query we gone
down an extensibility rathole that's hard to get out of.

> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20



--7oVqlqKaiP4aCCGC1aINtvQgNP4xPiRe6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLxjoMACgkQ8AA1q7Z/VrLgxgCfZnEod8/txDKQ6uT2aCVfRE6u
v14An07WDh0ABQfj1fbl1VFxBCFBW7nt
=5G/D
-----END PGP SIGNATURE-----

--7oVqlqKaiP4aCCGC1aINtvQgNP4xPiRe6--

From Ted.Lemon@nominum.com  Wed Feb  5 04:39:36 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CAEF1A00F4 for <dnsop@ietfa.amsl.com>; Wed,  5 Feb 2014 04:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jfuh1uZMPOaw for <dnsop@ietfa.amsl.com>; Wed,  5 Feb 2014 04:39:35 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 382C11A00F2 for <dnsop@ietf.org>; Wed,  5 Feb 2014 04:39:35 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUvIxBkUtEWX/WnSahqquR9e9DFTgeoGv@postini.com; Wed, 05 Feb 2014 04:39:34 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 860B41B8308 for <dnsop@ietf.org>; Wed,  5 Feb 2014 04:39:34 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 567F6190052; Wed,  5 Feb 2014 04:39:34 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 5 Feb 2014 04:39:34 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52F18E83.4070701@bogus.com>
Date: Wed, 5 Feb 2014 07:39:31 -0500
Content-Transfer-Encoding: 7bit
Message-ID: <2438677D-1F8B-41A3-B33A-087C404A3DB6@nominum.com>
References: <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <20140204084259.GB17756@nic.fr> <52F18E83.4070701@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: jonne.soininen@broadcom.com, dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 12:39:36 -0000

On Feb 4, 2014, at 8:06 PM, joel jaeggli <joelja@bogus.com> wrote:
> resolver libraries are being asked
> to make a decision on the basis of .tld how to handle a query we gone
> down an extensibility rathole that's hard to get out of.

Lookup tables are hard...

:)


From internet-drafts@ietf.org  Wed Feb  5 14:43:26 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A56011A0224; Wed,  5 Feb 2014 14:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBkLrxG3ukKu; Wed,  5 Feb 2014 14:43:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC8A1A0263; Wed,  5 Feb 2014 14:43:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140205224324.9768.60804.idtracker@ietfa.amsl.com>
Date: Wed, 05 Feb 2014 14:43:24 -0800
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 22:43:27 -0000

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

        Title           : Automating DNSSEC delegation trust maintenance
        Authors         : Warren Kumari
                          Olafur Gudmundsson
                          George Barwood
	Filename        : draft-ietf-dnsop-delegation-trust-maintainance-02.txt
	Pages           : 18
	Date            : 2014-02-05

Abstract:
   This document describes a method to allow DNS operators to more
   easily update DNSSEC Key Signing Keys using DNS as communication
   channel.  This document does not address the initial configuration of
   trust anchors for a domain.  The technique described is aimed at
   delegations in which it is currently hard to move information from
   the child to parent.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintainance/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-delegation-trust-maintainance-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-delegation-trust-maintainance-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From jinmei.tatuya@gmail.com  Thu Feb  6 10:29:53 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61BCB1A020F for <dnsop@ietfa.amsl.com>; Thu,  6 Feb 2014 10:29:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.922
X-Spam-Level: *
X-Spam-Status: No, score=1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWl-eTo6Etx2 for <dnsop@ietfa.amsl.com>; Thu,  6 Feb 2014 10:29:52 -0800 (PST)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id B1C721A01B6 for <dnsop@ietf.org>; Thu,  6 Feb 2014 10:29:51 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id t61so1570446wes.22 for <dnsop@ietf.org>; Thu, 06 Feb 2014 10:29:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=ywLsx+yI6mAi0xEo7iyv+6tMxPylpe3M3PAIIIkFF4w=; b=aUPZWf82A6qVbBTArZ1RHem0MOqnCHEvHntC0skjOqvIwlp1Ff3cMJ9+1eperZgKvC Qhl20O2rNZOE2AAe2VlwNq9tYj6bRLcOBeE6+d3E14SfuV1cYziGsmDa7adUuN40nKIH 2hKDhaRyVSf0gMsS2DEX3EEcyCOSKcxYYZeYe9nVf8LrbJUyT7oCVXAP2KT5md70+8gU AOGQsoG4X5/vM9h3krG+73AEAWmKExHoZihNfIE/4dPJA4g6UO3oB3+F8oD5JWWF90XN 4EHZcX3iXyUo33ESpFogsMUzinU36etmJLZmn9pchFAgzTZ2Z5MOw3eOpCsPSPDWLZ6a ZJcA==
MIME-Version: 1.0
X-Received: by 10.194.58.180 with SMTP id s20mr2783789wjq.54.1391711390203; Thu, 06 Feb 2014 10:29:50 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Thu, 6 Feb 2014 10:29:50 -0800 (PST)
Date: Thu, 6 Feb 2014 10:29:50 -0800
X-Google-Sender-Auth: tYnBLzehiC3vzNDHIso4eGkKXnk
Message-ID: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com>
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: dnsop@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 18:29:53 -0000

I have one quick question about CDS/CDNSKEY: what's the (or "an")
expected operation for the parent to remove a DS RR of a child that
was obsolete and is now removed from the child zone?

This point is not clear to me on a quick rescan of
draft-ietf-dnsop-delegation-trust-maintainance-02.

According to Section 3:

   The CDS / CDNSKEY record is published in the child zone and gives the
   child control of what is published for it in the parental zone.  The
   CDS / CDNSKEY RRset expresses what the child would like the DS RRset
   to look like after the change; [...]

it could read the child would remove the CDS or CDSKEY for the
now-removed DNSKEY, but it may contradict Section 4.1:

   Absence of CDS / CDNSKEY in child signals "No change" to the current
   DS set.

(BTW: this sentence is a bit ambiguous to me.  Does this mean there's
no CDS/CDNSKEY RR for the apex name, or the absence of CDS/CDNSKEY for
a specific DNSKEY?)

and also Section 5:

   When the Parent DS is "in-sync" with the CDS, the Child DNS Operator
   MAY delete the CDS RRset.

i.e., if the child may delete a CDS for a new DNSKEY after
synchronization, clearly it cannot use the removal of CDS as an
indication of the removal of DNSKEY.

Am I missing some part of the draft that answers my question, or is
this actually out of scope of CDS/CDNSKEY?

p.s. apologize in advance this was already discussed; I don't remember
all previous discussions of the proposal.

--
JINMEI, Tatuya

From warren@kumari.net  Thu Feb  6 11:13:10 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3991A0445 for <dnsop@ietfa.amsl.com>; Thu,  6 Feb 2014 11:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQk4Wm9rIS-X for <dnsop@ietfa.amsl.com>; Thu,  6 Feb 2014 11:13:07 -0800 (PST)
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5C51A03E4 for <dnsop@ietf.org>; Thu,  6 Feb 2014 11:13:07 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id e4so145242wiv.4 for <dnsop@ietf.org>; Thu, 06 Feb 2014 11:13:05 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JsQkHHicn1pM6KK/6xDVCY8fnu38tB1CE5F4dG4W9Gs=; b=WZ0kbKoFofxziroNs0vADVZrUWyJDAYC/G8lfoD44+WuAvVIWKLnANMbbOu1X+QI8M Our+H06hxt76/fOj0dE85QHrCDaPCv1CWlULeNs0fZFSjrbfZ04kE3ESTXwE3Bvdtky/ zs9js6PJaZ6BNvPpch3WFR+FPhtRPz1AtGthv5j8lSe4gGh8E2XHgRWegl3ejGAN9Cqi zIvhnwZHetDjlV4JOFD9p/H6WkZVKSo6jkOUd49V2k2kqdp1lOoPYFfdRxLPJTySkpSx sfQPY6hEQc4Rmsu7+x0bR3+yd6jFtR8Mjg8sh8s793cHJuGU5YTAxiLUG05GpOW03rM5 sq5A==
X-Gm-Message-State: ALoCoQmwnzMgsUS/F27JGaAF+Wbi0yh449l9E3t1Lr5TKJA81ACbbgi/gulK2u/35yATuVwuXDpM
MIME-Version: 1.0
X-Received: by 10.194.84.144 with SMTP id z16mr7275908wjy.23.1391713985677; Thu, 06 Feb 2014 11:13:05 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Thu, 6 Feb 2014 11:13:05 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com>
Date: Thu, 6 Feb 2014 14:13:05 -0500
Message-ID: <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 19:13:10 -0000

On Thu, Feb 6, 2014 at 1:29 PM, $B?@L@C#:H(B <jinmei@wide.ad.jp> wrote:
> I have one quick question about CDS/CDNSKEY: what's the (or "an")
> expected operation for the parent to remove a DS RR of a child that
> was obsolete and is now removed from the child zone?
>
> This point is not clear to me on a quick rescan of
> draft-ietf-dnsop-delegation-trust-maintainance-02.
>
> According to Section 3:
>
>    The CDS / CDNSKEY record is published in the child zone and gives the
>    child control of what is published for it in the parental zone.  The
>    CDS / CDNSKEY RRset expresses what the child would like the DS RRset
>    to look like after the change; [...]
>
> it could read the child would remove the CDS or CDSKEY for the
> now-removed DNSKEY, but it may contradict Section 4.1:
>
>    Absence of CDS / CDNSKEY in child signals "No change" to the current
>    DS set.
>
> (BTW: this sentence is a bit ambiguous to me.  Does this mean there's
> no CDS/CDNSKEY RR for the apex name, or the absence of CDS/CDNSKEY for
> a specific DNSKEY?)

Hmmm...

What we were trying to say is that the parent publishes verbatim what
the child says.


So, lets say that at time T things look like this:
Parent:
  example.com. 300  IN DS 31589 8 1 123456.....
Child:
   example.com. 300  IN CDS 31589 8 1 123456......
[ The parent and child are in sync ]

At time T+1 the child decides to perform a key rollover, so they
generate a new DNSKEY, compute the DS, etc.
Parent:
  example.com. 300  IN DS 31589 8 1 123456.....
Child:
  example.com. 300  IN CDS 31589 8 1 123456......
  example.com. 300  IN CDS 31589 8 1 789ABC......
[ The parent still has not updated yet ]

At time T+2 the parent performs the CDS action (either they polled, or
the person operating the child logged onto the web interface and
clicked a button):
The parent sees that what the child has published does not match with
the parent currently has, and so the parent copies the contents from
the child. Now things look like:
Parent:
  example.com. 300  IN DS 31589 8 1 123456......
  example.com. 300  IN DS 31589 8 1 789ABC......
Child:
  example.com. 300  IN CDS 31589 8 1 123456......
  example.com. 300  IN CDS 31589 8 1 789ABC......
[ The parent and child are now in sync / agreement again ]

At time T+3 the child sees that the parent has published the new key
information ( and the standard keyroll stuff has all happened (records
are signed with new key, waited for old TTLs to expire, etc)) and so
wants to remove the old key.
** This is, as far as I understand, what you were  asking about)
The child now publishes just the new key info. They stop publishing the old one.
Parent:
  example.com. 300  IN DS 31589 8 1 123456......
  example.com. 300  IN DS 31589 8 1 789ABC......
Child:
  example.com. 300  IN CDS 31589 8 1 789ABC......
[ Child is only publishing new record / they stop publishing the old one ]

At time T+4 the parent checks agin (it polls, the human clicks the
button on the web page, some other trigger happens, etc):
It sees that what the child has published does not match what the
parent currently has, and so it copies the contents from the child.
Parent:
  example.com. 300  IN DS 31589 8 1 789ABC......
Child:
  example.com. 300  IN CDS 31589 8 1 789ABC......
[ The child and parent are back in sync. The old key (123456...) is no
longer in use anywhere. ]


The CDS RR set says, in effect, "Please replace *all* of the key
information for me with *this* set of info."

>
> and also Section 5:
>
>    When the Parent DS is "in-sync" with the CDS, the Child DNS Operator
>    MAY delete the CDS RRset.
>
> i.e., if the child may delete a CDS for a new DNSKEY after
> synchronization, clearly it cannot use the removal of CDS as an
> indication of the removal of DNSKEY.

It at any point during this process the parent contacts the child and
does NOT find any CDS records, it simply does nothing.
This means that you can use this to update / replace / remove existing
DS records (if you have keys A, B, C and D and want to stop using C,
you simply publish A, B, D), but you cannot remove *all* DS records /
go unsigned.


>
> Am I missing some part of the draft that answers my question, or is
> this actually out of scope of CDS/CDNSKEY?

I think that it in in the draft, but we need to be clearer that the
CDS/CDNSKEY *RRset* that the child publishes should be published in
the parent exactly (after transforming DNSKEYs to DS if needed). This
isn't a "please add record X" or "please remove record Y", it is
"Please publish this *list*"
We specifically want to remove the need for the parent to maintain state, etc.

>
> p.s. apologize in advance this was already discussed; I don't remember
> all previous discussions of the proposal.

Me neither!
:-)

W


>
> --
> JINMEI, Tatuya
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

From fanf2@hermes.cam.ac.uk  Thu Feb  6 11:26:21 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9EDD1A0454 for <dnsop@ietfa.amsl.com>; Thu,  6 Feb 2014 11:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.135
X-Spam-Level: 
X-Spam-Status: No, score=-2.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIKqJsJRrHrV for <dnsop@ietfa.amsl.com>; Thu,  6 Feb 2014 11:26:19 -0800 (PST)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 887061A0415 for <dnsop@ietf.org>; Thu,  6 Feb 2014 11:26:19 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:59236) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1WBUaW-0006kJ-iC (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 06 Feb 2014 19:26:16 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WBUaW-0007AV-L8 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 06 Feb 2014 19:26:16 +0000
Date: Thu, 6 Feb 2014 19:26:16 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
In-Reply-To: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com>
Message-ID: <alpine.LSU.2.00.1402061913260.15645@hermes-1.csi.cam.ac.uk>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1870869256-1962937549-1391714776=:15645"
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 19:26:22 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1870869256-1962937549-1391714776=:15645
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinmei@wide.ad.jp> wrote:

> I have one quick question about CDS/CDNSKEY: what's the (or "an")
> expected operation for the parent to remove a DS RR of a child that
> was obsolete and is now removed from the child zone?
>
> This point is not clear to me on a quick rescan of
> draft-ietf-dnsop-delegation-trust-maintainance-02.
>
> According to Section 3:
>
>    The CDS / CDNSKEY record is published in the child zone and gives the
>    child control of what is published for it in the parental zone.  The
>    CDS / CDNSKEY RRset expresses what the child would like the DS RRset
>    to look like after the change; [...]
>
> it could read the child would remove the CDS or CDSKEY for the
> now-removed DNSKEY, but it may contradict Section 4.1:
>
>    Absence of CDS / CDNSKEY in child signals "No change" to the current
>    DS set.
>
> (BTW: this sentence is a bit ambiguous to me.  Does this mean there's
> no CDS/CDNSKEY RR for the apex name, or the absence of CDS/CDNSKEY for
> a specific DNSKEY?)

I think this second quote from the draft is supposed to mean: absence of
any CDS or CDNSKEY RRsets signals no change.

If there is a CDS or CDNSKEY RRset then the DS RRset should be changed to
match (provided the other acceptance rules are satisfied).

I believe the intent of the draft is that this mechanism cannot be used to
go insecure - though I cannot immediately find text which explicitly says
that. So for a CDS or CDNSKEY RRset to have any effect, it must exist,
which implies there must be at least one DS in the parent zone, which
implies you cannot go insecure.

> and also Section 5:
>
>    When the Parent DS is "in-sync" with the CDS, the Child DNS Operator
>    MAY delete the CDS RRset.
>
> i.e., if the child may delete a CDS for a new DNSKEY after
> synchronization, clearly it cannot use the removal of CDS as an
> indication of the removal of DNSKEY.

This quote from the draft talks about removing the entire RRset, so it is
consistent with my explanation above.

To indicate the removal of a DNSKEY, the child uses a CDS RRset which
does not include a record matching the removed DNSKEY, but does include
the other DNSKEYs that are still present.

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first=
=2E
Rough, becoming slight or moderate. Showers, rain at first. Moderate or goo=
d,
occasionally poor at first.
--1870869256-1962937549-1391714776=:15645--

From jinmei.tatuya@gmail.com  Fri Feb  7 09:18:23 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0510A1ACCE3 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 09:18:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.922
X-Spam-Level: *
X-Spam-Status: No, score=1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YP7vo2lFFaaM for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 09:18:21 -0800 (PST)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4F11A1ACC87 for <dnsop@ietf.org>; Fri,  7 Feb 2014 09:18:21 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id e4so1055005wiv.17 for <dnsop@ietf.org>; Fri, 07 Feb 2014 09:18:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=yuXj4KFnibguE6fjytCg4wlUgkqG+eoo4nlICOlQ86g=; b=pST9LKLI6tdrei5We1U5eDSzlqQ6iGO/A0BE1H218FPto0AYAA6PZtrQGMKbf8JncT DLc4msP1QjThPT2bVftGbJG8WInBFYX/lMba4TOZPL00qtObKio+1PHna4V2txhHsRSr gMRSOqFJkdXqFzlzVeMafqPnyE1EHfA6U2pmwcj/8N3cYJYqv4zKd59Iq/3wOR4N/K73 BUtP/Tqac3UpsUphl3PXmhhVeBGEaNz0pTpqH6VjuecmS4Yj9/GDk51uGXUyfyvP3Lll KfazbLnLq1SX+Lbk4f11CzM6B33nd2FSEDKZuFM3wqXyRDAMZ4Jjj9zeel5Y04o7uSwo q7lg==
MIME-Version: 1.0
X-Received: by 10.180.72.239 with SMTP id g15mr637511wiv.45.1391793500595; Fri, 07 Feb 2014 09:18:20 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Fri, 7 Feb 2014 09:18:20 -0800 (PST)
In-Reply-To: <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com>
Date: Fri, 7 Feb 2014 09:18:20 -0800
X-Google-Sender-Auth: GjGUBxeXAnnwdOEUmK7HmlE7dRY
Message-ID: <CAJE_bqc5gpEEx-OkkXv0dtsTQ6pwYb9kkEzELfvszz30+tvCPg@mail.gmail.com>
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 17:18:23 -0000

At Thu, 6 Feb 2014 14:13:05 -0500,
Warren Kumari <warren@kumari.net> wrote:

> At time T+3 the child sees that the parent has published the new key
> information ( and the standard keyroll stuff has all happened (records
> are signed with new key, waited for old TTLs to expire, etc)) and so
> wants to remove the old key.
> ** This is, as far as I understand, what you were  asking about)

Yes, and...

> The child now publishes just the new key info. They stop publishing the old one.
> Parent:
>   example.com. 300  IN DS 31589 8 1 123456......
>   example.com. 300  IN DS 31589 8 1 789ABC......
> Child:
>   example.com. 300  IN CDS 31589 8 1 789ABC......
> [ Child is only publishing new record / they stop publishing the old one ]
>
> At time T+4 the parent checks agin (it polls, the human clicks the
> button on the web page, some other trigger happens, etc):
> It sees that what the child has published does not match what the
> parent currently has, and so it copies the contents from the child.
> Parent:
>   example.com. 300  IN DS 31589 8 1 789ABC......
> Child:
>   example.com. 300  IN CDS 31589 8 1 789ABC......
> [ The child and parent are back in sync. The old key (123456...) is no
> longer in use anywhere. ]

...this makes sense, and actually matches what I first thought was the
intent of the draft.  With this clarification I guess my confusion
mainly came from the first sentence of Section 4.1:

   Absence of CDS / CDNSKEY in child signals "No change" to the current
   DS set.

Now I understand this is intended to mean "absence of CDS / CDNSKEY
*RRset*", i.e., absence of any CDS / CDNSKEY.  But it was not super
clear when I first read it and it could also mean the absence
(removal) of this CDS at time T+4

  example.com. 300  IN CDS 31589 8 1 123456......

maybe I was the only person who was confused about this, but it
wouldn't do any harm to clarify the wording.

My original question is now resolved, but I have now another about the
"absence of CDS / CDNSKEY"...

> This means that you can use this to update / replace / remove existing
> DS records (if you have keys A, B, C and D and want to stop using C,
> you simply publish A, B, D), but you cannot remove *all* DS records /
> go unsigned.

This is fine, but technically doesn't it contradict Section 3?

   The CDS / CDNSKEY record is published in the child zone and gives the
   child control of what is published for it in the parental zone.  The
   CDS / CDNSKEY RRset expresses what the child would like the DS RRset
   to look like after the change;

In that, technically, an empty CDS / CDNSKEY RRset should mean the DS
RRset at the parent should be empty.  I have no problem with treating
an empty set as an exception, but I think it would help if the draft
explains that more explicitly.

I'd also note that "absence of CDS" (or CDNSKEY) cannot happen once
one such RR is published, and it should mean something erroneous (most
likely an operation error at the child or a bug in its tool).  I think
it's worth noting in Section 4.1.

Finally, I'd suggest explicitly clarifying that CDS / CDNSKEY cannot
be used for a child from signed to unsigned (since it would have to
remove all CDS / CDNSKEY records to do so).  And, I suspect this is a
"MUST NOT", unlike the case of initial enrollment described in Section
9, because this would break interoperability.

--
JINMEI, Tatuya

From dougb@dougbarton.us  Fri Feb  7 10:12:38 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2931ACCEC for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.237
X-Spam-Level: 
X-Spam-Status: No, score=-2.237 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YSC0GPVbNxFv for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:12:37 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id A266B1A01B0 for <dnsop@ietf.org>; Fri,  7 Feb 2014 10:12:37 -0800 (PST)
Received: from [192.168.0.20] (home [12.207.105.210]) by dougbarton.us (Postfix) with ESMTPSA id 7AFFA22B2A; Fri,  7 Feb 2014 18:12:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1391796757; bh=VAkzEBIWloY0CZLb4IK5XoiHkmDolm5jx32mRsIP5lo=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=LarypBGs/oekN0wihd+ircYsg2ifposBSvbcEG7TDD0D0IPQiIsmpThRjAdfeG14N 7oOvGm0HYRjbJqLRNfyhpcYWDZG2fwU05Sb0eD5r83fXdJ+r3QyTw7pW6wYQ1AjKY8 qwcprjQFbrvVouwJ/5dylbVy95CVD9u3GaPa3r2Y=
Message-ID: <52F52215.9090709@dougbarton.us>
Date: Fri, 07 Feb 2014 10:12:37 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com>
In-Reply-To: <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 18:12:38 -0000

On 02/06/2014 11:13 AM, Warren Kumari wrote:
> This means that you can use this to update / replace / remove existing
> DS records (if you have keys A, B, C and D and want to stop using C,
> you simply publish A, B, D), but you cannot remove*all*  DS records /
> go unsigned.

If we're willing to allow zones to go from unsigned to signed via CDS, 
why not go from signed to unsigned? Both situations represent DOS 
vectors via MITM.

Doug


From warren@kumari.net  Fri Feb  7 10:14:41 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE3DB1ACC8B for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bR4odbYWS255 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:14:40 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2F7FC1ACCE4 for <dnsop@ietf.org>; Fri,  7 Feb 2014 10:14:40 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id l18so2478206wgh.11 for <dnsop@ietf.org>; Fri, 07 Feb 2014 10:14:39 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ZqD28IzAFH6ZFLZQoinvFAUANvbbi8J+hpLzXq2pCRk=; b=elxzYZ37mwOHnJtxfEluzsEtfaPeCVqPREXNK4vvnBOPoZr5YFK3tETj8gm8wm5zf9 YM/GjYPyGy8t9T6/95zAp5aILXDHzLF2p0vbwhUC3x4SQQ5W/2LCegPYRrQkmsqsJ0xa auZfKM1sFn6fFZTX6CKXtI1xqY19krVe4m1ujY/FRt12t52JqWJvN315s2Zl1UaEuQIv CXOo+eIDl/KNM693cnznKqPmMfu2NB8lm6y9mXm5AqinOe3pBmytpw+V5n6I+xZp8ScB N3QLSqIdYrd0+hkdOGqMuwnM2XLGWON5BwuU4+PtFNk93MGuMlGqh9fySayH2sOhBru4 SfdA==
X-Gm-Message-State: ALoCoQljq9OmqNyFgdQ8t4WmzzVUBbRPmumHvx34smb8XI+u0PMtXDl+o8mXPfaMj6jgMrDPbmVB
MIME-Version: 1.0
X-Received: by 10.180.19.65 with SMTP id c1mr830338wie.39.1391796879584; Fri, 07 Feb 2014 10:14:39 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Fri, 7 Feb 2014 10:14:39 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <52F52215.9090709@dougbarton.us>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <52F52215.9090709@dougbarton.us>
Date: Fri, 7 Feb 2014 13:14:39 -0500
Message-ID: <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 18:14:41 -0000

On Fri, Feb 7, 2014 at 1:12 PM, Doug Barton <dougb@dougbarton.us> wrote:
> On 02/06/2014 11:13 AM, Warren Kumari wrote:
>>
>> This means that you can use this to update / replace / remove existing
>> DS records (if you have keys A, B, C and D and want to stop using C,
>> you simply publish A, B, D), but you cannot remove*all*  DS records /
>> go unsigned.
>
>
> If we're willing to allow zones to go from unsigned to signed via CDS, why
> not go from signed to unsigned? Both situations represent DOS vectors via
> MITM.

We are not allowing zones to go from unsigned to signed:
"This document does not address the initial configuration of trust
anchors for a domain."
and
"While it may be tempting, this SHOULD NOT be used for initial
enrollment of keys since there is no way to ensure that the initial
key is the correct one. If is used, strict rules for inclusion of keys
like hold down times, challenge data inclusion etc., ought to be used,
along with some kind of challenge mechanism."

W

>
> Doug
>

From dougb@dougbarton.us  Fri Feb  7 10:18:48 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B8C01ACCE4 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JpbDOY3VZlOx for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:18:47 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 30F671ACC80 for <dnsop@ietf.org>; Fri,  7 Feb 2014 10:18:47 -0800 (PST)
Received: from [192.168.0.20] (home [12.207.105.210]) by dougbarton.us (Postfix) with ESMTPSA id 18BF222B2A; Fri,  7 Feb 2014 18:18:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1391797127; bh=ZalmjhdfPFmLRVV+M1TsX2YpliTfMqrfNbI1B1X5//8=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=g/Jj00MjxDJGRNSpK3KLzcC7mZH93uE541jlgENxsVH0AdFkLvnDppgFsbaQKOadr 6YaWNLmyJJFkMsOy0RbcO3ovPS7V2+/cVVMUxTq1nqWaBcIUYDpaSosOIBfXvQsVqv 0bhDc7ssMl5UoCiSDnIEtpemDtly0I+I3IBt0SM4=
Message-ID: <52F52386.4070305@dougbarton.us>
Date: Fri, 07 Feb 2014 10:18:46 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com>	<CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com>	<52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com>
In-Reply-To: <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 18:18:48 -0000

On 02/07/2014 10:14 AM, Warren Kumari wrote:
> On Fri, Feb 7, 2014 at 1:12 PM, Doug Barton <dougb@dougbarton.us> wrote:
>> On 02/06/2014 11:13 AM, Warren Kumari wrote:
>>>
>>> This means that you can use this to update / replace / remove existing
>>> DS records (if you have keys A, B, C and D and want to stop using C,
>>> you simply publish A, B, D), but you cannot remove*all*  DS records /
>>> go unsigned.
>>
>>
>> If we're willing to allow zones to go from unsigned to signed via CDS, why
>> not go from signed to unsigned? Both situations represent DOS vectors via
>> MITM.
>
> We are not allowing zones to go from unsigned to signed:

Right, and because it says not to do it in the RFC no one is going to do 
it? :)

Doug


From ogud@ogud.com  Fri Feb  7 10:26:55 2014
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9703B1ACCE9 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:26:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9a7AttGesKz6 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:26:53 -0800 (PST)
Received: from smtp117.ord1c.emailsrvr.com (smtp117.ord1c.emailsrvr.com [108.166.43.117]) by ietfa.amsl.com (Postfix) with ESMTP id AB8C51ACCDE for <dnsop@ietf.org>; Fri,  7 Feb 2014 10:26:53 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 6A5411B80B0; Fri,  7 Feb 2014 13:26:53 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id C5EDF1B8083;  Fri,  7 Feb 2014 13:26:52 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <CAJE_bqc5gpEEx-OkkXv0dtsTQ6pwYb9kkEzELfvszz30+tvCPg@mail.gmail.com>
Date: Fri, 7 Feb 2014 13:26:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C96F9895-3B54-410A-A70E-1D7EF25FB6C0@ogud.com>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <CAJE_bqc5gpEEx-OkkXv0dtsTQ6pwYb9kkEzELfvszz30+tvCPg@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1510)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 18:26:55 -0000

On Feb 7, 2014, at 12:18 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:

> At Thu, 6 Feb 2014 14:13:05 -0500,
> Warren Kumari <warren@kumari.net> wrote:
>=20
>> At time T+3 the child sees that the parent has published the new key
>> information ( and the standard keyroll stuff has all happened =
(records
>> are signed with new key, waited for old TTLs to expire, etc)) and so
>> wants to remove the old key.
>> ** This is, as far as I understand, what you were  asking about)
>=20
> Yes, and...
>=20
>> The child now publishes just the new key info. They stop publishing =
the old one.
>> Parent:
>>  example.com. 300  IN DS 31589 8 1 123456......
>>  example.com. 300  IN DS 31589 8 1 789ABC......
>> Child:
>>  example.com. 300  IN CDS 31589 8 1 789ABC......
>> [ Child is only publishing new record / they stop publishing the old =
one ]
>>=20
>> At time T+4 the parent checks agin (it polls, the human clicks the
>> button on the web page, some other trigger happens, etc):
>> It sees that what the child has published does not match what the
>> parent currently has, and so it copies the contents from the child.
>> Parent:
>>  example.com. 300  IN DS 31589 8 1 789ABC......
>> Child:
>>  example.com. 300  IN CDS 31589 8 1 789ABC......
>> [ The child and parent are back in sync. The old key (123456...) is =
no
>> longer in use anywhere. ]
>=20
> ...this makes sense, and actually matches what I first thought was the
> intent of the draft.  With this clarification I guess my confusion
> mainly came from the first sentence of Section 4.1:
>=20
>   Absence of CDS / CDNSKEY in child signals "No change" to the current
>   DS set.
>=20
> Now I understand this is intended to mean "absence of CDS / CDNSKEY
> *RRset*", i.e., absence of any CDS / CDNSKEY.  But it was not super
> clear when I first read it and it could also mean the absence
> (removal) of this CDS at time T+4
>=20

Jinmei thanks for pointing this out=20
yes you are absolutely right and I have added the word "RRset" into this =
sentence.=20
I'm reading the rest of the document to make sure we are clear in all =
places=20
like this one.=20


>  example.com. 300  IN CDS 31589 8 1 123456......
>=20
> maybe I was the only person who was confused about this, but it
> wouldn't do any harm to clarify the wording.
>=20
> My original question is now resolved, but I have now another about the
> "absence of CDS / CDNSKEY"...
>=20
>> This means that you can use this to update / replace / remove =
existing
>> DS records (if you have keys A, B, C and D and want to stop using C,
>> you simply publish A, B, D), but you cannot remove *all* DS records /
>> go unsigned.
>=20
> This is fine, but technically doesn't it contradict Section 3?
>=20
>   The CDS / CDNSKEY record is published in the child zone and gives =
the
>   child control of what is published for it in the parental zone.  The
>   CDS / CDNSKEY RRset expresses what the child would like the DS RRset
>   to look like after the change;
>=20
> In that, technically, an empty CDS / CDNSKEY RRset should mean the DS
> RRset at the parent should be empty.  I have no problem with treating
> an empty set as an exception, but I think it would help if the draft
> explains that more explicitly.
>=20

Semantics semantics, =20
No we are defining the semantics to be "IF C* is published parent DS =
should mirror that,
if no C* in child --> parent has no action to perform"=20

> I'd also note that "absence of CDS" (or CDNSKEY) cannot happen once
> one such RR is published, and it should mean something erroneous (most
> likely an operation error at the child or a bug in its tool).  I think
> it's worth noting in Section 4.1

Why?
Here is a perfectly fine time line
<At start parent DS reflects key A and child uses A to sign DNSKEY =
RRset>=20

Child publishes CDS with A and B=20
Parent updates DS to reflect A and B=20
Child deletes CDS  =20

<child performs key roll over from A to B>=20

Child publishes CDNSKEY reflecting B=20
Parent changes DS to reflect only B=20
Child deletes CDNSKEY=20


Do you think it is helpful to add an appendix with some examples of use =
of C* records ?=20

> .
>=20
> Finally, I'd suggest explicitly clarifying that CDS / CDNSKEY cannot
> be used for a child from signed to unsigned (since it would have to
> remove all CDS / CDNSKEY records to do so).  And, I suspect this is a
> "MUST NOT", unlike the case of initial enrollment described in Section
> 9, because this would break interoperability.
>=20

In theory we can use C* to perform the Going-Unsigned operation, and =
earlier version of this
document proposed that, but people objected and we removed that text.=20
We explicitly outlaw going from Unsigned --> Signed w/o some out-of-band =
validation.=20

	Olafur



From muks@isc.org  Fri Feb  7 10:31:36 2014
Return-Path: <muks@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 054C91A044B for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:31:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kA2H1UbzLh_f for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:31:35 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:140:644b::225]) by ietfa.amsl.com (Postfix) with ESMTP id BC7A21A0203 for <dnsop@ietf.org>; Fri,  7 Feb 2014 10:31:34 -0800 (PST)
Received: from totoro.home.mukund.org (unknown [115.118.107.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 67E0BE60088; Fri,  7 Feb 2014 18:31:32 +0000 (GMT)
Date: Sat, 8 Feb 2014 00:01:27 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Warren Kumari <warren@kumari.net>
Message-ID: <20140207183127.GA32053@totoro.home.mukund.org>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG"
Content-Disposition: inline
In-Reply-To: <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop <dnsop@ietf.org>
Subject: [DNSOP] DNSKEY Flags vs. CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 18:31:36 -0000

--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi Warren

Did you see my reply to your email a few weeks ago where I asked why new
CDS/CDNSKEY RR types are required instead of adding a new bit to the
Flags field of the DNSKEY RR. Please can you look for my last email
which lists some advantages? There may be a good reason for it, but I
don't want you to miss considering it. :)

		Mukund

--OgqxwSJOaUobr8KG
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQgcBAEBCgAGBQJS9SZ8AAoJENJq4EOcI417999AAKiGAMBr6dGFktfjHUZZPU3o
tQiWqBsMdmlwOc6mz2z2imnhuwjgribad2AD3ma7fKuepyxitqyS3USbzKSBUDI/
5AIrdVd/8kRtUVwmmsPglivgODW6L6Fs4riA3DwsnLMPYIlv24FkDMnFqou6cIBV
xTH6eGio9NrUryiSwgPKuiNz1e5SDumq5TGtExv4gKD4b4RyeIiIp+hRe7lN47pc
sORV2eXw3s/20cJs8fJsWzE9HIirAMG5LdR9B7p3ptSFSNSlPSYWmJHLpXKCP5bt
GO9lpc0455VUTyR7DuyGWZWV8YDC83G+zyAjxolmEeD7B+UXfzkE5po8EfAQScWC
Yo6RS2qUxnnPcK/9lxYeDfk1n+A3+KVPBQffAEUMvVuHwYeUVFKWejMwKOOFeg/c
wz3OyUgqYHaMQ0ebw80dQF8t+BRVWLQ4Fdd/9MnhJf9S4AE//i39U9Lb2ymEfJtj
wGpPvrP2SDVVu/2M27hsLpF+ZQOTka3MZhb97Q37BNpY4ChaelwBXTloeqY6Ftai
K7gosVwTUU5Rv2h5lEjX+/KbVdt0enSRWfcq1bF+5oz1vWvqo8dhASQuzt2RiyiR
8PGHg+i0Pa7Q+Gvz5qmeaFTjErHAwQudIlejiWi/YX8K0KkrGmhiM3mz14vxqVXm
yUt6BHAm2wvHmfb0+zk7xbo0xRq+lWi9ydcXA/geh5Tf7VCbc1J0gdq6ol3HJXeV
H2HMdS7MKf6DUqfS63vGKVPHTpIkWCXEP4bll5SCe0yL6+IPZ1wSLPPgmjz2onkI
TmsfSlWaCnK981k+cTCKzUyJzLLDC+WyqAT/zjA2HWsBgJDXHQ5NwQ7+xIIVPOee
zrkFVUniEX7dSnWkqVqtfcqnXs5dkdYRE5tc3yOK4FC53nlRwZa3C8tMOYSyiW2U
ThlibsoilLU28RstHe2UpdoVd1aDGRD6CbPc9oMDRZMhZmaoFaC/tmmj8G+zIxp2
tStP5lvULxsF3IxfEqq9LEZRmqg2Bq+Nkl7nceWtVrg5lA8Ayz9OWvPV3opl2M3K
xkSEQW+N1rbG9VEOiKpR+q6JRVyysPVl3Ntreu15HpGlUOpcLSSgz8j7R9l9Pl34
+SApmdCjLpalirFmU9spXOyY1vaN7Ed8OlQieHl+sv2HQ7K/TdOBVD8lZbhuvZlb
0eRRTEwtXUS+8n4vUYgssSf8NScsAUKBF7r5L9mFKa6T+Y0uW/QSFb8PiUewrOJd
6JQ+O/t1fbr/deM2S9HuOzIo5Y2VFDQZe5Y0EHmWphMFzYXMn5z2Kmzt5EaQ3KGf
bjkQ6gt3omq5oh3aNTKC8ujFoYx/5gkBj3Z1xq4nuwD38ezJxwTGzJSAUyC3L0HO
gd+93wvf+d6G8Ie/hx+PQyA0WGU5gie1FtcP4mtEDXb5Q69scMaJZ7OW+wN/Rh1u
61Kr80nIk1PZWjO0mSrmLupPDG2rH7qIYq0/2+q93sCGktHA/EhzTofHfYmx0a0E
j2FwrWY6K28DlOClzF3LaX+mee9o/0+TNWgbQ92E4s9qoqXq+PIagVGfRDu02VuS
sj3ECxj0K/2z8Ddd2t4WwwuqGGXnBvXxo0KZb/pkVDl2d2HIVTo+AanUQwmdFi50
WNr8XOaNvf0yYNSityJEOm8edGN65oK8PNwDsQ9zdqfRCGbu+yuAph5m2QwlJ3Px
U3IYTWsS+8zvkMgS0i9eT/gGutBJauCaCGGpCwRd+chRLChYPp1VZqnt9McssSF3
2EevjtnPqD7dJKhcKNgtpVzmKejCCXZm6iZ/gzsEAqgftlMslsCzB2hV3HFqfPOB
s7zGkclVEbMtMUxvbcIfAxORdUWK8UM/+j41o3UoMCaQFwFrZeN20qFWqxPtGw9G
AGWkEFifJohIdVWvA56sVBt1NvxYJrKMro+hsHSh1U7qKxtYdrhhaAqSzI6YqGL4
9eddEh8CVeL5NsAuZJVRpaxRBsHNG0K8cBCTQ4X/g4sw4jvL2p2NMNHLdErIGUrF
JuFdMfvS/1CJ8uddswXaz0eABX3xTNt7Qql+L/DX0f/85w13ZyTjjeQTcVeynoLs
DLO723eLW9dXttYQE6c+CmX6cBfybozbIjjMHDAHw09hJkahRinboFJRxg6jZwqZ
PQuzpc2OcNTy4stCw6xmppDiY8Lt2mOnmzNwRhggqYnSO7VFkGIXOfT2VCx0ZY8L
edcQiDWvm8r8kCNoPuv5A4IZOu6dwTVk7mfJxc8V94mgtUU8gwTfnTqkjUZCGcHc
9F5nsUIBZfl3ByCwvrRnNdBOIWckjv5w2PxHNIh6TEH8b4G1x09G8YpdUUvEVlE/
3pBnYdFYwr6MSLA56/F0IfJCPgDPSTevyZJGQSKL6qtdU5WS+h6mzl2nK5i/e4ef
/RMkt4caqSzBAKT6f/xVl2SdeEga1hrolK31l++AsawKzLnZzxCj1HXxpG1Z7nyq
lIGJu9WTmJRC06/AexFUx94kSAG6zzBmaq2duxxxmv9K8Q7NCNEJ6a72NGtLUvqI
kO5pQsvIXMODVvVCqY94t6i/frigC026XmgWyv4ybarcyWLPp5WxzfZG50JwNmjS
XTwMZFGPd5riYnN9OrvXkiqTs5ZJjHOH3NKWDMI5nzlor2r3yfR1BSN5GrCuBVsK
p0hIgcDzqsLME1khUdbr8uKbtWgZ8LDS9C7Hjx8kxjtoAnmGIch8s9gQFu/oWTk2
WWr8U5vOn/kyMqhUUAvO
=vNqN
-----END PGP SIGNATURE-----

--OgqxwSJOaUobr8KG--

From warren@kumari.net  Fri Feb  7 10:43:41 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D40C1AC7F2 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zh7ee9jI3-5y for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 10:43:39 -0800 (PST)
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id 08BD81ACCF5 for <dnsop@ietf.org>; Fri,  7 Feb 2014 10:43:27 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hm4so1129754wib.14 for <dnsop@ietf.org>; Fri, 07 Feb 2014 10:43:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UmceSI0sBznbOVD59D2DU5/CWMOZvDiHUXwo6Aon2wI=; b=PWC2sukj5U3oriWghskk4TKls0Su9PkPuLmxYi0Opx7g/2CsHLrZlkrh5P9uGQqBEX Xef04oiA1TOvfMvpMxKzz+kWNx61jkzN8jiPtZnaVziHD//2V6e5d0GL/dtRQK1+AQPB 3es1RMFarUTvy0ztPy9V/HkXGW6WxE2QXdQZErg2P5QdhZ7kHWnQlSONaIsGpOE6s1rY yOidhE88w5SzElA+sCFvsENoVH5htgRHKGNHH9tswYKyMJ4pLhCAniKHJgl2YcDmm3S3 bMP1B/SpVo/qRLEX7bbYmU1PJGl/+7FQN1sFsFlT1sfcEfCoVI0Tde2/E9sg8/egvrSN 7u/A==
X-Gm-Message-State: ALoCoQm4T78l/Z2uk0+n5nLf+rL2Q8VrbXO0N6A6SYZyV0X9HsT5kqa0FNn3NB4TnCEyVtDqN6gC
MIME-Version: 1.0
X-Received: by 10.180.37.193 with SMTP id a1mr1011683wik.52.1391798607395; Fri, 07 Feb 2014 10:43:27 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Fri, 7 Feb 2014 10:43:27 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <CAJE_bqc5gpEEx-OkkXv0dtsTQ6pwYb9kkEzELfvszz30+tvCPg@mail.gmail.com>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <CAJE_bqc5gpEEx-OkkXv0dtsTQ6pwYb9kkEzELfvszz30+tvCPg@mail.gmail.com>
Date: Fri, 7 Feb 2014 13:43:27 -0500
Message-ID: <CAHw9_iJ-_UBzqjgMU9MG-o7afV_jSshX9CZPKxN0X_4n_G0tQw@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 18:43:41 -0000

On Fri, Feb 7, 2014 at 12:18 PM, $B?@L@C#:H(B <jinmei@wide.ad.jp> wrote:
> At Thu, 6 Feb 2014 14:13:05 -0500,
> Warren Kumari <warren@kumari.net> wrote:
>
>> At time T+3 the child sees that the parent has published the new key
>> information ( and the standard keyroll stuff has all happened (records
>> are signed with new key, waited for old TTLs to expire, etc)) and so
>> wants to remove the old key.
>> ** This is, as far as I understand, what you were  asking about)
>
> Yes, and...
>
>> The child now publishes just the new key info. They stop publishing the old one.
>> Parent:
>>   example.com. 300  IN DS 31589 8 1 123456......
>>   example.com. 300  IN DS 31589 8 1 789ABC......
>> Child:
>>   example.com. 300  IN CDS 31589 8 1 789ABC......
>> [ Child is only publishing new record / they stop publishing the old one ]
>>
>> At time T+4 the parent checks agin (it polls, the human clicks the
>> button on the web page, some other trigger happens, etc):
>> It sees that what the child has published does not match what the
>> parent currently has, and so it copies the contents from the child.
>> Parent:
>>   example.com. 300  IN DS 31589 8 1 789ABC......
>> Child:
>>   example.com. 300  IN CDS 31589 8 1 789ABC......
>> [ The child and parent are back in sync. The old key (123456...) is no
>> longer in use anywhere. ]
>
> ...this makes sense, and actually matches what I first thought was the
> intent of the draft.  With this clarification I guess my confusion
> mainly came from the first sentence of Section 4.1:
>
>    Absence of CDS / CDNSKEY in child signals "No change" to the current
>    DS set.
>
> Now I understand this is intended to mean "absence of CDS / CDNSKEY
> *RRset*", i.e., absence of any CDS / CDNSKEY.  But it was not super
> clear when I first read it and it could also mean the absence
> (removal) of this CDS at time T+4
>
>   example.com. 300  IN CDS 31589 8 1 123456......
>
> maybe I was the only person who was confused about this, but it
> wouldn't do any harm to clarify the wording.
>

Yup, the wording was unclear / ambiguous.
I tried "The absence of *any* CDS..." but that was also unclear. I
also tried "Absence of a CDS / CDNSKEY *RRset* in child...", but ended
up settling on:
"If there are no CDS / CDNSKEY resource records in the child, this
signals that no change should be made to the current DS set. This
means that, once the child and parent are in sync, the child DNS
operator MAY remove all CDS records from the zone."
It this better?


> My original question is now resolved, but I have now another about the
> "absence of CDS / CDNSKEY"...
>
>> This means that you can use this to update / replace / remove existing
>> DS records (if you have keys A, B, C and D and want to stop using C,
>> you simply publish A, B, D), but you cannot remove *all* DS records /
>> go unsigned.
>
> This is fine, but technically doesn't it contradict Section 3?
>
>    The CDS / CDNSKEY record is published in the child zone and gives the
>    child control of what is published for it in the parental zone.  The
>    CDS / CDNSKEY RRset expresses what the child would like the DS RRset
>    to look like after the change;
>
> In that, technically, an empty CDS / CDNSKEY RRset should mean the DS
> RRset at the parent should be empty.
>  I have no problem with treating
> an empty set as an exception, but I think it would help if the draft
> explains that more explicitly.

Yup. I'm currently trying to craft text to that effect. Unfortunately
I'm having a hard time doing so cleanly.
I've just added "An empty CDS / CDNSKEY RRset means that no change is
needed." in my edit buffer, but I'm unclear on something -- is an
empty RRset the same as a non-existing RRset? I *think* it is, but it
somehow feels weird...

>
> I'd also note that "absence of CDS" (or CDNSKEY) cannot happen once
> one such RR is published, and it should mean something erroneous (most
> likely an operation error at the child or a bug in its tool).  I think
> it's worth noting in Section 4.1.

Um, I think I'm confused now.
Absence of CDS / CDNSKEY can happen. The child just stops including
CDS / CDNSKEY records in their zone - this signals "No change", and is
a special case.

Some background / justification for this:
Let's say that example.com is a company that sells Examples for use in
presentations. They have a few departments (accounting, sales and
development) who each run their own DNS servers, and currently have
the following in their zone:

accounting.example.com IN DS 1 1 12345...
sales.example.com   IN DS 1 1 6789....
development.example.com IN DS 1 1 ABCD123...

The IT group (who runs the main example.com nameservers) get tired of
each department rolling keys and asking for their DS to be updated, so
they decided to start using CDS for this. They mail the DNS person in
each department and say "Starting April 1st we will be supporting CDS,
so you can manage your own stinking DS records without us having to do
any work".

The accounting and development groups read this, shout "Yay!, no more
having to deal with the rude IT folk", and start publishing CDS
records.
The folk in the sales group are wither off playing golf, or see the
April 1st date and figure it's a very subtle joke. Anyway, they don't
bother publishing a CDS record....

If the "Empty CDS / CDSKEY RRset == no change" rule did NOT exist (or
if "Empty CDS / CDSKEY RRset" meant please go unsigned), what would
happen would be that, on April 1st the IT group would turn on some
home grown CDS tool. It would go off and look at all the child zones.
If would be happy with accounting,example.com and
development.example.com. For sales it would see no CDS record, and so
would "helpfully" remove all DS records, making the sales.exmaple.com
zone be unsigned.

Yes, there could be all sorts of logic built into the tool to keep
state / a record of which zones had opted into using CDS / CDNSKEY,
but this is a: error prone and b: requires state on the parent.


>
> Finally, I'd suggest explicitly clarifying that CDS / CDNSKEY cannot
> be used for a child from signed to unsigned (since it would have to
> remove all CDS / CDNSKEY records to do so).  And, I suspect this is a
> "MUST NOT", unlike the case of initial enrollment described in Section
> 9, because this would break interoperability.

I just added:
"While it may be tempting, this SHOULD NOT be used for initial
enrollment of keys since there is no way to ensure that the initial
key is the correct one. If is used, strict rules for inclusion of keys
like hold down times, challenge data inclusion etc., ought to be used,
along with some kind of challenge mechanism. A child cannot use this
mechanism to go from signed to unsigned (publishing an empty CDS /
CDNSKEY RRset means no-change should be made in the parent)."

Is this clear? I suspect I'm missing some subtleties here.

W



> --
> JINMEI, Tatuya

From jabley@hopcount.ca  Fri Feb  7 11:10:39 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A4F1ACCDE for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DX2x5Z-hfcyO for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:10:33 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 774381A0601 for <dnsop@ietf.org>; Fri,  7 Feb 2014 11:10:33 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id e14so1925084iej.4 for <dnsop@ietf.org>; Fri, 07 Feb 2014 11:10:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=U8OizpSxGOvM3xnPbQI5FEvy3c182UJe9HBLitXeKzU=; b=c84+YSmwxI2tMTw8rYBWqxs5QnoblI8RtQEpcJlUAvNXOpCbvi/3HSRxDDeLKMwjPl 6U9INY19TLi1qTPbUISKUrEeicDjG27tgxaz7dp/kHY6jiVjDEFWpY5MGn9hxfoZVqEb iJ4gYvmL24C3SxesAoTF4fKj5JgpyYzBWgXw0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=U8OizpSxGOvM3xnPbQI5FEvy3c182UJe9HBLitXeKzU=; b=IOLCxEcOVqUWOZNEaaPkBkrtTXFBzkxk3WNQdgzMwSCvomMVH4RZd5tjywetL9z/RG XaHO6llGCCXGJltJl+ESnJvoElNyTXYPqsIEl9B7o4HRyEopJmQivzW/qZAZeLPGO8q0 CPLvOkc5bRt9hwER3imOZWM7m3WOXpV4cMSBVo5MoSUV5cDWUzH5zLL3uMBvHQl+kBDe ZXrwyF3y7TJAU/OsP8g7LEob2gGcVnaKh7W9HRWrvw50jAlpGr3KREkYxaZHqouHiuR6 T5saLI6dJUowTV84+/55pN+6jpj1snQyJKqCSnB8ABmCdLnl8knALjlHzu4C7EWX2HR/ 8GEA==
X-Gm-Message-State: ALoCoQnIeb+SMwGSOqwUsfe6yf5Ms8NIuHHhpIxv/gH8BRPp1gBkvHEtXe1QnUKHQTfQZonwQOLd
X-Received: by 10.43.69.83 with SMTP id yb19mr5043136icb.45.1391800233284; Fri, 07 Feb 2014 11:10:33 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:94eb:1bb3:5e14:75f3? ([2001:4900:1042:1:94eb:1bb3:5e14:75f3]) by mx.google.com with ESMTPSA id h6sm12438206igy.8.2014.02.07.11.10.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 11:10:31 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_18E48C83-CF9E-4EDF-8A25-6537F589DF26"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20140207183127.GA32053@totoro.home.mukund.org>
Date: Fri, 7 Feb 2014 14:10:30 -0500
Message-Id: <0EE47BB3-678A-423A-AAD9-798B3CE61593@hopcount.ca>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com> <20140207183127.GA32053@totoro.home.mukund.org>
To: Mukund Sivaraman <muks@isc.org>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] DNSKEY Flags vs. CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 19:10:39 -0000

--Apple-Mail=_18E48C83-CF9E-4EDF-8A25-6537F589DF26
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-02-07, at 13:31, Mukund Sivaraman <muks@isc.org> wrote:

> Did you see my reply to your email a few weeks ago where I asked why =
new
> CDS/CDNSKEY RR types are required instead of adding a new bit to the
> Flags field of the DNSKEY RR. Please can you look for my last email
> which lists some advantages? There may be a good reason for it, but I
> don't want you to miss considering it. :)

The apex of a signed child zone already contains a DNSKEY RRSet, and =
that whole RRSet is retrieved by validators who want to validate =
signatures within the child zone.

Adding extra RRs to that set would inflate the response sizes towards =
those validators with information that is of no practical benefit to =
them.

Putting those extra RRs in a different RRSet (CDNSKEY) means they can be =
explicitly retrieved by clients (provisioningware of parents, or =
parental agents) who need them, without sending them to other clients =
unnecessarily.

We are, I think, more comfortable with large responses in 2014 than we =
were in 2010 (at least, we are more comfortable that there are not =
hideous, fireball-type consequences) but I don't think we should be in =
the business of inflating responses for no reason.

Also, reflection attacks, amplification potential.


Joe

--Apple-Mail=_18E48C83-CF9E-4EDF-8A25-6537F589DF26
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlL1L6YACgkQNI8MvYZSOiz92ACgqGeZN7zatWIaGWdzevJRjQXh
KRYAnjdUfzDWybBFxFISh0coUAZoq9Qd
=QwMo
-----END PGP SIGNATURE-----

--Apple-Mail=_18E48C83-CF9E-4EDF-8A25-6537F589DF26--

From jabley@hopcount.ca  Fri Feb  7 11:12:04 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A6371ACCF8 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:12:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CEvRu35JVBHw for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:12:02 -0800 (PST)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D321C1ACCEF for <dnsop@ietf.org>; Fri,  7 Feb 2014 11:12:02 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id ar20so1836647iec.6 for <dnsop@ietf.org>; Fri, 07 Feb 2014 11:12:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=A65gtCINO1b9jw6wdzZh4HCKqExy0csUpfIciBVpqMg=; b=IA8Ag4n+LzlNHRBJbBLXCKzinM5+qYf20msT1qM03/huoL8nX8uBEvk3G14JII+Cdw NCUom7w8PBrE9c6z5aoHRRndCPDi6/Fme4+rOaEe7nVYVbMt6inNfWQQosCTIaYxJT/2 7OutzmYZ9+VqJ2Lzs6O7/fFo8Ixa+zVGYNxMQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=A65gtCINO1b9jw6wdzZh4HCKqExy0csUpfIciBVpqMg=; b=CsNW3z7sstputuxQ5xJZ3brRuzF5A9g3AdVtkkRq5fggjzojTy/mtnOG/vik/Ch5hD dpiQvgyfeaNIueAiUx8kU8w6ZcDMHxZ0nDcCjp++aV8nU2IjcfVjmCBWdBS5X5u3ABp+ h67He43EonrTeKkqxXw4Pv3gmzY7u66jj9oPTpSC2IHNUjuiAkXI9yJtFHD/6l+CAj7V Cs1gTzcwaUAVsDDoQmNkeB/RENUDVVkWF7ak6GcREbztwI5RFlgZoBY13uRDH5ejgIu8 FhPOWXXXVDxkCQmLI8PKrVz28Jt4TJMrROSSFL0bndt9A3TV2rgqhPQtVIYslMQq6vNR srUg==
X-Gm-Message-State: ALoCoQlAgBwZFrFLg7kAY+Xrnvyl5APcZBuBGGjRAPVS2PZU9iXlHizvPHmuoKsxU5CCwxv1rvnJ
X-Received: by 10.42.53.10 with SMTP id l10mr5189346icg.33.1391800322670; Fri, 07 Feb 2014 11:12:02 -0800 (PST)
Received: from [199.212.90.58] (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id l7sm12499555igx.2.2014.02.07.11.12.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 11:12:01 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_2B294060-FF31-4390-8760-DDF4497B9D81"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <52F52386.4070305@dougbarton.us>
Date: Fri, 7 Feb 2014 14:12:00 -0500
Message-Id: <0D3FD7ED-0A92-4B8E-9619-2B7D84013DD6@hopcount.ca>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com>	<CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com>	<52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com> <52F52386.4070305@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 19:12:04 -0000

--Apple-Mail=_2B294060-FF31-4390-8760-DDF4497B9D81
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-02-07, at 13:18, Doug Barton <dougb@dougbarton.us> wrote:

> On 02/07/2014 10:14 AM, Warren Kumari wrote:
>=20
>> We are not allowing zones to go from unsigned to signed:
>=20
> Right, and because it says not to do it in the RFC no one is going to =
do it? :)

I don't see how it would work. The parental agent has no automated way =
to trust the C* RRSets published in a zone with no secure delegation =
from its parent.


Joe


--Apple-Mail=_2B294060-FF31-4390-8760-DDF4497B9D81
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlL1MAAACgkQNI8MvYZSOiwGMwCfR4OOUx4ryM5gKk77L6jChdxO
c9EAnRYkj1lA7Dj3HSUWKmbwJlOV0h4f
=RYgP
-----END PGP SIGNATURE-----

--Apple-Mail=_2B294060-FF31-4390-8760-DDF4497B9D81--

From warren@kumari.net  Fri Feb  7 11:22:38 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5D331ACCFF for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:22:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lnHRmkO07K4L for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:22:37 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id C71D11A01D2 for <dnsop@ietf.org>; Fri,  7 Feb 2014 11:22:36 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hm4so1166747wib.1 for <dnsop@ietf.org>; Fri, 07 Feb 2014 11:22:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tAdRGGeYbsIge8D7BsA6TqXuDCMFKNBLMtc0kG6la0g=; b=IbDcEjjX6Ej063CAuOfvE+xg8wSflbML5mFtw8kgVKaq6Chs3Qz5Os9ga/dp0kppwb YBEmaDa91iKR/2NLhOt8FXuLu59Xw/6oANZh8Dj+v83Mm4YPUMYC9zVMbYDaXk8ItND4 fRNZ1sRah2rrrJdO9saTUmjciV+PwX3pTOLgtN+c5YDFTJOL+em8CvvnYTQb2vNzxr/c OGnTj6t+dBr2n7Or6bdqmmHrbn87BeIy3R2rzbwRk/M5ISuUHG3YFuDz1bwiLBGBx1SU Ia6N4BoUaEhKNNAxumbkZXK85IusTsMkndv8B8EB7EzbwADI8BfBiHrS/0Rf2pfbd544 pomw==
X-Gm-Message-State: ALoCoQnIwsahByuFlg/vWfhJK9pwbiXe/jROlPDSiTJYJ2ZnpGl70ThAP+5ODco56QTOWTNXusac
MIME-Version: 1.0
X-Received: by 10.194.58.180 with SMTP id s20mr3307634wjq.54.1391800956113; Fri, 07 Feb 2014 11:22:36 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Fri, 7 Feb 2014 11:22:36 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <0D3FD7ED-0A92-4B8E-9619-2B7D84013DD6@hopcount.ca>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com> <52F52386.4070305@dougbarton.us> <0D3FD7ED-0A92-4B8E-9619-2B7D84013DD6@hopcount.ca>
Date: Fri, 7 Feb 2014 14:22:36 -0500
Message-ID: <CAHw9_iLw6+php0bNg4UTm0z2Xf8Luzbx-TRC8xxZBKvGcgz+ew@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 19:22:39 -0000

On Fri, Feb 7, 2014 at 2:12 PM, Joe Abley <jabley@hopcount.ca> wrote:
>
> On 2014-02-07, at 13:18, Doug Barton <dougb@dougbarton.us> wrote:
>
>> On 02/07/2014 10:14 AM, Warren Kumari wrote:
>>
>>> We are not allowing zones to go from unsigned to signed:
>>
>> Right, and because it says not to do it in the RFC no one is going to do it? :)
>
> I don't see how it would work. The parental agent has no automated way to trust the C* RRSets published in a zone with no secure delegation from its parent.
>
No no no... You don't see how it would work *securely*.

We actually say:
"While it may be tempting, this SHOULD NOT be used for initial
enrollment of keys since there is no way to ensure that the initial
key is the correct one. If is used, strict rules for inclusion of keys
like hold down times, challenge data inclusion etc., ought to be used,
along with some kind of challenge mechanism. "

The thought behind this was that an unsigned child *could* start
publishing a CDS / CDSNKEY record. The child would then "securely,
through some out of band mechanism" (hand wave, hand wave) contact the
parent and they would agree that this is the correct key and the
parent would then manually include it. Please note that A: we say
don't do this, B: the hand-wave, and c: the fact that we are not
specifying how this should happen.

W



>
> Joe
>

From jabley@hopcount.ca  Fri Feb  7 11:56:33 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 407DA1AD0EA for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:56:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kearbSacRtko for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 11:56:28 -0800 (PST)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id EA4F61ACCDF for <dnsop@ietf.org>; Fri,  7 Feb 2014 11:56:27 -0800 (PST)
Received: by mail-ie0-f180.google.com with SMTP id at1so1961054iec.11 for <dnsop@ietf.org>; Fri, 07 Feb 2014 11:56:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=aGBZLQ5MP58tBrJOy/jxBIhUuqXwJh/8xUDocXkBui0=; b=DRaRCF17rbdn94LsyJv7trNEbSnxCDSr0M6uJpSAMeug5yfjcTMfFQYkqVZB5ZUPq+ zYyrKvyzh4zRP+GWJXl0ofEWkhqF4YU5cqL12qd5shruEhoe9HL5/Idb5BHG4G1kbSiQ xdVur2gD2opmsCMzjU2ljtbvlFAXB/maj8HRQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=aGBZLQ5MP58tBrJOy/jxBIhUuqXwJh/8xUDocXkBui0=; b=UbXg0G0SCrz/VQnbxoejSHPyzIAg94/w+k+bF/neq43DVpOoByOr+Z/ciAxVFqPcbf bZ0vdyFZCxt8VfXJm6k3onY09tytrg1Wr/Xt5SwlBQXsViMrwy8LSt3EcVh6vP0GFKTj 2Mmo/a7Ky2upNUMMoR3aZPStZtmFCU4YixX59LchWzfusxHOiTv0wME85ynvp26bD5AH tQFyyyeuJ20BkABm7JnwC0bCLUqcpy+fkza8rvoGeIigU75kKH0NwpJqZgc4IsDnoHob zkCxIgc22BjNfkL53bZRAhzndkWEz9VJl8WQe5BIR5SosxcJ/WbCsUU4caKchjh6LK5w 102A==
X-Gm-Message-State: ALoCoQnIbGRrnm4HrhnrolK4niyBRt/mfTAPArxmjpx/L1lUE/coVdeGw/7f2Ym5pbo/YSBPaO2o
X-Received: by 10.43.153.138 with SMTP id la10mr8954263icc.10.1391802987737; Fri, 07 Feb 2014 11:56:27 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:94eb:1bb3:5e14:75f3? ([2001:4900:1042:1:94eb:1bb3:5e14:75f3]) by mx.google.com with ESMTPSA id z5sm12880544igw.0.2014.02.07.11.56.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 11:56:26 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_F7624359-B49E-45E6-B0BB-F97198D97BB6"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <CAHw9_iLw6+php0bNg4UTm0z2Xf8Luzbx-TRC8xxZBKvGcgz+ew@mail.gmail.com>
Date: Fri, 7 Feb 2014 14:56:24 -0500
Message-Id: <3F1E65D0-BD09-4465-8D94-EB601420C07B@hopcount.ca>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com> <52F52386.4070305@dougbarton.us> <0D3FD7ED-0A92-4B8E-9619-2B7D84013DD6@hopcount.ca> <CAHw9_iLw6+php0bNg4UTm0z2Xf8Luzbx-TRC8xxZBKvGcgz+ew@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 19:56:33 -0000

--Apple-Mail=_F7624359-B49E-45E6-B0BB-F97198D97BB6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 2014-02-07, at 14:22, Warren Kumari <warren@kumari.net> wrote:

> On Fri, Feb 7, 2014 at 2:12 PM, Joe Abley <jabley@hopcount.ca> wrote:
>=20
>> On 2014-02-07, at 13:18, Doug Barton <dougb@dougbarton.us> wrote:
>>=20
>>> On 02/07/2014 10:14 AM, Warren Kumari wrote:
>>>=20
>>>> We are not allowing zones to go from unsigned to signed:
>>>=20
>>> Right, and because it says not to do it in the RFC no one is going =
to do it? :)
>>=20
>> I don't see how it would work. The parental agent has no automated =
way to trust the C* RRSets published in a zone with no secure delegation =
from its parent.
>=20
> No no no... You don't see how it would work *securely*.

Fair enough. I had taken that as a given, but you're right, it makes =
sense to spell it out.


Joe


--Apple-Mail=_F7624359-B49E-45E6-B0BB-F97198D97BB6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlL1OmgACgkQNI8MvYZSOiwHYwCeP2Rxm8gT5R0FE4Vt+xp50aje
dNwAoKVET3znuvogqMs4tpKwjkSswyLy
=mZhO
-----END PGP SIGNATURE-----

--Apple-Mail=_F7624359-B49E-45E6-B0BB-F97198D97BB6--

From paul@cypherpunks.ca  Fri Feb  7 15:31:03 2014
Return-Path: <paul@cypherpunks.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C561A0566 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 15:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJuL3azuT951 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 15:31:01 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id B6B601A0444 for <dnsop@ietf.org>; Fri,  7 Feb 2014 15:31:01 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 8E004800C0; Fri,  7 Feb 2014 18:31:00 -0500 (EST)
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s17NUxqL019364; Fri, 7 Feb 2014 18:31:00 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Fri, 7 Feb 2014 18:30:59 -0500 (EST)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Mukund Sivaraman <muks@isc.org>
In-Reply-To: <20140207183127.GA32053@totoro.home.mukund.org>
Message-ID: <alpine.LFD.2.10.1402071829350.28278@bofh.nohats.ca>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com> <20140207183127.GA32053@totoro.home.mukund.org>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] DNSKEY Flags vs. CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 23:31:03 -0000

On Sat, 8 Feb 2014, Mukund Sivaraman wrote:

> Did you see my reply to your email a few weeks ago where I asked why new
> CDS/CDNSKEY RR types are required instead of adding a new bit to the
> Flags field of the DNSKEY RR.

That does not allow prepublishing of DS records for DNSKEY's not
published in the zone yet, which is a strategy for publishing an
emergency rollover key at the parent in case of a compromise of
the signer. This key can be completely offline and even the public
key part unknown to any party.

Paul

From ogud@ogud.com  Fri Feb  7 15:46:13 2014
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 824CF1AD739 for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 15:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agUPoX_FL0ac for <dnsop@ietfa.amsl.com>; Fri,  7 Feb 2014 15:46:11 -0800 (PST)
Received: from smtp69.ord1c.emailsrvr.com (smtp69.ord1c.emailsrvr.com [108.166.43.69]) by ietfa.amsl.com (Postfix) with ESMTP id C36281AD72A for <dnsop@ietf.org>; Fri,  7 Feb 2014 15:46:11 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 139571483F1; Fri,  7 Feb 2014 18:46:07 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 64F7A148467;  Fri,  7 Feb 2014 18:46:06 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <20140207183127.GA32053@totoro.home.mukund.org>
Date: Fri, 7 Feb 2014 18:46:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <52FF9BF5-30BD-48C3-B2AC-A35818C24FC2@ogud.com>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <52F52215.9090709@dougbarton.us> <CAHw9_i+Aanz5NZVO5Q_x=1zyFzHZSmeU6yoLx3cDkwD2sC-XMA@mail.gmail.com> <20140207183127.GA32053@totoro.home.mukund.org>
To: Mukund Sivaraman <muks@isc.org>
X-Mailer: Apple Mail (2.1510)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] DNSKEY Flags vs. CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 23:46:13 -0000

On Feb 7, 2014, at 1:31 PM, Mukund Sivaraman <muks@isc.org> wrote:

> Hi Warren
>=20
> Did you see my reply to your email a few weeks ago where I asked why =
new
> CDS/CDNSKEY RR types are required instead of adding a new bit to the
> Flags field of the DNSKEY RR. Please can you look for my last email
> which lists some advantages? There may be a good reason for it, but I
> don't want you to miss considering it. :)
>=20

We considered it but there are drawbacks including:
- changing a flag on a DNSKEY record means the key footprint and hash of =
key change, so matching=20
  a key after a change in flags is hard for parents as they do not know =
which flag was changed.=20
- Publishing a future TA in the DNSKEY set makes the DNSKEY RRset larger=20=


There are advantages to the new RR types=20
- CDS allows the publication of a new Trust Anchor without exposing the =
public key of the new trust anchor=20
- Putting a new key in a different RRset keeps DNSKEY smaller=20
- less chance of confusion by parents.=20

So in short we considered it and rejected that approach.=20

	Olafur



From internet-drafts@ietf.org  Fri Feb  7 16:01:38 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4261AD72A; Fri,  7 Feb 2014 16:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TClrwYT6BN3Y; Fri,  7 Feb 2014 16:01:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2461AD739; Fri,  7 Feb 2014 16:01:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140208000130.26677.92507.idtracker@ietfa.amsl.com>
Date: Fri, 07 Feb 2014 16:01:30 -0800
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Feb 2014 00:01:38 -0000

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

        Title           : Automating DNSSEC delegation trust maintenance
        Authors         : Warren Kumari
                          Olafur Gudmundsson
                          George Barwood
	Filename        : draft-ietf-dnsop-delegation-trust-maintainance-03.txt
	Pages           : 18
	Date            : 2014-02-07

Abstract:
   This document describes a method to allow DNS operators to more
   easily update DNSSEC Key Signing Keys using DNS as communication
   channel.  This document does not address the initial configuration of
   trust anchors for a domain.  The technique described is aimed at
   delegations in which it is currently hard to move information from
   the child to parent.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintainance/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-delegation-trust-maintainance-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-delegation-trust-maintainance-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From jinmei@wide.ad.jp  Sat Feb  8 10:59:36 2014
Return-Path: <jinmei@wide.ad.jp>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 615AC1A055C for <dnsop@ietfa.amsl.com>; Sat,  8 Feb 2014 10:59:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.081
X-Spam-Level: 
X-Spam-Status: No, score=0.081 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, NML_ADSP_CUSTOM_MED=0.9, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uu-qyPMp-2v0 for <dnsop@ietfa.amsl.com>; Sat,  8 Feb 2014 10:59:33 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id D5F061A0451 for <dnsop@ietf.org>; Sat,  8 Feb 2014 10:59:33 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 1C0A3C9423; Sat,  8 Feb 2014 18:59:22 +0000 (UTC) (envelope-from jinmei@wide.ad.jp)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Sat,  8 Feb 2014 18:59:22 +0000 (UTC) (envelope-from jinmei@wide.ad.jp)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 7593016004E; Sat,  8 Feb 2014 19:00:03 +0000 (UTC)
Received: from jmb.jinmei.org (99-115-129-51.uvs.sntcca.sbcglobal.net [99.115.129.51]) by zmx1.isc.org (Postfix) with ESMTPSA id 4395216004B; Sat,  8 Feb 2014 19:00:03 +0000 (UTC)
Date: Sat, 08 Feb 2014 10:59:20 -0800
Message-ID: <m28utlzb07.wl%jinmei.tatuya@gmail.com>
From: JINMEI Tatuya / =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei.tatuya@gmail.com>
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAHw9_iJ-_UBzqjgMU9MG-o7afV_jSshX9CZPKxN0X_4n_G0tQw@mail.gmail.com>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <CAJE_bqc5gpEEx-OkkXv0dtsTQ6pwYb9kkEzELfvszz30+tvCPg@mail.gmail.com> <CAHw9_iJ-_UBzqjgMU9MG-o7afV_jSshX9CZPKxN0X_4n_G0tQw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-DCC--Metrics: post.isc.org; whitelist
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using	CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Feb 2014 18:59:36 -0000

At Fri, 7 Feb 2014 13:43:27 -0500,
Warren Kumari <warren@kumari.net> wrote:

> > Now I understand this is intended to mean "absence of CDS / CDNSKEY
> > *RRset*", i.e., absence of any CDS / CDNSKEY.  But it was not super
> > clear when I first read it and it could also mean the absence
> > (removal) of this CDS at time T+4
> >
> >   example.com. 300  IN CDS 31589 8 1 123456......
> >
> > maybe I was the only person who was confused about this, but it
> > wouldn't do any harm to clarify the wording.
> >
> 
> Yup, the wording was unclear / ambiguous.
> I tried "The absence of *any* CDS..." but that was also unclear. I
> also tried "Absence of a CDS / CDNSKEY *RRset* in child...", but ended
> up settling on:
> "If there are no CDS / CDNSKEY resource records in the child, this
> signals that no change should be made to the current DS set. This
> means that, once the child and parent are in sync, the child DNS
> operator MAY remove all CDS records from the zone."
> It this better?

(Now that I've understood the intent I may not be in a good position
for judging the clarity of the text, but anyway) Yes, I think so.

> > In that, technically, an empty CDS / CDNSKEY RRset should mean the DS
> > RRset at the parent should be empty.
> >  I have no problem with treating
> > an empty set as an exception, but I think it would help if the draft
> > explains that more explicitly.
> 
> Yup. I'm currently trying to craft text to that effect. Unfortunately
> I'm having a hard time doing so cleanly.
> I've just added "An empty CDS / CDNSKEY RRset means that no change is
> needed." in my edit buffer, but I'm unclear on something -- is an
> empty RRset the same as a non-existing RRset? I *think* it is, but it
> somehow feels weird...

Mathematically I think so, but in any case, the point here is to make
the draft so it won't be misunderstood, rather than try to give
a mathematically perfect definition.  In that sense I think it's
sufficient as long as it's clear that "the fact that there are no CDS
/ CDNSKEY records in the child does *not* mean that DS records should
be removed from the parent" around this text of Section 3.

   The
   CDS / CDNSKEY RRset expresses what the child would like the DS RRset
   to look like after the change;

For example, we could say something like "note, however, that the
absence of CDS / CDNSKEY RRset does not mean that the DS RRset be
removed (see Section 4.1)".

This additional note might be too obvious and sound redundant for some
people, but it would help readers like me to avoid possible confusion.

> > I'd also note that "absence of CDS" (or CDNSKEY) cannot happen once
> > one such RR is published, and it should mean something erroneous (most
> > likely an operation error at the child or a bug in its tool).  I think
> > it's worth noting in Section 4.1.
> 
> Um, I think I'm confused now.
> Absence of CDS / CDNSKEY can happen. The child just stops including
> CDS / CDNSKEY records in their zone - this signals "No change", and is
> a special case.

Sorry, it was actually me who was confused.  When I made this comment
I thought the only possible case where the child zone admin removes
all CDS is an (incorrect) attempt of going unsigned.  That's why I
said "it should mean something erroneous".  With this being
clarified...

[...]

> If the "Empty CDS / CDSKEY RRset == no change" rule did NOT exist (or
> if "Empty CDS / CDSKEY RRset" meant please go unsigned), what would
> happen would be that, on April 1st the IT group would turn on some
> home grown CDS tool. It would go off and look at all the child zones.
> If would be happy with accounting,example.com and
> development.example.com. For sales it would see no CDS record, and so
> would "helpfully" remove all DS records, making the sales.exmaple.com
> zone be unsigned.

...note the "once one such RR (= CDS/CDNSKEY) is published" part of my
original comment.  It's about the case where all CDS/CDNSKEY RRs are
removed, and is different from the scenario of the lazy child admins.

> Yes, there could be all sorts of logic built into the tool to keep
> state / a record of which zones had opted into using CDS / CDNSKEY,
> but this is a: error prone and b: requires state on the parent.

Note that I'm not against the "no change if no CDS / CDNSKEY RRs" rule
at the parent side.  This is a discussion about a child removing all
CDS / CDNSKEY RRs.  My original comment was based on my confusion that
it could only happen when the child (incorrectly) tries to signal to
the parent that it goes unsigned.  Now I understand it *MAY* do it for
some other reason, so this is not necessarily an erroneous
condition...but, at this point I also wonder, mainly just out of
curiosity: what's the intended reason(s) for the child to do that?  If
there's no specific purpose for the operation but it's allowed (as a
MAY) just to give the child the flexibility, isn't it better to say
"the child MUST NOT (or if it's too strong, SHOULD NOT) remove all CDS
/ CDNSKEY RRs"?  Then, even if the parent side of operation or tool
has a defect and (incorrectly) interprets the removal as the child
going unsigned, that accident will be even less likely to happen.

Just a thought, not a strong opinion.

> > Finally, I'd suggest explicitly clarifying that CDS / CDNSKEY cannot
> > be used for a child from signed to unsigned (since it would have to
> > remove all CDS / CDNSKEY records to do so).  And, I suspect this is a
> > "MUST NOT", unlike the case of initial enrollment described in Section
> > 9, because this would break interoperability.
> 
> I just added:
> "While it may be tempting, this SHOULD NOT be used for initial
> enrollment of keys since there is no way to ensure that the initial
> key is the correct one. If is used, strict rules for inclusion of keys
> like hold down times, challenge data inclusion etc., ought to be used,
> along with some kind of challenge mechanism. A child cannot use this
> mechanism to go from signed to unsigned (publishing an empty CDS /
> CDNSKEY RRset means no-change should be made in the parent)."
> 
> Is this clear? I suspect I'm missing some subtleties here.

Yes, I think so.

--
JINMEI, Tatuya

From jinmei@wide.ad.jp  Sat Feb  8 11:06:35 2014
Return-Path: <jinmei@wide.ad.jp>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 134201A0203 for <dnsop@ietfa.amsl.com>; Sat,  8 Feb 2014 11:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.481
X-Spam-Level: *
X-Spam-Status: No, score=1.481 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, NML_ADSP_CUSTOM_MED=0.9, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCgh5aPXPSsy for <dnsop@ietfa.amsl.com>; Sat,  8 Feb 2014 11:06:34 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id E1EEE1A055C for <dnsop@ietf.org>; Sat,  8 Feb 2014 11:06:33 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 2211A2383E2; Sat,  8 Feb 2014 19:06:22 +0000 (UTC) (envelope-from jinmei@wide.ad.jp)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id F1D3A16004B; Sat,  8 Feb 2014 19:07:02 +0000 (UTC)
Received: from jmb.jinmei.org (99-115-129-51.uvs.sntcca.sbcglobal.net [99.115.129.51]) by zmx1.isc.org (Postfix) with ESMTPSA id C419016004A; Sat,  8 Feb 2014 19:07:02 +0000 (UTC)
Date: Sat, 08 Feb 2014 11:06:20 -0800
Message-ID: <m27g95zaoj.wl%jinmei.tatuya@gmail.com>
From: JINMEI Tatuya / =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei.tatuya@gmail.com>
To: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <C96F9895-3B54-410A-A70E-1D7EF25FB6C0@ogud.com>
References: <CAJE_bqe95pn8rHvK3UffPDn+_rGYiq2G5sfdgqisH4JG7gFjBA@mail.gmail.com> <CAHw9_i+Jt4Ok+CddheGT_nA=e4srgbUSQy98GeQ9qGn_Cncjag@mail.gmail.com> <CAJE_bqc5gpEEx-OkkXv0dtsTQ6pwYb9kkEzELfvszz30+tvCPg@mail.gmail.com> <C96F9895-3B54-410A-A70E-1D7EF25FB6C0@ogud.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] how to delete obsolete DS for obsolete DNSKEY using	CDS/CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Feb 2014 19:06:35 -0000

At Fri, 7 Feb 2014 13:26:53 -0500,
Olafur Gudmundsson <ogud@ogud.com> wrote:

> > In that, technically, an empty CDS / CDNSKEY RRset should mean the DS
> > RRset at the parent should be empty.  I have no problem with treating
> > an empty set as an exception, but I think it would help if the draft
> > explains that more explicitly.
> 
> Semantics semantics,  
> No we are defining the semantics to be "IF C* is published parent DS should mirror that,
> if no C* in child --> parent has no action to perform" 

Yes, I now understand that.  Please see my latest response to Warren;
I still think it helps to clarify that explicitly.

> > I'd also note that "absence of CDS" (or CDNSKEY) cannot happen once
> > one such RR is published, and it should mean something erroneous (most
> > likely an operation error at the child or a bug in its tool).  I think
> > it's worth noting in Section 4.1
> 
> Why?
> Here is a perfectly fine time line
> <At start parent DS reflects key A and child uses A to sign DNSKEY RRset> 
> 
> Child publishes CDS with A and B 
> Parent updates DS to reflect A and B 
> Child deletes CDS   

Right, I was still a bit confused here.  Now I understand it, but I
also wonder why would the child deletes the CDS's (again, please see
my latest response to Warren).

> Do you think it is helpful to add an appendix with some examples of use of C* records ? 

Yes, I think so (I don't think I wouldn't need the example myself now
that I understand it, but I guess it helps other fresh readers:-).

> > Finally, I'd suggest explicitly clarifying that CDS / CDNSKEY cannot
> > be used for a child from signed to unsigned (since it would have to
> > remove all CDS / CDNSKEY records to do so).  And, I suspect this is a
> > "MUST NOT", unlike the case of initial enrollment described in Section
> > 9, because this would break interoperability.
> > 
> 
> In theory we can use C* to perform the Going-Unsigned operation, and earlier version of this
> document proposed that, but people objected and we removed that text. 
> We explicitly outlaw going from Unsigned --> Signed w/o some out-of-band validation. 

That's fine.  I just tried to point out that (even if allowed)
"removing all *Cs as a signal of signed->unsigned" and the "no change
if no *Cs rule" can't coexist.

--
JINMEI, Tatuya

From tjw.ietf@gmail.com  Mon Feb 10 20:13:47 2014
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 709021A0782 for <dnsop@ietfa.amsl.com>; Mon, 10 Feb 2014 20:13:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztzWrLWypOvZ for <dnsop@ietfa.amsl.com>; Mon, 10 Feb 2014 20:13:45 -0800 (PST)
Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 81BB11A055E for <dnsop@ietf.org>; Mon, 10 Feb 2014 20:13:45 -0800 (PST)
Received: by mail-qa0-f47.google.com with SMTP id j5so10822352qaq.20 for <dnsop@ietf.org>; Mon, 10 Feb 2014 20:13:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=qGfQNazNGmqUqGPqK2ZEuPFjrQiofy8y/a70DVmGujs=; b=ugPMWo3UN2UxtMZCFK0jixmbwakSYHpRzBGrq0/18TPGQkRVycl/lnmjbJjTsWBovc GLh2tfMpdkQqZmVoyNNXHUm6zTBKudV3NP0JZp+x4DVzCHWpAYqeQVkS2qnQUTt5p990 e4G0YaM02dJGQsHUoNvz+wDGcjozoAFi8F1m62LUPbrIrXJldVQJWelp+G3MRlPXTAQh k6NPT5x4KbKfrGu7AsLMR5GMJB66oi5cCblErO4Am5DBAIoz90IVmZ5buTh5bCJKlz28 80oaceoi7RGPH5ADvLkkrxeh4YneFHNO7RzKte2a1j/2XGH4lQ2byd2f6yfSZtO10Wev PGag==
X-Received: by 10.224.67.6 with SMTP id p6mr38617830qai.6.1392092024759; Mon, 10 Feb 2014 20:13:44 -0800 (PST)
Received: from [10.33.3.95] ([204.14.236.215]) by mx.google.com with ESMTPSA id r13sm49289631qan.7.2014.02.10.20.13.43 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Feb 2014 20:13:44 -0800 (PST)
Message-ID: <52F9A377.1080008@gmail.com>
Date: Mon, 10 Feb 2014 23:13:43 -0500
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dnsop@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [DNSOP] Call for agenda items for London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2014 04:13:47 -0000

Greetings,

London is less than a month away, and we should start soliciting agenda 
items.  I requsted a 2 hour session instead of the normally tight 1.5 
hours, and they gave us Friday Morning for 2.5 hours.  I attempted to do 
some horse trading with httpbis as they liked that slot, but nothing 
quite worked.

We already have some time for the privacy drafts floating around, 
especially discussing the requirements.  But feel free to email us with 
suggestions, requests, etc.  As we did in Vancouver, we've been given 
some latitude from our great and glorious AD to be more open in what we 
accept.

thanks
tim



From nweaver@icsi.berkeley.edu  Wed Feb 12 07:35:51 2014
Return-Path: <nweaver@icsi.berkeley.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F061A08DB for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 07:35:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, J_CHICKENPOX_24=0.6, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wctoxlILTIvi for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 07:35:48 -0800 (PST)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) by ietfa.amsl.com (Postfix) with ESMTP id 87FE31A057E for <dnsop@ietf.org>; Wed, 12 Feb 2014 07:35:48 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 08B472C403A for <dnsop@ietf.org>; Wed, 12 Feb 2014 07:35:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at ICSI.Berkeley.EDU
Received: from rock.ICSI.Berkeley.EDU ([127.0.0.1]) by localhost (maihub.ICSI.Berkeley.EDU [127.0.0.1]) (amavisd-new, port 10024) with LMTP id fGhLU-zNZj7m; Wed, 12 Feb 2014 07:35:47 -0800 (PST)
Received: from gala.icir.org (gala.icir.org [192.150.187.130]) (Authenticated sender: nweaver) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 721D12C4009; Wed, 12 Feb 2014 07:35:47 -0800 (PST)
From: Nicholas Weaver <nweaver@icsi.berkeley.edu>
Content-Type: multipart/signed; boundary="Apple-Mail=_6E3D2411-F1A7-42AF-859A-5E585CAD0C2A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Date: Wed, 12 Feb 2014 07:35:47 -0800
Message-Id: <390BFAA1-3108-4922-A6C0-E666C0BD25A9@icsi.berkeley.edu>
To: dnsop WG <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
Cc: Nicholas Weaver <nweaver@icsi.berkeley.edu>
Subject: [DNSOP] Any suggestion on what I'm doing that is stupid here on NSEC3?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 15:35:51 -0000

--Apple-Mail=_6E3D2411-F1A7-42AF-859A-5E585CAD0C2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I'm trying to do my own implementation of NSEC3 as part of my dynamic =
DNSSEC server (in order to do NSEC3 lies for NXDOMAIN, since you can't =
do such a lie with NSEC, NSEC lies only allow "0 answer noerror" which =
is unfortunately NOT the same)

But I appear to be doing something stupid, and am not operating the hash =
right:



Looking at com, the NSEC3 for "com" is:
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - ...

(Algorithm 1 -> SHA-1, flag =3D 1, iterations =3D 0, salt =3D None, =
fetched by "dig +dnssec MX com @a.gtld-servers.net")

Reading RFC5155, the calculation of the hash is:

>    The hash calculation uses three of the NSEC3 RDATA fields: Hash
>    Algorithm, Salt, and Iterations.
>=20
>    Define H(x) to be the hash of x using the Hash Algorithm selected =
by
>    the NSEC3 RR, k to be the number of Iterations, and || to indicate
>    concatenation.  Then define:
>=20
>       IH(salt, x, 0) =3D H(x || salt), and
>=20
>       IH(salt, x, k) =3D H(IH(salt, x, k-1) || salt), if k > 0
>=20
>    Then the calculated hash of an owner name is
>=20
>       IH(salt, owner name, iterations),
>=20
>    where the owner name is in the canonical form, defined as:
>=20
>    The wire format of the owner name where:
>=20
>    1.  The owner name is fully expanded (no DNS name compression) and
>        fully qualified;
>=20
>    2.  All uppercase US-ASCII letters are replaced by the =
corresponding
>        lowercase US-ASCII letters;
>=20
>    3.  If the owner name is a wildcard name, the owner name is in its
>        original unexpanded form, including the "*" label (no wildcard
>        substitution);

So it should be the base32 encoding of the SHA1 hash of the wire format =
for "com" (since there is no salt), which in python is:

"\x03com\x00", (3 characters, the string "com", and 0 as a terminator in =
wire format.  This matches the wire format I get from my name packer in =
my DNS server)

Yet when I try to calculate the SHA1 hash in python's library, I get:
>>> m =3D hashlib.sha1()=20
>>> m.update("\x03com\x00") # There is no salt and 0 additional =
iterations
>>> base64.b32encode(m.digest())=20
'MUAZYTWQIHEVT3OPHOPXIEDA27S5IL4W'
>>> m.hexdigest()
'65019c4ed041c959edcf3b9f741060d7e5d42f96'

But at the same time, this matches the sha1sum for a file containing =
just the string "\x03com\x00", so the hash is correct for sha1.


So the conclusion is I'm not putting in the right input into the hash =
function.  Thoughts on what I'm doing wrong?

--
Nicholas Weaver                  it is a tale, told by an idiot,
nweaver@icsi.berkeley.edu                full of sound and fury,
510-666-2903                                 .signifying nothing
PGP: http://www1.icsi.berkeley.edu/~nweaver/data/nweaver_pub.asc


--Apple-Mail=_6E3D2411-F1A7-42AF-859A-5E585CAD0C2A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCgAGBQJS+5TTAAoJEG2B1w+SDi/uB14P+gLQnOkketAL7kzY9BH3JKoS
pqO6OEBwvfKlCtE+yY438W+VMju2F3qV1SMIwYS1JBUQ1bFTHsmsif9GSunTbxT+
HxVZU0XLWGy7b8m48FcnGhewsyoq+aFhNY7O8isNtOTxK402cnsTykTx1fpXM1aj
46SB0bsRNNZ+qhea7ePLsUD2jkDXdHYtix6Kk2ND31LHXZx+ny3HHg56tD7Onvlh
mQe1OfRKZbOxZT8Y1PX/92+dRA85meljFQA8fM3kzGWXOG6wJbl5O0Apl4UZTuH6
FnSNo23QCKIh+aUw7F1vCUhqCEmKrys2O0NKvMdhxJkujStLf892TnqQO7EsSmSF
JjpdBvT3uCDGlhSBVNGqk5aIMOuLoPNWHbG8W4FG5942UAxA9ycdq7vzIFrI/7ib
5ixTjyUdkw78REOgagAOOmyjQsopdtaFMKsTueLDFQEl0HFmvXRyyygDcLwS4Gj2
9kjmx7rWkKOOJtgwRWMhirgD/qxsgIC+2giEu/7nVWltTnFXHvyWE+96S0PfbkWN
UKlqf/j2EZ0FddIdEWMhvcDd8iJX3UABWRIh7heJEzhh1hubyOLH+XSrKHGsGpgD
TPDpYhmPi5CInFmsRIHp4BWXFz9VMQ9A2BgKUZfCMzGKcjEupFiLHFd/OgwTTUZq
tBJ5ZnWJeUDlzIu/s82i
=u/Pz
-----END PGP SIGNATURE-----

--Apple-Mail=_6E3D2411-F1A7-42AF-859A-5E585CAD0C2A--


From shuque@upenn.edu  Wed Feb 12 07:57:13 2014
Return-Path: <shuque@upenn.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67D3E1A09BD for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 07:57:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.989
X-Spam-Level: 
X-Spam-Status: No, score=-2.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_24=0.6] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wBDQAN_F9sPo for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 07:57:11 -0800 (PST)
Received: from mopeypopo.net.isc.upenn.edu (www.huque.com [IPv6:2607:f470:2:1::a:2]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADE41A0601 for <dnsop@ietf.org>; Wed, 12 Feb 2014 07:57:11 -0800 (PST)
Received: by mopeypopo.net.isc.upenn.edu (Postfix, from userid 500) id 0B0C6A01A1; Wed, 12 Feb 2014 10:57:10 -0500 (EST)
Date: Wed, 12 Feb 2014 10:57:09 -0500
From: Shumon Huque <shuque@upenn.edu>
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
Message-ID: <20140212155709.GA15950@upenn.edu>
References: <390BFAA1-3108-4922-A6C0-E666C0BD25A9@icsi.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <390BFAA1-3108-4922-A6C0-E666C0BD25A9@icsi.berkeley.edu>
Organization: University of Pennsylvania
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Any suggestion on what I'm doing that is stupid here on NSEC3?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 15:57:13 -0000

It might be because NSEC3 uses base32 with extended hex alphabet.
Looks like you're using plain base32.

See http://tools.ietf.org/html/rfc4648#section-7

--Shumon.

On Wed, Feb 12, 2014 at 07:35:47AM -0800, Nicholas Weaver wrote:
> I'm trying to do my own implementation of NSEC3 as part of my dynamic DNSSEC server (in order to do NSEC3 lies for NXDOMAIN, since you can't do such a lie with NSEC, NSEC lies only allow "0 answer noerror" which is unfortunately NOT the same)
> 
> But I appear to be doing something stupid, and am not operating the hash right:
> 
> 
> 
> Looking at com, the NSEC3 for "com" is:
> CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - ...
> 
> (Algorithm 1 -> SHA-1, flag = 1, iterations = 0, salt = None, fetched by "dig +dnssec MX com @a.gtld-servers.net")
> 
> Reading RFC5155, the calculation of the hash is:
> 
> >    The hash calculation uses three of the NSEC3 RDATA fields: Hash
> >    Algorithm, Salt, and Iterations.
> > 
> >    Define H(x) to be the hash of x using the Hash Algorithm selected by
> >    the NSEC3 RR, k to be the number of Iterations, and || to indicate
> >    concatenation.  Then define:
> > 
> >       IH(salt, x, 0) = H(x || salt), and
> > 
> >       IH(salt, x, k) = H(IH(salt, x, k-1) || salt), if k > 0
> > 
> >    Then the calculated hash of an owner name is
> > 
> >       IH(salt, owner name, iterations),
> > 
> >    where the owner name is in the canonical form, defined as:
> > 
> >    The wire format of the owner name where:
> > 
> >    1.  The owner name is fully expanded (no DNS name compression) and
> >        fully qualified;
> > 
> >    2.  All uppercase US-ASCII letters are replaced by the corresponding
> >        lowercase US-ASCII letters;
> > 
> >    3.  If the owner name is a wildcard name, the owner name is in its
> >        original unexpanded form, including the "*" label (no wildcard
> >        substitution);
> 
> So it should be the base32 encoding of the SHA1 hash of the wire format for "com" (since there is no salt), which in python is:
> 
> "\x03com\x00", (3 characters, the string "com", and 0 as a terminator in wire format.  This matches the wire format I get from my name packer in my DNS server)
> 
> Yet when I try to calculate the SHA1 hash in python's library, I get:
> >>> m = hashlib.sha1() 
> >>> m.update("\x03com\x00") # There is no salt and 0 additional iterations
> >>> base64.b32encode(m.digest()) 
> 'MUAZYTWQIHEVT3OPHOPXIEDA27S5IL4W'
> >>> m.hexdigest()
> '65019c4ed041c959edcf3b9f741060d7e5d42f96'
> 
> But at the same time, this matches the sha1sum for a file containing just the string "\x03com\x00", so the hash is correct for sha1.
> 
> 
> So the conclusion is I'm not putting in the right input into the hash function.  Thoughts on what I'm doing wrong?
> 
> --
> Nicholas Weaver                  it is a tale, told by an idiot,
> nweaver@icsi.berkeley.edu                full of sound and fury,
> 510-666-2903                                 .signifying nothing
> PGP: http://www1.icsi.berkeley.edu/~nweaver/data/nweaver_pub.asc
> 



> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


-- 
Shumon Huque
University of Pennsylvania.


From muks@isc.org  Wed Feb 12 08:09:33 2014
Return-Path: <muks@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E69671A03FB for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:09:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.465
X-Spam-Level: 
X-Spam-Status: No, score=-0.465 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SORBS_WEB=0.77, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BUc5dx1M5IvL for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:09:32 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:140:644b::225]) by ietfa.amsl.com (Postfix) with ESMTP id 4466F1A0335 for <dnsop@ietf.org>; Wed, 12 Feb 2014 08:09:32 -0800 (PST)
Received: from totoro.home.mukund.org (unknown [115.118.26.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 7768FE60091; Wed, 12 Feb 2014 16:09:29 +0000 (GMT)
Date: Wed, 12 Feb 2014 21:39:24 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
Message-ID: <20140212160924.GA23506@totoro.home.mukund.org>
References: <390BFAA1-3108-4922-A6C0-E666C0BD25A9@icsi.berkeley.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH"
Content-Disposition: inline
In-Reply-To: <390BFAA1-3108-4922-A6C0-E666C0BD25A9@icsi.berkeley.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Any suggestion on what I'm doing that is stupid here on NSEC3?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 16:09:34 -0000

--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Nicholas

On Wed, Feb 12, 2014 at 07:35:47AM -0800, Nicholas Weaver wrote:
> Looking at com, the NSEC3 for "com" is:
> CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - ...
>=20
> (Algorithm 1 -> SHA-1, flag =3D 1, iterations =3D 0, salt =3D None, fetch=
ed by "dig +dnssec MX com @a.gtld-servers.net")
>=20
> Reading RFC5155, the calculation of the hash is:
>=20
> [snip]
>=20
> So it should be the base32 encoding of the SHA1 hash of the wire
> format for "com" (since there is no salt), which in python is:
>=20
> "\x03com\x00", (3 characters, the string "com", and 0 as a terminator
> in wire format.  This matches the wire format I get from my name
> packer in my DNS server)
>=20
> Yet when I try to calculate the SHA1 hash in python's library, I get:
> >>> m =3D hashlib.sha1()=20
> >>> m.update("\x03com\x00") # There is no salt and 0 additional iterations
> >>> base64.b32encode(m.digest())=20
> 'MUAZYTWQIHEVT3OPHOPXIEDA27S5IL4W'

This is where the problem is. NSEC3 uses base32hex encoding, not
base32. See the difference in RFC 4648 section 7. It should be trivial
to convert the output of the above b32encode() to the base32hex encoding
using a simple lookup map.

If you want to look at some C++ code, clone the BIND 10 repo and look at
the following files:

src/lib/dns/nsec3hash.{h,cc}
src/lib/util/encode/base32hex.h
src/lib/util/encode/base_n.cc

I suggest avoiding the last file and just doing your own base64hex
implementation.. it can make you upset. ;)

		Mukund

--ReaqsoxgOBHFXBhH
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQgcBAEBCgAGBQJS+5yxAAoJENJq4EOcI41746FAAMAJbPIB+1unx1yeMKi+AOqo
5ov215U+wOzDDxHzXjno4jJZaPKYoIs9ilUBCyqd6H3dsT882rqk2RPAtIQ3Q8Xf
Ptdyp1E8FdUJLYdw8rvQWrGP9jnUc0txxFyBP1bUlNJSBgVhImkQZjoldLPm+2cE
4nW+VvrUAiKrWgsMJY1B6yq33TGqIWlIMe9GGCpCD+vcj6M3q2d1EWZ7iWJZMjIb
2PvvuD7KC8kzwlE7xpeNcpVyA6vFlvbkXWG+f9w4c+7sWRLI0JcP75mfuhLwv6+I
Z4Ocsj4Qxlr6oI0HAhdVjYn6vULwZi28xEscRd0OVGn+1chuOGM5fo4yKUpagU+9
7VG7OYogCOUJhbFouw5Hop8sH/p6iLB95jgpoCYpqtsRgoasXyh6bxf49eZSL0Zo
RpiR/AUdsH7zc3yiUFUk16ttuItFoC/w39+uEUWPKLnc4f03+9PCcPNhIOt9XK7A
JWbB8ON5S+WUEloA17C4lw19xoZp16L9u41yC9FnaRiJT3wMzGHPqVvArju2YV6/
6iT2kp1bUoewB7dm4xXW/+ywVsOO3YWGF1g7vuqsFnQbjMkm4jKtklnO0gAmr4NA
RG+SkUAuub++NCgX3YBWIXnHptWYKyVZnPxXd0SE8reBI+aB+h0WRG9vIudPf1W/
y1/SbnJrPFErlF/lJ2pqTHCBXP2eUskhqjGp6QwITTisfL9rmp7wGLuAfpWYsP4u
1MGOOj4jnT9/F/8vnQFdCbRyS24vTUefvl6Xm3wbozHdstomozlnKCrN5rljYjHD
GZbExLZqHgP0W5RaOwxTMw3NabEeK9jQrvNHu7L43GZpE/exMYADaKZoIhqYljfe
eEdA3d0es4xOwlRGvRTZseDulqj0KXHYbwvO0+6bZwTl0aHYdGMUHzYDQCXLtBZk
/b9oJVGedl+J7oIRQ3/jkAtUxRT8FukX8grMhO/cAIjwypGGxNmLWxUI5xKf9L+k
A1JZBrj+r219kAVTVuKllnCHaj/AfqUi8bYpCzPC4aEpEWwaPHxGilOuN9UNJ4FL
v8wslrQU2C4qFNnd7omC4sWUPipyg4trOUM44d5QiI/g+ffWmumqu5yEDcyEJKW/
/bQ3fKPCZCZ4YUviE0zrl68MKbozws4n5ygZJp8iSsCMpb7Ty8dNQF90e+/wA3a9
/udAeaBXqQ6gYxARNU0jHMcRG3/pzRjwUwWfEn9P/NYFCk4zD+v5SrjHX9PnTBOX
3Gioa1mdmUwh8eLHsLshNW5UIdGj2z+PsVekbhjv7Eor8+sl/+g7YrzNQpAYzoBH
Xo1QvXdfHgeWKIWplW3ecytX9+Y5Pi2KpwYhy10Wb3qZorUY/U2XDH+AUcvrMLno
QB7wFt77+U35Z5BY0UqvjlTuG2xRfjwoiJrOuzZi+1nD53vC9E9e17F0U/yJ//Zw
q+rOIFJxnZEbJ/yQlvfzDyrh+bjSSuo9OKahsyNNKEaPVPyVOYNG+6u8DxhA4q8m
iZ4mVTjtwJnCF882VXsbmd+uRxTFXOK4SkYWg+lf6futt0ADlhbeJDdy0wxW8zXn
mIf7IAOCxzqbFwgOrNUxe72WXKE8vfzJt4V4xokt26xOQCTdq/nDRVv4HCbY57g1
kkYe37GlQ97tHRn40LQGZsACOBkklsxig1d9UU9yM5MIfBD5YqAKmqQZXnX/aqeU
HbQG5J1DHbRveUX7/fjeHIGW6VZWKP12QqF44Pr/OsVeMAY6+LmMZav74sS4Yn+G
Q2B3i8g/gbuyDrjrxWbZFkGjZDv7LguNziymbN/x9kH1CHVygqImH0IxPv/mic5g
ifDegcUaImEWAuvssqy5twN2/IC149ujr44ZkmrDh4eulhjVwWeW+jbwAyQn6731
Ac40PYPFM8ajit7mQitERqnctB3WcRrPSswzeExt4SRxJVsxds2oYVdtDuUQHjcY
9ZdgujGvtlquyExsaITZqMRxpc73wh2MlL2/0Vn9uVcxTTpKSZCG7iq36VmsvZOw
KkaLWqxArucomgZ+YK0JP65skgMqDVRgCju7RGJqVc8vdfCzG1g1qR1XXAChL+uE
kjkhy7fbFCfMzn0k/ztbdfvgjbV5MxNTvOtMSD/aV0siQFQcMbCKsywTzOAb6OYu
myQTh6Dmoo7N1QL5JyFwtjSQXBNTmf8hxGQOuy6K+L6X4o2eytd7XrywzsypZq8l
LcRZWVTNDwjxyFoaieQeTQDhrZU5Fx35SiOBRJmg2e+TUE22+quWvXwW8U7hD1FC
/U1viG90T+yC2ZDs1HU/gO+52M1XjYWVauYWpcVsn645wveNQfCkFaHuYTqF3AXE
BjzH7x0LTS/d86Dp+KWmYznlBnc9KvaUlRgfVDejAOQR1CQWDFfkyGzpDiUpAlJT
7jwzlAbEbq6uyEEvNr+vIvfOh5vr0U5SVujXR0M+EwirRf0F9cJVN5Ds43It7C/p
A5aqodWs+rC8DuYs4+DINs5yTU52FZHBIAym3JX6mk0gv+XvhF/uvpKWgnAoufWG
aTMi3YnkQWaU3+fHWmSG27WYmQaqvoQFh8oHX0vlq71eVucB2i7T+zLN4axlg+zz
DZfPve65BxdvT92BSB2SbEH6XLYloVqmN2hremtwKBYBq+9ktNblU4ivUh7ZJVik
LvZp2PPp7ZYR0j1IVpy0WHE04LE3oj1eoDQfFd9jooKN1dj/+EHWO27vPf87edE2
tpDYdmJUUtk6XjlpvOc5
=l+0W
-----END PGP SIGNATURE-----

--ReaqsoxgOBHFXBhH--


From bortzmeyer@nic.fr  Wed Feb 12 08:14:24 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E861A09C0 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWVF6rIBwmj6 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:14:21 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 389F51A09D0 for <dnsop@ietf.org>; Wed, 12 Feb 2014 08:14:21 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 70C7928015A for <dnsop@ietf.org>; Wed, 12 Feb 2014 17:14:19 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 6CE26280102 for <dnsop@ietf.org>; Wed, 12 Feb 2014 17:14:19 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 6A9B24C0053 for <dnsop@ietf.org>; Wed, 12 Feb 2014 17:13:49 +0100 (CET)
Date: Wed, 12 Feb 2014 17:13:49 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dnsop@ietf.org
Message-ID: <20140212161349.GA31661@nic.fr>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140210205838.15973.63281.idtracker@ietfa.amsl.com>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 16:14:24 -0000

On Mon, Feb 10, 2014 at 12:58:38PM -0800,
 internet-drafts@ietf.org <internet-drafts@ietf.org> wrote 
 a message of 36 lines which said:

>         Title           : The ALT Special Use Top Level Domain
>         Authors         : Warren Kumari
>                           Andrew Sullivan
> 	Filename        : draft-wkumari-dnsop-alt-tld-00.txt

The goal is laudable and I like the end of section 3, acknoweledging
that, existing TLDs like .onion won't move to the new .ALT

However, I disagree with the terminology.

> DNS context: The namespace administered by ICANN.

No. The DNS is a protocol. It exists whether or not it is rooted at
ICANN. When you use an "alternative root" (RFC 2826), you use the
DNS. When a big closed organization has its own infrastructure, with
root servers and so on, it is still the same DNS protocol.

> the DNS "standard" of a series of labels separated with dots

Many other systems work with this syntax (domain names can be resolved
by other protocols than the DNS, for instance /etc/hosts or LDAP) so
it should not be called "DNS standard".


From marc.blanchet@viagenie.ca  Wed Feb 12 08:28:43 2014
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49AFC1A09AB for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:28:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjJXWl3R7ArX for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:28:33 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC141A09B3 for <dnsop@ietf.org>; Wed, 12 Feb 2014 08:28:33 -0800 (PST)
Received: from [IPv6:2620::230:c000:15af:a828:676a:ed0d] (unknown [IPv6:2620:0:230:c000:15af:a828:676a:ed0d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5C2DB4690E; Wed, 12 Feb 2014 11:28:32 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <20140210205838.15973.63281.idtracker@ietfa.amsl.com>
Date: Wed, 12 Feb 2014 11:28:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com>
To: draft-wkumari-dnsop-alt-tld@tools.ietf.org
X-Mailer: Apple Mail (2.1827)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 16:28:43 -0000

- I like better that approach than the previous draft registering many =
tlds.
- I would prefer an IANA registry under .alt with "expert" review =
policy.  A namespace with possible collisions (past or future) have very =
low value to me. names are leaking in various contexts, so collisions =
would be bad for the protocols and deployment using that .alt tld.

Marc.

Le 2014-02-10 =E0 15:58, internet-drafts@ietf.org a =E9crit :

>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>=20
>=20
>        Title           : The ALT Special Use Top Level Domain
>        Authors         : Warren Kumari
>                          Andrew Sullivan
> 	Filename        : draft-wkumari-dnsop-alt-tld-00.txt
> 	Pages           : 6
> 	Date            : 2014-02-10
>=20
> Abstract:
>   This document reserves a string to be used as a TLD label in non-DNS
>   contexts.  [Ed note: By now you should be wildly confused.  Go read
>   the intro / background :-P ]
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-wkumari-dnsop-alt-tld-00
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nweaver@icsi.berkeley.edu  Wed Feb 12 08:46:31 2014
Return-Path: <nweaver@icsi.berkeley.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFB51A0459 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfeL9um2kuUL for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 08:46:29 -0800 (PST)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) by ietfa.amsl.com (Postfix) with ESMTP id 82B241A040E for <dnsop@ietf.org>; Wed, 12 Feb 2014 08:46:29 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id E36982C403A; Wed, 12 Feb 2014 08:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at ICSI.Berkeley.EDU
Received: from rock.ICSI.Berkeley.EDU ([127.0.0.1]) by localhost (maihub.ICSI.Berkeley.EDU [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tw4a+W1DqhrX; Wed, 12 Feb 2014 08:46:28 -0800 (PST)
Received: from gala.icir.org (gala.icir.org [192.150.187.130]) (Authenticated sender: nweaver) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 726E32C4009; Wed, 12 Feb 2014 08:46:28 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_F8E18D91-D86A-4BF3-AAF7-F2197AB1011B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Nicholas Weaver <nweaver@icsi.berkeley.edu>
In-Reply-To: <20140212160924.GA23506@totoro.home.mukund.org>
Date: Wed, 12 Feb 2014 08:46:28 -0800
Message-Id: <7ED0A37B-661B-49CF-B4E7-37F367B00EE6@icsi.berkeley.edu>
References: <390BFAA1-3108-4922-A6C0-E666C0BD25A9@icsi.berkeley.edu> <20140212160924.GA23506@totoro.home.mukund.org>
To: Mukund Sivaraman <muks@isc.org>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop WG <dnsop@ietf.org>, Nicholas Weaver <nweaver@icsi.berkeley.edu>
Subject: Re: [DNSOP] Any suggestion on what I'm doing that is stupid here on NSEC3?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 16:46:31 -0000

--Apple-Mail=_F8E18D91-D86A-4BF3-AAF7-F2197AB1011B
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks.  Indeed I was stupid: wrong base32 encoding....

--
Nicholas Weaver                  it is a tale, told by an idiot,
nweaver@icsi.berkeley.edu                full of sound and fury,
510-666-2903                                 .signifying nothing
PGP: http://www1.icsi.berkeley.edu/~nweaver/data/nweaver_pub.asc


--Apple-Mail=_F8E18D91-D86A-4BF3-AAF7-F2197AB1011B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCgAGBQJS+6VkAAoJEG2B1w+SDi/umkkQALDHzClqxj+7lN/mNZE/h+nO
ahY/gLCJ2M/FPqD8t+vRW/BwOffpExLVBrftxfLX15o7HqdMDvtPe7HUuJkUGMPe
TiSF2Gkv1ubcL3bAmReYGGJYtjHD8JmuFFjVZd/6f0eRnpedUi1PP20/jJlpB7gc
FwE0Gr7V3qighqkhPXziSZv1vw8BLta2FwiMH8IUoRtdPwAKtmse26v0W/+R1SFA
hx3oZsgWdEMmRACfyB1StRqjZxInLwVa2KR0iNL68ve0DW4JgvbBaABKW6H+d/P/
S7j3YT2qfEEtMktMKZmYZnm9Zb+BkddOFPN74hLXvf2I8iLPCPiIbra/8kc5ix3q
AbeqL+A93/P7aXzX8e4PiBDkKxaWjIGntYBkc5DRwMOgXwmXQalgPCXoy8zWkqSL
J+4AhSVL3CxxZjLArHCTSdykTJP6ZXWScqVUzn+YJeNrx2fulh/9IOfB1ROSPLhy
TqA5PuMrcI040RztKVFERydiTgpmeO6rp/CoZOC9KBBRQq0M2/z6sKSkxY533gEm
hdFKBielDBRTy5kvZBbxWfcc5xlrVrzaKPYljarS5bC8AouVTLAshMYjgoeUENZB
/wjRa2HZPMpS9S5e2QfnDwxg5C0QL7vGUr5wXh+ot14bxZThbDA2r5EYmmj78Zi6
L/CcdbtNid/VVKbumYw6
=zgk9
-----END PGP SIGNATURE-----

--Apple-Mail=_F8E18D91-D86A-4BF3-AAF7-F2197AB1011B--


From jabley@hopcount.ca  Wed Feb 12 10:24:14 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 866921A0605 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 10:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_54=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1FoCgosWhUdZ for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 10:24:11 -0800 (PST)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 973871A0502 for <dnsop@ietf.org>; Wed, 12 Feb 2014 10:24:11 -0800 (PST)
Received: by mail-qc0-f182.google.com with SMTP id c9so16090740qcz.27 for <dnsop@ietf.org>; Wed, 12 Feb 2014 10:24:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=THFl4g2A/ouQtUBoRZI+TuhFvjmWqQU4PMmX+7b0tc0=; b=THuTKoGRTTzF75h9qQeIMvCmEqtziRIvsSqOm2UPdxGtqjMD46ghCgThKg5Pp8Yqsg QRU1oWIefQfN6xmx3dxoFG3H0i5SK6MtR1cPHkcbj9M14awWvn2tJhU3L2parEaMhXC+ QcGeI2Q6K8VHg4V09rpIfzfSqAoEGtfdv3h6E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=THFl4g2A/ouQtUBoRZI+TuhFvjmWqQU4PMmX+7b0tc0=; b=N0NEThgH3soH7P3pcs5MvvclaaMJtGAQtv8jDtutJ+MOac6RcDDFrJKaUc88NDQAwH ZojpBa62Kr+BplYIOPx2Cnij91iDUQy76bYN6lN1fNfDt+ToHTBsVvzpFGngetOzRAeB e0zm2760/Xc7lC7umECenoTfXTzrQ4dJBHkWASx0w220D6OLMw6f0lM7WvnjNOj7Ke1Y fECmGsnZQ0Y/PTOnFaNnAbgjtUwSV2K8auIwbbAYK2UGRS2X9RYyxMIJ6jaj8FjiGxJE MjvT91V+EhpjZKXEYssAiV90CprVSG8yA/L6QjlAfYXGUaCpdLjGpcPMJrxFcHbkHY8d h8WQ==
X-Gm-Message-State: ALoCoQkAksHtQsYSWca0+j/5tT4TJGUHTJDKk6sP1f8esm7HzigjxayJQ+1W1FQoqRhf32T6QxkH
X-Received: by 10.140.50.131 with SMTP id s3mr33188352qga.12.1392229450583; Wed, 12 Feb 2014 10:24:10 -0800 (PST)
Received: from dh24.r1.hopcount.ca (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id k61sm34756692qge.12.2014.02.12.10.24.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 10:24:09 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_C9368500-23FF-40BC-9451-15CA20D072E5"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca>
Date: Wed, 12 Feb 2014 13:24:07 -0500
Message-Id: <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
X-Mailer: Apple Mail (2.1827)
Cc: draft-wkumari-dnsop-alt-tld@tools.ietf.org, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 18:24:14 -0000

--Apple-Mail=_C9368500-23FF-40BC-9451-15CA20D072E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 2014-02-12, at 11:28, Marc Blanchet <marc.blanchet@viagenie.ca> =
wrote:

> - I like better that approach than the previous draft registering many =
tlds.

The previous draft (at least for some of the TLDs) was anchored in the =
reality that changing the name already in use was not practical, e.g. =
there's a sufficient deployed base that uses DNS-like names ending in =
ONION that proposals to use things like ONION.ARPA were non-starters.

I think therefore that the ALT draft addresses quite a different =
problem: the choice of DNS-like (but not DNS) name structure for new =
applications that we don't know about yet.

I suspect that there would be fewer roadblocks involved in choosing an =
anchor ALT.ARPA than ALT, since ARPA is under the control of an IETF =
family member while the root is controlled by distant cousins. If I'm =
right that this proposal is for future, as-yet-unknown applications, =
then the choice of anchor should be arbitrary; it feels in that case =
like the path of least resistance is the right one.

> - I would prefer an IANA registry under .alt with "expert" review =
policy.  A namespace with possible collisions (past or future) have very =
low value to me. names are leaking in various contexts, so collisions =
would be bad for the protocols and deployment using that .alt tld.

I think that if we are talking about DNS names, we already have =
mechanisms to ensure uniqueness.

If we're not talking about DNS names, then the only consideration we =
really need is to avoid collisions with the DNS. We can do that by =
reserving ALT (or ALT.ARPA, or whatever), specifying that it's a =
reasonable domain to sink locally (RFC 6303) and perhaps providing some =
kind of AS112++ sink for leaks to the wider network =
(draft-ietf-dnsop-as112-dname).

(An AS112++ sink for a domain is probably easier to realise for ALT.ARPA =
than it is for ALT, since the root zone is maintained using specific =
registry machinery that would require changes to support DNAME, I think, =
and the track record suggests such changes might take a long time to =
action.)

I don't see an obvious reason to insist on IETF restrictions on an =
ALT-like namespace if the point of the namespace is to be available for =
use outside the IETF. If restrictions existed (no matter how simple we =
imagine they were to follow) the likely outcome is that ALT would either =
be abused (used without registration) or ignored.


Joe


--Apple-Mail=_C9368500-23FF-40BC-9451-15CA20D072E5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlL7vEcACgkQNI8MvYZSOizTFgCfeGwPPj6F5m9omHC6tXXlK3yA
gKAAnRaUY6pupj4yq6PDNF6ZmahUIDGd
=AQug
-----END PGP SIGNATURE-----

--Apple-Mail=_C9368500-23FF-40BC-9451-15CA20D072E5--


From Ted.Lemon@nominum.com  Wed Feb 12 12:24:41 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF261A06B2 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 12:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UaCRgl-knHlG for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 12:24:39 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 882E61A06BE for <dnsop@ietf.org>; Wed, 12 Feb 2014 12:24:39 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5476E1B832C for <dnsop@ietf.org>; Wed, 12 Feb 2014 10:40:14 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 26650190052; Wed, 12 Feb 2014 10:40:14 -0800 (PST)
Received: from [192.168.43.232] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 12 Feb 2014 10:40:13 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca>
Date: Wed, 12 Feb 2014 13:40:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <982167BD-10FC-4D06-9E85-47F371BBCA90@nominum.com>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop <dnsop@ietf.org>, draft-wkumari-dnsop-alt-tld@tools.ietf.org
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 20:24:41 -0000

On Feb 12, 2014, at 1:24 PM, Joe Abley <jabley@hopcount.ca> wrote:
> I suspect that there would be fewer roadblocks involved in choosing an =
anchor ALT.ARPA than ALT, since ARPA is under the control of an IETF =
family member while the root is controlled by distant cousins. If I'm =
right that this proposal is for future, as-yet-unknown applications, =
then the choice of anchor should be arbitrary; it feels in that case =
like the path of least resistance is the right one.

It really shouldn't be difficult to make this work, although if .ALT is =
already spoken for a different name might be needed.   If it is in fact =
difficult, then RFC 6761 is pretty pointless.

I agree with your other point, though=97this may be useful for future =
efforts, but doesn't address the same problem as the other two documents =
we've talked about.


From joelja@bogus.com  Wed Feb 12 12:34:43 2014
Return-Path: <joelja@bogus.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 270FE1A04C6 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 12:34:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-VEIlEAXiQs for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 12:34:41 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1C8011A0450 for <dnsop@ietf.org>; Wed, 12 Feb 2014 12:34:41 -0800 (PST)
Received: from mb-aye.local ([173.247.205.34]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s1CKYcbt001819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 12 Feb 2014 20:34:39 GMT (envelope-from joelja@bogus.com)
Message-ID: <52FBDADE.6020306@bogus.com>
Date: Wed, 12 Feb 2014 12:34:38 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, Joe Abley <jabley@hopcount.ca>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <982167BD-10FC-4D06-9E85-47F371BBCA90@nominum.com>
In-Reply-To: <982167BD-10FC-4D06-9E85-47F371BBCA90@nominum.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="F9q8nVDE7x1U9W83PhAGqgT9URjlnsx1g"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Wed, 12 Feb 2014 20:34:39 +0000 (UTC)
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop <dnsop@ietf.org>, draft-wkumari-dnsop-alt-tld@tools.ietf.org
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 20:34:43 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--F9q8nVDE7x1U9W83PhAGqgT9URjlnsx1g
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 2/12/14, 10:40 AM, Ted Lemon wrote:
> On Feb 12, 2014, at 1:24 PM, Joe Abley <jabley@hopcount.ca> wrote:
>> I suspect that there would be fewer roadblocks involved in choosing
>> an anchor ALT.ARPA than ALT, since ARPA is under the control of an
>> IETF family member while the root is controlled by distant cousins.
>> If I'm right that this proposal is for future, as-yet-unknown
>> applications, then the choice of anchor should be arbitrary; it
>> feels in that case like the path of least resistance is the right
>> one.
>=20
> It really shouldn't be difficult to make this work, although if .ALT
> is already spoken for a different name might be needed.   If it is in
> fact difficult, then RFC 6761 is pretty pointless.

this discuss could dangerously veer into vanity territory and I'm
probably doing so by dorking with it but.

=2EIANA

seems kind of unambiguous as to where the registry for these things
would be.

> I agree with your other point, though=97this may be useful for future
> efforts, but doesn't address the same problem as the other two
> documents we've talked about.
>=20
> _______________________________________________ DNSOP  mailing list=20
> DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
>=20



--F9q8nVDE7x1U9W83PhAGqgT9URjlnsx1g
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlL72t4ACgkQ8AA1q7Z/VrI+8QCeNVadQbWQn2i+FxohPpZTFKED
LxcAnRDlq1+Cu5+ftmdTIZ0gWmSxNLej
=IQ4I
-----END PGP SIGNATURE-----

--F9q8nVDE7x1U9W83PhAGqgT9URjlnsx1g--


From marka@isc.org  Wed Feb 12 15:10:45 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CA91A0026 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 15:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.55
X-Spam-Level: 
X-Spam-Status: No, score=-0.55 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfCtqOSb9tVM for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 15:10:43 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id B52CA1A002F for <dnsop@ietf.org>; Wed, 12 Feb 2014 15:10:43 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 166472383F5; Wed, 12 Feb 2014 23:10:34 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 82639160058; Wed, 12 Feb 2014 23:11:17 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 89F69160057; Wed, 12 Feb 2014 23:11:16 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id D7572F3414F; Thu, 13 Feb 2014 10:10:29 +1100 (EST)
To: Tim Wicinski <tjw.ietf@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <52F9A377.1080008@gmail.com>
In-reply-to: Your message of "Mon, 10 Feb 2014 23:13:43 -0500." <52F9A377.1080008@gmail.com>
Date: Thu, 13 Feb 2014 10:10:29 +1100
Message-Id: <20140212231029.D7572F3414F@rock.dv.isc.org>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Call for agenda items for London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 23:10:45 -0000

I think there should be some discussion on how to deal with nameservers
that fail to respond to legitimate queries.
draft-andrews-dns-no-response-issue contains some thoughts on the
matter.

I also think we should establish requirements for updating parent
zones.  As a wg we have jumped in the deep end and gone straight
to solutions without working out the actual requirements.

draft-andrews-dnsop-update-parent-zone contains a short requirements
section that may be a good starting point.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From ggm@algebras.org  Wed Feb 12 15:38:55 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 708E41A004E for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 15:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cScDaKqmln45 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 15:38:54 -0800 (PST)
Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCB21A0052 for <dnsop@ietf.org>; Wed, 12 Feb 2014 15:38:51 -0800 (PST)
Received: by mail-pa0-f48.google.com with SMTP id kx10so9847518pab.21 for <dnsop@ietf.org>; Wed, 12 Feb 2014 15:38:50 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7EXWLCVEClQt5dVyQRxTx1CN6pIHCphdNBJDDVFOlGU=; b=UvLBPRA/tuZJ3yXZYz+dJI/tXNcUr/sDNKk9PPoCigeWMMLs0P0qf+yjOuSX6arBLa xbT2XK8hqLqH0oDZtAOObj2CQegsdHFVHvOSeNjJJXc8qrsF6Up71965ylLPiPL9lSUY oI8FhBUHCPLvf7ZtFxKC3NicndSZ7KL9M+KhTm2tGqho2Gsr/hZredDiGRt2OmQdVJ/Q 8W4WDafwRUZLMl9rHlDfiQFSEbKROowOcKin1QUL9LoaESewvmNVZRE9Y68reWi6iTA2 xrLbOlFg+ov9HBXcSMWRYoJMSVSpKfXVIlWOY3x4O65Mg7/6WucfgPCppUQxt1/GAB+1 nHGg==
X-Gm-Message-State: ALoCoQlKXlvTDl1DmZBPo4fUYhsCkn4hevnS8+JtHWn8d4j33fUPqyL2zhthzM3Z0jC7qbhILwQL
MIME-Version: 1.0
X-Received: by 10.67.23.135 with SMTP id ia7mr41868729pad.5.1392248330276; Wed, 12 Feb 2014 15:38:50 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Wed, 12 Feb 2014 15:38:50 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:154b:c651:8e62:8ab5]
In-Reply-To: <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca>
Date: Thu, 13 Feb 2014 09:38:50 +1000
Message-ID: <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: draft-wkumari-dnsop-alt-tld@tools.ietf.org
Content-Type: multipart/alternative; boundary=001a1134519a2a68fd04f23e132e
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 23:38:55 -0000

--001a1134519a2a68fd04f23e132e
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Feb 13, 2014 at 4:24 AM, Joe Abley <jabley@hopcount.ca> wrote:

>
> On 2014-02-12, at 11:28, Marc Blanchet <marc.blanchet@viagenie.ca> wrote:
>
> > - I like better that approach than the previous draft registering many
> tlds.
>
> The previous draft (at least for some of the TLDs) was anchored in the
> reality that changing the name already in use was not practical, e.g.
> there's a sufficient deployed base that uses DNS-like names ending in ONION
> that proposals to use things like ONION.ARPA were non-starters.
>

I dissent from this view. I strongly disagree with any characterisation of
the problem of code replacement in service being intractable, and I think
it is a false premise.

I realize I am probably a lone voice on this, but at *no* time have I felt
the "there are too many already" argument has merit, and it has materially
impeded several outcomes we now face, because of failure to accept the
necessary transition pain. The future is always bigger.


> I think therefore that the ALT draft addresses quite a different problem:
> the choice of DNS-like (but not DNS) name structure for new applications
> that we don't know about yet.
>

And as a consequence I disagree with this too. An orderly migration from
.ONION to another namespace is both feasible and capable of being planned
for.

-G

--001a1134519a2a68fd04f23e132e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Feb 13, 2014 at 4:24 AM, Joe Abley <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:jabley@hopcount.ca" target=3D"_blank">jabley@hopcount.ca</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D""><br>
On 2014-02-12, at 11:28, Marc Blanchet &lt;<a href=3D"mailto:marc.blanchet@=
viagenie.ca">marc.blanchet@viagenie.ca</a>&gt; wrote:<br>
<br>
&gt; - I like better that approach than the previous draft registering many=
 tlds.<br>
<br>
</div>The previous draft (at least for some of the TLDs) was anchored in th=
e reality that changing the name already in use was not practical, e.g. the=
re&#39;s a sufficient deployed base that uses DNS-like names ending in ONIO=
N that proposals to use things like ONION.ARPA were non-starters.<br>
</blockquote><div><br></div><div>I dissent from this view. I strongly disag=
ree with any characterisation of the problem of code replacement in service=
 being intractable, and I think it is a false premise.</div><div><br></div>
<div>I realize I am probably a lone voice on this, but at *no* time have I =
felt the &quot;there are too many already&quot; argument has merit, and it =
has materially impeded several outcomes we now face, because of failure to =
accept the necessary transition pain. The future is always bigger.=A0</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<br>
I think therefore that the ALT draft addresses quite a different problem: t=
he choice of DNS-like (but not DNS) name structure for new applications tha=
t we don&#39;t know about yet.<br></blockquote><div><br></div><div>And as a=
 consequence I disagree with this too. An orderly migration from .ONION to =
another namespace is both feasible and capable of being planned for.</div>
<div><br></div><div>-G=A0</div></div></div></div>

--001a1134519a2a68fd04f23e132e--


From marka@isc.org  Wed Feb 12 16:27:01 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2AE51A0051 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 16:27:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.849
X-Spam-Level: 
X-Spam-Status: No, score=-6.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FH4d27kfsOBW for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 16:26:59 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0C31A0047 for <dnsop@ietf.org>; Wed, 12 Feb 2014 16:26:59 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id B61932383B6; Thu, 13 Feb 2014 00:26:45 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 355A9160058; Thu, 13 Feb 2014 00:27:29 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id C3324160057; Thu, 13 Feb 2014 00:27:28 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id BDB3CF34A2A; Thu, 13 Feb 2014 11:26:42 +1100 (EST)
To: George Michaelson <ggm@algebras.org>
From: Mark Andrews <marka@isc.org>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com>
In-reply-to: Your message of "Thu, 13 Feb 2014 09:38:50 +1000." <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com>
Date: Thu, 13 Feb 2014 11:26:42 +1100
Message-Id: <20140213002642.BDB3CF34A2A@rock.dv.isc.org>
Cc: draft-wkumari-dnsop-alt-tld@tools.ietf.org, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 00:27:01 -0000

In message <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com>,
 George Michaelson writes:
> 
> >
> > On 2014-02-12, at 11:28, Marc Blanchet <marc.blanchet@viagenie.ca> wrote:
> >
> > > - I like better that approach than the previous draft registering many
> > tlds.
> >
> > The previous draft (at least for some of the TLDs) was anchored in the
> > reality that changing the name already in use was not practical, e.g.
> > there's a sufficient deployed base that uses DNS-like names ending in ONION
> > that proposals to use things like ONION.ARPA were non-starters.
> >
> 
> I dissent from this view. I strongly disagree with any characterisation of
> the problem of code replacement in service being intractable, and I think
> it is a false premise.
> 
> I realize I am probably a lone voice on this, but at *no* time have I felt
> the "there are too many already" argument has merit, and it has materially
> impeded several outcomes we now face, because of failure to accept the
> necessary transition pain. The future is always bigger.

You are not a lone voice.  I have already described how to do such
migrations.  They take time but they are do able.
 
> > I think therefore that the ALT draft addresses quite a different problem:
> > the choice of DNS-like (but not DNS) name structure for new applications
> > that we don't know about yet.
> 
> And as a consequence I disagree with this too. An orderly migration from
> .ONION to another namespace is both feasible and capable of being planned
> for.
> 
> -G
> 
> --001a1134519a2a68fd04f23e132e
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
> _quote">On Thu, Feb 13, 2014 at 4:24 AM, Joe Abley <span dir=3D"ltr">&lt;<a=
>  href=3D"mailto:jabley@hopcount.ca" target=3D"_blank">jabley@hopcount.ca</a=
> >&gt;</span> wrote:<br>
> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
> x #ccc solid;padding-left:1ex"><div class=3D""><br>
> On 2014-02-12, at 11:28, Marc Blanchet &lt;<a href=3D"mailto:marc.blanchet@=
> viagenie.ca">marc.blanchet@viagenie.ca</a>&gt; wrote:<br>
> <br>
> &gt; - I like better that approach than the previous draft registering many=
>  tlds.<br>
> <br>
> </div>The previous draft (at least for some of the TLDs) was anchored in th=
> e reality that changing the name already in use was not practical, e.g. the=
> re&#39;s a sufficient deployed base that uses DNS-like names ending in ONIO=
> N that proposals to use things like ONION.ARPA were non-starters.<br>
> </blockquote><div><br></div><div>I dissent from this view. I strongly disag=
> ree with any characterisation of the problem of code replacement in service=
>  being intractable, and I think it is a false premise.</div><div><br></div>
> <div>I realize I am probably a lone voice on this, but at *no* time have I =
> felt the &quot;there are too many already&quot; argument has merit, and it =
> has materially impeded several outcomes we now face, because of failure to =
> accept the necessary transition pain. The future is always bigger.=A0</div>
> <div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
> ;border-left:1px #ccc solid;padding-left:1ex">
> <br>
> I think therefore that the ALT draft addresses quite a different problem: t=
> he choice of DNS-like (but not DNS) name structure for new applications tha=
> t we don&#39;t know about yet.<br></blockquote><div><br></div><div>And as a=
>  consequence I disagree with this too. An orderly migration from .ONION to =
> another namespace is both feasible and capable of being planned for.</div>
> <div><br></div><div>-G=A0</div></div></div></div>
> 
> --001a1134519a2a68fd04f23e132e--
> 
> 
> --===============0150303104473161178==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
> 
> --===============0150303104473161178==--
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From paul@cypherpunks.ca  Wed Feb 12 16:43:46 2014
Return-Path: <paul@cypherpunks.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8323B1A0054 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 16:43:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFyA2ORDaz8p for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 16:43:44 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 6F22F1A0089 for <dnsop@ietf.org>; Wed, 12 Feb 2014 16:43:44 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 7F65E800AA; Wed, 12 Feb 2014 19:43:42 -0500 (EST)
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s1D0hfWd007418; Wed, 12 Feb 2014 19:43:42 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Wed, 12 Feb 2014 19:43:41 -0500 (EST)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Mark Andrews <marka@isc.org>
In-Reply-To: <20140212231029.D7572F3414F@rock.dv.isc.org>
Message-ID: <alpine.LFD.2.10.1402121942230.4632@bofh.nohats.ca>
References: <52F9A377.1080008@gmail.com> <20140212231029.D7572F3414F@rock.dv.isc.org>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Call for agenda items for London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 00:43:46 -0000

On Thu, 13 Feb 2014, Mark Andrews wrote:

> I also think we should establish requirements for updating parent
> zones.  As a wg we have jumped in the deep end and gone straight
> to solutions without working out the actual requirements.

We tried before and failed

http://tools.ietf.org/html/draft-wouters-dnsop-secure-update-use-cases-00

then people got tired of waiting for the problem statement to mature,
and worked on solutions instead.

Paul


From marka@isc.org  Wed Feb 12 17:10:49 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D75AD1A00BA for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 17:10:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c_QjBy8LU71h for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 17:10:48 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF921A00A3 for <dnsop@ietf.org>; Wed, 12 Feb 2014 17:10:42 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 18024C9425; Thu, 13 Feb 2014 01:10:29 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1392253841; bh=IEbUuUT/wn1n8T4RbFlx75hAi82N3wxvsU/MMKT7KR4=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=EzGVCd7l/qzGE9mxDNmXh3zgLGVDCtkgC8EPY+8Au7uK5n++nkvLlRgKloY/DKkCa N9F4atiB6l7n2+XUHJ93DXkVR8U0sxbI/GDbz15Lwukw52Bn5Dle/goXq4mcGIxQAx izxSTP1u3Tz0re3jB5oPK2UCIz5LshOH/C+dZSNM=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Thu, 13 Feb 2014 01:10:29 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 1DC5416005A; Thu, 13 Feb 2014 01:11:13 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id DFABD160057; Thu, 13 Feb 2014 01:11:12 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id BEE96F35057; Thu, 13 Feb 2014 12:10:26 +1100 (EST)
To: Paul Wouters <paul@cypherpunks.ca>
From: Mark Andrews <marka@isc.org>
References: <52F9A377.1080008@gmail.com> <20140212231029.D7572F3414F@rock.dv.isc.org> <alpine.LFD.2.10.1402121942230.4632@bofh.nohats.ca>
In-reply-to: Your message of "Wed, 12 Feb 2014 19:43:41 -0500." <alpine.LFD.2.10.1402121942230.4632@bofh.nohats.ca>
Date: Thu, 13 Feb 2014 12:10:26 +1100
Message-Id: <20140213011026.BEE96F35057@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Call for agenda items for London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 01:10:50 -0000

In message <alpine.LFD.2.10.1402121942230.4632@bofh.nohats.ca>, Paul Wouters wri
tes:
> On Thu, 13 Feb 2014, Mark Andrews wrote:
> 
> > I also think we should establish requirements for updating parent
> > zones.  As a wg we have jumped in the deep end and gone straight
> > to solutions without working out the actual requirements.
> 
> We tried before and failed
> 
> http://tools.ietf.org/html/draft-wouters-dnsop-secure-update-use-cases-00
> 
> then people got tired of waiting for the problem statement to mature,
> and worked on solutions instead.
> 
> Paul

Which is no reason to not to try to get a list of requirements out
of it now.  draft-wouters-dnsop-secure-update-use-cases provides
useful background to evaluate the requirements listed in
draft-andrews-dnsop-update-parent-zones.  Are they complete?

We need to look at what goes over the wire.  Does it support all
the use cases?

We need to look at whether there are places to put the policy knobs.

Mark

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From drc@virtualized.org  Wed Feb 12 17:48:16 2014
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA4C1A00AB for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 17:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_54=0.6, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXxx-dE0wHwF for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2014 17:48:12 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 083701A0091 for <dnsop@ietf.org>; Wed, 12 Feb 2014 17:48:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id C3EC684CEE; Wed, 12 Feb 2014 20:48:09 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 35141-08; Wed, 12 Feb 2014 20:48:09 -0500 (EST)
Received: from [10.0.1.2] (50-201-180-2-static.hfc.comcastbusiness.net [50.201.180.2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id E09BB84B43; Wed, 12 Feb 2014 20:48:08 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_AAEF8AEC-4921-4852-B85C-B21200B1BAC7"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com>
Date: Wed, 12 Feb 2014 20:48:01 -0500
Message-Id: <24C0A347-0230-4760-9E49-05F701A11AE2@virtualized.org>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.1827)
Cc: draft-wkumari-dnsop-alt-tld@tools.ietf.org, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 01:48:16 -0000

--Apple-Mail=_AAEF8AEC-4921-4852-B85C-B21200B1BAC7
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_401D545D-E39C-4F6A-83F4-CAC12415873D"


--Apple-Mail=_401D545D-E39C-4F6A-83F4-CAC12415873D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Feb 12, 2014, at 6:38 PM, George Michaelson <ggm@algebras.org> wrote:
> The previous draft (at least for some of the TLDs) was anchored in the =
reality that changing the name already in use was not practical, e.g. =
there's a sufficient deployed base that uses DNS-like names ending in =
ONION that proposals to use things like ONION.ARPA were non-starters.
>=20
> I dissent from this view. I strongly disagree with any =
characterisation of the problem of code replacement in service being =
intractable, and I think it is a false premise.

+1=20

> I realize I am probably a lone voice on this, but at *no* time have I =
felt the "there are too many already" argument has merit, and it has =
materially impeded several outcomes we now face, because of failure to =
accept the necessary transition pain. The future is always bigger.=20

I once heard a story about the author of make(1) realizing that perhaps =
having the tab character be significant in makefiles might not have been =
the best choice, but deciding against fixing it because the installed =
base of systems using make(1) at the time -- all 200 of them -- was too =
large.

>=20
> I think therefore that the ALT draft addresses quite a different =
problem: the choice of DNS-like (but not DNS) name structure for new =
applications that we don't know about yet.
>=20
> And as a consequence I disagree with this too. An orderly migration =
from .ONION to another namespace is both feasible and capable of being =
planned for.

While I agree, pragmatically, I'm unsure there is incentive for the =
maintainers to move (which I think where Joe was going). As such, we're =
in the increasingly common quandary of figuring out how to document =
reality despite violation of policy or ignoring reality to ensure purity =
of policy.

Has anyone asked the folks coding .ONION (or others) if they're willing =
to migrate, pointing out the downsides if they choose not to?=20

Regards,
-drc


--Apple-Mail=_401D545D-E39C-4F6A-83F4-CAC12415873D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Feb =
12, 2014, at 6:38 PM, George Michaelson &lt;<a =
href=3D"mailto:ggm@algebras.org">ggm@algebras.org</a>&gt; =
wrote:<br><div><blockquote type=3D"cite"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto;">The previous draft (at least for some of the TLDs) was anchored =
in the reality that changing the name already in use was not practical, =
e.g. there's a sufficient deployed base that uses DNS-like names ending =
in ONION that proposals to use things like ONION.ARPA were =
non-starters.<br>
</blockquote><div><br></div><div>I dissent from this view. I strongly =
disagree with any characterisation of the problem of code replacement in =
service being intractable, and I think it is a false =
premise.</div></div></div></div></blockquote><div><br></div>+1&nbsp;</div>=
<div><br><blockquote type=3D"cite"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div>I realize I am =
probably a lone voice on this, but at *no* time have I felt the "there =
are too many already" argument has merit, and it has materially impeded =
several outcomes we now face, because of failure to accept the necessary =
transition pain. The future is always =
bigger.&nbsp;</div></div></div></div></blockquote><div><br></div><div>I =
once heard a story about the author of make(1) realizing that perhaps =
having the tab character be significant in makefiles might not have been =
the best choice, but deciding against fixing it because the installed =
base of systems using make(1) at the time -- all 200 of them -- was too =
large.</div><br><blockquote type=3D"cite"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto;"><br>I think therefore that the ALT draft addresses quite a =
different problem: the choice of DNS-like (but not DNS) name structure =
for new applications that we don't know about =
yet.<br></blockquote><div><br></div><div>And as a consequence I disagree =
with this too. An orderly migration from .ONION to another namespace is =
both feasible and capable of being planned for.</div>
</div></div></div></blockquote><br></div><div>While I agree, =
pragmatically, I'm unsure there is incentive for the maintainers to move =
(which I think where Joe was going). As such, we're in the increasingly =
common quandary of figuring out how to document reality despite =
violation of policy or ignoring reality to ensure purity of =
policy.</div><div><br></div><div>Has anyone asked the folks coding =
.ONION (or others) if they're willing to migrate, pointing out the =
downsides if they choose not =
to?&nbsp;</div><div><br></div><div>Regards,</div><div>-drc</div><div><br><=
/div></body></html>=

--Apple-Mail=_401D545D-E39C-4F6A-83F4-CAC12415873D--

--Apple-Mail=_AAEF8AEC-4921-4852-B85C-B21200B1BAC7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJS/CRSAAoJENV6ebf0/4rXhekIANmQhi1q7cyULv0JRLQCrcA9
4vAgOMCIEL9q/jQA07fO5VdZ3ro8RR7wSpEL7qkoi8KYimtkK3pPg2sRRxZzbyK6
Pxtiu7O9IXiuKJMCAMiUCY0U6iSK56vWqJ4o7Ly/ERFS0RkaZd7tfEK/wgqwdinp
gwt6KxiCYlpfimgqMxEc/nWID+bbSmYWWqxC7OJ8FBjt8/eUHIg5ORFaQ6drOphP
v1/KgKypohhRTBc6mGysoALSQq0Rn9WdQlWzr9f9xcF5uMLkbvnFx7u+iPpf0I/l
GD1zymghQII0Ge3mPj/cSE2qOQoZbGk4RJvoQYIftQ2Hbssuc4bjFzDxCAgfxEw=
=O4cG
-----END PGP SIGNATURE-----

--Apple-Mail=_AAEF8AEC-4921-4852-B85C-B21200B1BAC7--


From arturo.servin@gmail.com  Thu Feb 13 04:01:45 2014
Return-Path: <arturo.servin@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 054771A0203 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 04:01:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3q9llk7ww0o for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 04:01:43 -0800 (PST)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id BE0B51A018C for <dnsop@ietf.org>; Thu, 13 Feb 2014 04:01:42 -0800 (PST)
Received: by mail-qg0-f41.google.com with SMTP id i50so1120571qgf.0 for <dnsop@ietf.org>; Thu, 13 Feb 2014 04:01:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=xW6q/QCOKeqsImFvVHaGP5T7w4BM8O7250+1SNr5lvE=; b=zQSWIb2gLZhTq3ZJX1QXvgLIXQYn2/Vrtuo1ptd244w7Ft60m0i07w27fprUjgz7QJ KLYIssslRTlNFtMu0Cj3Z2vrVoNw9fjiLPAz3tBV77T9tKvLWFf/mNpLq2RPrNAsQquU tVJSc5QziXoeXNdQJuk5QKFOGjgPicqM35d12AcAAOjtSFNaMpc3nQALaTEJVyxNwpVq qMFD40ykZ2Te4MQDRuAaEuo1+lpfbbCucBWTOzHc5OrRK/17d9QcQa9GHRUeaurZCGJY lNyrT9joM5FaIanWSFr4kPF2fgpBDRcatqgonD8H5tZHXh4mS2SE0ZTj7z+30VxMRZSM Jnjg==
X-Received: by 10.140.51.170 with SMTP id u39mr1492813qga.69.1392292901440; Thu, 13 Feb 2014 04:01:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.87.69 with HTTP; Thu, 13 Feb 2014 04:01:21 -0800 (PST)
In-Reply-To: <20140210205838.15973.63281.idtracker@ietfa.amsl.com>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com>
From: Arturo Servin <arturo.servin@gmail.com>
Date: Thu, 13 Feb 2014 13:01:21 +0100
Message-ID: <CALo9H1Y_ANcNmHzNDg3oGzTOD8N5QVc9Pjk10bdMeSBtaq_0KA@mail.gmail.com>
To: dnsop@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 12:01:45 -0000

"4.  IANA Considerations"

I prefer option 2. A fully uncoordinated space, otherwise we will open
a policy can of worms.

-as



On Mon, Feb 10, 2014 at 9:58 PM,  <internet-drafts@ietf.org> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>         Title           : The ALT Special Use Top Level Domain
>         Authors         : Warren Kumari
>                           Andrew Sullivan
>         Filename        : draft-wkumari-dnsop-alt-tld-00.txt
>         Pages           : 6
>         Date            : 2014-02-10
>
> Abstract:
>    This document reserves a string to be used as a TLD label in non-DNS
>    contexts.  [Ed note: By now you should be wildly confused.  Go read
>    the intro / background :-P ]
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-wkumari-dnsop-alt-tld-00
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From ajs@anvilwalrusden.com  Thu Feb 13 06:59:41 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F40151A01F1 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 06:59:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tx3rlmqDuemZ for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 06:59:39 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9DB1A008E for <dnsop@ietf.org>; Thu, 13 Feb 2014 06:59:39 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id BE95A8A031 for <dnsop@ietf.org>; Thu, 13 Feb 2014 14:59:37 +0000 (UTC)
Date: Thu, 13 Feb 2014 09:59:32 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140213145932.GE25409@mx1.yitter.info>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 14:59:41 -0000

On Wed, Feb 12, 2014 at 01:24:07PM -0500, Joe Abley wrote:
> 
> I think therefore that the ALT draft addresses quite a different problem: the choice of DNS-like (but not DNS) name structure for new applications that we don't know about yet.
> 

I won't speak for Warren, but certainly this is _my_ view of our goal.
I do not want our current proposal (which doubtless needs improvements
in details) to get bound up with whether existing uses ought instead
to be subsumed.  But on another list we just heard about yet _another_
of these "pseudo-TLDs" crawling out of the woodwork.  When it was
observed to said pseudo-TLD pusher that the approach might run into
fewer problems if it were anchored somewhere else, he said that it was
a feature that it attacked the IANA root.  If we don't have an
ordinary and standard place where such uses can fit, then these sorts
of vandals will have a pragmatic argument open to them.  If we _do_
have a standard place for this stuff, then at least the pragmatic
argument will be closed, and we can have a discussion about the merits,
understanding that the goal really is in many cases to attack the
orderly operation of the public DNS.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From mglt.ietf@gmail.com  Thu Feb 13 07:18:00 2014
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32F611A01F1 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHImEoaFaPpJ for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:17:53 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 421DD1A0291 for <dnsop@ietf.org>; Thu, 13 Feb 2014 07:17:47 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id u57so7555086wes.39 for <dnsop@ietf.org>; Thu, 13 Feb 2014 07:17:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ebNmL4IwzQnVruE73BhUz+cZAqLcm1jDo08wweVvHwg=; b=J2e6d25Yf+X291AN5xc5VfkJz1Gtk+l5Og6qlXMP1m3KHga8wJzz5Qdl56vOZZVYRv gzLER2xKxnsNRnxEpMKN7kpuq7IrmCa0j+813SWBYnKfCklamcioSxzkWr3OHqQ1dJLE H1m9EEj3LVtKrye3oB+mZZjvVC+j/9MoBNyIfKpKKU8NPJnKAyJS1XgyD1wceyiEl+jW mIQU4FLEWOtdVr614aL/0Skv28OEI6xxVF/wUub2zPJawX00Au57bBnmA6/7ta+ZZYOM XwcL0S/2gTFgggzGoBgFxyfbhRrH5/pfkWWscaLSpQ4YG2xQhYry5L6MD9ggM19f4ezM qe/g==
MIME-Version: 1.0
X-Received: by 10.180.91.17 with SMTP id ca17mr6978199wib.41.1392304665680; Thu, 13 Feb 2014 07:17:45 -0800 (PST)
Received: by 10.194.171.129 with HTTP; Thu, 13 Feb 2014 07:17:45 -0800 (PST)
Date: Thu, 13 Feb 2014 16:17:45 +0100
Message-ID: <CADZyTkk1LOM9R=vP+fc4HGjUVoZE2VxtpmSyEE-0A8mTHUKgNA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [DNSOP] draft-mglt-dnsop-dnssec-validator-requirements-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 15:18:00 -0000

Hi,

Please find a draft listing requirements for a DNSSEC Validator.
Initially, I presented a draft in homenet about DHCP options for a
DNSSEC validators. After feed backs I received I decided to work first
on the requirements.

Feel free to comment them.

BR,
Daniel


A new version of I-D, draft-mglt-dnsop-dnssec-validator-requirements-00.txt
has been successfully submitted by Daniel Migault and posted to the
IETF repository.

Name: draft-mglt-dnsop-dnssec-validator-requirements
Revision: 00
Title: DNSSEC Validators Requirements
Document date: 2014-02-13
Group: Individual Submission
Pages: 9
URL:
http://www.ietf.org/internet-drafts/draft-mglt-dnsop-dnssec-validator-requirements-00.txt
Status:
https://datatracker.ietf.org/doc/draft-mglt-dnsop-dnssec-validator-requirements/
Htmlized:
http://tools.ietf.org/html/draft-mglt-dnsop-dnssec-validator-requirements-00


Abstract:
   DNSSEC provides data integrity and authentication for DNSSEC
   validators.  However, without valid trust anchor(s) and an acceptable
   value for the current time, DNSSEC validation cannot be performed.
   This document lists the requirements to be addressed so resolvers can
   have DNSSEC validation can be always-on.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58


From marc.blanchet@viagenie.ca  Thu Feb 13 07:23:58 2014
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3971E1A0273 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIjRMC42MTLi for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:23:55 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id CE0C81A01F7 for <dnsop@ietf.org>; Thu, 13 Feb 2014 07:23:55 -0800 (PST)
Received: from [IPv6:2620:0:230:2002::1001] (unknown [IPv6:2620:0:230:2002::1001]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 49886401F9 for <dnsop@ietf.org>; Thu, 13 Feb 2014 10:23:53 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <20140213145932.GE25409@mx1.yitter.info>
Date: Thu, 13 Feb 2014 10:23:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info>
To: dnsop@ietf.org
X-Mailer: Apple Mail (2.1827)
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 15:23:58 -0000

ok, maybe this suggestion below is weird, but...=20
- since they are not looking at a real delegated TLD.
- why not just register a URN namespace and use it as they see fit?

Marc.

Le 2014-02-13 =E0 09:59, Andrew Sullivan <ajs@anvilwalrusden.com> a =
=E9crit :

> On Wed, Feb 12, 2014 at 01:24:07PM -0500, Joe Abley wrote:
>>=20
>> I think therefore that the ALT draft addresses quite a different =
problem: the choice of DNS-like (but not DNS) name structure for new =
applications that we don't know about yet.
>>=20
>=20
> I won't speak for Warren, but certainly this is _my_ view of our goal.
> I do not want our current proposal (which doubtless needs improvements
> in details) to get bound up with whether existing uses ought instead
> to be subsumed.  But on another list we just heard about yet _another_
> of these "pseudo-TLDs" crawling out of the woodwork.  When it was
> observed to said pseudo-TLD pusher that the approach might run into
> fewer problems if it were anchored somewhere else, he said that it was
> a feature that it attacked the IANA root.  If we don't have an
> ordinary and standard place where such uses can fit, then these sorts
> of vandals will have a pragmatic argument open to them.  If we _do_
> have a standard place for this stuff, then at least the pragmatic
> argument will be closed, and we can have a discussion about the =
merits,
> understanding that the goal really is in many cases to attack the
> orderly operation of the public DNS.
>=20
> Best regards,
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From paf@frobbit.se  Thu Feb 13 07:49:49 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 405781A02EF for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2rfQEbF2FWna for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:49:48 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 42E741A02DE for <dnsop@ietf.org>; Thu, 13 Feb 2014 07:49:47 -0800 (PST)
Received: from ix-2.local (c-98-218-15-63.hsd1.dc.comcast.net [98.218.15.63]) by mail.frobbit.se (Postfix) with ESMTPSA id 7E91120400; Thu, 13 Feb 2014 16:49:44 +0100 (CET)
Message-ID: <52FCE993.3070005@frobbit.se>
Date: Thu, 13 Feb 2014 10:49:39 -0500
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop@ietf.org
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info> <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca>
In-Reply-To: <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vdwv25i6Ds3CoF7HNbruNpSbwLngjcTcD"
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 15:49:49 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--vdwv25i6Ds3CoF7HNbruNpSbwLngjcTcD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-13 10:23, Marc Blanchet wrote:
> - why not just register a URN namespace and use it as they see fit?

Because you only type in a string that "looks like a domain name" in
applications (for example browsers) without the URI scheme nowadays, and
people want that to work also with strings in other namespaces.

I.e. it all, from my perspective, have to do with where the signalling
is on what namespace to use. And if that signalling is inline, then we
do have something that can be viewed as the equivalent of a namespace
collision.

If people had entered the URI scheme all the time, including "http",
then we would have been in a different situation.

   Patrik



--vdwv25i6Ds3CoF7HNbruNpSbwLngjcTcD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS/OmWrMabGguI180RAnIjAJ4+gd81TamT6QtV1OkYAFVGtpgS2gCePfJV
jvawgH0eX7X2QhT2jr1d2Go=
=F3kI
-----END PGP SIGNATURE-----

--vdwv25i6Ds3CoF7HNbruNpSbwLngjcTcD--


From ajs@anvilwalrusden.com  Thu Feb 13 07:58:42 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D41F11A020D for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:58:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQ-6b9Au_KZM for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 07:58:41 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 8CECB1A02F5 for <dnsop@ietf.org>; Thu, 13 Feb 2014 07:58:41 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 494098A031 for <dnsop@ietf.org>; Thu, 13 Feb 2014 15:58:40 +0000 (UTC)
Date: Thu, 13 Feb 2014 10:58:38 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140213155838.GH25409@mx1.yitter.info>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info> <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 15:58:43 -0000

On Thu, Feb 13, 2014 at 10:23:52AM -0500, Marc Blanchet wrote:
> ok, maybe this suggestion below is weird, but... 
> - since they are not looking at a real delegated TLD.
> - why not just register a URN namespace and use it as they see fit?

Why didn't they do that in the first place?

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From ogud@ogud.com  Thu Feb 13 08:19:30 2014
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A95A1A0334 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 08:19:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WFxS_jV_yvxN for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 08:19:29 -0800 (PST)
Received: from smtp125.ord1c.emailsrvr.com (smtp125.ord1c.emailsrvr.com [108.166.43.125]) by ietfa.amsl.com (Postfix) with ESMTP id 256881A030A for <dnsop@ietf.org>; Thu, 13 Feb 2014 08:19:29 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D6D3B1A0227; Thu, 13 Feb 2014 11:19:27 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp8.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id AC0561A01C8;  Thu, 13 Feb 2014 11:19:26 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <52FCE993.3070005@frobbit.se>
Date: Thu, 13 Feb 2014 11:19:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D38F596A-9DC3-49A1-A4D7-FF86F3AC1FBD@ogud.com>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info> <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca> <52FCE993.3070005@frobbit.se>
To: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1510)
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 16:19:30 -0000

On Feb 13, 2014, at 10:49 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:

> On 2014-02-13 10:23, Marc Blanchet wrote:
>> - why not just register a URN namespace and use it as they see fit?
>=20
> Because you only type in a string that "looks like a domain name" in
> applications (for example browsers) without the URI scheme nowadays, =
and
> people want that to work also with strings in other namespaces.
>=20
> I.e. it all, from my perspective, have to do with where the signalling
> is on what namespace to use. And if that signalling is inline, then we
> do have something that can be viewed as the equivalent of a namespace
> collision.
>=20
> If people had entered the URI scheme all the time, including "http",
> then we would have been in a different situation.


I think that the draft is not radical enough it is trying to provide =
some belt and suspenders to a=20
syntom rather than address the actual problem.=20

The Meta problem is Multiple Namespaces with different resolution =
technologies.=20
Addressing this via a SUFFIX in the domain name feels wrong,=20
What I will propose is a Namespace layer solution that is a prefix to =
the name presented,=20
thus names will be presented to the namespace layer as =
<namespace/name-encoding><space separator><name>=20
Examples using ## as the separator
	DNS##www.example.com    This is normal DNS name,=20
	GNU##eff=20
	DUTF8##=85.. (DNS name in UTF8 format)=20
	www.example.net    (by default the name is DNS)=20
=09
With a namespace layer we can have the host reject lookup locally if it =
does not know how to handle the namespace,
rather than dump it out as ".alt" query.=20

I know this requires changes in lookup services and code, but it moves =
the effort to the people that want new namespaces.=20

	Olafur
PS: IANA should maintain a registry of namespaces


From nobody Thu Feb 13 12:56:49 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D079B1A045B for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 12:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OliSga2yMUQ for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 12:56:45 -0800 (PST)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id 935601A04CC for <dnsop@ietf.org>; Thu, 13 Feb 2014 12:56:27 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:59709) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1WE3Kb-0000Hq-1h (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 13 Feb 2014 20:56:25 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WE3Kb-0005mT-Fd (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 13 Feb 2014 20:56:25 +0000
Date: Thu, 13 Feb 2014 20:56:25 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: dnsop@ietf.org
Message-ID: <alpine.LSU.2.00.1402132050440.18502@hermes-1.csi.cam.ac.uk>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/EXspj6PJyE8DllvhO9fc-U1uttk
Cc: Tony Finch <dot@dotat.at>
Subject: [DNSOP] draft-fanf-dnsop-trust-anchor-witnesses-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 20:56:49 -0000

There was some discussion last month about dispersing trust in the root.
http://www.ietf.org/mail-archive/web/dnsop/current/msg10977.html

This inspired me to write up a concrete proposal for the
quorum-of-witnesses idea that I have vaguely suggested several
times over the last few years.

All thoughts / suggestions / criticisms welcomed.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

---------- Forwarded message ----------
Date: Thu, 13 Feb 2014 12:50:35 -0800
From: internet-drafts@ietf.org
To: Tony Finch <dot@dotat.at>, Tony Finch <dot@dotat.at>
Subject: New Version Notification for
    draft-fanf-dnsop-trust-anchor-witnesses-00.txt


A new version of I-D, draft-fanf-dnsop-trust-anchor-witnesses-00.txt
has been successfully submitted by Tony Finch and posted to the
IETF repository.

Name:		draft-fanf-dnsop-trust-anchor-witnesses
Revision:	00
Title:		The WS resource record: dispersing trust in the DNSSEC root keys
Document date:	2014-02-13
Group:		Individual Submission
Pages:		11
URL:            http://www.ietf.org/internet-drafts/draft-fanf-dnsop-trust-anchor-witnesses-00.txt
Status:         https://datatracker.ietf.org/doc/draft-fanf-dnsop-trust-anchor-witnesses/
Htmlized:       http://tools.ietf.org/html/draft-fanf-dnsop-trust-anchor-witnesses-00


Abstract:
   At the moment the root DNSSEC key is a single point of trust and a
   single point of failure for the whole system.  This memo describes a
   mechanism for dispersing trust in the root key.  Witnesses vouch for
   the root trust anchor by publishing WS records in the DNS.
   Validators only update their root trust anchors if multiple witnesses
   agree.  The root-witnesses.arpa zone enables a validator to bootstrap
   trust when it has no working trust anchors other than its witnesses.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


From nobody Thu Feb 13 15:40:18 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 025E51A0023 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 15:40:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05kL8YsvuNXW for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 15:40:12 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 4B3161A000B for <dnsop@ietf.org>; Thu, 13 Feb 2014 15:40:12 -0800 (PST)
Received: from ix-2.local (c-98-218-15-63.hsd1.dc.comcast.net [98.218.15.63]) by mail.frobbit.se (Postfix) with ESMTPSA id 83B571FD41; Fri, 14 Feb 2014 00:40:09 +0100 (CET)
Message-ID: <52FD57D7.30004@frobbit.se>
Date: Thu, 13 Feb 2014 18:40:07 -0500
From: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info> <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca> <52FCE993.3070005@frobbit.se> <D38F596A-9DC3-49A1-A4D7-FF86F3AC1FBD@ogud.com>
In-Reply-To: <D38F596A-9DC3-49A1-A4D7-FF86F3AC1FBD@ogud.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QDwKdCffre1QnRLJIgXfHkLJVXrxNeM06"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Dc4xTzM0NT5KyZER1nseRYz7X1Q
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 23:40:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--QDwKdCffre1QnRLJIgXfHkLJVXrxNeM06
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 2014-02-13 11:19, Olafur Gudmundsson wrote:
>=20
> On Feb 13, 2014, at 10:49 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wro=
te:
>=20
>> On 2014-02-13 10:23, Marc Blanchet wrote:
>>> - why not just register a URN namespace and use it as they see fit?
>>
>> Because you only type in a string that "looks like a domain name" in
>> applications (for example browsers) without the URI scheme nowadays, a=
nd
>> people want that to work also with strings in other namespaces.
>>
>> I.e. it all, from my perspective, have to do with where the signalling=

>> is on what namespace to use. And if that signalling is inline, then we=

>> do have something that can be viewed as the equivalent of a namespace
>> collision.
>>
>> If people had entered the URI scheme all the time, including "http",
>> then we would have been in a different situation.
>=20
>=20
> I think that the draft is not radical enough it is trying to provide so=
me belt and suspenders to a=20
> syntom rather than address the actual problem.=20
>=20
> The Meta problem is Multiple Namespaces with different resolution techn=
ologies.=20
> Addressing this via a SUFFIX in the domain name feels wrong,=20
> What I will propose is a Namespace layer solution that is a prefix to t=
he name presented,=20
> thus names will be presented to the namespace layer as <namespace/name-=
encoding><space separator><name>=20
> Examples using ## as the separator
> 	DNS##www.example.com    This is normal DNS name,=20
> 	GNU##eff=20
> 	DUTF8##=85.. (DNS name in UTF8 format)=20
> 	www.example.net    (by default the name is DNS)=20
> =09
> With a namespace layer we can have the host reject lookup locally if it=
 does not know how to handle the namespace,
> rather than dump it out as ".alt" query.=20
>=20
> I know this requires changes in lookup services and code, but it moves =
the effort to the people that want new namespaces.=20
>=20
> 	Olafur
> PS: IANA should maintain a registry of namespaces

This is to me approximately like the URI scheme idea, but a different
syntax. Can fly, might not fly.

The whole question is what the application developers and marketing
people will print on bulletin boards and accept in input fields in
applications (and their configurations).

Which unfortunately means we do not know until some time after we have
tried to standardize it... :-P

   Patrik




--QDwKdCffre1QnRLJIgXfHkLJVXrxNeM06
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS/VfXrMabGguI180RAlqkAJ44iv46gcd357xE5dVcjVBRxv7OxgCcC6Pm
JA/4Nb68wwiekQiZkzmIvs4=
=EkaP
-----END PGP SIGNATURE-----

--QDwKdCffre1QnRLJIgXfHkLJVXrxNeM06--


From nobody Thu Feb 13 15:45:55 2014
Return-Path: <matthaeus.wander@uni-due.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 736BB1A04E3 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 15:45:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbFBE4Xo7vRs for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 15:45:46 -0800 (PST)
Received: from mailout.uni-due.de (mailout.uni-due.de [132.252.185.19]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1431A0037 for <dnsop@ietf.org>; Thu, 13 Feb 2014 15:45:45 -0800 (PST)
Received: from [192.168.178.20] (dsbg-4db57a18.pool.mediaWays.net [77.181.122.24]) (authenticated bits=0) by mailout.uni-due.de (8.13.1/8.13.1) with ESMTP id s1DNjfme026140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 14 Feb 2014 00:45:41 +0100
Message-ID: <52FD5922.40205@uni-due.de>
Date: Fri, 14 Feb 2014 00:45:38 +0100
From: =?ISO-8859-1?Q?Matth=E4us_Wander?= <matthaeus.wander@uni-due.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>, dnsop@ietf.org
References: <alpine.LSU.2.00.1402132050440.18502@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1402132050440.18502@hermes-1.csi.cam.ac.uk>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020203030500020003010400"
X-Virus-Scanned: Clam Anti Virus - http://www.clamav.net
X-Spam-Scanned: SpamAssassin: 3.002004 - http://www.spamassassin.org
X-Scanned-By: MIMEDefang 2.57 on 132.252.185.19
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/NnXd54oqn-N06R3GP9IZnkxs1xE
Subject: Re: [DNSOP] draft-fanf-dnsop-trust-anchor-witnesses-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 23:45:49 -0000

This is a cryptographically signed message in MIME format.

--------------ms020203030500020003010400
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

* Tony Finch [2014-02-13 21:56]:
> There was some discussion last month about dispersing trust in the root=
=2E
> http://www.ietf.org/mail-archive/web/dnsop/current/msg10977.html
>=20
> This inspired me to write up a concrete proposal for the
> quorum-of-witnesses idea that I have vaguely suggested several
> times over the last few years.

The proposed approach disperses the trust into which TA to choose and
when to rollover to a new TA. However, it does not disperse the trust
that the TA is not misused and not compromised. If I have to fully trust
the TA private key holder anyway, my personal assessment would be to
trust their TA publication channel as well, e.g. the ones in
draft-jabley-dnssec-trust-anchor.

The problem I see is the asymmetry of roles between the TA private key
holder and the witnesses. The witnesses have no means to assert that the
TA holder does not share the key with their government or anybody else.
To disperse the trust of a key, you would need a threshold cryptosystem
where the TA private key portions are shared among equal peers.

Regards,
Matt

--=20
Universit=E4t Duisburg-Essen
Verteilte Systeme
Bismarckstr. 90 / BC 316
47057 Duisburg


--------------ms020203030500020003010400
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIPTzCC
BCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVy
MSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBa
Fw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAw
DgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U
1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6
fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869
080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqD
oZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkh
nSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYDVR0fBGkwZzBloGOgYYZfaHR0cDov
L3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNy
bF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/
6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX
3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvhERHua3iR
M347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0Ja6ba
hWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ
hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyH
xQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIFYDCCBEigAwIBAgIEDBrviDAN
BgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4G
A1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTA4MDQwODEzMjQxMFoXDTE5MDYzMDAwMDAwMFowgcYxCzAJBgNVBAYTAkRFMSQwIgYDVQQK
ExtVbml2ZXJzaXRhZXQgRHVpc2J1cmctRXNzZW4xNTAzBgNVBAsTLFplbnRydW0gZnVlciBJ
bmZvcm1hdGlvbnMtIHVuZCBNZWRpZW5kaWVuc3RlMSwwKgYDVQQDEyNVbml2ZXJzaXRhZXQg
RHVpc2J1cmctRXNzZW4gQ0EgLUcwMTEsMCoGCSqGSIb3DQEJARYdY2FhZG1pbkB1bmktZHVp
c2J1cmctZXNzZW4uZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCrlesmTmiM
kKzPuHIJDUpxpjiCkPL18fopC9Cue4n1xRBxPnSEssI/2XAb4kHWrJmlPjd2281P2HmIQkaj
+mPOw0xGkzYan/rKRb8gvwb4v/cJhC7TIioPTQ7NfvfMg5hoNYW7mcykAEY0eFlO80dLHNLL
MUQm8VRxPDS9sDlHgIUadmM1YNkgJ3PB0f0DqR7WiLoyggLdvxIZDkCncFpkhbrvfXU0kQVU
cj8kMNG5F5EgNUa/1kTpqfOU+3jAikYMPlPhfW4NvKbSpm8p5BbRHJQlte20pTeWFGAatv6R
jO10eWHoP88lS9qiOmH+kk/cqqP2tzPo4aE62BiGi4OJAgMBAAGjggG/MIIBuzASBgNVHRMB
Af8ECDAGAQH/AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQUZma8lptITejdvCKnplvVqEGf
le4wHwYDVR0jBBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwKAYDVR0RBCEwH4EdY2FhZG1p
bkB1bmktZHVpc2J1cmctZXNzZW4uZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2Rw
MS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdo
dHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3Js
MIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5k
ZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0
dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQu
Y3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCOZYvvu9iso7h38+NZkO9pxV5B7IqOutVj0U3c1b4W
DgcGO+FIm61k4uFTr8FMh2CCZYl6mhJEimSIHMn5LUGAguLh7DrouddbPiHTfuS5obYEwf+g
udzFutXFDD+D3zKaQE8+gZUzIWZQCP1Zw9r02X0K7N8y3l3cQRysh13vGAdK0DQShuRYIEaP
fpkqJdBIvP+KzMjvAovEeg7v7emsGgZakVKrghmlzEiIxcEUY5XKhPZRSYvONTOO/rFQ28m6
mfmO8mPKSYni57PG26eNNyRQJXMO8lodXTIlw6wUSuncMSd0IrwDLcLA6ayxuQaFzChSIHaT
nwdpvAv9QEu4MIIFwjCCBKqgAwIBAgIHFAVKqFI8xjANBgkqhkiG9w0BAQUFADCBxjELMAkG
A1UEBhMCREUxJDAiBgNVBAoTG1VuaXZlcnNpdGFldCBEdWlzYnVyZy1Fc3NlbjE1MDMGA1UE
CxMsWmVudHJ1bSBmdWVyIEluZm9ybWF0aW9ucy0gdW5kIE1lZGllbmRpZW5zdGUxLDAqBgNV
BAMTI1VuaXZlcnNpdGFldCBEdWlzYnVyZy1Fc3NlbiBDQSAtRzAxMSwwKgYJKoZIhvcNAQkB
Fh1jYWFkbWluQHVuaS1kdWlzYnVyZy1lc3Nlbi5kZTAeFw0xMjA2MjMxNDA1MTJaFw0xNTA2
MjMxNDA1MTJaMGoxCzAJBgNVBAYTAkRFMSQwIgYDVQQKExtVbml2ZXJzaXRhZXQgRHVpc2J1
cmctRXNzZW4xGjAYBgNVBAsTEVZlcnRlaWx0ZSBTeXN0ZW1lMRkwFwYDVQQDExBNYXR0aGFl
dXMgV2FuZGVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnb3m8zkICsRFcXby
DiMh6u5E68UcglCXg0Z10nmripU5DCJqWnPAiaFt14GL3S9Sgongm1z3lS88rbXJv/xW1yKh
RcTbBCUx80+Cdz+JQsx2pQWVSY+0FwY4GsMFmZOgZAObJkcKP/LtGyQlLIonk8CxNtO5BM6Q
x8h7IoYDbpKbPnPe8HxgQFdVHSrjsy/hM0gqskaxotsiDNd2Z1yeolYYqwJs3Q2FHcQctvCT
oD66hCgJ/B1w6xqrVsHl0pKzrGsVHWzJ/4+BeyfU1vpqMfdnfGN8unIlpAh5SP7X1ayRY+Fg
UsVVob++KQMtBWRrLeViiF0+XRo9K7k2GhIHJQIDAQABo4ICDjCCAgowHAYDVR0gBBUwEzAR
Bg8rBgEEAYGtIYIsAQEEAgIwCQYDVR0TBAIwADALBgNVHQ8EBAMCBeAwHQYDVR0lBBYwFAYI
KwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTaAPmgfOfyKtJ9FoeGvPD28Uun8zAfBgNV
HSMEGDAWgBRmZryWm0hN6N28IqemW9WoQZ+V7jAmBgNVHREEHzAdgRttYXR0aGFldXMud2Fu
ZGVyQHVuaS1kdWUuZGUwgZcGA1UdHwSBjzCBjDBEoEKgQIY+aHR0cDovL2NkcDEucGNhLmRm
bi5kZS91bmktZHVpc2J1cmctZXNzZW4tY2EvcHViL2NybC9jYWNybC5jcmwwRKBCoECGPmh0
dHA6Ly9jZHAyLnBjYS5kZm4uZGUvdW5pLWR1aXNidXJnLWVzc2VuLWNhL3B1Yi9jcmwvY2Fj
cmwuY3JsMIGwBggrBgEFBQcBAQSBozCBoDBOBggrBgEFBQcwAoZCaHR0cDovL2NkcDEucGNh
LmRmbi5kZS91bmktZHVpc2J1cmctZXNzZW4tY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0ME4G
CCsGAQUFBzAChkJodHRwOi8vY2RwMi5wY2EuZGZuLmRlL3VuaS1kdWlzYnVyZy1lc3Nlbi1j
YS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAAAtpWHGZfdNb8wT
dDuYr5LAtcSOuXWn4l0ZHeIhdy13kIA3m9YN/E4Dz2UTkn0cyihDAX5LOSLzcvfM4qmG5A7i
zT8m22fvj2UKxY3qnzoEGZqmGfk8otj121Sa10Ko69MyspewpqVkOfGpA5VCF92cuY6mHmnH
HWEX75GgqRwSwYJmvgs+jC6w9rFA2ArhMj671PMrrd2EbiH9Nvmr5bEV+alumh5ismB1ujm2
4w1Zz2AdOKGnyaMNF37OyVAzmk1FTjfkVgSumha2w37QCmIJ4Wn0XKuYhJfoObbnaI/VHSO8
JPp8oLJ2z3c5cb3iSWkWjGQaqxSxtcr4dSdVDVIxggSXMIIEkwIBATCB0jCBxjELMAkGA1UE
BhMCREUxJDAiBgNVBAoTG1VuaXZlcnNpdGFldCBEdWlzYnVyZy1Fc3NlbjE1MDMGA1UECxMs
WmVudHJ1bSBmdWVyIEluZm9ybWF0aW9ucy0gdW5kIE1lZGllbmRpZW5zdGUxLDAqBgNVBAMT
I1VuaXZlcnNpdGFldCBEdWlzYnVyZy1Fc3NlbiBDQSAtRzAxMSwwKgYJKoZIhvcNAQkBFh1j
YWFkbWluQHVuaS1kdWlzYnVyZy1lc3Nlbi5kZQIHFAVKqFI8xjAJBgUrDgMCGgUAoIICmTAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDAyMTMyMzQ1Mzha
MCMGCSqGSIb3DQEJBDEWBBSIdpsKuJbAkQR7g+tKhei3IulRYDBsBgkqhkiG9w0BCQ8xXzBd
MAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHjBgkrBgEEAYI3EAQx
gdUwgdIwgcYxCzAJBgNVBAYTAkRFMSQwIgYDVQQKExtVbml2ZXJzaXRhZXQgRHVpc2J1cmct
RXNzZW4xNTAzBgNVBAsTLFplbnRydW0gZnVlciBJbmZvcm1hdGlvbnMtIHVuZCBNZWRpZW5k
aWVuc3RlMSwwKgYDVQQDEyNVbml2ZXJzaXRhZXQgRHVpc2J1cmctRXNzZW4gQ0EgLUcwMTEs
MCoGCSqGSIb3DQEJARYdY2FhZG1pbkB1bmktZHVpc2J1cmctZXNzZW4uZGUCBxQFSqhSPMYw
geUGCyqGSIb3DQEJEAILMYHVoIHSMIHGMQswCQYDVQQGEwJERTEkMCIGA1UEChMbVW5pdmVy
c2l0YWV0IER1aXNidXJnLUVzc2VuMTUwMwYDVQQLEyxaZW50cnVtIGZ1ZXIgSW5mb3JtYXRp
b25zLSB1bmQgTWVkaWVuZGllbnN0ZTEsMCoGA1UEAxMjVW5pdmVyc2l0YWV0IER1aXNidXJn
LUVzc2VuIENBIC1HMDExLDAqBgkqhkiG9w0BCQEWHWNhYWRtaW5AdW5pLWR1aXNidXJnLWVz
c2VuLmRlAgcUBUqoUjzGMA0GCSqGSIb3DQEBAQUABIIBABf8wyL5Z5oZR/X1LFl327MxRsn9
Th2Wzn/FLT9h7/oompcuMrmTgRrWzxsAi1T//zryVHFH9XXaPCqQNkx9ib6MisJxSS+yybOK
Na3ZvfZYrJwkiscvVFzAk8TYz036WIGScAsxKO/w8HOeSLnoH5q3dyBl4AaNGUA6Ql3fxtrU
1YxaawEghBL75R0Q3VB5w9BjRUTaTjwNCCfskUkb9jBEwn+mIdyUnaAy2J48ZnoXJ1VwL8+Q
rizyejUZSNQWKJNqUSbgot1+okV74RlwVTgOAeLOB3UHpWT/wBr5NxxDdZ2+j7ja8IzuJJeT
dO/pnbhk9B+6bGA4tGsdeeR7rq4AAAAAAAA=
--------------ms020203030500020003010400--


From nobody Thu Feb 13 16:02:38 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90D2B1A0015 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 16:02:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNxXY8BcMbXs for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 16:02:31 -0800 (PST)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 656BC1A0006 for <dnsop@ietf.org>; Thu, 13 Feb 2014 16:02:31 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id to1so6981570ieb.14 for <dnsop@ietf.org>; Thu, 13 Feb 2014 16:02:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=G06dQ0dwAhekSYC25fdceV28cXoWT2cM0o5FEzMNtr0=; b=GKtQv5dPZrtoB7tjU+vJve8YLgPs6+pUrCZWKZhGuaKVBHDE8dGMIfdWy3b5Da4xzP 2XKiI50dYS6SWReOE8qIewnGg8NiLC9lwfQNnoLbJorz8yuW+fYX8WwwY9q9TexnPFsW t4Vsy6zmqHszMzVWFP5x4kEEHWrvM33mG1aA0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=G06dQ0dwAhekSYC25fdceV28cXoWT2cM0o5FEzMNtr0=; b=CNmn3aBBd0MPOBJHSNOb/O9laDoNxhGsnZgTILBMooSU61CW22LsyOGxIujtVDPdBS gnLx01IvcUVUdc2xfvlkO6L6A7+6gNy3OC1ZzTWFkIEKf2wSrA4JpVAB6Qyw7u4G50K/ 8q6kaYzLvD9TCN0sAfLT5mNjDi2VprudC1KN6YYcLNzQXZIb+WoDZkuszwoVZi9fFPIe UZY87XZOCLxdlpIMWj/yaklidcePrp+L4rteb6rt2QT9CbHN4RUmwzDeGO/U8AEjnSks 9tbMZqXstAVGC0vSnurrCP0XVnP01P1nthXX8dDJDe/cjGDwK/xgqyx4qJIg/m1W1OWj 5xXg==
X-Gm-Message-State: ALoCoQlTKRyxuGNAulAtCdIt/z6k33e4RNmCv9inUx8YyVdGA0Sb5a1Ug0lXKCW0jZSCscyebxww
X-Received: by 10.50.3.9 with SMTP id 9mr6511584igy.16.1392336149788; Thu, 13 Feb 2014 16:02:29 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:1908:f66a:35d:e606? ([2001:4900:1042:1:1908:f66a:35d:e606]) by mx.google.com with ESMTPSA id f9sm10250423igz.3.2014.02.13.16.02.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Feb 2014 16:02:28 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_BCA4F9FF-550A-48AF-99E7-3CF5AFDEF0E6"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.LSU.2.00.1402132050440.18502@hermes-1.csi.cam.ac.uk>
Date: Thu, 13 Feb 2014 19:02:26 -0500
Message-Id: <79F80225-91C0-4185-9FB7-172E643DCE90@hopcount.ca>
References: <alpine.LSU.2.00.1402132050440.18502@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/agjyDVvJ5xqa-1DaMDNHQIjDsVs
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] draft-fanf-dnsop-trust-anchor-witnesses-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 00:02:35 -0000

--Apple-Mail=_BCA4F9FF-550A-48AF-99E7-3CF5AFDEF0E6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Tony,

On 2014-02-13, at 15:56, Tony Finch <dot@dotat.at> wrote:

> There was some discussion last month about dispersing trust in the =
root.
> http://www.ietf.org/mail-archive/web/dnsop/current/msg10977.html
>=20
> This inspired me to write up a concrete proposal for the
> quorum-of-witnesses idea that I have vaguely suggested several
> times over the last few years.
>=20
> All thoughts / suggestions / criticisms welcomed.

I agree with your thoughts in the draft that (to paraphrase) there has =
been remarkably little interest in working on (or implementing) the =
suggestions in draft-jabley-dnssec-trust-anchor.

The ability to bootstrap the trust anchor for the root zone without =
operator intervention (e.g. on embedded devices, or any computer system =
or application with a non-technical user) is weak as currently deployed. =
An approach which is robust and for which there is enthusiasm to =
implement is sorely needed.

Some additional thoughts on the actual text, below. This started off =
being brief, but then I got on a roll. Sorry about that.

One comment, in case it's not obvious: I once worked for ICANN, and I =
once had some responsibility for parts of the root zone DNSSEC system. I =
no longer work for ICANN, however, and anything you read below that =
looks like a fact should be treated with distrust and suspicion.

> Abstract
>=20
>    At the moment the root DNSSEC key is a single point of trust and a
>    single point of failure for the whole system.  This memo describes =
a
>    mechanism for dispersing trust in the root key.  Witnesses vouch =
for
>    the root trust anchor by publishing WS records in the DNS.
>    Validators only update their root trust anchors if multiple =
witnesses
>    agree.  The root-witnesses.arpa zone enables a validator to =
bootstrap
>    trust when it has no working trust anchors other than its =
witnesses.

You're using "root key" and "root trust anchor" a bit loosely here; my =
presumption is that you're talking about the root zone KSKs, and a trust =
anchor set which corresponds to a set of active (non-revoked, published) =
KSKs in the root zone.

> 1.  Introduction
>=20
>    At the moment the root DNSSEC key is a single point of trust and a
>    single point of failure for the whole system.  It has a number of
>    problems:
>=20
>    o  Root trust anchor rollovers using [RFC5011] require validators =
to
>       be online while the rollover happens.  With the current root key
>       management plan, rollovers take a few weeks.  This is
>       uncomfortably long for emergency rollovers.

I don't believe the various systems that manage DNSSEC in the root zone =
have a way to execute an emergency KSK roll whilst still following RFC =
5011 semantics. There's a single active key, for example, and no standby =
key. What was specified in the root zone was the use of 5011 timers for =
scheduled rollovers; a definitive compromise of the active KSK would =
trigger other action. It would be nice if this was more definitively =
specified (and better mechanisms to bootstrap trust would help with =
that).

>    o  Systems that are offline during a rollover have to use an =
out-of-
>       band mechanism to update their trust anchors, relying on non-DNS
>       sources of trust.  There is no clear specification or security
>       analysis for this process.

Well, there were a couple of attempts:

  draft-jabley-dnssec-trust-anchor-08
  draft-jabley-dnsop-validator-bootstrap-00 (expired)

>    o  The root key is a single point of failure with no standby, =
though
>       its storage and management is extremely resilient and =
trustworthy
>       (in stark contrast to the out-of-band trust anchor update keys).

I presume by that you mean the X.509 certs published on =
data.iana.org/root-anchors. The goal there was to facilitate =
endorsements by multiple independent actors, each following a documented =
and audited process to verify that what they were signing was accurate. =
The use of X.509 certificates anticipated vendors of operating systems =
and embedded devices already having certificate machinery for =
code-signing, and hence this seemed like an approach that had a low =
implementation cost.

Turns out the actual approach (do nothing) had an even lower =
implementation cost.

>    o  The concentration of trust in the root is politically
>       uncomfortable.

This may be true, depending on exactly what you mean, but I doubt it's =
universally true (perhaps not even widely true). I'm not sure I =
understand the motivation for including that statement has in a =
technical specification, especially when you consider that the intended =
trust mechanisms were designed to be dispersed amongst multiple (e.g. =
vendor) authorities.

>    This memo describes a mechanism for dispersing trust in the root =
key.

"another mechanism" :-)

>    Witnesses vouch for the root trust anchor by publishing WS records =
in
>    the DNS.  Validators only update their root trust anchors if =
multiple
>    witnesses agree.
>=20
>    There are some potential advantages:
>=20
>    o  It can allow for a crash rollover of the root key, in the event
>       that it is lost or compromised, with validators recovering
>       automatically rather than having to be manually forced to fetch
>       and authenticate the replacement trust anchor.

crash -> emergency, presumably.

The existing mechanisms (again, lamentably light on implementation) =
would also facilitate this. The mechanisms in the validator-bootstrap =
draft I referred to earlier allow trust anchor retrieval with no ability =
to validate, authenticating the retrieved data using appropriate local =
methods (e.g. the key that signed the code is used to test the signature =
of the data the code retrieved).

>    o  It could allow a smaller root DNSKEY RRset by allowing the
>       witnesses to vouch for the root ZSK directly instead of via a =
KSK.
>       This saves the cost of high-assurance storage for the root KSK,
>       but requires more frequent communication between the root DNSSEC
>       key managers and the witnesses.

As I'm sure you appreciate, this advantage would only be realised if =
there was a change in the way that the work is divided up amongst the =
root zone partners. At present, there is a deliberate separation between =
KSK management and ZSK management. The intersection between the two is =
entirely conducted at key ceremonies which are widely scrutinised.

I suspect a transition to a single key solution would be a difficult =
transition from an administrative perspective, bordering on the =
non-actionable. Listing impossible things as advantages seems like a bit =
of a stretch. :-)

>    There are some limitations and disadvantages:
>=20
>    o  It does not disperse trust in the root zone signing key or root
>       zone maintenance.

"root zone signing key" is a bit vague. I presume you mean the ZSK.

"root zone maintenance" is a bit vague. I presume you mean the process =
of applying changes to the root zone and signing it by the root zone =
maintainer, and not the various other pieces of the system?

>    o  A lot more co-ordination between organizations is necessary, for
>       the witnesses to get out-of-band authentication of new trust
>       anchors.

This should not be underestimated (or at least should be characterised). =
Presumably if we expect people (and devices) to trust a collection of =
witnesses to the authenticity of a particular copy of the KSK, we don't =
want that process to dilute the security of the process used to =
generate, store and exercise the KSK. Are we talking about additional =
ceremonies, potentially tens or hundreds of them, with each witness? Or =
are we talking about something that might fit with minimal change into =
the existing ceremonies?

I realise you're not trying to boil the ocean with this -00; this is not =
criticism, just ideas for future typing :-)

>    This mechanism can be used to automatically update any trust =
anchor,
>    though it is designed for and includes some special considerations
>    for the root trust anchor.  The root-witnesses.arpa zone is set up =
to
>    enable a validator to bootstrap trust when it has no working trust
>    anchors other than its witnesses.

I'm not sure I understand the benefit of making this a general =
mechanism. The only real application it has, in these heady days of DS =
RRSet proliferation, is in the root zone; it's hard to imagine it being =
easier to set up a plausible array of witnesses for an island with an =
otherwise insecure delegation than it is to sign the parent (or just =
choose a different parent).

> 3.  How validators use WS records
>=20
> 3.1.  Trust anchor configuration
>=20
>    A validator's configuration for a trust anchor consists of the the
>    trust anchor owner name, and either a set of public keys or a set =
of
>    DS records, as described in [RFC4035] section 4.4.
>=20
>    A trust anchor that is automatically updated is associated with the
>    witnesses that vouch for it.  It has a quorum value stating how =
many
>    witnesses must agree before the trust anchor is updated.

Where is that quorum parameter published? By the KSK maintainer, or by =
individual witnesses, or is it up to the validator operator to follow =
local policy?

Bad choices in this parameter seem likely to cause pain (too high and =
you need to worry about the currency of a lot of witness zones; too low =
and you are at risk of shenanigans by a small number of conspiring =
witnesses).

>    Each witness is a normal statically-configured trust anchor.  That
>    is, witnesses are not updated automatically except by out-of-band
>    configuration updates or software updates.  Each witness is
>    associated with one automatically updated trust anchor for which it
>    vouches.

I worry slightly that you've just shifted the problem that ICANN =
anticipated with vendors shipping a single trust anchor and made it =
larger, a problem of shipping many trust anchors from different places. =
This is the core problem we're trying to address, I think; if it's also =
a problem that needs to be solved for this proposal, we may have just =
found our own footprints on the beach.

> 3.2.  When to try a trust anchor update
>=20
>    The validator SHALL keep track of the DNSKEY records from the DNS =
at
>    the trust anchor name. It only tracks the set of all records with
>    the SEP flag set, or the subset of SEP keys with algorithms =
supported
>    by the validator.  (This is so that ZSK rollovers do not trigger
>    trust anchor updates.)

So, the validator receives responses to the query ./IN/DNSKEY from =
somewhere (not necessarily directly from the authority servers) and =
discards any RRs in the set with SEP=3D0.

>    When the validator notices that this set has changed it SHOULD
>    attempt to update the trust anchor as described below.  During the
>    update process it SHOULD continue to serve clients and use the
>    existing trust anchor to validate responses.
>=20
>    The validator MAY track the DNSKEY records persistently in order to
>    make restarts faster.  If so, it SHOULD discard any saved DNSKEY
>    records after their RRSIG expiry time.  If it does not, it SHOULD
>    perform an update attempt at restart.

persistently -> regularly?

>    When starting, a validator can find that its existing trust anchor
>    does not work, perhaps because a key rollover happened while it was
>    offline.  In this situation it cannot serve clients until the =
update
>    process completes successfully.

What about queries received from clients with CD=3D1?

>    A broken trust anchor is not expected to happen during normal
>    operations, since validation ought to work at every point in a key
>    rollover.  However, if some disaster occurs and the trust anchor
>    private key is lost or compromised, there might be a disruptive =
crash
>    key rollover.
>=20
>    When it sees a crash rollover, a validator will not be able to
>    validate the new DNSKEY RRset, so will discard it and retry the =
query
>    in an attempt to obtain a working version.  If this problem =
persists
>    the validator MAY attempt to update the trust anchor using an =
invalid
>    DNSKEY response.
>=20
> 3.3.  Trust anchor update process
>=20
>    Trust anchor updates are performed with respect to a DNSKEY RRset
>    from the trust anchor owner name.  This allows the validator to
>    ensure that a successful update will lead to a working =
configuration.

I presume you're talking about the trust anchor for the root zone here, =
and not a trust anchor for any witness zone. "trust anchor owner name" =
is a bit of a weird phrase, but that's probably just me.

>    The validator queries for the WS RRset at each of the trust =
anchor's
>    witnesses.  The witnesses SHOULD be queried in a random order, so
>    that the validator avoids relying too much on a subset of the
>    witnesses.  The query process SHOULD stop when a quorum has been
>    achieved for one or more WS RRs.  The queries MAY be performed
>    concurrently to improve performance (though it doesn't make sense =
to
>    use a level of concurrency greater than the quorum size).

How does the validator obtain a list of witness zones? That's manually =
configured? How are additions, removals and changes to the list of =
witness zones managed?

>    The witness queries follow normal DNS resolution and DNSSEC
>    validation rules.  The response from a witness MUST validate as
>    secure using that witness's trust anchor.  (The special =
arrangements
>    for the root trust anchor witnesses described in Section 5.1 ensure
>    that the requirements in this paragraph can be satisfied even when
>    the root trust anchor is broken.)
>=20
>    The validator MUST ensure there are no duplicate WS RRs in the
>    response from a witness.  Duplicate RRs are not allowed (see
>    [RFC2181] section 5), but it is particularly important to prevent
>    duplicate WS RRs so that a witness cannot count more than once
>    towards a quorum.
>=20
>    The validator SHOULD ignore a WS RR if it does not contain a valid
>    digest of a DNSKEY record with the SEP flag set.  This ensures that
>    the validator does not count a quorum of useless WS RRs.
>=20
>    For each usable WS RR that the validator receives from a witness, =
it
>    keeps a count of the number of responses that contained that WS RR.
>=20
>    A WS RR can be trusted when this count reaches the required quorum.

You mean a particular DNSKEY RR, retrieved without authentication from =
some arbitrary source, can be trusted when sufficient validated WS =
responses that match the DNSKEY RR under scrutiny have been retrieved?

Surely any WS RRSet can be trusted as well as the locally-configured =
trust anchor for the zone that contains it, once you validate the WS =
RRSet's signature.

>    If the trust anchor that is being updated is configured with DS =
RRs,
>    then the validator converts the trusted WS RRs into DS RRs by
>    changing their RR TYPE fields and uses those for the new
>    configuration.  If the trust anchor is configured with public keys,
>    then the new keys are taken from the DNSKEY RRs that are
>    authenticated by the trusted WS RRs.
>=20
>=20
> 4.  How witnesses publish WS records
>=20
>    The administrative arrangements for publishing WS records in a
>    witness zone are analogous to publishing DS records in a parent =
zone.
>=20
>    There MUST be an out-of-band (non-DNS) communications channel =
between
>    the witnesses and the owner of the zone for which they vouch.  This
>    is used to authenticate WS RRset changes.

If this process is to be trusted as secure, sufficient to allow =
unattended operation, etc then presumably these processes need to be =
carefully specified and audited.

> 4.2.  Lifecycle of witness zones
>=20
>    A trust anchor SHOULD have many witness zones, in order to provide
>    resilience as well as dispersal of trust.
>=20
>    Each witness zone is tied to a fixed witness trust anchor.  The =
zone
>    lasts as long as its trust anchor.  This SHOULD be at least 10 =
years,
>    since old software and configurations cannot function after too =
many
>    of their witnesses have been retired.

"10 years" seems like a bit of a hard-coded parameter. The root zone KSK =
was expected to be rolled every 5 years. There is enthusiasm in some =
circles for rolling the root zone KSK much more frequently than that. If =
there are reasons to roll the root zone KSK that often, then presumably =
the same reasons dictate that witness zones' KSKs should roll similarly?

>    Witnesses are continually retired.  It is expected that some
>    witnesses will have to retire early, for instance, if their keys =
are
>    lost or compromised, or if their host organization is no longer =
able
>    to maintain them.  This is OK since there are plenty of other
>    witnesses.
>=20
>    New witnesses are continually introduced.  Validators configured =
with
>    an up-to-date set of witnesses will have a decent lifetime.  Given =
an
>    average witness lifetime of W years, a pool of P witnesses, and a
>    quorum size of Q, we expect P/W witness retirements per year.  A
>    validator configuration will last until there are Q witnesses left,
>    that is, until there have been P-Q retirements, which takes V=3D(P-
>    Q)*(W/P) years.  For example, if P=3D30, W=3D10, and Q=3D6, then =
V=3D8.
>=20
>    A witness organization may run multiple witness zones on a rolling
>    replacement schedule in order to avoid a hiatus when a zone is
>    retired.  Validators SHOULD be configured to use only one witness
>    zone from each witness organization, to avoid trusting one
>    organization too much.

It's not obvious from your description how anybody should (a) obtain a =
list of witness zones, or (b) should retrieve authenticated, local trust =
anchors for sufficient witness zones such that a quorum can reliably be =
achieved. These seem like important gaps to fill.

> 5.  The root trust anchor
>=20
> 5.1.  Locating root trust anchor witness zones
>=20
>    There is a bootstrapping problem when a validator has an =
out-of-date
>    root trust anchor: it needs to find the name servers for the =
witness
>    zones in order to be able to get the WS records that vouch for the
>    new root trust anchor; however it is unable to validate the =
responses
>    it gets while resolving the name server addresses.  This section
>    describes how to minimize this bootstrapping problem.
>=20
>    All root witness zones SHALL be delegated from a single parent =
zone,
>    called root-witnesses.arpa.  This zone is to be maintained by IANA.
>    A delegation in this zone indicates that there are out-of-band
>    arrangements between the root DNSSEC key managers (XXX do they have =
a
>    better name?) and the witness organization allowing the witness
>    organization to meaningfully vouch for changes to the root DNSSEC
>    trust anchor.

The Root Zone Manager role is currently carried out by Verisign. They =
manage the ZSKs, they edit the zone to apply authorised changes, they =
sign the root zone, and they distribute it to root servers.

The IANA Functions Operator role is currently carried out by ICANN. They =
manage the KSKs, publish trust anchors, and exercise the KSK during =
ceremonies to sign enough DNSKEY RRSets provided by the Root Zone =
Maintainer for the root zone to be re-signed and published for the next =
N months.

Changes to the root zone are authorised by US DoC NTIA.

Collectively, the Root Zone Manager, the IANA Functions Operator and =
NTIA are referred to as the Root Zone Partners.

(I think. I no longer have to worry about these details on a daily =
basis. The IANA Functions Contract and the Cooperative Agreement are =
public, I think; you'll probably find them on ntia.doc.gov if you're =
interested. All those phrases are surely in those documents, somewhere.)

>    The root-witnesses.arpa zone SHOULD NOT be signed.  Leaving the =
zone
>    unsigned prevents the risk that validators will use some =
higher-level
>    trust anchor to validate responses from a witness zone rather than
>    the witness trust anchor itself.  In particular we want to avoid a
>    compromised root key being used to vouch for itself.  The purpose =
of
>    the root-witnesses.arpa zone is to contain delegation NS RRs and =
glue
>    address records for the witness zones, and these records are never
>    signed.  The signed parts of delegations are the DS RRsets; =
omitting
>    those prevents unsafe witness validation, but also leaves almost
>    nothing in the root-witnesses.arpa zone to sign.
>=20
>    Each witness zone's name servers have names inside that witness =
zone
>    so that they can be validated by the witness trust anchor without
>    depending on any other part of the DNS.

I'm not sure I understand the purpose of this. Are you suggesting that =
if I send a query to address X but find out in the response from the =
server at that address that I should really have been talking to address =
Y, I should apply the mind bleach and start again?

Surely it's the WS RRSets we want to validate. How we get them is =
largely irrelevant. They either validate against a locally-configured =
trust anchor or they don't. If someone pilosov/kapela's a route for a =
real witness server and sneakily sends me a perfectly good response =
which validates, then giddy up, I'm using it.

>    The root-witnesses.arpa zone SHALL be served by the root name
>    servers.  This is so that a bootstrapping validating resolver can
>    find its witnesses using just its root hints, and get a direct
>    referral to the right witness zone name servers, again without
>    depending on any other part of the DNS.

There's some enthusiasm for paring back the root servers even further =
than they are, and having them serve just the root and ROOT-SERVERS.NET =
zones (the latter so that priming responses can be fattened with lovely =
tasty glue).

To clarify your intent, are you suggesting the root servers should serve =
ROOT-WITNESSES.ARPA simply because there's a lot of them, i.e. the =
requirement is that those zones be served competently? If not, where =
does the requirement come from?

> Appendix A.  Questions
>=20
>    Should this this scheme be extended to be more like DLV?

I think the answer to that is no, regardless of what scheme you're =
talking about. :-)


Joe


--Apple-Mail=_BCA4F9FF-550A-48AF-99E7-3CF5AFDEF0E6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlL9XRIACgkQNI8MvYZSOizvxwCeIb5YNuQNzT8nt4L9Wx3r3gC7
OuUAoIHnE+Rh+pw6vLMRXykHq27LJw9N
=cvF2
-----END PGP SIGNATURE-----

--Apple-Mail=_BCA4F9FF-550A-48AF-99E7-3CF5AFDEF0E6--


From nobody Thu Feb 13 17:22:13 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B5F51A0045 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 17:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level: 
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uF6bvvio0ugW for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 17:22:07 -0800 (PST)
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by ietfa.amsl.com (Postfix) with ESMTP id 961E81A006A for <dnsop@ietf.org>; Thu, 13 Feb 2014 17:22:07 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id e4so9440679wiv.10 for <dnsop@ietf.org>; Thu, 13 Feb 2014 17:22:05 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1pVRkwJOt3hsbYLZ4KaaSf8ZFguqrXLpcG99diei1dg=; b=nGC+q38BG6alA2ivODc5oeAYk08wn2BzKhcH3CmB94424h4xrTs+CRiiC6UHTmLlgd pQCUnTPevdj2XkPfCJ2pPt+JDjjl4hzbzUxpCRqHlufrmjFlrpKdeDErG/nDxlrgM66N jO9HkG1BO0mMMMeD6wCv76EtouDmWu4+7Vv4yDx1Ngzz7+13/Lvcx0T49wJ/oY8Vvbo1 6PbEo39Qmg9c1Vy9DSV4Ae22DMZ4TbM3cgSYcAaBnk2ia9vCZ6N5myhPyy6DQ1Z/geyf hpirN4tA/I7DNxTTxB9RRSRQr8QRjSR3rQyC5KMYTyw5XfBcyggjfrwMpkpN1RTTGVv7 eq6w==
X-Gm-Message-State: ALoCoQmsxLqCN046K5oPlDV1iPmr2hEa/7wHyEBmQITLJCjTNP/cI9DqTozVl60G1J4eEFmEsTGK
MIME-Version: 1.0
X-Received: by 10.194.108.41 with SMTP id hh9mr42213wjb.89.1392340925627; Thu, 13 Feb 2014 17:22:05 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Thu, 13 Feb 2014 17:22:05 -0800 (PST)
X-Originating-IP: [50.201.180.2]
In-Reply-To: <52FD57D7.30004@frobbit.se>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info> <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca> <52FCE993.3070005@frobbit.se> <D38F596A-9DC3-49A1-A4D7-FF86F3AC1FBD@ogud.com> <52FD57D7.30004@frobbit.se>
Date: Thu, 13 Feb 2014 20:22:05 -0500
Message-ID: <CAHw9_iKEuOf+AZpDfB0EUsU9uVvGcAXJVs6DDTD1XsjkOp+_MQ@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/PBVzv3A-ILTg6_ITLseOmBQW9Ko
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 01:22:10 -0000

[ Replying to a bunch of comments in one mail (not just Patrik's). I'm
stuck in the storm in ATL (
http://www.cnn.com/2014/02/13/us/winter-weather/ ), and so am behind
on mail, etc. ]

Just so folk know, Olafur and I chatted about this before he submitted
his draft. I think that we are in agreement that the two drafts are
complementary, not conflicting.
Using a URI / Prefix / <something> to indicate another namespace (to
me at least) seems like an elegant, clean, sane, "better" solution --
unfortunately it seems that making pseudo-TLDs has suddenly become
popular, and so I think that reserving .ALT is an important *tactical*
solution. It creates a safe area for people who want to do this sort
of thing to do so, and lets the IETF push back on people trying to
reserve .foo in the future. I think we should work on Olafur's
proposal in parallel.

On Stephane's terminology comments...
Yes, the terminology section sucks -- unfortunately it was the best I
could come up with.
I'm really bad at terminology thingie whatzits. Andrew made it better,
but it is still bad. Much of the problem is that we are talking about
somewhat squishy things -- people using names in places where you
would usually put a "DNS name" (whatever that means).
1:  'the DNS "standard" of a series of labels separated with dots' --
An earlier version of the doc had some long and contrived text about
"names that are comprised of short strings (<=3D63) of LDH characters,
separated by dots" until Andrew hit me with a stick and reminded me
about 1: IDNs and 2: DNS being 8bit clean. I'd put the word "standard"
in quotes to try and make it clear that this isn't really the DNS
standard.
2: 'DNS context: The namespace administered by ICANN.'  -- Yup, it's
not clear / correct. But I couldn't figure out how to make it better.
It's not really the 'DNS protocol', because some of these solutions
use the DNS protocol, and then intercept it. What I was aiming for was
something like "The thingie that most people would think of if you
asked them to go resolve a name".
Suggestions / text more than welcome!


On the "should e.g .onion move under this?" discussion...
Personally I think that the Right Thing(tm) would be for .onion / .bit
/ etc to move under .alt -- unfortunately they are already deployed in
the wild, and there is running code, etc. If I had a wand I'd wave it,
magic would happen, everyone would have a pony and .onion would
suddenly be under .alt. Unfortunately I think that the reality is
that, whether or not the IETF approves the grothoff names, they will
continue to be used. I'd rather that that is documented. The .ALT
proposal is largely a solution so that we don't end up in the same
place in the future.  Olafur's namespace prefix solution is *better*,
but is (IMO) much more of a long term solution.


On the "Should there be an IANA registry?" bit.
I have no idea. I'm very conflicted on this. There are definite
advantages and disadvantages to both.
I want it to be easy for someone to start using a name here, so that
they have no excuse not to, but I'm also concerned about the chaos /
anarchy. An option (but an ugly one!) would be that we reserve
something like unmanaged.alt (or u.alt or swamp.alt, or...) as
unmanaged space within the ALT TLD. Other SLD would require expert
review or something.

Well, I'm off to go see if I can find any food -- when I went for
lunch earlier in the day the restaurant had already run out of
french-fries, tomatoes and a number of beers...
Wish me luck.
W


On Thu, Feb 13, 2014 at 6:40 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrot=
e:
> On 2014-02-13 11:19, Olafur Gudmundsson wrote:
>>
>> On Feb 13, 2014, at 10:49 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrot=
e:
>>
>>> On 2014-02-13 10:23, Marc Blanchet wrote:
>>>> - why not just register a URN namespace and use it as they see fit?
>>>
>>> Because you only type in a string that "looks like a domain name" in
>>> applications (for example browsers) without the URI scheme nowadays, an=
d
>>> people want that to work also with strings in other namespaces.
>>>
>>> I.e. it all, from my perspective, have to do with where the signalling
>>> is on what namespace to use. And if that signalling is inline, then we
>>> do have something that can be viewed as the equivalent of a namespace
>>> collision.
>>>
>>> If people had entered the URI scheme all the time, including "http",
>>> then we would have been in a different situation.
>>
>>
>> I think that the draft is not radical enough it is trying to provide som=
e belt and suspenders to a
>> syntom rather than address the actual problem.
>>
>> The Meta problem is Multiple Namespaces with different resolution techno=
logies.
>> Addressing this via a SUFFIX in the domain name feels wrong,
>> What I will propose is a Namespace layer solution that is a prefix to th=
e name presented,
>> thus names will be presented to the namespace layer as <namespace/name-e=
ncoding><space separator><name>
>> Examples using ## as the separator
>>       DNS##www.example.com    This is normal DNS name,
>>       GNU##eff
>>       DUTF8##..... (DNS name in UTF8 format)
>>       www.example.net    (by default the name is DNS)
>>
>> With a namespace layer we can have the host reject lookup locally if it =
does not know how to handle the namespace,
>> rather than dump it out as ".alt" query.
>>
>> I know this requires changes in lookup services and code, but it moves t=
he effort to the people that want new namespaces.
>>
>>       Olafur
>> PS: IANA should maintain a registry of namespaces
>
> This is to me approximately like the URI scheme idea, but a different
> syntax. Can fly, might not fly.
>
> The whole question is what the application developers and marketing
> people will print on bulletin boards and accept in input fields in
> applications (and their configurations).
>
> Which unfortunately means we do not know until some time after we have
> tried to standardize it... :-P
>
>    Patrik
>
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Thu Feb 13 17:33:32 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CDB91A0016 for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 17:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qlHxNXI5VUaf for <dnsop@ietfa.amsl.com>; Thu, 13 Feb 2014 17:33:29 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 716171A0058 for <dnsop@ietf.org>; Thu, 13 Feb 2014 17:33:29 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id cc10so9459492wib.5 for <dnsop@ietf.org>; Thu, 13 Feb 2014 17:33:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1Sk1A0mvdEPrwJitcZZTTiwemNxBialBhSnyZ1uUMO4=; b=LBnqa/sl2M+dtw4YREDwcwcxQsEehwG3jia/bTI2vencAruen1Y3HrxUHR1bHQrCS9 0QMiKErwoI1mDSiKFyImawI/++NbZOgWnMMIyRLHsmFdCFTOrDswMHnc7jnsggTDapnG Sfe+lgQDHS060rNkI8XPd3ElAXnqIyuO1KlBIkEjN7eOQsZI/wW4Ylmn0uSXzmzAj1yj wfv+5s79cz54ddgW8nX7T3LLBIIAwT+eUybIGbwEq//0GbWp8p3+O5WfHUC2hhy5HfUf 1AJmYM/ZlrjgCqZ/KPGR3Eb8/9M8q7NFpntqyJTZNrSooDn5p1BbeTFfaXAqtW+sRNlw f30w==
X-Gm-Message-State: ALoCoQkYwoOXZX4ZI9usws+pCgGqTNkkylEThG8JtZDQiPdKodeezIVR5w8C0t8CypL/9GQMJNhj
MIME-Version: 1.0
X-Received: by 10.180.77.74 with SMTP id q10mr32972wiw.39.1392341607610; Thu, 13 Feb 2014 17:33:27 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Thu, 13 Feb 2014 17:33:27 -0800 (PST)
X-Originating-IP: [50.201.180.2]
In-Reply-To: <982167BD-10FC-4D06-9E85-47F371BBCA90@nominum.com>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <982167BD-10FC-4D06-9E85-47F371BBCA90@nominum.com>
Date: Thu, 13 Feb 2014 20:33:27 -0500
Message-ID: <CAHw9_iJ8YOTJ+3ZVV7J9RpA+OPHwjjpyUS45CJeSZSoEvyr-mQ@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/BEiEtyjnhvtMqoMz2pVaV4v-ew0
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, draft-wkumari-dnsop-alt-tld@tools.ietf.org
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 01:33:31 -0000

On Wed, Feb 12, 2014 at 1:40 PM, Ted Lemon <ted.lemon@nominum.com> wrote:
> On Feb 12, 2014, at 1:24 PM, Joe Abley <jabley@hopcount.ca> wrote:
>> I suspect that there would be fewer roadblocks involved in choosing an a=
nchor ALT.ARPA than ALT, since ARPA is under the control of an IETF family =
member while the root is controlled by distant cousins. If I'm right that t=
his proposal is for future, as-yet-unknown applications, then the choice of=
 anchor should be arbitrary; it feels in that case like the path of least r=
esistance is the right one.
>
> It really shouldn't be difficult to make this work, although if .ALT is a=
lready spoken for a different name might be needed.

Nope, checked, no-one has applied for .ALT....

> If it is in fact difficult, then RFC 6761 is pretty pointless.
>
> I agree with your other point, though--this may be useful for future effo=
rts, but doesn't address the same problem as the other two documents we've =
talked about.

Yup. This is to primarily to prevent this sort of issue in the future...

W

>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Fri Feb 14 00:19:51 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F341A0114 for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 00:19:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYnPjJyZ9erp for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 00:19:46 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 915BE1A0121 for <dnsop@ietf.org>; Fri, 14 Feb 2014 00:19:46 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id A83542802C7; Fri, 14 Feb 2014 09:19:44 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id A3B13280129; Fri, 14 Feb 2014 09:19:44 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 97DEBB38038; Fri, 14 Feb 2014 09:19:14 +0100 (CET)
Date: Fri, 14 Feb 2014 09:19:14 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Message-ID: <20140214081914.GA3151@nic.fr>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info> <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca> <20140213155838.GH25409@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140213155838.GH25409@mx1.yitter.info>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/9ZD2M5YuQDObKBKV_9gpoQdtGGo
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 08:19:49 -0000

On Thu, Feb 13, 2014 at 10:58:38AM -0500,
 Andrew Sullivan <ajs@anvilwalrusden.com> wrote 
 a message of 18 lines which said:

> > - why not just register a URN namespace and use it as they see fit?
> 
> Why didn't they do that in the first place?

Some did. For instance, the magnet people. (Although they apparently
did not register the URI scheme they are using...)


From nobody Fri Feb 14 00:30:34 2014
Return-Path: <dengguangqing@cnnic.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 083101A0174 for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 00:30:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.922
X-Spam-Level: 
X-Spam-Status: No, score=0.922 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FSL_NEW_HELO_USER=0.668, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kLm7UcyiYjrY for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 00:30:30 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 2FFD41A0158 for <dnsop@ietf.org>; Fri, 14 Feb 2014 00:30:29 -0800 (PST)
X-EYOUMAIL-SMTPAUTH: dengguangqing@cnnic.cn
Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 14 Feb 2014 16:30:25 +0800
Date: Fri, 14 Feb 2014 16:30:30 +0800
From: "Guangqing Deng" <dengguangqing@cnnic.cn>
To: "Tim Wicinski" <tjw.ietf@gmail.com>
References: <52F9A377.1080008@gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 0, 108[cn]
Mime-Version: 1.0
Message-ID: <2014021416302937189415@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart011070616858_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/H3_b6Q-fB6p79QKu7_46GBbktFM
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Call for agenda items for London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 08:30:33 -0000

This is a multi-part message in MIME format.

------=_001_NextPart011070616858_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

CgoKCgoKIArCoEhpLCBUaW0sIEkgd291bGQgbGlrZSB0byByZXF1ZXN0IGEgdGltZSBzbG90IG9m
IDE1IG1pbnV0ZXMgdG8gZGlzY3VzcyB0aGUgdG9waWMgb24gb3B0aW1pemluZyBETlMgYXV0aG9y
aXR5IHNlcnZlciBwbGFjZW1lbnQuIEFzIHdlIGtub3csIHRoZSBnZW9ncmFwaGljYWwgZGlzdHJp
YnV0aW9uIG9mIEROUyBhdXRob3JpdHkgc2VydmVycyAoaW5jbHVkZSByb290LCBUTEQgYW5kIG90
aGVyIGF1dGhvcml0eSBzZXJ2ZXJzIGluIHRoZSBETlMgaGllcmFyY2h5KSBoaWdobHkgYWZmZWN0
cyB0aGUgZmluYW5jaWFsIGNvc3RzIChzdWNoIGFzIHNlcnZlciwgZW5lcmd5IGFuZCBiYW5kd2lk
dGggY29zdHMpIGZyb20gdGhlIEROUyBvcGVyYXRvcidzIHBvaW50IG9mIHZpZXcgYW5kIGFsc28g
dGhlIEROUyByZXNvbHV0aW9uIGxhdGVuY3kgZnJvbSB0aGUgRE5TIGNsaWVudCdzIHBvaW50IG9m
IHZpZXcuIExldCB1cyBjb25zaWRlciB0aGUgZm9sbG93aW5nIHF1ZXN0aW9uOiB3aGVuIGh1bmRy
ZWRzIGV2ZW4gdGhvdXNhbmRzIG9mIHBvdGVudGlhbCBkZXBsb3ltZW50IGxvY2F0aW9ucyBhcmUg
Z2l2ZW4sIHdoaWNoIGxvY2F0aW9ucyAobWF5IGJlIHNldmVyYWwgb3IgdGVucyBvZikgc2hvdWxk
IGJlIHNlbGVjdGVkIHRvIGRlcGxveSBETlMgYXV0aG9yaXR5IHNlcnZlcnMgb2YgYSBzcGVjaWZp
YyBETlMgem9uZSAoZm9yIGluc3RhbmNlLCAuQ04pIHNvIHRoYXQgdGhlIEROUyByZXNvbHV0aW9u
IGRlbGF5IGlzIG1pbmltaXplZCB3aGlsZSB0aGUgZmluYW5jaWFsIGNvc3RzIGRvIG5vdCBleGNl
ZWQgdGhlaXIgYnVkZ2V0PyBJdCBpcyBub3QgZWFzeSB0byBhbnN3ZXIgdGhpcyBxdWVzdGlvbiB0
aG91Z2ggZnVuZGFtZW50YWxseSB3ZSB0aGluayB0aGF0IHRob3NlIGxvY2F0aW9ucyB3aXRoIGxv
dyBmaW5hbmNpYWwgbGV2ZWwgYW5kIGNsb3NlIHByb3hpbWl0eSB0byBETlMgY2xpZW50cyBzaG91
bGQgYmUgc2VsZWN0ZWQuIFRvIHRoZSBiZXN0IG9mIG91ciBrbm93bGVkZ2UsIHRoZXJlIGlzIHN0
aWxsIG5vIHJpZ29yb3VzIGF1dGhvcml0eSBzZXJ2ZXIgcGxhY2VtZW50IGFwcHJvYWNoIHlldCBh
bmQgdGh1cyBtb3N0IEROUyBvcGVyYXRvcnMganVzdCBjaG9vc2UgbG9jYXRpb25zIGFjY29yZGlu
ZyB0byB0aGVpciBwZXJzb25hbCBleHBlcmllbmNlLsKgCgpEdWUgdG8gRE5TIGF0dGFja3MgbGlr
ZSBERE9TIGF0dGFjaywgdGhlIGRlcGxveW1lbnQgb2YgRE5TU0VDIGFzIHdlbGwgYXMgdGhlIGxh
dW5jaCBvZiBuZXcgZ1RMRHMsIG1vcmUgYW5kIG1vcmUgYXV0aG9yaXR5IHNlcnZlcnMgd2lsbCBi
ZSBkZXBsb3llZCBhbmQgdGh1cyB3ZSB0aGluayBpdCBtYWtlcyBzZW5zZSB0byBkaXNjdXNzIHRo
aXMgdG9waWMgaW4gRE5TT1AgV0cuIE9uIHRoZSBmb2xsb3dpbmcgbWVldGluZywgd2Ugd291bGQg
bGlrZSB0byBkaXNjdXNzIHVzZSBjYXNlcyBhbmQgdHdvIGFwcHJvYWNoZXMgcHJvcG9zZWQgYnkg
dXMgb24gdGhpcyB0b3BpYy4gCgoKCkFueSBzdWdnZXN0aW9ucz8gCgpMb29rIGZvcndhcmQgdG8g
c2VlIHlvdSBzb29uIGluIExvbmRvbiEKCgrCoAoKCgpHdWFuZ3FpbmcgCkRlbmcKQ05OSUPCoMKg
RnJvbTrCoFRpbSBXaWNpbnNraURhdGU6wqAyMDE0LTAyLTExwqAxMjoxM1RvOsKgZG5zb3BTdWJq
ZWN0OsKgW0ROU09QXSBDYWxsIGZvciBhZ2VuZGEgaXRlbXMgZm9yIExvbmRvbsKgCsKgCkdyZWV0
aW5ncywKwqAKTG9uZG9uIGlzIGxlc3MgdGhhbiBhIG1vbnRoIGF3YXksIGFuZCB3ZSBzaG91bGQg
c3RhcnQgc29saWNpdGluZyBhZ2VuZGEgCml0ZW1zLsKgIEkgcmVxdXN0ZWQgYSAyIGhvdXIgc2Vz
c2lvbiBpbnN0ZWFkIG9mIHRoZSBub3JtYWxseSB0aWdodCAxLjUgCmhvdXJzLCBhbmQgdGhleSBn
YXZlIHVzIEZyaWRheSBNb3JuaW5nIGZvciAyLjUgaG91cnMuwqAgSSBhdHRlbXB0ZWQgdG8gZG8g
CnNvbWUgaG9yc2UgdHJhZGluZyB3aXRoIGh0dHBiaXMgYXMgdGhleSBsaWtlZCB0aGF0IHNsb3Qs
IGJ1dCBub3RoaW5nIApxdWl0ZSB3b3JrZWQuCsKgCldlIGFscmVhZHkgaGF2ZSBzb21lIHRpbWUg
Zm9yIHRoZSBwcml2YWN5IGRyYWZ0cyBmbG9hdGluZyBhcm91bmQsIAplc3BlY2lhbGx5IGRpc2N1
c3NpbmcgdGhlIHJlcXVpcmVtZW50cy7CoCBCdXQgZmVlbCBmcmVlIHRvIGVtYWlsIHVzIHdpdGgg
CnN1Z2dlc3Rpb25zLCByZXF1ZXN0cywgZXRjLsKgIEFzIHdlIGRpZCBpbiBWYW5jb3V2ZXIsIHdl
J3ZlIGJlZW4gZ2l2ZW4gCnNvbWUgbGF0aXR1ZGUgZnJvbSBvdXIgZ3JlYXQgYW5kIGdsb3Jpb3Vz
IEFEIHRvIGJlIG1vcmUgb3BlbiBpbiB3aGF0IHdlIAphY2NlcHQuCsKgCnRoYW5rcwp0aW0KwqAK
wqAKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRE5TT1Ag
bWFpbGluZyBsaXN0CkROU09QQGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vZG5zb3AKCg==

------=_001_NextPart011070616858_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html><head><meta charset=3D"utf-8"><style>body { line-height: 1.5; }block=
quote { margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em; }body { f=
ont-size: 12pt; font-family: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; color: =
rgb(0, 0, 0); line-height: 1.5; }body { line-height: 1.5; font-family: ver=
dana; color: rgb(0, 0, 0); font-size: 10pt; }</style></head><body>=0A =0A<=
div style=3D"FONT-FAMILY: Times New Roman; FONT-SIZE: 11pt"><span></span>&=
nbsp;<span style=3D"font-family: verdana; font-size: 10pt; line-height: 1.=
5; background-color: window;">Hi, Tim, I would like to request a time slot=
 of 15 minutes to discuss the topic on optimizing DNS authority server pla=
cement. As we know, the geographical distribution of DNS authority servers=
 (include root, TLD and other authority servers in the DNS hierarchy) high=
ly affects the financial costs (such as server, energy and bandwidth costs=
) from the DNS operator's point of view and also the DNS resolution latenc=
y from the DNS client's point of view. Let us consider the following quest=
ion: when hundreds even thousands of potential deployment locations are gi=
ven, which locations (may be several or tens of) should be selected to dep=
loy DNS authority servers of a specific DNS zone (for instance, .CN) so th=
at the DNS resolution delay is minimized while the financial costs do not =
exceed their budget? It is not easy to answer this question though fundame=
ntally we think that those locations with low financial level and close pr=
oximity to DNS clients should be selected. To the best of our knowledge, t=
here is still no rigorous authority server placement approach yet and thus=
 most DNS operators just choose locations according to their personal expe=
rience.&nbsp;</span></div>=0A<br>Due to DNS attacks like DDOS attack, the =
deployment of DNSSEC as well as the launch of new gTLDs, more and more aut=
hority servers will be deployed and thus we think it makes sense to discus=
s this topic in DNSOP WG. On the following meeting, we would like to discu=
ss use cases and two approaches proposed by us on this topic. =0A<br>=0A<b=
r>Any suggestions? =0A<br>Look forward to see you soon in London!=0A<br>=
=0A<div>&nbsp;</div>=0A<hr style=3D"WIDTH: 210px; HEIGHT: 1px" align=3D"le=
ft" color=3D"#b5c4df" size=3D"1">=0A<div style=3D"FONT-FAMILY: Verdana"><s=
pan><div style=3D"MARGIN-TOP: 10px; MARGIN-LEFT: 10px; MARGIN-RIGHT: 10px"=
>=0A<div><span style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; F=
ONT-SIZE: 10.5pt">Guangqing =0ADeng</span></div>=0A<div><span style=3D"FON=
T-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; FONT-SIZE: 10.5pt">CNNIC&nbs=
p;</span></div></div></span></div><blockquote style=3D"margin-top: 0px; ma=
rgin-bottom: 0px; margin-left: 2em;"><div>&nbsp;</div><div style=3D"border=
:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><div style=
=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;FONT-FAMILY:tah=
oma;COLOR:#000000; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: =
8px"><div><b>From:</b>&nbsp;<a href=3D"mailto:tjw.ietf@gmail.com">Tim Wici=
nski</a></div><div><b>Date:</b>&nbsp;2014-02-11&nbsp;12:13</div><div><b>To=
:</b>&nbsp;<a href=3D"mailto:dnsop@ietf.org">dnsop</a></div><div><b>Subjec=
t:</b>&nbsp;[DNSOP] Call for agenda items for London</div></div></div><div=
><div>&nbsp;</div>=0A<div>&nbsp;</div>=0A<div>Greetings,</div>=0A<div>&nbs=
p;</div>=0A<div>London is less than a month away, and we should start soli=
citing agenda </div>=0A<div>items.&nbsp; I requsted a 2 hour session inste=
ad of the normally tight 1.5 </div>=0A<div>hours, and they gave us Friday =
Morning for 2.5 hours.&nbsp; I attempted to do </div>=0A<div>some horse tr=
ading with httpbis as they liked that slot, but nothing </div>=0A<div>quit=
e worked.</div>=0A<div>&nbsp;</div>=0A<div>We already have some time for t=
he privacy drafts floating around, </div>=0A<div>especially discussing the=
 requirements.&nbsp; But feel free to email us with </div>=0A<div>suggesti=
ons, requests, etc.&nbsp; As we did in Vancouver, we've been given </div>=
=0A<div>some latitude from our great and glorious AD to be more open in wh=
at we </div>=0A<div>accept.</div>=0A<div>&nbsp;</div>=0A<div>thanks</div>=
=0A<div>tim</div>=0A<div>&nbsp;</div>=0A<div>&nbsp;</div>=0A<div>_________=
______________________________________</div>=0A<div>DNSOP mailing list</di=
v>=0A<div>DNSOP@ietf.org</div>=0A<div>https://www.ietf.org/mailman/listinf=
o/dnsop</div>=0A</div></blockquote>=0A</body></html>
------=_001_NextPart011070616858_=------


From nobody Fri Feb 14 05:46:16 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF661A0218; Fri, 14 Feb 2014 05:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bCfukisQLg4B; Fri, 14 Feb 2014 05:46:12 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6911A0249; Fri, 14 Feb 2014 05:46:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140214134610.15238.66099.idtracker@ietfa.amsl.com>
Date: Fri, 14 Feb 2014 05:46:10 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/4foIrUem6Fdg6J3Uoj6kP6mXuXM
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-as112-dname-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 13:46:14 -0000

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

        Title           : AS112 Redirection using DNAME
        Authors         : Joe Abley
                          Brian Dickson
                          Warren Kumari
                          George Michaelson
	Filename        : draft-ietf-dnsop-as112-dname-01.txt
	Pages           : 21
	Date            : 2014-02-14

Abstract:
   Many sites connected to the Internet make use of IPv4 addresses that
   are not globally unique.  Examples are the addresses designated in
   RFC 1918 for private use within individual sites.

   Devices in such environments may occasionally originate Domain Name
   System (DNS) queries (so-called "reverse lookups") corresponding to
   those private-use addresses.  Since the addresses concerned have only
   local significance, it is good practice for site administrators to
   ensure that such queries are answered locally.  However, it is not
   uncommon for such queries to follow the normal delegation path in the
   public DNS instead of being answered within the site.

   It is not possible for public DNS servers to give useful answers to
   such queries.  In addition, due to the wide deployment of private-use
   addresses and the continuing growth of the Internet, the volume of
   such queries is large and growing.  The AS112 project aims to provide
   a distributed sink for such queries in order to reduce the load on
   the IN-ADDR.ARPA authoritative servers.  The AS112 project is named
   after the Autonomous System Number (ASN) that was assigned to it.

   The AS112 project does not accommodate the addition and removal of
   DNS zones elegantly.  Since additional zones of definitively local
   significance are known to exist, this presents a problem.  This
   document describes modifications to the deployment and use of AS112
   infrastructure that will allow zones to be added and dropped much
   more easily.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-as112-dname-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-as112-dname-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Feb 14 06:08:37 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7355E1A0278 for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 06:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hTDZ-msv4bO for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 06:08:32 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEA01A0279 for <dnsop@ietf.org>; Fri, 14 Feb 2014 06:08:31 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id y20so4631506ier.4 for <dnsop@ietf.org>; Fri, 14 Feb 2014 06:08:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version; bh=JPacX2phVhPg26bs47AUzI3h+d+Tmd/t4hjFuvF39cI=; b=NUvxEIQSsL8QbKdJImu360G7o0JsLaNV8rhJ3wb0FJwaWBNY+0qTV6GzqLlnJF9GOy SAC2sUULVwJUduMbYxXEDaCp1IDYTpdqbU7mT9NM2YYKQD/g+Jk5vughjVxn8EggvydC uce8vmuP8mCoy2VYAVQ2GnB3ACiWVWDSrRVew=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:date:references:to:message-id:mime-version; bh=JPacX2phVhPg26bs47AUzI3h+d+Tmd/t4hjFuvF39cI=; b=hnkNspIjLLPI0IOgcQKA6QZgwLUr0Aztj9Ft65MCx9IAsbLBKdAAj60ZIXlf3Tf/4t tZfboCOzJZ7YyIKICHC6c9yhqXD2opIPm6TGlE/13sgZsgo62xeKZ26GRwurQGL7QX9j bDlebUfvfarzyy7h2vyIgiyQQaPS8tCc1aeZR4tOFxDnR5P00DSvYj4d9f+YDsri2XX3 NfGqI8LGsOf75JAREm/i4v5HtA01tcDycq0gh153tiR1s6NiwCBIomu4N1cNqCWX3GZb 7upCP/vEFoZXV64ScLPYDr8/M4qEhk1yxN/wgktqn7oLLaprJ1I+JSrvgUbRE/PezXpa jUTg==
X-Gm-Message-State: ALoCoQlbqYkb2hA4aZe0TOhjDtYX7F3JIlO+QqsXojuckEeMynchVKcBM6qVVubNpn8Y9dibUmI8
X-Received: by 10.50.56.109 with SMTP id z13mr2772686igp.6.1392386909785; Fri, 14 Feb 2014 06:08:29 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:1908:f66a:35d:e606? ([2001:4900:1042:1:1908:f66a:35d:e606]) by mx.google.com with ESMTPSA id pn6sm4528936igb.4.2014.02.14.06.08.28 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 14 Feb 2014 06:08:29 -0800 (PST)
From: Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Feb 2014 09:08:27 -0500
References: <20140214134610.15238.66099.idtracker@ietfa.amsl.com>
To: dnsop <dnsop@ietf.org>
Message-Id: <F0F8E35F-4ED7-4D8D-8860-BB1D6D97CB85@hopcount.ca>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/zYabf-x_4O817TC3zReqsoS97TE
Subject: [DNSOP] AS112 bits and pieces
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 14:08:34 -0000

Hi all,

We've just submitted

  draft-ietf-dnsop-as112-dname-01
  draft-jabley-dnsop-rfc6304bis-00

which together specify an approach to extend the current AS112 project =
to be able to sink queries from arbitrary zones, whilst still supporting =
existing AS112 semantics.

We hope to present a brief overview of the approach in London.

Reactions and reviews of the two documents would be most welcome!

Thanks,


Joe

Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: [DNSOP] I-D Action: draft-ietf-dnsop-as112-dname-01.txt
> Date: 14 February 2014 at 08:46:10 EST
> To: i-d-announce@ietf.org
> Cc: dnsop@ietf.org
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Domain Name System Operations Working =
Group of the IETF.
>=20
>        Title           : AS112 Redirection using DNAME
>        Authors         : Joe Abley
>                          Brian Dickson
>                          Warren Kumari
>                          George Michaelson
> 	Filename        : draft-ietf-dnsop-as112-dname-01.txt
> 	Pages           : 21
> 	Date            : 2014-02-14
>=20
> Abstract:
>   Many sites connected to the Internet make use of IPv4 addresses that
>   are not globally unique.  Examples are the addresses designated in
>   RFC 1918 for private use within individual sites.
>=20
>   Devices in such environments may occasionally originate Domain Name
>   System (DNS) queries (so-called "reverse lookups") corresponding to
>   those private-use addresses.  Since the addresses concerned have =
only
>   local significance, it is good practice for site administrators to
>   ensure that such queries are answered locally.  However, it is not
>   uncommon for such queries to follow the normal delegation path in =
the
>   public DNS instead of being answered within the site.
>=20
>   It is not possible for public DNS servers to give useful answers to
>   such queries.  In addition, due to the wide deployment of =
private-use
>   addresses and the continuing growth of the Internet, the volume of
>   such queries is large and growing.  The AS112 project aims to =
provide
>   a distributed sink for such queries in order to reduce the load on
>   the IN-ADDR.ARPA authoritative servers.  The AS112 project is named
>   after the Autonomous System Number (ASN) that was assigned to it.
>=20
>   The AS112 project does not accommodate the addition and removal of
>   DNS zones elegantly.  Since additional zones of definitively local
>   significance are known to exist, this presents a problem.  This
>   document describes modifications to the deployment and use of AS112
>   infrastructure that will allow zones to be added and dropped much
>   more easily.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-dnsop-as112-dname-01
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dnsop-as112-dname-01
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Fri Feb 14 12:48:44 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E721A037C; Fri, 14 Feb 2014 12:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvA7xD9Qrxbw; Fri, 14 Feb 2014 12:48:37 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 46FFD1A03C4; Fri, 14 Feb 2014 12:48:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140214204836.436.76075.idtracker@ietfa.amsl.com>
Date: Fri, 14 Feb 2014 12:48:36 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/nnmFe1Ih3uP1lG5XFffhJVkCuIc
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-respsize-15.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 20:48:40 -0000

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

        Title           : DNS Referral Response Size Issues
        Authors         : Paul Vixie
                          Akira Kato
                          Joe Abley
	Filename        : draft-ietf-dnsop-respsize-15.txt
	Pages           : 21
	Date            : 2014-02-14

Abstract:
   With a mandated default minimum maximum UDP message size of 512
   octets, the DNS protocol presents some special problems for zones
   wishing to expose a moderate or high number of authority servers (NS
   resource records).  This document explains the operational issues
   caused by, or related to this response size limit, and suggests ways
   to optimize the use of this limited space.  Guidance is offered to
   DNS server implementors and to DNS zone administrators.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-respsize/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-respsize-15

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-respsize-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Feb 14 13:00:52 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF9031A02C0; Fri, 14 Feb 2014 13:00:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07StMvvfdEwz; Fri, 14 Feb 2014 13:00:45 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 37CE81A03C8; Fri, 14 Feb 2014 13:00:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140214210042.32090.68445.idtracker@ietfa.amsl.com>
Date: Fri, 14 Feb 2014 13:00:42 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/bsBR7pwUdwCnUSzRWdSMzEEc7sc
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-as112-dname-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:00:49 -0000

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

        Title           : AS112 Redirection using DNAME
        Authors         : Joe Abley
                          Brian Dickson
                          Warren Kumari
                          George Michaelson
	Filename        : draft-ietf-dnsop-as112-dname-02.txt
	Pages           : 23
	Date            : 2014-02-14

Abstract:
   Many sites connected to the Internet make use of IPv4 addresses that
   are not globally unique.  Examples are the addresses designated in
   RFC 1918 for private use within individual sites.

   Devices in such environments may occasionally originate Domain Name
   System (DNS) queries (so-called "reverse lookups") corresponding to
   those private-use addresses.  Since the addresses concerned have only
   local significance, it is good practice for site administrators to
   ensure that such queries are answered locally.  However, it is not
   uncommon for such queries to follow the normal delegation path in the
   public DNS instead of being answered within the site.

   It is not possible for public DNS servers to give useful answers to
   such queries.  In addition, due to the wide deployment of private-use
   addresses and the continuing growth of the Internet, the volume of
   such queries is large and growing.  The AS112 project aims to provide
   a distributed sink for such queries in order to reduce the load on
   the IN-ADDR.ARPA authoritative servers.  The AS112 project is named
   after the Autonomous System Number (ASN) that was assigned to it.

   The AS112 project does not accommodate the addition and removal of
   DNS zones elegantly.  Since additional zones of definitively local
   significance are known to exist, this presents a problem.  This
   document describes modifications to the deployment and use of AS112
   infrastructure that will allow zones to be added and dropped much
   more easily.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-as112-dname-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-as112-dname-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Feb 14 13:02:42 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A313A1A03E6 for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajcXckGCd5Jw for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:02:32 -0800 (PST)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f52]) by ietfa.amsl.com (Postfix) with ESMTP id 39BB71A03F9 for <dnsop@ietf.org>; Fri, 14 Feb 2014 13:02:32 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:39027) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1WEPu1-0006Et-F5 (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 14 Feb 2014 21:02:29 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WEPu1-0004h6-Jd (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 14 Feb 2014 21:02:29 +0000
Date: Fri, 14 Feb 2014 21:02:29 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <79F80225-91C0-4185-9FB7-172E643DCE90@hopcount.ca>
Message-ID: <alpine.LSU.2.00.1402141550460.14957@hermes-1.csi.cam.ac.uk>
References: <alpine.LSU.2.00.1402132050440.18502@hermes-1.csi.cam.ac.uk> <79F80225-91C0-4185-9FB7-172E643DCE90@hopcount.ca>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/JNnExFg72V28sA1uj9GOwcLK3WQ
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] draft-fanf-dnsop-trust-anchor-witnesses-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:02:39 -0000

Joe Abley <jabley@hopcount.ca> wrote:

> Hi Tony,

Hi Joe, many thanks for the thorough review. It is greatly appreciated.

I think it's fairly obvious that I wrote just enough to get the idea
across in a reasonably complete form, but didn't bother with thorough
references (in particular not to your previous work, sorry!) or thorough
review of formal terminology.

> >    o  The root key is a single point of failure with no standby, though
> >       its storage and management is extremely resilient and trustworthy
> >       (in stark contrast to the out-of-band trust anchor update keys).
>
> I presume by that you mean the X.509 certs published on
> data.iana.org/root-anchors. The goal there was to facilitate
> endorsements by multiple independent actors, each following a documented
> and audited process to verify that what they were signing was accurate.
> The use of X.509 certificates anticipated vendors of operating systems
> and embedded devices already having certificate machinery for
> code-signing, and hence this seemed like an approach that had a low
> implementation cost.
>
> Turns out the actual approach (do nothing) had an even lower implementation cost.

Yeah :-/

> >    o  The concentration of trust in the root is politically
> >       uncomfortable.
>
> This may be true, depending on exactly what you mean, but I doubt it's
> universally true (perhaps not even widely true). I'm not sure I
> understand the motivation for including that statement has in a
> technical specification, especially when you consider that the intended
> trust mechanisms were designed to be dispersed amongst multiple (e.g.
> vendor) authorities.

Unfortunately the X.509 signatures do not disperse trust, they duplicate
it. A bootstrapping validator trusts (== is vulnerable to compromise of)
any one of its X.509 CAs.

The key point of the quorum-of-witnesses idea is that no single witness is
trusted in the way that an X.509 CA is.

> crash -> emergency, presumably.

Yes. (When my wife had her first C-section I learned that the
obstetricians use the term "emergency" to mean "proceed with normal
preparation timing" and "crash" to mean "do it right now or someone will
die".)

> The existing mechanisms (again, lamentably light on implementation)
> would also facilitate this. The mechanisms in the validator-bootstrap
> draft I referred to earlier allow trust anchor retrieval with no ability
> to validate, authenticating the retrieved data using appropriate local
> methods (e.g. the key that signed the code is used to test the signature
> of the data the code retrieved).

However the existing mechanisms rely on a lot of infrastructure which has
to be accessed with validation turned off. My root witnesses idea uses
only the DNS and leaves validation switched on while bootstrapping.

> >    o It could allow a smaller root DNSKEY RRset
>
> I suspect a transition to a single key solution would be a difficult
> transition from an administrative perspective, bordering on the
> non-actionable. Listing impossible things as advantages seems like a bit
> of a stretch. :-)

Yes, I'm rather tentative about that one.

However I generally want root trust anchor rollovers to be utterly routine
and relatively frequent, so we are sure they work, and so we have a better
chance of being able to upgrade algorithms when necessary.

So I have a vague idea that we could keep the existing KSK around to
support old validators, while validators that know about witnesses use
different more frequently updated keys for their trust anchors.

> >    o A lot more co-ordination between organizations is necessary, for
> >       the witnesses to get out-of-band authentication of new trust
> >       anchors.
>
> This should not be underestimated (or at least should be characterised).
> Presumably if we expect people (and devices) to trust a collection of
> witnesses to the authenticity of a particular copy of the KSK, we don't
> want that process to dilute the security of the process used to
> generate, store and exercise the KSK. Are we talking about additional
> ceremonies, potentially tens or hundreds of them, with each witness? Or
> are we talking about something that might fit with minimal change into
> the existing ceremonies?

The latter.

If the witnesses are just authenticating the root KSK then they only need
to do so when it changes.

If we go for the slightly more radical idea of authenticating the ZSK
instead, then the witnesses would have to observe each ceremony so they
can vouch for the new ZSK(s).

Witnesses will have their own key generation and publication processes.
IANA will run the root-witnesses.arpa registry so that validator vendors
can find the witnsesses, but IANA doesn't need to do anything with the
witness keys.

> >    This mechanism can be used to automatically update any trust anchor,
> >    though it is designed for and includes some special considerations
> >    for the root trust anchor.  The root-witnesses.arpa zone is set up to
> >    enable a validator to bootstrap trust when it has no working trust
> >    anchors other than its witnesses.
>
> I'm not sure I understand the benefit of making this a general
> mechanism. The only real application it has, in these heady days of DS
> RRSet proliferation, is in the root zone; it's hard to imagine it being
> easier to set up a plausible array of witnesses for an island with an
> otherwise insecure delegation than it is to sign the parent (or just
> choose a different parent).

True. But I think that making the design general helps to ensure it is
clean - good intellectual discipline :-)

There's also the potential for supporting TLD trust anchors to disperse
trust more thoroughly. I would like to make this possible even if it turns
out the lawyers only care about blowing gas and not practical changes.

>
> > 3.  How validators use WS records
> >
> > 3.1.  Trust anchor configuration
> >
> >    A validator's configuration for a trust anchor consists of the the
> >    trust anchor owner name, and either a set of public keys or a set of
> >    DS records, as described in [RFC4035] section 4.4.
> >
> >    A trust anchor that is automatically updated is associated with the
> >    witnesses that vouch for it.  It has a quorum value stating how many
> >    witnesses must agree before the trust anchor is updated.
>
> Where is that quorum parameter published? By the KSK maintainer, or by
> individual witnesses, or is it up to the validator operator to follow
> local policy?

The latter.

> Bad choices in this parameter seem likely to cause pain (too high and
> you need to worry about the currency of a lot of witness zones; too low
> and you are at risk of shenanigans by a small number of conspiring
> witnesses).

Right. And it depends on the size of the witness pool. But even a quorum
of two or three is a lot safer than being vulnerable to dozens of X.509
CAs.

> >    Each witness is a normal statically-configured trust anchor.  That
> >    is, witnesses are not updated automatically except by out-of-band
> >    configuration updates or software updates.  Each witness is
> >    associated with one automatically updated trust anchor for which it
> >    vouches.
>
> I worry slightly that you've just shifted the problem that ICANN
> anticipated with vendors shipping a single trust anchor and made it
> larger, a problem of shipping many trust anchors from different places.
> This is the core problem we're trying to address, I think; if it's also
> a problem that needs to be solved for this proposal, we may have just
> found our own footprints on the beach.

I tried to address this worry in the "lifecycle" section. A reasonably
large level of breakage in the witness trust anchors is OK, so witness
trust anchor updates do not have to be particularly timely - they can
happen as part of the normal software update cycle. The scheme can
tolerate breakage up to P-Q, the witness pool size minus the quorum size,
provided there are fewer than Q witness compromises.

> > 3.2.  When to try a trust anchor update
>
> So, the validator receives responses to the query ./IN/DNSKEY from
> somewhere (not necessarily directly from the authority servers) and
> discards any RRs in the set with SEP=0.

Right.

> >    The validator MAY track the DNSKEY records persistently in order to
> >    make restarts faster.  If so, it SHOULD discard any saved DNSKEY
> >    records after their RRSIG expiry time.  If it does not, it SHOULD
> >    perform an update attempt at restart.
>
> persistently -> regularly?

I intended to mean on non-volatile storage.

> >    When starting, a validator can find that its existing trust anchor
> >    does not work, perhaps because a key rollover happened while it was
> >    offline.  In this situation it cannot serve clients until the update
> >    process completes successfully.
>
> What about queries received from clients with CD=1?

Good point :-) They can be served of course.

> > 3.3.  Trust anchor update process
> >
> >    Trust anchor updates are performed with respect to a DNSKEY RRset
> >    from the trust anchor owner name.  This allows the validator to
> >    ensure that a successful update will lead to a working configuration.
>
> I presume you're talking about the trust anchor for the root zone here,
> and not a trust anchor for any witness zone. "trust anchor owner name"
> is a bit of a weird phrase, but that's probably just me.

Right. I am not particularly happy with the terminology either.

> How does the validator obtain a list of witness zones? That's manually
> configured? How are additions, removals and changes to the list of
> witness zones managed?

Yes, part of the validator configuration, usually shipped by the software
vendor but could be overridden by an admin - like root hints.

> You mean a particular DNSKEY RR, retrieved without authentication from
> some arbitrary source, can be trusted when sufficient validated WS
> responses that match the DNSKEY RR under scrutiny have been retrieved?

Right.

> Surely any WS RRSet can be trusted as well as the locally-configured
> trust anchor for the zone that contains it, once you validate the WS
> RRSet's signature.

The validator needs to be sure that it gets WS records from different
sources, so that its count of the quorum is meaningful. If the validator
accepts WS RRsets that validate regardless of the key that authenticates
them, there is the risk that one compromised witness may be able to
convince the validator that it observed a quorum when really it was
bamboozled by smoke and mirrors.

Making the root-witnesses.arpa zone unsigned ensures that validators can
only validate a root witness WS RRset with the corresponding witness key.
Other witness zones (if there ever are any) should probably have similar
arrangements. And the validator code should probably check this too, for
added safety.

> > 4.  How witnesses publish WS records
> >
> >    The administrative arrangements for publishing WS records in a
> >    witness zone are analogous to publishing DS records in a parent zone.
> >
> >    There MUST be an out-of-band (non-DNS) communications channel between
> >    the witnesses and the owner of the zone for which they vouch.  This
> >    is used to authenticate WS RRset changes.
>
> If this process is to be trusted as secure, sufficient to allow
> unattended operation, etc then presumably these processes need to be
> carefully specified and audited.

I expect so. I wonder if there is any advantage to having different
witnesses follow different procedures, to reduce the chance of common
vulnerabilities. But perhaps that would be too awkward from IANA's point
of view. There is perhaps easier scope for variation in the witnesses'
publication procedures.

> > 4.2.  Lifecycle of witness zones
> >
> >    A trust anchor SHOULD have many witness zones, in order to provide
> >    resilience as well as dispersal of trust.
> >
> >    Each witness zone is tied to a fixed witness trust anchor.  The zone
> >    lasts as long as its trust anchor.  This SHOULD be at least 10 years,
> >    since old software and configurations cannot function after too many
> >    of their witnesses have been retired.
>
> "10 years" seems like a bit of a hard-coded parameter.

It needs to be long enough to give validators a decent shelf life.

> The root zone KSK was expected to be rolled every 5 years. There is
> enthusiasm in some circles for rolling the root zone KSK much more
> frequently than that. If there are reasons to roll the root zone KSK
> that often, then presumably the same reasons dictate that witness zones'
> KSKs should roll similarly?

No, instead of rolling witness trust anchors, witnesses are replaced.
This is so that witness configurations can be static, so we don't get into
an infinite regress.

But yes, rolling witness replacement should involve fairly frequent
changes to the current recommended set of witnesses.

> It's not obvious from your description how anybody should (a) obtain a
> list of witness zones, or (b) should retrieve authenticated, local trust
> anchors for sufficient witness zones such that a quorum can reliably be
> achieved. These seem like important gaps to fill.

Yes, good point. I have said a bit about that above in this message.

> >    Each witness zone's name servers have names inside that witness zone
> >    so that they can be validated by the witness trust anchor without
> >    depending on any other part of the DNS.
>
> I'm not sure I understand the purpose of this. Are you suggesting that
> if I send a query to address X but find out in the response from the
> server at that address that I should really have been talking to address
> Y, I should apply the mind bleach and start again?

No, you don't need to go that far :-) I was probably wrong to refer to
validation here - the key is being able to resolve the WS RRs with the
absolute minimum of unnecessary dependencies, so you want witness zones to
have in-zone name servers.

> >    The root-witnesses.arpa zone SHALL be served by the root name
> >    servers.  This is so that a bootstrapping validating resolver can
> >    find its witnesses using just its root hints, and get a direct
> >    referral to the right witness zone name servers, again without
> >    depending on any other part of the DNS.
>
> There's some enthusiasm for paring back the root servers even further
> than they are, and having them serve just the root and ROOT-SERVERS.NET
> zones (the latter so that priming responses can be fattened with lovely
> tasty glue).

Yes, I am aware that this part of the proposal might be contentious :-)

> To clarify your intent, are you suggesting the root servers should serve
> ROOT-WITNESSES.ARPA simply because there's a lot of them, i.e. the
> requirement is that those zones be served competently? If not, where
> does the requirement come from?

This is to support bootstrapping without depending on too much
infrastructure, so that a validator with a broken root trust anchor can
still resolve and validate WS RRsets with something very close if not
identical to normal resolution and validation logic.

So it'll make a query like a.root-witnesses.arpa. IN WS ?
It'll start by sending the query to the root servers using its hints. It
will get an immediate referral to the a.root-witnesses.arpa name servers.
It has a trust anchor for that zone so it doesn't need to validate the
referral. It will repeats the WS query to the witness name servers, then
it can validate the query by asking the same servers for their DNSKEY
RRset and using its witness trust anchor.

If the zone were hosted elsewhere, the referral from the root name servers
would be to the arpa servers. Normal logic would be to validate this
referral, but it can't because its root trust anchor is broken. You don't
want bootstrapping to fail so quickly...

Thanks again for the review.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.


From nobody Fri Feb 14 13:02:52 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090171A03FE for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:02:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fz_mfrYFxj4f for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:02:43 -0800 (PST)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 610EE1A03EB for <dnsop@ietf.org>; Fri, 14 Feb 2014 13:02:43 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:36677) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1WEPuD-0001kR-6e (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 14 Feb 2014 21:02:41 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WEPuD-0004hv-0A (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 14 Feb 2014 21:02:41 +0000
Date: Fri, 14 Feb 2014 21:02:40 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <F0F8E35F-4ED7-4D8D-8860-BB1D6D97CB85@hopcount.ca>
Message-ID: <alpine.LSU.2.00.1402141456450.14957@hermes-1.csi.cam.ac.uk>
References: <20140214134610.15238.66099.idtracker@ietfa.amsl.com> <F0F8E35F-4ED7-4D8D-8860-BB1D6D97CB85@hopcount.ca>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/ZkTi-PprvzJy0Krav4fk7fAUEB8
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] AS112 bits and pieces
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:02:46 -0000

Joe Abley <jabley@hopcount.ca> wrote:
>
> Reactions and reviews of the two documents would be most welcome!

The as112-dname draft still does not mention the glibc DNAME logging bug.

https://www.ietf.org/mail-archive/web/dnsop/current/msg10638.html

Typo: "flexibl"

Apart from that, looks OK :-)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.


From nobody Fri Feb 14 13:18:10 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F94E1A0394 for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQ7WdSqRd5TA for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:18:06 -0800 (PST)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 23BA71A02C0 for <dnsop@ietf.org>; Fri, 14 Feb 2014 13:18:06 -0800 (PST)
Received: by mail-qc0-f171.google.com with SMTP id n7so21317265qcx.30 for <dnsop@ietf.org>; Fri, 14 Feb 2014 13:18:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=4q6EpEv+N7zgPGURQjZkQulo1a62D2zhWYGgRoOE57Q=; b=JFoWfKH3pDZEOTrNOTPc8qSTQ/XmskOHUfPPzGqdwDeltkjyU8LgJJG4lPbljbiIIP CwHMjhtc/fo+sFwjftA6R4DEAqETMmK4Z8ggfNa98iUC1Ng5lszAjKbNnlL2SByu6vUk awqPsXU8hAX9Rmk783CwHyCcKTjDmYr0azhpA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=4q6EpEv+N7zgPGURQjZkQulo1a62D2zhWYGgRoOE57Q=; b=bO6ZpQiDjKnfOTuHdrcD0xyvNwL87Aee1uLk065ZrA9KpJH9HnEdfMHLB/kNOWOdMv +ME6qbjo8r5qxrRK7+yXEno3/w/SGhRUJMpS0tHhlVwH2AsXc02/IzZivs5JdXLgh/46 +8xrqvCZMGzl0SUS9hxncjGKa1i7KLq/R/d1WEQxPe6z4lqz45B6xTpTIrz1yPCQpi5s eP/hJqx+I6Fh92DaxkbmXsVsQzMiK/stgKfe1aUAimYDO3yWPhHVqgOHxWPSnVut4WRU lWK3r+3R8QYlI/F1AqQnJkDHtN4T1htZRRHSMRsBDqRIo6TQZESsxCLeNvIig/af8qer /6uA==
X-Gm-Message-State: ALoCoQk3xniPmcYQNMdth11KpqF1O8CxnaTv9vhzA4Ryaxrb+LWpNvW2HaLoZaheebP+XkAqhIZC
X-Received: by 10.140.89.167 with SMTP id v36mr16361737qgd.27.1392412684318; Fri, 14 Feb 2014 13:18:04 -0800 (PST)
Received: from [199.212.90.53] (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id u4sm19059660qai.21.2014.02.14.13.18.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 14 Feb 2014 13:18:03 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_484B37E9-4D43-4607-8628-C13FF1118006"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.LSU.2.00.1402141456450.14957@hermes-1.csi.cam.ac.uk>
Date: Fri, 14 Feb 2014 16:18:14 -0500
Message-Id: <668CAA22-052D-476A-9E49-6FB9514E5756@hopcount.ca>
References: <20140214134610.15238.66099.idtracker@ietfa.amsl.com> <F0F8E35F-4ED7-4D8D-8860-BB1D6D97CB85@hopcount.ca> <alpine.LSU.2.00.1402141456450.14957@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/kkWqYdyGATM0WnFzjelUWnN_t-E
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] AS112 bits and pieces
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:18:08 -0000

--Apple-Mail=_484B37E9-4D43-4607-8628-C13FF1118006
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-02-14, at 16:02, Tony Finch <dot@dotat.at> wrote:

> Joe Abley <jabley@hopcount.ca> wrote:
>>=20
>> Reactions and reviews of the two documents would be most welcome!
>=20
> The as112-dname draft still does not mention the glibc DNAME logging =
bug.

Oops, sorry for missing that, and thanks for the reminder.

In other news, you may have noticed that I just posted a -02, hot on the =
heels of the -01. I received some useful advice regarding the IANA =
Considerations section, and felt that it was worth making changes sooner =
rather than later.

Thanks for the review of -01!


Joe


--Apple-Mail=_484B37E9-4D43-4607-8628-C13FF1118006
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlL+iBYACgkQNI8MvYZSOizFgACdH9J0XcmAw6eYzQa+NDyyr+57
KokAoI4rrI4+ui73YAwLdVigvIVX2Sbg
=lPlO
-----END PGP SIGNATURE-----

--Apple-Mail=_484B37E9-4D43-4607-8628-C13FF1118006--


From nobody Fri Feb 14 13:26:13 2014
Return-Path: <wmaton@ottix.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87221A027F for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XF6VzcY-gtZq for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:26:08 -0800 (PST)
Received: from iskra.ottix.net (iskra.ottix.net [IPv6:2001:410:90ff::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3383B1A0358 for <dnsop@ietf.org>; Fri, 14 Feb 2014 13:25:55 -0800 (PST)
Received: from iskra.ottix.net (localhost [127.0.0.1]) by iskra.ottix.net (8.14.6/8.14.6) with ESMTP id s1ELPkGW027759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 Feb 2014 16:25:46 -0500
Received: from localhost (wmaton@localhost) by iskra.ottix.net (8.14.6/8.14.6/Submit) with ESMTP id s1ELPkG8027755; Fri, 14 Feb 2014 16:25:46 -0500
Date: Fri, 14 Feb 2014 16:25:46 -0500 (EST)
From: "William F. Maton Sotomayor" <wmaton@ottix.net>
To: Tony Finch <dot@dotat.at>
In-Reply-To: <alpine.LSU.2.00.1402141456450.14957@hermes-1.csi.cam.ac.uk>
Message-ID: <alpine.DEB.2.03.1402141618310.14904@iskra.ottix.net>
References: <20140214134610.15238.66099.idtracker@ietfa.amsl.com> <F0F8E35F-4ED7-4D8D-8860-BB1D6D97CB85@hopcount.ca> <alpine.LSU.2.00.1402141456450.14957@hermes-1.csi.cam.ac.uk>
User-Agent: Alpine 2.03 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Urg1KBfaUM1NkNxicG9OMrYa9lY
Cc: dnsop <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] AS112 bits and pieces
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:26:11 -0000

On Fri, 14 Feb 2014, Tony Finch wrote:

> Joe Abley <jabley@hopcount.ca> wrote:
>>
>> Reactions and reviews of the two documents would be most welcome!
>
> The as112-dname draft still does not mention the glibc DNAME logging bug.

Which Linux distro, or a set of Linux distros?  Some seaches yield various 
bug reports related to DNAME over the last few years in a couple of 
distros.

> https://www.ietf.org/mail-archive/web/dnsop/current/msg10638.html
>
> Typo: "flexibl"
>
> Apart from that, looks OK :-)

+1

>
> Tony.
> -- 
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
> Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
> occasionally poor at first.
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

wfms


From nobody Fri Feb 14 13:54:37 2014
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDDB1A03C8 for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ucl1TdpqiF7t for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 13:54:31 -0800 (PST)
Received: from smtp117.ord1c.emailsrvr.com (smtp117.ord1c.emailsrvr.com [108.166.43.117]) by ietfa.amsl.com (Postfix) with ESMTP id D1D801A0455 for <dnsop@ietf.org>; Fri, 14 Feb 2014 13:54:25 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 379001B8135; Fri, 14 Feb 2014 16:54:24 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id CBBD41B8099;  Fri, 14 Feb 2014 16:54:22 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_844867F8-09CE-4D53-A626-EDC7213F1023"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <CAHw9_iKEuOf+AZpDfB0EUsU9uVvGcAXJVs6DDTD1XsjkOp+_MQ@mail.gmail.com>
Date: Fri, 14 Feb 2014 16:54:22 -0500
Message-Id: <163BA378-C0DF-4067-938E-81ED4E0FC087@ogud.com>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <20140213145932.GE25409@mx1.yitter.info> <BA548E83-4D14-4A08-A958-190F541D2337@viagenie.ca> <52FCE993.3070005@frobbit.se> <D38F596A-9DC3-49A1-A4D7-FF86F3AC1FBD@ogud.com> <52FD57D7.30004@frobbit.se> <CAHw9_iKEuOf+AZpDfB0EUsU9uVvGcAXJVs6DDTD1XsjkOp+_MQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/aDy2eCZH2D36LfNOk1SB_bX900g
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:54:35 -0000

--Apple-Mail=_844867F8-09CE-4D53-A626-EDC7213F1023
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1



I posted my draft on this this topic,=20
I do not think it is a DNS topic thus I put the appsawg in my draft =
name:=20

A new version of I-D, draft-ogud-appsawg-multiple-namespaces-00.txt
has been successfully submitted by Olafur Gudmundsson and posted to the
IETF repository.

Name:		draft-ogud-appsawg-multiple-namespaces
Revision:	00
Title:		Providing support for multiple namespaces to Internet =
protocols.
Document date:	2014-02-14
Group:		Individual Submission
Pages:		6
URL:            =
http://www.ietf.org/internet-drafts/draft-ogud-appsawg-multiple-namespaces=
-00.txt
Status:         =
https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-namespaces/
Htmlized:       =
http://tools.ietf.org/html/draft-ogud-appsawg-multiple-namespaces-00


Abstract:
  Over the years there have been various proposals as to use namespaces
  other than the DNS/IN namespace that is under ICANN administration.
  Some of these were simple DNS competitors others use different lookup
  technologies.  In addition it is hard to supply different character
  encodings to DNS as each application needs to provide the translation
  between the encoding used and the format expected by DNS.

  This draft proposes a new service layer to provide multiplexing of
  different namespaces into appropriate function calls.

Olafur


On Feb 13, 2014, at 8:22 PM, Warren Kumari <warren@kumari.net> wrote:

> [ Replying to a bunch of comments in one mail (not just Patrik's). I'm
> stuck in the storm in ATL (
> http://www.cnn.com/2014/02/13/us/winter-weather/ ), and so am behind
> on mail, etc. ]
>=20
> Just so folk know, Olafur and I chatted about this before he submitted
> his draft. I think that we are in agreement that the two drafts are
> complementary, not conflicting.
> Using a URI / Prefix / <something> to indicate another namespace (to
> me at least) seems like an elegant, clean, sane, "better" solution --
> unfortunately it seems that making pseudo-TLDs has suddenly become
> popular, and so I think that reserving .ALT is an important *tactical*
> solution. It creates a safe area for people who want to do this sort
> of thing to do so, and lets the IETF push back on people trying to
> reserve .foo in the future. I think we should work on Olafur's
> proposal in parallel.
>=20
> On Stephane's terminology comments...
> Yes, the terminology section sucks -- unfortunately it was the best I
> could come up with.
> I'm really bad at terminology thingie whatzits. Andrew made it better,
> but it is still bad. Much of the problem is that we are talking about
> somewhat squishy things -- people using names in places where you
> would usually put a "DNS name" (whatever that means).
> 1:  'the DNS "standard" of a series of labels separated with dots' --
> An earlier version of the doc had some long and contrived text about
> "names that are comprised of short strings (<=3D63) of LDH characters,
> separated by dots" until Andrew hit me with a stick and reminded me
> about 1: IDNs and 2: DNS being 8bit clean. I'd put the word "standard"
> in quotes to try and make it clear that this isn't really the DNS
> standard.
> 2: 'DNS context: The namespace administered by ICANN.'  -- Yup, it's
> not clear / correct. But I couldn't figure out how to make it better.
> It's not really the 'DNS protocol', because some of these solutions
> use the DNS protocol, and then intercept it. What I was aiming for was
> something like "The thingie that most people would think of if you
> asked them to go resolve a name".
> Suggestions / text more than welcome!
>=20
>=20
> On the "should e.g .onion move under this?" discussion...
> Personally I think that the Right Thing(tm) would be for .onion / .bit
> / etc to move under .alt -- unfortunately they are already deployed in
> the wild, and there is running code, etc. If I had a wand I'd wave it,
> magic would happen, everyone would have a pony and .onion would
> suddenly be under .alt. Unfortunately I think that the reality is
> that, whether or not the IETF approves the grothoff names, they will
> continue to be used. I'd rather that that is documented. The .ALT
> proposal is largely a solution so that we don't end up in the same
> place in the future.  Olafur's namespace prefix solution is *better*,
> but is (IMO) much more of a long term solution.
>=20
>=20
> On the "Should there be an IANA registry?" bit.
> I have no idea. I'm very conflicted on this. There are definite
> advantages and disadvantages to both.
> I want it to be easy for someone to start using a name here, so that
> they have no excuse not to, but I'm also concerned about the chaos /
> anarchy. An option (but an ugly one!) would be that we reserve
> something like unmanaged.alt (or u.alt or swamp.alt, or...) as
> unmanaged space within the ALT TLD. Other SLD would require expert
> review or something.
>=20
> Well, I'm off to go see if I can find any food -- when I went for
> lunch earlier in the day the restaurant had already run out of
> french-fries, tomatoes and a number of beers...
> Wish me luck.
> W
>=20
>=20
> On Thu, Feb 13, 2014 at 6:40 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:
>> On 2014-02-13 11:19, Olafur Gudmundsson wrote:
>>>=20
>>> On Feb 13, 2014, at 10:49 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:
>>>=20
>>>> On 2014-02-13 10:23, Marc Blanchet wrote:
>>>>> - why not just register a URN namespace and use it as they see =
fit?
>>>>=20
>>>> Because you only type in a string that "looks like a domain name" =
in
>>>> applications (for example browsers) without the URI scheme =
nowadays, and
>>>> people want that to work also with strings in other namespaces.
>>>>=20
>>>> I.e. it all, from my perspective, have to do with where the =
signalling
>>>> is on what namespace to use. And if that signalling is inline, then =
we
>>>> do have something that can be viewed as the equivalent of a =
namespace
>>>> collision.
>>>>=20
>>>> If people had entered the URI scheme all the time, including =
"http",
>>>> then we would have been in a different situation.
>>>=20
>>>=20
>>> I think that the draft is not radical enough it is trying to provide =
some belt and suspenders to a
>>> syntom rather than address the actual problem.
>>>=20
>>> The Meta problem is Multiple Namespaces with different resolution =
technologies.
>>> Addressing this via a SUFFIX in the domain name feels wrong,
>>> What I will propose is a Namespace layer solution that is a prefix =
to the name presented,
>>> thus names will be presented to the namespace layer as =
<namespace/name-encoding><space separator><name>
>>> Examples using ## as the separator
>>>      DNS##www.example.com    This is normal DNS name,
>>>      GNU##eff
>>>      DUTF8##..... (DNS name in UTF8 format)
>>>      www.example.net    (by default the name is DNS)
>>>=20
>>> With a namespace layer we can have the host reject lookup locally if =
it does not know how to handle the namespace,
>>> rather than dump it out as ".alt" query.
>>>=20
>>> I know this requires changes in lookup services and code, but it =
moves the effort to the people that want new namespaces.
>>>=20
>>>      Olafur
>>> PS: IANA should maintain a registry of namespaces
>>=20
>> This is to me approximately like the URI scheme idea, but a different
>> syntax. Can fly, might not fly.
>>=20
>> The whole question is what the application developers and marketing
>> people will print on bulletin boards and accept in input fields in
>> applications (and their configurations).
>>=20
>> Which unfortunately means we do not know until some time after we =
have
>> tried to standardize it... :-P
>>=20
>>   Patrik
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop


--Apple-Mail=_844867F8-09CE-4D53-A626-EDC7213F1023
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div><br></div>I posted my draft on this this =
topic,&nbsp;<div>I do not think it is a DNS topic thus I put the appsawg =
in my draft name:&nbsp;</div><div><br></div><div>A new version of I-D, =
draft-ogud-appsawg-multiple-namespaces-00.txt<br>has been successfully =
submitted by Olafur Gudmundsson and posted to the<br>IETF =
repository.<br><br>Name:<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	=
</span>draft-ogud-appsawg-multiple-namespaces<br>Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>00<br>Title:<span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span><span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">	</span>Providing support for multiple namespaces to Internet =
protocols.<br>Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>2014-02-14<br>Group:<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>Individual Submission<br>Pages:<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>6<br>URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/internet-drafts/draft-ogud-appsawg-multiple-na=
mespaces-00.txt">http://www.ietf.org/internet-drafts/draft-ogud-appsawg-mu=
ltiple-namespaces-00.txt</a><br>Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-names=
paces/">https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-names=
paces/</a><br>Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ogud-appsawg-multiple-namespaces-=
00">http://tools.ietf.org/html/draft-ogud-appsawg-multiple-namespaces-00</=
a><br><br><br>Abstract:<br>&nbsp;&nbsp;Over the years there have been =
various proposals as to use namespaces<br>&nbsp;&nbsp;other than the =
DNS/IN namespace that is under ICANN administration.<br>&nbsp;&nbsp;Some =
of these were simple DNS competitors others use different =
lookup<br>&nbsp;&nbsp;technologies. &nbsp;In addition it is hard to =
supply different character<br>&nbsp;&nbsp;encodings to DNS as each =
application needs to provide the translation<br>&nbsp;&nbsp;between the =
encoding used and the format expected by DNS.<br><br>&nbsp;&nbsp;This =
draft proposes a new service layer to provide multiplexing =
of<br>&nbsp;&nbsp;different namespaces into appropriate function =
calls.<br><br>Olafur</div><div><br></div><div><br></div><div><div><div>On =
Feb 13, 2014, at 8:22 PM, Warren Kumari &lt;<a =
href=3D"mailto:warren@kumari.net">warren@kumari.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">[ Replying to a bunch of comments in one mail (not just =
Patrik's). I'm<br>stuck in the storm in ATL (<br><a =
href=3D"http://www.cnn.com/2014/02/13/us/winter-weather/">http://www.cnn.c=
om/2014/02/13/us/winter-weather/</a> ), and so am behind<br>on mail, =
etc. ]<br><br>Just so folk know, Olafur and I chatted about this before =
he submitted<br>his draft. I think that we are in agreement that the two =
drafts are<br>complementary, not conflicting.<br>Using a URI / Prefix / =
&lt;something&gt; to indicate another namespace (to<br>me at least) =
seems like an elegant, clean, sane, "better" solution =
--<br>unfortunately it seems that making pseudo-TLDs has suddenly =
become<br>popular, and so I think that reserving .ALT is an important =
*tactical*<br>solution. It creates a safe area for people who want to do =
this sort<br>of thing to do so, and lets the IETF push back on people =
trying to<br>reserve .foo in the future. I think we should work on =
Olafur's<br>proposal in parallel.<br><br>On Stephane's terminology =
comments...<br>Yes, the terminology section sucks -- unfortunately it =
was the best I<br>could come up with.<br>I'm really bad at terminology =
thingie whatzits. Andrew made it better,<br>but it is still bad. Much of =
the problem is that we are talking about<br>somewhat squishy things -- =
people using names in places where you<br>would usually put a "DNS name" =
(whatever that means).<br>1: &nbsp;'the DNS "standard" of a series of =
labels separated with dots' --<br>An earlier version of the doc had some =
long and contrived text about<br>"names that are comprised of short =
strings (&lt;=3D63) of LDH characters,<br>separated by dots" until =
Andrew hit me with a stick and reminded me<br>about 1: IDNs and 2: DNS =
being 8bit clean. I'd put the word "standard"<br>in quotes to try and =
make it clear that this isn't really the DNS<br>standard.<br>2: 'DNS =
context: The namespace administered by ICANN.' &nbsp;-- Yup, it's<br>not =
clear / correct. But I couldn't figure out how to make it =
better.<br>It's not really the 'DNS protocol', because some of these =
solutions<br>use the DNS protocol, and then intercept it. What I was =
aiming for was<br>something like "The thingie that most people would =
think of if you<br>asked them to go resolve a name".<br>Suggestions / =
text more than welcome!<br><br><br>On the "should e.g .onion move under =
this?" discussion...<br>Personally I think that the Right Thing(tm) =
would be for .onion / .bit<br>/ etc to move under .alt -- unfortunately =
they are already deployed in<br>the wild, and there is running code, =
etc. If I had a wand I'd wave it,<br>magic would happen, everyone would =
have a pony and .onion would<br>suddenly be under .alt. Unfortunately I =
think that the reality is<br>that, whether or not the IETF approves the =
grothoff names, they will<br>continue to be used. I'd rather that that =
is documented. The .ALT<br>proposal is largely a solution so that we =
don't end up in the same<br>place in the future. &nbsp;Olafur's =
namespace prefix solution is *better*,<br>but is (IMO) much more of a =
long term solution.<br><br><br>On the "Should there be an IANA =
registry?" bit.<br>I have no idea. I'm very conflicted on this. There =
are definite<br>advantages and disadvantages to both.<br>I want it to be =
easy for someone to start using a name here, so that<br>they have no =
excuse not to, but I'm also concerned about the chaos /<br>anarchy. An =
option (but an ugly one!) would be that we reserve<br>something like =
unmanaged.alt (or u.alt or swamp.alt, or...) as<br>unmanaged space =
within the ALT TLD. Other SLD would require expert<br>review or =
something.<br><br>Well, I'm off to go see if I can find any food -- when =
I went for<br>lunch earlier in the day the restaurant had already run =
out of<br>french-fries, tomatoes and a number of beers...<br>Wish me =
luck.<br>W<br><br><br>On Thu, Feb 13, 2014 at 6:40 PM, Patrik F=E4ltstr=F6=
m &lt;<a href=3D"mailto:paf@frobbit.se">paf@frobbit.se</a>&gt; =
wrote:<br><blockquote type=3D"cite">On 2014-02-13 11:19, Olafur =
Gudmundsson wrote:<br><blockquote type=3D"cite"><br>On Feb 13, 2014, at =
10:49 AM, Patrik F=E4ltstr=F6m &lt;<a =
href=3D"mailto:paf@frobbit.se">paf@frobbit.se</a>&gt; =
wrote:<br><br><blockquote type=3D"cite">On 2014-02-13 10:23, Marc =
Blanchet wrote:<br><blockquote type=3D"cite">- why not just register a =
URN namespace and use it as they see fit?<br></blockquote><br>Because =
you only type in a string that "looks like a domain name" =
in<br>applications (for example browsers) without the URI scheme =
nowadays, and<br>people want that to work also with strings in other =
namespaces.<br><br>I.e. it all, from my perspective, have to do with =
where the signalling<br>is on what namespace to use. And if that =
signalling is inline, then we<br>do have something that can be viewed as =
the equivalent of a namespace<br>collision.<br><br>If people had entered =
the URI scheme all the time, including "http",<br>then we would have =
been in a different situation.<br></blockquote><br><br>I think that the =
draft is not radical enough it is trying to provide some belt and =
suspenders to a<br>syntom rather than address the actual =
problem.<br><br>The Meta problem is Multiple Namespaces with different =
resolution technologies.<br>Addressing this via a SUFFIX in the domain =
name feels wrong,<br>What I will propose is a Namespace layer solution =
that is a prefix to the name presented,<br>thus names will be presented =
to the namespace layer as &lt;namespace/name-encoding&gt;&lt;space =
separator&gt;&lt;name&gt;<br>Examples using ## as the separator<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS##<a =
href=3D"http://www.example.com">www.example.com</a> =
&nbsp;&nbsp;&nbsp;This is normal DNS name,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;GNU##eff<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DUTF8##..... (DNS name in UTF8 format)<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.example.net">www.example.net</a> =
&nbsp;&nbsp;&nbsp;(by default the name is DNS)<br><br>With a namespace =
layer we can have the host reject lookup locally if it does not know how =
to handle the namespace,<br>rather than dump it out as ".alt" =
query.<br><br>I know this requires changes in lookup services and code, =
but it moves the effort to the people that want new namespaces.<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Olafur<br>PS: IANA should maintain a =
registry of namespaces<br></blockquote><br>This is to me approximately =
like the URI scheme idea, but a different<br>syntax. Can fly, might not =
fly.<br><br>The whole question is what the application developers and =
marketing<br>people will print on bulletin boards and accept in input =
fields in<br>applications (and their configurations).<br><br>Which =
unfortunately means we do not know until some time after we =
have<br>tried to standardize it... :-P<br><br> =
&nbsp;&nbsp;Patrik<br><br><br><br><br>____________________________________=
___________<br>DNSOP mailing list<br><a =
href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/dnsop<br></blockquote></blockquote></div><br></div></body=
></html>=

--Apple-Mail=_844867F8-09CE-4D53-A626-EDC7213F1023--


From nobody Fri Feb 14 14:04:26 2014
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2782F1A00B0; Fri, 14 Feb 2014 14:04:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBopjzHqelyx; Fri, 14 Feb 2014 14:04:16 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id ADA231A00C6; Fri, 14 Feb 2014 14:04:07 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 112EB800AA; Fri, 14 Feb 2014 17:04:06 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1392415446; bh=JuzXP6NxPTww83ldK7QDSX+LF/HTlY1p8P1TSwfTX6A=; h=Date:From:To:cc:Subject; b=t+Qu/BFrtFE2ng7IZOn1xCkOvJIKzhcjqO+s4ThJ2fGD/jlEQkt98IDNDerUrrnJ+ n7uOywd6M8JYDILv/pXzR1AlnRJApwj1ldyOcEm5YBm1ksSJJwhPNaUalAtQhbo+Oe qR0kUDYYGh3vaajBTgIp/Rh9uVT/0wLVLfjvkd9w=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s1EM45sb016374; Fri, 14 Feb 2014 17:04:05 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Fri, 14 Feb 2014 17:04:05 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: DNSEXT Group Working <dnsext@ietf.org>
Message-ID: <alpine.LFD.2.10.1402141655560.9049@bofh.nohats.ca>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/GLiXj9MC8DWxikRnDOpUjhIAjXA
Cc: dnsop <dnsop@ietf.org>
Subject: [DNSOP] updated draft-wouters-edns-chain-query and draft-wouters-edns-tcp-keepalive
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 22:04:22 -0000

Due to lack of a WG list, sent to dnsop and dnsext

I've updated two drafts:

https://datatracker.ietf.org/doc/draft-wouters-edns-tcp-keepalive/

By popular request, the TIMEOUT value can now be used by both clients
and servers to manage their resources and expectations.

Various people requested we should not be too strict on anycast servers,
and we no longer require them to only use a TIMEOUT of 0.

Addressed comments from Ray, Mark, Tatuya, and others, and findings of
me as a result of testing using a patched dig against common DNS servers
capability to keep TCP sessions open already.

Reference the problem of 5966 recommending closing idle TCP sessions in
seconds.

https://datatracker.ietf.org/doc/draft-wouters-edns-chain-query/
(formerly draft-wouters-edns-tcp-chain-query)

Most importantly, it no longer requires TCP, but will allow any "source
ip validated" transport, and references draft-eastlake-cookies for UDP.

Addresses Marc's comment regarding DNS requests > 512 bytes

Clarifies why we want NS records (in case we switch from forwarder to
standalone recursive)

Update on justification why this is better than rapid-fire UDP.

Paul


From nobody Fri Feb 14 15:07:57 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B434D1A0459; Fri, 14 Feb 2014 15:07:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHYzjm80mqon; Fri, 14 Feb 2014 15:07:42 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 878AD1A0450; Fri, 14 Feb 2014 15:07:37 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 5529823E24C2; Fri, 14 Feb 2014 23:07:35 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e_TVKLuP8jKQ; Sat, 15 Feb 2014 00:07:33 +0100 (CET)
Received: from kopoli (f052005189.adsl.alicedsl.de [78.52.5.189]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id EFF8F23E24BC; Sat, 15 Feb 2014 00:07:32 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <dnsext@ietf.org>, <DNSOP@ietf.org>
Date: Sat, 15 Feb 2014 00:07:31 +0100
Message-ID: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8p2Ydc1m63NpXkQOSaC46ODJ+WHQ==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/TF4Ysd2qn1vdHlyrVg5hYtNKEeQ
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, 'Marc Buijsman' <Marc.Buijsman@os3.nl>
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 23:07:46 -0000

Thanks for the information you've provided, I improved the document
according to comments and found out that the report also has a few problems
which is due to the fact that it misinterpreted the of CGA-TSIG document.

Here I explain the problems or the reasons of choices:

- CGA-TSIG cannot use MAC as a signature field. The purpose was that to have
all the CGA data in one section instead of trying to find them in different
sections of TSIG. 

- sizes of length encoding: It is one byte. It is enough for any key sizes.
If you also check the "checksum" field in the packets, you will find out
that it is only 8 bits or one byte. In the emails I explained to you that it
is the multiple of 8. In no RFC you can find out that the value is the
length of data in bits. It is always the length of data in bytes. But how
you showed in your report is that you consider the number of bits and not
bytes so you had the following example
2048/8=256 (now you only converted the number of bits to bytes) so you
needed to divide it by another 8 that is 256/8=32 and this is the value you
set to length. If you even consider the key size 7680, then the length will
be only 120.
nd
- old signature only contains time signed. The reason is to avoid increasing
the packet length 

I appreciate further comments and would like more people review it so that
we can go ahead with this document.

Thanks,
Hosnieh



A new version of I-D, draft-rafiee-intarea-cga-tsig-07.txt
has been successfully submitted by Hosnieh Rafiee and posted to the IETF
repository.

Name:		draft-rafiee-intarea-cga-tsig
Revision:	07
Title:		Secure DNS Authentication using CGA/SSAS Algorithm in IPv6
Document date:	2014-02-15
Group:		Individual Submission
Pages:		26
URL:
http://www.ietf.org/internet-drafts/draft-rafiee-intarea-cga-tsig-07.txt
Status:
https://datatracker.ietf.org/doc/draft-rafiee-intarea-cga-tsig/
Htmlized:       http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-07
Diff:
http://www.ietf.org/rfcdiff?url2=draft-rafiee-intarea-cga-tsig-07

Abstract:
   This document describes a new mechanism that can be used to reduce
   the need for human intervention during DNS authentication and secure
   DNS authentication in various scenarios such as the DNS
   authentication of resolvers to stub resolvers, authentication during
   zone transfers, authentication of root DNS servers to recursive DNS
   servers, and authentication during the FQDN (RFC 4703) update.

   Especially in the last scenario, i.e., FQDN, if the node uses the
   Neighbor Discovery Protocol (NDP) (RFC 4861, RFC 4862), unlike the
   Dynamic Host Configuration Protocol (DHCP) (RFC 3315), the node has
   no way of updating his FQDN records on the DNS and has no means for a
   secure authentication with the DNS server. While this is a major
   problem in NDP-enabled networks, this is a minor problem in DHCPv6.
   This is because the DHCP server updates the FQDN records on behalf of
   the nodes on the network. This document also introduces a possible
   algorithm for DNS data confidentiality.





 


> -----Original Message-----
> From: dnsext [mailto:dnsext-bounces@ietf.org] On Behalf Of Marc Buijsman
> Sent: Thursday, January 16, 2014 3:45 PM
> To: dnsext@ietf.org
> Cc: Jeroen van der Ham
> Subject: [dnsext] CGA-TSIG research report
> 
> Dear working group members,
> 
> For my master's thesis I have performed an investigation at NLnet Labs on
> CGA-TSIG as a solution to the last mile problem of DNS. The version of the
> CGA-TSIG proposal that I reviewed is the current latest version at
> http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-06. During the
course of
> my research I have already had some contact with Ms. Rafiee.
> 
> In order to do a verification of the CGA-TSIG proposal I have created a
proof
> of concept implementation in NLnet Labs' "ldns" library. Since the scope
of
> the project was limited to the last mile problem it only includes the code
> required for this purpose, but the implementation could easily be extended
> to support other applications (like zone transfers). I have found that
CGA-TSIG
> has potential to be an adequate solution to the last mile problem on IPv6
> networks, although some future research is needed with regard to
> bootstrapping the authentication.
> 
> As a result, I would hereby like to refer you to my report which can be
found
> at http://www.nlnetlabs.nl/downloads/publications/report-rp2-buijsman.pdf.
> I have outlined my results in section 4.2 which contains suggestions on
how I
> believe the CGA-TSIG draft could be clarified and otherwise improved. I
hope
> my suggestions will be adopted in the next version of the draft. The PoC
code
> can be found in the online Git repository of NLnet Labs at
> http://git.nlnetlabs.nl/ldns/?h=cga-tsig.
> 
> I hope my work will be helpful in standardising CGA-TSIG.
> 
> Yours sincerely,
> 
> Marc Buijsman
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext


From nobody Fri Feb 14 15:32:41 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08101A00E8; Fri, 14 Feb 2014 15:32:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KKc4984uQ9ZZ; Fri, 14 Feb 2014 15:32:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 835FA1A04BF; Fri, 14 Feb 2014 15:32:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140214233234.9823.63120.idtracker@ietfa.amsl.com>
Date: Fri, 14 Feb 2014 15:32:34 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/x9vWxYw-3wTkgzyA2JAJkxgjVPk
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-resolver-priming-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 23:32:36 -0000

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

        Title           : Initializing a DNS Resolver with Priming Queries
        Authors         : Peter Koch
                          Matt Larson
	Filename        : draft-ietf-dnsop-resolver-priming-04.txt
	Pages           : 9
	Date            : 2014-02-14

Abstract:
   This document describes the initial queries a DNS resolver is
   supposed to emit to initialize its cache with a current NS RRSet for
   the root zone as well as the necessary address information.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-resolver-priming-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-resolver-priming-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Feb 14 19:03:39 2014
Return-Path: <zihu@usc.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67AB41A0026 for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 19:03:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GoOzyJYYUA-q for <dnsop@ietfa.amsl.com>; Fri, 14 Feb 2014 19:03:33 -0800 (PST)
Received: from mail-yh0-f46.google.com (mail-yh0-f46.google.com [209.85.213.46]) by ietfa.amsl.com (Postfix) with ESMTP id B854B1A0031 for <dnsop@ietf.org>; Fri, 14 Feb 2014 19:03:33 -0800 (PST)
Received: by mail-yh0-f46.google.com with SMTP id v1so12469466yhn.33 for <dnsop@ietf.org>; Fri, 14 Feb 2014 19:03:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=n/IWQo+9HbsfbpaqwNwACT1D8tHmK8q7CGrSMAmO7ew=; b=Cg/HnVh1iotMUNbU2sWWWAdp2FUYAkrgk0XO8cHHolzlCp4L4nL6qG0FVeC50henDf c7LKHG1dCjEXKmOlMfHaL3ubha6Oe3Y4sOt04s17eUGK5+91z9xp0WXhtzdWSkLZQElx KSQvWYxRsmwkBOyrsLcgvkLDrUkh2ty08Sb4P4hX/kgxqADO6dB4/UXRHxEm0dTTDqnf jKhsHnGZ0u6dnBZe/1nw0AXiWOJFcuwavEYxKKgprouElgCX+6DjqS8KeP5sPiFKRSA6 Gq7OduUN9qRZoDiMQJo1Bos1T6KHbgn4I+OaVL+KV/ZxzroWKSGi0mDVLyFIed9aWggr 9wiA==
X-Gm-Message-State: ALoCoQk4kemxyL6XTLKzLClWDnxh2nBVVCBwdDIQO6tmsNzm/G0uk+yvoIBLmoOfc20IR31a1UHm
MIME-Version: 1.0
X-Received: by 10.236.129.36 with SMTP id g24mr770176yhi.103.1392433411385; Fri, 14 Feb 2014 19:03:31 -0800 (PST)
Received: by 10.170.155.70 with HTTP; Fri, 14 Feb 2014 19:03:31 -0800 (PST)
Date: Fri, 14 Feb 2014 19:03:31 -0800
Message-ID: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com>
From: Zi Hu <zihu@usc.edu>
To: dnsop@ietf.org, perpass@ietf.org
Content-Type: multipart/alternative; boundary=20cf300e5761dc2b7604f2692a74
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/vY-34K9BimUwcaGfd1GzVA2Fhiw
Subject: [DNSOP] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 03:03:35 -0000

--20cf300e5761dc2b7604f2692a74
Content-Type: text/plain; charset=ISO-8859-1

We recently posted draft-hzhwm-start-tls-for-dns-00 ("Starting TLS over
DNS") to explore one proposal to add standard TLS over standard DNS to
improve privacy.
http://tools.ietf.org/html/draft-hzhwm-start-tls-for-dns-00

This topic may be of interest to DNSOP and PERPASS.  Some of the authors
will be at the London IETF and can discuss it at the DNS privacy BOF if
there is interest.

An obvious concern about combining DNS and TLS is the performance
implications, both for client latency and server state.  The above i-d
focuses only on the protocol parts, but we have a separate technical
report at ftp://ftp.isi.edu/isi-pubs/tr-688.pdf that evaluates these
questions.

We would love feedback on either document.

thanks
-Zi Hu

--20cf300e5761dc2b7604f2692a74
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:12.7=
27272033691406px">We recently posted draft-hzhwm-start-tls-for-dns-</span><=
span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">=
00 (&quot;Starting TLS over</span><br style=3D"font-family:arial,sans-serif=
;font-size:12.727272033691406px">
<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>DNS&quot;) to explore one proposal to add standard TLS over standard DNS t=
o</span><br style=3D"font-family:arial,sans-serif;font-size:12.727272033691=
406px">
<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>improve privacy.</span><div style=3D"font-family:arial,sans-serif;font-siz=
e:12.727272033691406px"><a href=3D"http://tools.ietf.org/html/draft-hzhwm-s=
tart-tls-for-dns-00" target=3D"_blank">http://tools.ietf.org/html/draft-hzh=
wm-start-tls-for-dns-00</a><div>
<br>This topic may be of interest to DNSOP and PERPASS. =A0Some of the auth=
ors<br>will be at the London IETF and can discuss it at the DNS privacy BOF=
 if<br>there is interest.<br><br>An obvious concern about combining DNS and=
 TLS is the performance<br>
implications, both for client latency and server state. =A0The above i-d<br=
>focuses only on the protocol parts, but we have a separate technical<br>re=
port at=A0<a href=3D"ftp://ftp.isi.edu/isi-pubs/tr-688.pdf" target=3D"_blan=
k">ftp://ftp.isi.edu/isi-pubs/tr-688.pdf</a>=A0that evaluates these<br>
questions.<br><br>We would love feedback on either document.<br><br>thanks<=
/div><div>-Zi Hu</div></div></div>

--20cf300e5761dc2b7604f2692a74--


From nobody Fri Feb 14 20:58:40 2014
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32FFE1A0010; Fri, 14 Feb 2014 20:58:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQo71zImlT7W; Fri, 14 Feb 2014 20:58:37 -0800 (PST)
Received: from ss.vix.su (ss.vix.su [IPv6:2001:559:8000:cb::2]) by ietfa.amsl.com (Postfix) with ESMTP id 628301A0021; Fri, 14 Feb 2014 20:58:37 -0800 (PST)
Received: from [IPv6:2001:559:8000:cb:4c62:fe7c:58aa:4607] (unknown [IPv6:2001:559:8000:cb:4c62:fe7c:58aa:4607]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ss.vix.su (Postfix) with ESMTPSA id 74FC2EBDCE; Sat, 15 Feb 2014 04:58:35 +0000 (UTC) (envelope-from paul@redbarn.org)
Message-ID: <52FEF407.30405@redbarn.org>
Date: Fri, 14 Feb 2014 20:58:47 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.9 (Windows/20140128)
MIME-Version: 1.0
To: Zi Hu <zihu@usc.edu>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com>
In-Reply-To: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/alternative; boundary="------------040200040506040505050406"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/DhUgRNmqRQ8PcB-WdIcvfqKLmwA
Cc: dnsop@ietf.org, perpass@ietf.org
Subject: Re: [DNSOP] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 04:58:39 -0000

This is a multi-part message in MIME format.
--------------040200040506040505050406
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit



Zi Hu wrote:
> We recently posted draft-hzhwm-start-tls-for-dns-00 ("Starting TLS over
> DNS") to explore one proposal to add standard TLS over standard DNS to
> improve privacy.
> http://tools.ietf.org/html/draft-hzhwm-start-tls-for-dns-00
>
> This topic may be of interest to DNSOP and PERPASS.  Some of the authors
> will be at the London IETF and can discuss it at the DNS privacy BOF if
> there is interest.
> ...

this is good work. i recommend it be adopted by the working group, and i
will act as a reviewer.

vixie

--------------040200040506040505050406
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body style="font-family: tt; font-size: 11pt;" bgcolor="#FFFFFF"
 text="#000000"><div style="font-size: 11pt;font-family: tt;"><br><br>Zi
 Hu wrote:<blockquote 
cite="mid:CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com"
 type="cite"><div dir="ltr"><span 
style="font-family:arial,sans-serif;font-size:12.727272033691406px">We 
recently posted draft-hzhwm-start-tls-for-dns-</span><span 
style="font-family:arial,sans-serif;font-size:12.727272033691406px">00 
("Starting TLS over</span><br 
style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span 
style="font-family:arial,sans-serif;font-size:12.727272033691406px">DNS")
 to explore one proposal to add standard TLS over standard DNS to</span><br
 style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span 
style="font-family:arial,sans-serif;font-size:12.727272033691406px">improve
 privacy.</span><div style="font-family: arial,sans-serif; font-size: 
12.7273px;"><a moz-do-not-send="true" 
href="http://tools.ietf.org/html/draft-hzhwm-start-tls-for-dns-00" 
target="_blank">http://tools.ietf.org/html/draft-hzhwm-start-tls-for-dns-00</a><div>
<br>This topic may be of interest to DNSOP and PERPASS. &nbsp;Some of the 
authors<br>will be at the London IETF and can discuss it at the DNS 
privacy BOF if<br>there is interest.<br><span style="font-family: 
monospace;">...</span></div></div></div></blockquote><br>this is good 
work. i recommend it be adopted by the working group, and i will act as a
 reviewer.<br><br>vixie<br></div></body></html>

--------------040200040506040505050406--


From nobody Sat Feb 15 06:03:17 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A93C1A0234; Sat, 15 Feb 2014 06:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y4ZjrfUrGG1j; Sat, 15 Feb 2014 06:03:10 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) by ietfa.amsl.com (Postfix) with ESMTP id 0A6151A023A; Sat, 15 Feb 2014 06:03:09 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 3C8A63B459; Sat, 15 Feb 2014 14:03:06 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 2441F1907BD; Sat, 15 Feb 2014 15:01:33 +0100 (CET)
Date: Sat, 15 Feb 2014 15:01:33 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Paul Vixie <paul@redbarn.org>
Message-ID: <20140215140133.GA6990@sources.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52FEF407.30405@redbarn.org>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 7.3
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/3R_oSRRy31XuumOekOI7Uy98BLY
Cc: dnsop@ietf.org, perpass@ietf.org, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 14:03:12 -0000

On Fri, Feb 14, 2014 at 08:58:47PM -0800,
 Paul Vixie <paul@redbarn.org> wrote 
 a message of 76 lines which said:

> this is good work.

I fully agree. But do note we did not discuss yet the alternatives
(draft-wijngaards-dnsop-confidentialdns, DNScrypt or simply
IPsec). The BoF "DNS encryption" in London seems a good start 
<http://trac.tools.ietf.org/bof/trac/wiki/WikiStart> and 
<https://datatracker.ietf.org/wg/dnse/charter/>.

> i recommend it be adopted by the working group, 

DNSOP? Some people say it is outside the charter since it is a
modification of the protocol. I myself are not favorable to an
ultra-strict interpretation of the charter so I'll hummmmmm with you.


From nobody Sat Feb 15 06:42:23 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 217B61A0241 for <dnsop@ietfa.amsl.com>; Sat, 15 Feb 2014 06:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.427
X-Spam-Level: 
X-Spam-Status: No, score=-1.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RP_MATCHES_RCVD=-0.548] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUBQuAuEbTz3 for <dnsop@ietfa.amsl.com>; Sat, 15 Feb 2014 06:42:20 -0800 (PST)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id CC5441A0234 for <dnsop@ietf.org>; Sat, 15 Feb 2014 06:42:19 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:46980) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1WEgRd-0001Mc-7V (Exim 4.82_3-c0e5623) for dnsop@ietf.org (return-path <fanf2@hermes.cam.ac.uk>); Sat, 15 Feb 2014 14:42:17 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WEgRd-00069O-95 (Exim 4.72) for dnsop@ietf.org (return-path <fanf2@hermes.cam.ac.uk>); Sat, 15 Feb 2014 14:42:17 +0000
Date: Sat, 15 Feb 2014 14:42:17 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
cc: dnsop@ietf.org
In-Reply-To: <20140214233234.9823.63120.idtracker@ietfa.amsl.com>
Message-ID: <alpine.LSU.2.00.1402151407020.15381@hermes-1.csi.cam.ac.uk>
References: <20140214233234.9823.63120.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tfmE1vhSG48PNip-sfNn513rptE
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-resolver-priming-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 14:42:22 -0000

This is a worthwhile clarification and update to the original specs.

Some questions and comments:

2.1.  Parameters of a Priming Query

   A priming query SHOULD use a QNAME of "." and a QTYPE of NS.  The
   priming query MUST be sent over UDP (section 6.1.3.2 of [RFC1123]).

Is this supposed to forbid fallback to TCP? That seems wrong to me.
Fallback to TCP isn't expected in practice, but it seems wasteful to
require extra logic in the resolver to suppress it in this special case.

   The resolver SHOULD also use EDNS0 [RFC6891] and SHOULD announce and
   handle a reassembly size of at least 1024 octets [RFC3226].

Again I think priming queries should use the resolver's normal EDNS buffer
size. It ought to be OK for a resolver on a network with a small MTU and
broken fragment support to advertise a small buffer.

2.2.  Repeating Priming Queries

   A resolver SHOULD NOT originate a priming query more often than once
   per day (or whenever the resolver starts).  It SHOULD adhere to the
   TTL values given in the priming response.

Why the special once per day requirement? Shouldn't this be entirely
driven by the NS RRset TTL?

3.3.  Completeness of the Response

   For an EDNS response, a resolver SHOULD consider the address
   information found in the additional section complete for any
   particular server that appears at all.

   If the resolver did not announce a reassembly size larger than 512
   octets, this assumption is invalid.

This extra SHOULD seems to over-simplify the normal DNS reply processing
rules, which I suppose is what the following paragraph is about. I think
it would be better to describe what is expected to happen non-normatively
rather than imposing new rules.

   [[Issue 2: Do the TTLs for the root NS RRSet and address RRSets in
   the root and the ROOT-SERVERS.NET. zones need to be aligned?  In real
   life responses, the address RRSet's TTL values vary by name server
   implementation.  Is this diversity we can live with?  Should the
   authoritative source prevail?  Is it therefore a protocol issue
   rather than an operational choice of parameters?]]

Oh that's a bit weird and interesting :-)

Looks like some servers fill the additional section with the glue RRs from
the root zone (TTL 6 days) and some with the authoritative RRs from the
root-servers.net zone (TTL 1000 hours).

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.


From nobody Sat Feb 15 07:40:55 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA93B1A0087; Sat, 15 Feb 2014 07:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhQNv8AD6D8v; Sat, 15 Feb 2014 07:40:51 -0800 (PST)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id B87AF1A0040; Sat, 15 Feb 2014 07:40:50 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:45868) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1WEhMG-0004k3-0e (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Sat, 15 Feb 2014 15:40:48 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WEhMG-0000Gp-4U (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Sat, 15 Feb 2014 15:40:48 +0000
Date: Sat, 15 Feb 2014 15:40:48 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Zi Hu <zihu@usc.edu>
In-Reply-To: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com>
Message-ID: <alpine.LSU.2.00.1402151448290.15381@hermes-1.csi.cam.ac.uk>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/-xnJ73pAzE5d-ZTgw8-qZHZJrjc
Cc: dnsop@ietf.org, perpass@ietf.org
Subject: Re: [DNSOP] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 15:40:54 -0000

Zi Hu <zihu@usc.edu> wrote:

> We recently posted draft-hzhwm-start-tls-for-dns-00 ("Starting TLS over
> DNS") to explore one proposal to add standard TLS over standard DNS to
> improve privacy.

I like this. The general approach of the extension looks sensible to me.

Some comments:

   This document defines only the protocol extensions necessary to
   support TLS negotiation.  It does not describe how DNS clients might
   validate server certificates or specify trusted certificate
   authorities.  Solutions for certificate authentication are outside
   the scope of this document.

This absolutely needs to be defined before the protocol is deployed and I
think it is a huge mistake to rule it out of scope.

SMTP made this mistake (RFC 3207) and as a result most certificates
offered by SMTP servers cannot be validated, and SMTP over TLS is
vulnerable to MITM attacks. Fixing this is a huge headache. I don't
want to see it happen again.

But solving this problem is really hard especially in this context :-(

A DANE-like approach might work for authoritative servers.

Dunno about stub <-> recursive connections...

2.1.2.  Receiving Responses

   A DNS client that receives a response using UDP transport that has
   the TO bit set MUST handle that response as usual.  It MAY record the
   server's support for DNS-over-TLS and use that information as part of
   its server selection algorithm in the case where multiple servers are
   available to service a particular query.  [For discussion: UDP is
   subject to spoofing and a client which depends on TO=1 in a UDP
   response may be tricked into never upgrading to TLS.]

This is also true for DNS over TCP. It would be nice to have some stronger
protection against downgrade attacks. Point 3 in the security
considerations needs more thought.

   A DNS client that receives a response to its initial query using TCP
   transport that has the TO bit clear MUST not initiate a TLS handshake
   and SHOULD utilize the existing TCP connection for subsequent
   queries.

I think in this situation it would be better for the client to go back to
using UDP. Existing DNS servers do not handle TCP queries concurrently, so
the client will suffer much worse performance by continuing to use TCP.

2.4.  Middleboxes

   2.  The DNS client sends a TO=1 query and receives a TO=1 response,
       but the TLS handshake fails because the server's certificate
       cannot be authenticated.  In this case the client SHOULD close
       the established connection and fall back to unencrypted DNS for a
       reasonable period (as discussed in Section 2.1.2).

Having said that certificate validation is really important, I still think
that unauthenticated encryption is strictly better than nothing, since it
defeats passive (but not active) eavesdropping. But this kind of soft
failure is a great way to introduce downgrade attacks.

3.  Performance Considerations

This section should require servers to handle DNS queries over TCP and TLS
concurrently. They should be prepared to send responses as soon as they
are available, and out of order when necessary, to avoid head-of-line
blocking. This minimises the performance penalty relative to UDP.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.


From nobody Sat Feb 15 08:53:15 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917B01A017C; Sat, 15 Feb 2014 08:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDbinCx1Faht; Sat, 15 Feb 2014 08:53:10 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by ietfa.amsl.com (Postfix) with ESMTP id ACD901A017A; Sat, 15 Feb 2014 08:53:10 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 5B2C63B459; Sat, 15 Feb 2014 16:53:06 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 89C4A190662; Sat, 15 Feb 2014 17:52:56 +0100 (CET)
Date: Sat, 15 Feb 2014 17:52:56 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tony Finch <dot@dotat.at>
Message-ID: <20140215165256.GA21498@sources.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <alpine.LSU.2.00.1402151448290.15381@hermes-1.csi.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LSU.2.00.1402151448290.15381@hermes-1.csi.cam.ac.uk>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 7.3
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/rZZ8HOxOP0hqdyu3kBEf7EUm7fk
Cc: dnsop@ietf.org, perpass@ietf.org, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 16:53:12 -0000

On Sat, Feb 15, 2014 at 03:40:48PM +0000,
 Tony Finch <dot@dotat.at> wrote 
 a message of 84 lines which said:

> A DANE-like approach might work for authoritative servers.

It is mentioned in the draft but it raises an interesting
chicken-and-egg problem when you want to secure DNS with info found in
the DNS.


From nobody Sat Feb 15 08:58:11 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E41D11A01B0; Sat, 15 Feb 2014 08:58:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEizYphaUS81; Sat, 15 Feb 2014 08:58:08 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by ietfa.amsl.com (Postfix) with ESMTP id 826F71A017C; Sat, 15 Feb 2014 08:58:08 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 576513B459; Sat, 15 Feb 2014 16:58:05 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 577C6190662; Sat, 15 Feb 2014 17:57:18 +0100 (CET)
Date: Sat, 15 Feb 2014 17:57:18 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Watson Ladd <watsonbladd@gmail.com>
Message-ID: <20140215165718.GA21660@sources.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 7.3
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/8d8KeVLKIbnzb3kr1X0fk80Hb2M
Cc: Paul Vixie <paul@redbarn.org>, dnsop@ietf.org, perpass@ietf.org, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] [perpass] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 16:58:10 -0000

On Sat, Feb 15, 2014 at 08:44:27AM -0800,
 Watson Ladd <watsonbladd@gmail.com> wrote 
 a message of 25 lines which said:

> Fourthly, there is substantial operational knowledge and deployed,
> working, code implementing DNSCurve.

While you raise some interesting points, this specific one pushes me
to ask you a list of domain names secured by DNScurve (DNScrypt is a
bit different).

In exchange, I can produce a list of Web sites secured with TLS.


From nobody Sat Feb 15 09:24:06 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8959B1A01C8; Sat, 15 Feb 2014 09:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h57VQJrmZWeD; Sat, 15 Feb 2014 09:24:00 -0800 (PST)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 655901A00EF; Sat, 15 Feb 2014 09:24:00 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:49691) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1WEiy5-0000G7-7B (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Sat, 15 Feb 2014 17:23:57 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WEiy5-0006Xt-5Z (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Sat, 15 Feb 2014 17:23:57 +0000
Date: Sat, 15 Feb 2014 17:23:57 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20140215165256.GA21498@sources.org>
Message-ID: <alpine.LSU.2.00.1402151714050.15381@hermes-1.csi.cam.ac.uk>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <alpine.LSU.2.00.1402151448290.15381@hermes-1.csi.cam.ac.uk> <20140215165256.GA21498@sources.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/4ZjvQRAZi8wpEliyYh2UtGdlJV4
Cc: dnsop@ietf.org, perpass@ietf.org, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 17:24:02 -0000

Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

> On Sat, Feb 15, 2014 at 03:40:48PM +0000,
>  Tony Finch <dot@dotat.at> wrote
>  a message of 84 lines which said:
>
> > A DANE-like approach might work for authoritative servers.
>
> It is mentioned in the draft but it raises an interesting
> chicken-and-egg problem when you want to secure DNS with info found in
> the DNS.

Very interesting :-)

The resolver needs to find out that an auth server supports TLS before it
sends a query. This implies that the information needs to be part of the
referral. It would be wrong to shoe-horn it into the DS RRset (e.g. by
adding semantics to one of the algorithm fields) since DS records relate
to the zone not to the name servers. So it should go into the NS RRset -
but referral NS records aren't signed!

Maybe the resolver could go and ask elsewhere. This could be quite
plausible for out-of-zone name servers, but it does not help for in-zone
server names. Or use the reverse DNS?

No palatable options that I can see :-/

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Malin, Hebrides, Bailey: Northwest 7 to severe gale 9 decreasing 4 or 5,
occasionally variable 3 later. Very rough or high, becoming rough later.
Showers, squally at first. Moderate or poor becoming good.


From nobody Sat Feb 15 10:08:25 2014
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE94E1A025A; Sat, 15 Feb 2014 10:08:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNuEopCK_-tS; Sat, 15 Feb 2014 10:08:20 -0800 (PST)
Received: from ss.vix.su (ss.vix.su [24.104.150.2]) by ietfa.amsl.com (Postfix) with ESMTP id B21A91A0259; Sat, 15 Feb 2014 10:08:20 -0800 (PST)
Received: from [IPv6:2001:559:8000:cb:8089:a9c6:4d5:bd6c] (unknown [IPv6:2001:559:8000:cb:8089:a9c6:4d5:bd6c]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ss.vix.su (Postfix) with ESMTPSA id BCA1AEBDB9; Sat, 15 Feb 2014 18:08:17 +0000 (UTC) (envelope-from paul@redbarn.org)
Message-ID: <52FFAD1E.1040509@redbarn.org>
Date: Sat, 15 Feb 2014 10:08:30 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.9 (Windows/20140128)
MIME-Version: 1.0
To: Watson Ladd <watsonbladd@gmail.com>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com>
In-Reply-To: <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/c5xwt7xIPMyTo4EJSCzxZ0rAIxQ
Cc: dnsop@ietf.org, perpass@ietf.org, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] [perpass] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 18:08:23 -0000

Watson Ladd wrote:
> Dear all,
> This proposal has multiple shortcomings compared to DNSCurve.
>
> First off, it says that the rationale for TLS over DNSCurve is simply
> to "take advantage of TLS". I would respectfully submit that DJB can
> do a better job than the TLS committee, and did. Merely adding bolts
> and nuts onto a design is not improving it.

has mr. bernstein's Curve25519 (see
http://en.wikipedia.org/wiki/Curve25519) been explicitly validated by
other crypto experts? last i knew he was the only one claiming it was
correct and strong enough for production use. this matters, because no
one person ought to be trusted to get something like this right sans
review. mr. bernstein's competence isn't being questioned, it's just the
"second set of eyes" requirement for technology at scale. i'm speaking
as an x.509-hater, which means, i tend to agree with what you said about
committees.

as a bolter-onner of many of dns's nuts including EDNS, i'm ready to
quibble with anyone who says DNS has not been improved by the post-1987
work that's been done to it. i won't claim it's gotten prettier, but
that's not the only metric for "improvement".

> Secondly, this proposal only works on TCP. This imposes latency and
> state requirements that most people would rather avoid. The use of
> keepalive only addresses computational burden, not state burden, and
> with the DH speed records we have today unnecessary.

my understanding is that this is a hop-by-hop cover protocol for adding
confidentiality when needed, and that something like dnssec will still
be needed for end-to-end content authenticity. in that sense the tcp
requirement isn't itself burdensome, though i will certainly recommend a
block-cipher mode so that udp can also be supported. this is not
something we can fix with DTLS or SCTP because of the all-pervasive
"middlebox problem". even getting EDNS options through has proved
difficult, a completely new transport is unthinkable.

> Thirdly, this proposal ignores entirely how to validate the server
> over the TLS connection. Does it need a certificate? Who should be
> allowed to sign it? How should it be validated? DNSSEC provides a PKI,
> and this proposal provides another one. Their interactions will not be
> fun.

see above; i don't think this proposal offers or intends to offer a PKI,
merely a hop-by-hop confidentiality option. DNSSEC will still be required.

> Fourthly, there is substantial operational knowledge and deployed,
> working, code implementing DNSCurve. This does not hold for this
> proposal.

dnscurve was offered to the ietf community but it didn't stick for
reasons unrelated to this newer proposal. i don't see any sense in
comparing their installed bases.

> Sincerely,
> Watson Ladd

warmly,

vixie


From nobody Sat Feb 15 11:58:10 2014
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6C31A0306; Sat, 15 Feb 2014 11:58:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i8fW6AWf0jNz; Sat, 15 Feb 2014 11:58:04 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 69E1B1A0303; Sat, 15 Feb 2014 11:58:03 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id B3610800AA; Sat, 15 Feb 2014 14:57:59 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1392494279; bh=9mh2ZIZlShm8q0flcPX5viluoyb+uQ+lUmdJwUPgh38=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=ZDBTOqjfnDiaxP5yPt7SYd7kZo+bt9BIPTseBi7BD++Xhd8xc4xIYjoasivChPj2q R5aKS69Oj5kRyRD60l6PvnyW+XetZNaHwZEcy4RpVgQDVE//UuN7eWINAbEsx5QnNy SsauxGfThAWla0c3IrotnMgCSj+WgjvpbX7CwtfY=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s1FJvwd3021513; Sat, 15 Feb 2014 14:57:59 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Sat, 15 Feb 2014 14:57:58 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20140215140133.GA6990@sources.org>
Message-ID: <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/z0dIP-wrshjvrzrgafuN5BSvBz4
Cc: dnsop@ietf.org, Paul Vixie <paul@redbarn.org>, perpass@ietf.org, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 19:58:08 -0000

On Sat, 15 Feb 2014, Stephane Bortzmeyer wrote:


(D)TLS for DNS makes a lot of sense to me.

> I fully agree. But do note we did not discuss yet the alternatives
> (draft-wijngaards-dnsop-confidentialdns, DNScrypt or simply
> IPsec). The BoF "DNS encryption" in London seems a good start

"simply IPsec"? bootstrapping DNS from IPsec which relies on DNS is not
trivial (and the versign proposal seems to only deal with nameservers
with access to their reverse dns, which excludes the DNS servers that
really need the protection, those supplied by DHCP in coffeeshops,
and completely lacks understanding of IPsec realities such as NAT-T)

> <http://trac.tools.ietf.org/bof/trac/wiki/WikiStart> and
> <https://datatracker.ietf.org/wg/dnse/charter/>.
>
>> i recommend it be adopted by the working group,
>
> DNSOP? Some people say it is outside the charter since it is a
> modification of the protocol. I myself are not favorable to an
> ultra-strict interpretation of the charter so I'll hummmmmm with you.

At ietf87 it was planned to  have a discussion at dnsop about this
continued problem of drafts that fall between operations and extensions
and the fact that dnsext closed down. Nothing happened at ietf87 or
ietf88. I hope to see this as agenda item for dnsop this meeting.

We need a WG to discuss DNS innovation.

Paul


From nobody Sat Feb 15 12:16:49 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D70B1A0297; Sat, 15 Feb 2014 12:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wUjT6Jo9nsy; Sat, 15 Feb 2014 12:16:42 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id DF6F01A028A; Sat, 15 Feb 2014 12:16:41 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 9B00323E24C2; Sat, 15 Feb 2014 20:16:38 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKnf0uqF-dNm; Sat, 15 Feb 2014 21:16:37 +0100 (CET)
Received: from kopoli (g226188167.adsl.alicedsl.de [92.226.188.167]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 4F1AB23E24BC; Sat, 15 Feb 2014 21:16:37 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <dnsext@ietf.org>, <DNSOP@ietf.org>
Date: Sat, 15 Feb 2014 21:16:35 +0100
Message-ID: <001601cf2a8a$d39b7db0$7ad27910$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8qitKEr99V05bSR9Kkz6v/ha91lQ==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/r3KcEMslSLm6vxjZFGhR-HhqDSc
Subject: Re: [DNSOP] [dnsext] draft-rafiee-intarea-cga-tsig-07 -
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 20:16:47 -0000

Follow up,
I forgot to mention that, this document also provide a possible solution for
DNS data confidentiality (for IPv6 enabled networks) to protect users'
privacy in a very simple step. It does not need TLS for doing this like
other draft in the mailing list.
Please take a look and comment on it.
Hosnieh


> 
> A new version of I-D, draft-rafiee-intarea-cga-tsig-07.txt
> has been successfully submitted by Hosnieh Rafiee and posted to the IETF
> repository.
> 
> Name:		draft-rafiee-intarea-cga-tsig
> Revision:	07
> Title:		Secure DNS Authentication using CGA/SSAS Algorithm
in IPv6
> Document date:	2014-02-15
> Group:		Individual Submission
> Pages:		26
> URL:
> http://www.ietf.org/internet-drafts/draft-rafiee-intarea-cga-tsig-07.txt
> Status:
> https://datatracker.ietf.org/doc/draft-rafiee-intarea-cga-tsig/
> Htmlized:
http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-07
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-rafiee-intarea-cga-tsig-07
> 
> Abstract:
>    This document describes a new mechanism that can be used to reduce
>    the need for human intervention during DNS authentication and secure
>    DNS authentication in various scenarios such as the DNS
>    authentication of resolvers to stub resolvers, authentication during
>    zone transfers, authentication of root DNS servers to recursive DNS
>    servers, and authentication during the FQDN (RFC 4703) update.
> 
>    Especially in the last scenario, i.e., FQDN, if the node uses the
>    Neighbor Discovery Protocol (NDP) (RFC 4861, RFC 4862), unlike the
>    Dynamic Host Configuration Protocol (DHCP) (RFC 3315), the node has
>    no way of updating his FQDN records on the DNS and has no means for a
>    secure authentication with the DNS server. While this is a major
>    problem in NDP-enabled networks, this is a minor problem in DHCPv6.
>    This is because the DHCP server updates the FQDN records on behalf of
>    the nodes on the network. This document also introduces a possible
>    algorithm for DNS data confidentiality.
> 
> 
> 


From nobody Sat Feb 15 18:05:10 2014
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF9B31A0333 for <dnsop@ietfa.amsl.com>; Sat, 15 Feb 2014 18:05:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Rs3lOVHG-Ds for <dnsop@ietfa.amsl.com>; Sat, 15 Feb 2014 18:05:04 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 039C21A0332 for <dnsop@ietf.org>; Sat, 15 Feb 2014 18:05:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 84D1B84CEE; Sat, 15 Feb 2014 21:05:01 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 76887-08; Sat, 15 Feb 2014 21:05:01 -0500 (EST)
Received: from [10.0.1.3] (c-67-169-100-133.hsd1.ca.comcast.net [67.169.100.133]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 7B4C184B43; Sat, 15 Feb 2014 21:05:00 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_766A2852-A689-438E-8E69-48965AC7D457"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca>
Date: Sat, 15 Feb 2014 18:04:54 -0800
Message-Id: <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tN8RnuZXPhgtSuv7_TYx67hEEm8
Cc: dnsop <dnsop@ietf.org>
Subject: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 02:05:07 -0000

--Apple-Mail=_766A2852-A689-438E-8E69-48965AC7D457
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

[perpass dropped from ccs]

On Feb 15, 2014, at 11:57 AM, Paul Wouters <paul@nohats.ca> wrote:
> At ietf87 it was planned to  have a discussion at dnsop about this
> continued problem of drafts that fall between operations and =
extensions
> and the fact that dnsext closed down. Nothing happened at ietf87 or
> ietf88. I hope to see this as agenda item for dnsop this meeting.
>=20
> We need a WG to discuss DNS innovation.

At the Vancouver DNSOP meeting when there was some discussion I thought =
was protocol development related, I got up to the mike asked if DNSOP =
was the right place for that discussion, being righteously indignant =
that DNSOP would discuss something non-operational.  However, after =
sitting down someone pointed out to me that one of the common recurrent =
complaints about the IETF is that operators tend to get excluded and =
that maybe DNSOP is actually the best place to discuss DNS protocol =
development since that's where operators go. =20

Perhaps DNSOP actually is the DNS innovation WG (if perhaps only as a =
seeding ground)?

Regards,
-drc


--Apple-Mail=_766A2852-A689-438E-8E69-48965AC7D457
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTABzHAAoJENV6ebf0/4rX9PEH/RVwuAoMGpI0bhRvEF5Pltk/
hpb8oSmky5DhO8isM2JM+peIa5SmC/U71u5ELbMMRsqhwQEdMAXBPxYLy4HIdQwb
1SVFg8PpdeRiXxO47nvMgNJWw1LUxR9nWhb9mM4oaiyERzNZVqMiD0au09IMfsjh
Awly6zG22nbcJGYOvDvIyOwZBSWCz888puLcu1bDV66FmdPndLUd3yCBfgn0NQ47
/U3CWZ3ZtT99TNL1acbIcDJoD16BW0bFDBrJX42xcluFkjZNMAS5W94OJlP4Uv4E
3tYgeh5IZ6IIFxeVH02o/ydkxqNPUL+KTdnlhBkTVi8GKCx+D2dJ8Ywg1hXOfno=
=981x
-----END PGP SIGNATURE-----

--Apple-Mail=_766A2852-A689-438E-8E69-48965AC7D457--


From nobody Sat Feb 15 23:15:40 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D5D1A008E for <dnsop@ietfa.amsl.com>; Sat, 15 Feb 2014 23:15:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vO9mvzP5rAwo for <dnsop@ietfa.amsl.com>; Sat, 15 Feb 2014 23:15:37 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 22C121A0065 for <dnsop@ietf.org>; Sat, 15 Feb 2014 23:15:37 -0800 (PST)
Received: from ix-2.local (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 3856D20217; Sun, 16 Feb 2014 08:15:34 +0100 (CET)
Message-ID: <53006595.5010207@frobbit.se>
Date: Sun, 16 Feb 2014 08:15:33 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>, Paul Wouters <paul@nohats.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org>
In-Reply-To: <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uf4WoIDt5f7o7lLIQD81xfgmLQcltnuWf"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/ACva_BRqKz6qdl_FhIIiL3dHN-s
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 07:15:38 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--uf4WoIDt5f7o7lLIQD81xfgmLQcltnuWf
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-16 03:04, David Conrad wrote:
> Perhaps DNSOP actually is the DNS innovation WG (if perhaps only as a s=
eeding ground)?

The largest problem for IETF and DNS innovation is that the consensus in
IETF seems to be that innovation of DNS is not possible unless it
involves reuse of the TXT resource record.

Unless that is put to rest, we can not do much at all.

   Patrik



--uf4WoIDt5f7o7lLIQD81xfgmLQcltnuWf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTAGWWrMabGguI180RAoexAJsFrHsWGpOHjNwNf0s3Qm9bzk411wCdGsV/
vzLb/xPfQKSs6hmycPo8HSk=
=wg9I
-----END PGP SIGNATURE-----

--uf4WoIDt5f7o7lLIQD81xfgmLQcltnuWf--


From nobody Sun Feb 16 03:41:45 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D520E1A03D6; Sun, 16 Feb 2014 03:41:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXSSh-n4bvzT; Sun, 16 Feb 2014 03:41:34 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id BFCC01A03D5; Sun, 16 Feb 2014 03:41:33 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 4773B23E2D48; Sun, 16 Feb 2014 11:41:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KIhpjMQ7utCt; Sun, 16 Feb 2014 12:41:28 +0100 (CET)
Received: from kopoli (g225015008.adsl.alicedsl.de [92.225.15.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 1CB5823E2B25; Sun, 16 Feb 2014 12:41:28 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Marc Buijsman'" <Marc.Buijsman@os3.nl>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl>
In-Reply-To: <53009CFE.9030900@os3.nl>
Date: Sun, 16 Feb 2014 12:41:26 +0100
Message-ID: <003a01cf2b0c$067d2360$13776a20$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQOKWVpFurMI2Qzh8V0RHyHseiUo8gI85gZYly97AHA=
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/48HbJ8JNOTWsefEyrBej0gnKERY
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 11:41:37 -0000

Dear Marc,

Thanks for your comments.

> 
> Regarding the size of the length fields, however, I'm still confused by
what you
> are trying to say. I did not consider the number of bits, I really
considered the
> number of bytes (octets). If I wanted to encode the length in bits (and I
don't),
> I would have set the value to 2048.
> But I'm dividing by 8 and set the value to 256 instead, which is the
length in
> *bytes* as you said yourself. The reason why you divide by 8 a second time
is
> a mystery to me. The outcome would then be the number of groups of 8
> bytes, but I've never seen a length encoding before that counts such
> 'octobytes' (which is not a byte, but 8 bytes). So you are counting 32
> octobytes, while I am counting 256 bytes (as usual).


> Also, I don't understand what you mean to say by "multiple of 8". If the
> encoding would be in bits (and again, it's not) and the data is always a
number
> of whole bytes, then yes the value would be a multiple of 8. But we are
talking
> about an encoding in bytes here, which do not necessarily come in groups
of
> 8 (and is therefore not necessarily a multiple of 8).
> I also don't know what checksum fields you mean or how their length is
> relevant here, but the IPv4 header checksum field and UDP checksum field
in
> a regular DNS packet are two bytes each.

http://tools.ietf.org/html/rfc3971#section-5.1
maybe my wording is not correct. Check the length field here. 8 bits is
really not enough for that. So, If you check the implementation of SeNDs
(Docomo, etc). what they do is they shift the values or easier way is to
divide by 8.

> With regard to the old signature: how would including more fields in the
> digest operation increase the packet size? No matter how many fields you
> digest, the resulting signature is always of the same length. And the
fields I was
> referring to are already part of the packet. In order to be able to
authenticate
> the new public key, you MUST at least include the new public key in the
digest
> operation. Otherwise the packet could be intercepted and the new public
key
> could be replaced without notice.

You're not talking about SHA1 digest, you're talking about digital
signature. It depends on the input data. This is why , for example, in SeND
they included padding at the end that this value can be the multiple of 8.
If this value had a fixed size, they would not include any length to it. In
RFCs they usually include lengths when the length of value is variable and
without length field, one cannot determine the length.
http://tools.ietf.org/html/rfc3971#section-5.2
So, this value is not actually the same size and depends on the plain text
that one wants to sign. 
Secondly, if you check the content of the signature, you will notice that I
included all the DNS message and it is not like before. Because the new
signature is verified before old signature, no replay attack can be happened
since the new signature verification will be failed. So no need to sign a
large data for old signature field and only timestamp or a small value is
enough just to show that this node is the owner of this public key. To avoid
replay attack again, I consider to sign the timestamp.

I hope this answer your questions.


Thanks,
Best,
Hosnieh

> Kind regards,
> 
> Marc Buijsman
> 
> Hosnieh Rafiee schreef op 15-2-2014 0:07:
> > Thanks for the information you've provided, I improved the document
> > according to comments and found out that the report also has a few
> > problems which is due to the fact that it misinterpreted the of CGA-TSIG
> document.
> >
> > Here I explain the problems or the reasons of choices:
> >
> > - CGA-TSIG cannot use MAC as a signature field. The purpose was that
> > to have all the CGA data in one section instead of trying to find them
> > in different sections of TSIG.
> >
> > - sizes of length encoding: It is one byte. It is enough for any key
sizes.
> > If you also check the "checksum" field in the packets, you will find
> > out that it is only 8 bits or one byte. In the emails I explained to
> > you that it is the multiple of 8. In no RFC you can find out that the
> > value is the length of data in bits. It is always the length of data
> > in bytes. But how you showed in your report is that you consider the
> > number of bits and not bytes so you had the following example
> > 2048/8=256 (now you only converted the number of bits to bytes) so you
> > needed to divide it by another 8 that is 256/8=32 and this is the
> > value you set to length. If you even consider the key size 7680, then
> > the length will be only 120.
> > nd
> > - old signature only contains time signed. The reason is to avoid
> > increasing the packet length
> >
> > I appreciate further comments and would like more people review it so
> > that we can go ahead with this document.
> >
> > Thanks,
> > Hosnieh
> >
> >
> >
> > A new version of I-D, draft-rafiee-intarea-cga-tsig-07.txt
> > has been successfully submitted by Hosnieh Rafiee and posted to the
> > IETF repository.
> >
> > Name:		draft-rafiee-intarea-cga-tsig
> > Revision:	07
> > Title:		Secure DNS Authentication using CGA/SSAS Algorithm
in IPv6
> > Document date:	2014-02-15
> > Group:		Individual Submission
> > Pages:		26
> > URL:
> > http://www.ietf.org/internet-drafts/draft-rafiee-intarea-cga-tsig-07.t
> > xt
> > Status:
> > https://datatracker.ietf.org/doc/draft-rafiee-intarea-cga-tsig/
> > Htmlized:
http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-07
> > Diff:
> > http://www.ietf.org/rfcdiff?url2=draft-rafiee-intarea-cga-tsig-07
> >
> > Abstract:
> >    This document describes a new mechanism that can be used to reduce
> >    the need for human intervention during DNS authentication and secure
> >    DNS authentication in various scenarios such as the DNS
> >    authentication of resolvers to stub resolvers, authentication during
> >    zone transfers, authentication of root DNS servers to recursive DNS
> >    servers, and authentication during the FQDN (RFC 4703) update.
> >
> >    Especially in the last scenario, i.e., FQDN, if the node uses the
> >    Neighbor Discovery Protocol (NDP) (RFC 4861, RFC 4862), unlike the
> >    Dynamic Host Configuration Protocol (DHCP) (RFC 3315), the node has
> >    no way of updating his FQDN records on the DNS and has no means for a
> >    secure authentication with the DNS server. While this is a major
> >    problem in NDP-enabled networks, this is a minor problem in DHCPv6.
> >    This is because the DHCP server updates the FQDN records on behalf of
> >    the nodes on the network. This document also introduces a possible
> >    algorithm for DNS data confidentiality.
> >
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: dnsext [mailto:dnsext-bounces@ietf.org] On Behalf Of Marc
> >> Buijsman
> >> Sent: Thursday, January 16, 2014 3:45 PM
> >> To: dnsext@ietf.org
> >> Cc: Jeroen van der Ham
> >> Subject: [dnsext] CGA-TSIG research report
> >>
> >> Dear working group members,
> >>
> >> For my master's thesis I have performed an investigation at NLnet
> >> Labs on CGA-TSIG as a solution to the last mile problem of DNS. The
> >> version of the CGA-TSIG proposal that I reviewed is the current
> >> latest version at
> >> http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-06. During
> >> the
> > course of
> >> my research I have already had some contact with Ms. Rafiee.
> >>
> >> In order to do a verification of the CGA-TSIG proposal I have created
> >> a
> > proof
> >> of concept implementation in NLnet Labs' "ldns" library. Since the
> >> scope
> > of
> >> the project was limited to the last mile problem it only includes the
> >> code required for this purpose, but the implementation could easily
> >> be extended to support other applications (like zone transfers). I
> >> have found that
> > CGA-TSIG
> >> has potential to be an adequate solution to the last mile problem on
> >> IPv6 networks, although some future research is needed with regard to
> >> bootstrapping the authentication.
> >>
> >> As a result, I would hereby like to refer you to my report which can
> >> be
> > found
> >> at http://www.nlnetlabs.nl/downloads/publications/report-rp2-
> buijsman.pdf.
> >> I have outlined my results in section 4.2 which contains suggestions
> >> on
> > how I
> >> believe the CGA-TSIG draft could be clarified and otherwise improved.
> >> I
> > hope
> >> my suggestions will be adopted in the next version of the draft. The
> >> PoC
> > code
> >> can be found in the online Git repository of NLnet Labs at
> >> http://git.nlnetlabs.nl/ldns/?h=cga-tsig.
> >>
> >> I hope my work will be helpful in standardising CGA-TSIG.
> >>
> >> Yours sincerely,
> >>
> >> Marc Buijsman
> >> _______________________________________________
> >> dnsext mailing list
> >> dnsext@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dnsext


From nobody Sun Feb 16 04:10:26 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48F841A03E5; Sun, 16 Feb 2014 04:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zn9NxYdc0V4Y; Sun, 16 Feb 2014 04:10:16 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 480E01A00FF; Sun, 16 Feb 2014 04:10:16 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 2F30E23E2D48; Sun, 16 Feb 2014 12:10:13 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uI2Kq0GiCWjr; Sun, 16 Feb 2014 13:10:11 +0100 (CET)
Received: from kopoli (g225015008.adsl.alicedsl.de [92.225.15.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id C67E923E2B25; Sun, 16 Feb 2014 13:10:10 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Marc Buijsman'" <Marc.Buijsman@os3.nl>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl> <003a01cf2b0c$067d2360$13776a20$@rozanak.com>
In-Reply-To: <003a01cf2b0c$067d2360$13776a20$@rozanak.com>
Date: Sun, 16 Feb 2014 13:10:08 +0100
Message-ID: <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQOKWVpFurMI2Qzh8V0RHyHseiUo8gI85gZYAcBsuHqXIYESAA==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tXzGTKOzT6Sf097u3GTWq2Dn2DQ
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 12:10:20 -0000

Follow up,

I thought again about the possible attacks scenarios. I concluded that I
also need to include the new public key in the content of the old signature.
This means the old signature should be "new public key + timestamp",
otherwise the attacker might have a possibility (a few seconds) to do the
replay attack by copying the old public key and oldsignature.  So, you're
right, it still might cause the attacker to attack. But to avoid increasing
packet size, it is only enough for the two values that is new public key and
timestamp. Since the new public key is verified by both CGA verification
process and also the new signature and the old public key is verified by old
signature.

I will correct this in the next version of the document.

Thanks,
Best,
Hosnieh


> -----Original Message-----
> From: dnsext [mailto:dnsext-bounces@ietf.org] On Behalf Of Hosnieh Rafiee
> Sent: Sunday, February 16, 2014 12:41 PM
> To: 'Marc Buijsman'
> Cc: 'Jeroen van der Ham'; DNSOP@ietf.org; dnsext@ietf.org
> Subject: Re: [dnsext] CGA-TSIG - new version
> 
> Dear Marc,
> 
> Thanks for your comments.
> 
> >
> > Regarding the size of the length fields, however, I'm still confused
> > by
> what you
> > are trying to say. I did not consider the number of bits, I really
> considered the
> > number of bytes (octets). If I wanted to encode the length in bits
> > (and I
> don't),
> > I would have set the value to 2048.
> > But I'm dividing by 8 and set the value to 256 instead, which is the
> length in
> > *bytes* as you said yourself. The reason why you divide by 8 a second
> > time
> is
> > a mystery to me. The outcome would then be the number of groups of 8
> > bytes, but I've never seen a length encoding before that counts such
> > 'octobytes' (which is not a byte, but 8 bytes). So you are counting 32
> > octobytes, while I am counting 256 bytes (as usual).
> 
> 
> > Also, I don't understand what you mean to say by "multiple of 8". If
> > the encoding would be in bits (and again, it's not) and the data is
> > always a
> number
> > of whole bytes, then yes the value would be a multiple of 8. But we
> > are
> talking
> > about an encoding in bytes here, which do not necessarily come in
> > groups
> of
> > 8 (and is therefore not necessarily a multiple of 8).
> > I also don't know what checksum fields you mean or how their length is
> > relevant here, but the IPv4 header checksum field and UDP checksum
> > field
> in
> > a regular DNS packet are two bytes each.
> 
> http://tools.ietf.org/html/rfc3971#section-5.1
> maybe my wording is not correct. Check the length field here. 8 bits is
really
> not enough for that. So, If you check the implementation of SeNDs (Docomo,
> etc). what they do is they shift the values or easier way is to divide by
8.
> 
> > With regard to the old signature: how would including more fields in
> > the digest operation increase the packet size? No matter how many
> > fields you digest, the resulting signature is always of the same
> > length. And the
> fields I was
> > referring to are already part of the packet. In order to be able to
> authenticate
> > the new public key, you MUST at least include the new public key in
> > the
> digest
> > operation. Otherwise the packet could be intercepted and the new
> > public
> key
> > could be replaced without notice.
> 
> You're not talking about SHA1 digest, you're talking about digital
signature. It
> depends on the input data. This is why , for example, in SeND they
included
> padding at the end that this value can be the multiple of 8.
> If this value had a fixed size, they would not include any length to it.
In RFCs
> they usually include lengths when the length of value is variable and
without
> length field, one cannot determine the length.
> http://tools.ietf.org/html/rfc3971#section-5.2
> So, this value is not actually the same size and depends on the plain text
that
> one wants to sign.
> Secondly, if you check the content of the signature, you will notice that
I
> included all the DNS message and it is not like before. Because the new
> signature is verified before old signature, no replay attack can be
happened
> since the new signature verification will be failed. So no need to sign a
large
> data for old signature field and only timestamp or a small value is enough
just
> to show that this node is the owner of this public key. To avoid replay
attack
> again, I consider to sign the timestamp.
> 
> I hope this answer your questions.
> 
> 
> Thanks,
> Best,
> Hosnieh
> 
> > Kind regards,
> >
> > Marc Buijsman
> >
> > Hosnieh Rafiee schreef op 15-2-2014 0:07:
> > > Thanks for the information you've provided, I improved the document
> > > according to comments and found out that the report also has a few
> > > problems which is due to the fact that it misinterpreted the of
> > > CGA-TSIG
> > document.
> > >
> > > Here I explain the problems or the reasons of choices:
> > >
> > > - CGA-TSIG cannot use MAC as a signature field. The purpose was that
> > > to have all the CGA data in one section instead of trying to find
> > > them in different sections of TSIG.
> > >
> > > - sizes of length encoding: It is one byte. It is enough for any key
> sizes.
> > > If you also check the "checksum" field in the packets, you will find
> > > out that it is only 8 bits or one byte. In the emails I explained to
> > > you that it is the multiple of 8. In no RFC you can find out that
> > > the value is the length of data in bits. It is always the length of
> > > data in bytes. But how you showed in your report is that you
> > > consider the number of bits and not bytes so you had the following
> > > example
> > > 2048/8=256 (now you only converted the number of bits to bytes) so
> > > you needed to divide it by another 8 that is 256/8=32 and this is
> > > the value you set to length. If you even consider the key size 7680,
> > > then the length will be only 120.
> > > nd
> > > - old signature only contains time signed. The reason is to avoid
> > > increasing the packet length
> > >
> > > I appreciate further comments and would like more people review it
> > > so that we can go ahead with this document.
> > >
> > > Thanks,
> > > Hosnieh
> > >
> > >
> > >
> > > A new version of I-D, draft-rafiee-intarea-cga-tsig-07.txt
> > > has been successfully submitted by Hosnieh Rafiee and posted to the
> > > IETF repository.
> > >
> > > Name:		draft-rafiee-intarea-cga-tsig
> > > Revision:	07
> > > Title:		Secure DNS Authentication using CGA/SSAS Algorithm
> in IPv6
> > > Document date:	2014-02-15
> > > Group:		Individual Submission
> > > Pages:		26
> > > URL:
> > > http://www.ietf.org/internet-drafts/draft-rafiee-intarea-cga-tsig-07
> > > .t
> > > xt
> > > Status:
> > > https://datatracker.ietf.org/doc/draft-rafiee-intarea-cga-tsig/
> > > Htmlized:
> http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-07
> > > Diff:
> > > http://www.ietf.org/rfcdiff?url2=draft-rafiee-intarea-cga-tsig-07
> > >
> > > Abstract:
> > >    This document describes a new mechanism that can be used to reduce
> > >    the need for human intervention during DNS authentication and
secure
> > >    DNS authentication in various scenarios such as the DNS
> > >    authentication of resolvers to stub resolvers, authentication
during
> > >    zone transfers, authentication of root DNS servers to recursive DNS
> > >    servers, and authentication during the FQDN (RFC 4703) update.
> > >
> > >    Especially in the last scenario, i.e., FQDN, if the node uses the
> > >    Neighbor Discovery Protocol (NDP) (RFC 4861, RFC 4862), unlike the
> > >    Dynamic Host Configuration Protocol (DHCP) (RFC 3315), the node has
> > >    no way of updating his FQDN records on the DNS and has no means for
a
> > >    secure authentication with the DNS server. While this is a major
> > >    problem in NDP-enabled networks, this is a minor problem in DHCPv6.
> > >    This is because the DHCP server updates the FQDN records on behalf
of
> > >    the nodes on the network. This document also introduces a possible
> > >    algorithm for DNS data confidentiality.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> -----Original Message-----
> > >> From: dnsext [mailto:dnsext-bounces@ietf.org] On Behalf Of Marc
> > >> Buijsman
> > >> Sent: Thursday, January 16, 2014 3:45 PM
> > >> To: dnsext@ietf.org
> > >> Cc: Jeroen van der Ham
> > >> Subject: [dnsext] CGA-TSIG research report
> > >>
> > >> Dear working group members,
> > >>
> > >> For my master's thesis I have performed an investigation at NLnet
> > >> Labs on CGA-TSIG as a solution to the last mile problem of DNS. The
> > >> version of the CGA-TSIG proposal that I reviewed is the current
> > >> latest version at
> > >> http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-06. During
> > >> the
> > > course of
> > >> my research I have already had some contact with Ms. Rafiee.
> > >>
> > >> In order to do a verification of the CGA-TSIG proposal I have
> > >> created a
> > > proof
> > >> of concept implementation in NLnet Labs' "ldns" library. Since the
> > >> scope
> > > of
> > >> the project was limited to the last mile problem it only includes
> > >> the code required for this purpose, but the implementation could
> > >> easily be extended to support other applications (like zone
> > >> transfers). I have found that
> > > CGA-TSIG
> > >> has potential to be an adequate solution to the last mile problem
> > >> on
> > >> IPv6 networks, although some future research is needed with regard
> > >> to bootstrapping the authentication.
> > >>
> > >> As a result, I would hereby like to refer you to my report which
> > >> can be
> > > found
> > >> at http://www.nlnetlabs.nl/downloads/publications/report-rp2-
> > buijsman.pdf.
> > >> I have outlined my results in section 4.2 which contains
> > >> suggestions on
> > > how I
> > >> believe the CGA-TSIG draft could be clarified and otherwise improved.
> > >> I
> > > hope
> > >> my suggestions will be adopted in the next version of the draft.
> > >> The PoC
> > > code
> > >> can be found in the online Git repository of NLnet Labs at
> > >> http://git.nlnetlabs.nl/ldns/?h=cga-tsig.
> > >>
> > >> I hope my work will be helpful in standardising CGA-TSIG.
> > >>
> > >> Yours sincerely,
> > >>
> > >> Marc Buijsman
> > >> _______________________________________________
> > >> dnsext mailing list
> > >> dnsext@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/dnsext
> 
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext


From nobody Sun Feb 16 05:46:51 2014
Return-Path: <dhc2@dcrocker.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE7D1A01CE for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 05:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pz022M_bkCv5 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 05:46:48 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 66D9D1A01FD for <dnsop@ietf.org>; Sun, 16 Feb 2014 05:46:48 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1GDkXQk001866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 16 Feb 2014 05:46:36 -0800
Message-ID: <5300C10A.8010308@dcrocker.net>
Date: Sun, 16 Feb 2014 05:45:46 -0800
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, David Conrad <drc@virtualized.org>, Paul Wouters <paul@nohats.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se>
In-Reply-To: <53006595.5010207@frobbit.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 16 Feb 2014 05:46:39 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/jonaE6f0temxxUhLtaA3TK2pYPo
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 13:46:50 -0000

On 2/15/2014 11:15 PM, Patrik Fältström wrote:
> The largest problem for IETF and DNS innovation is that the consensus in
> IETF seems to be that innovation of DNS is not possible unless it
> involves reuse of the TXT resource record.


That assertion is quite wrong on both process and technical grounds

Process:

      There is certainly a long history of very strong resistance from a 
core group of DNS advocates in the IETF; and yes, there is an IAB report 
that doesn't like TXT usage.

      But there is also a long history of other folk adding DNS usage in 
spite of that.

      So a casual claim of "IETF consensus" is simply false.

Technical:

      The use of underscore-based naming variations has provided an 
easy, efficient and safe means of eliminating TXT usage ambiguity.  By 
way of examples, note the SRV record and DKIM, but there are others.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Feb 16 06:03:34 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFD51A03F1 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 06:03:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBjTKIV4YEUS for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 06:03:29 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id CD3CF1A03F0 for <dnsop@ietf.org>; Sun, 16 Feb 2014 06:03:28 -0800 (PST)
Received: from ix-2.local (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 9E8842272A; Sun, 16 Feb 2014 15:03:25 +0100 (CET)
Message-ID: <5300C52A.9050802@frobbit.se>
Date: Sun, 16 Feb 2014 15:03:22 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, David Conrad <drc@virtualized.org>,  Paul Wouters <paul@nohats.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net>
In-Reply-To: <5300C10A.8010308@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="c4cFkFlEVWthjKPVJwDwLF1qH1EuLR9hR"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/WoiDUZI2yZErwyTi0wBu0dAUo54
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 14:03:30 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--c4cFkFlEVWthjKPVJwDwLF1qH1EuLR9hR
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-16 14:45, Dave Crocker wrote:
> On 2/15/2014 11:15 PM, Patrik F=E4ltstr=F6m wrote:
>> The largest problem for IETF and DNS innovation is that the consensus =
in
>> IETF seems to be that innovation of DNS is not possible unless it
>> involves reuse of the TXT resource record.
>=20
>=20
> That assertion is quite wrong on both process and technical grounds
>=20
> Process:
>=20
>      There is certainly a long history of very strong resistance from a=

> core group of DNS advocates in the IETF; and yes, there is an IAB repor=
t
> that doesn't like TXT usage.
>=20
>      But there is also a long history of other folk adding DNS usage in=

> spite of that.
>=20
>      So a casual claim of "IETF consensus" is simply false.
>=20
> Technical:
>=20
>      The use of underscore-based naming variations has provided an easy=
,
> efficient and safe means of eliminating TXT usage ambiguity.  By way of=

> examples, note the SRV record and DKIM, but there are others.

I think this email make exactly my point.

Q.E.D.

   Patrik




--c4cFkFlEVWthjKPVJwDwLF1qH1EuLR9hR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTAMUtrMabGguI180RAqL/AJ0dy5ei4XzWFCkNkRWvVTHzxeWWSACbBFUR
6XDNZ2a/9ysb8NzTWeeHsrE=
=209q
-----END PGP SIGNATURE-----

--c4cFkFlEVWthjKPVJwDwLF1qH1EuLR9hR--


From nobody Sun Feb 16 06:51:34 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043581A0225; Sun, 16 Feb 2014 06:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maDieItrSixU; Sun, 16 Feb 2014 06:51:28 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 682F61A0238; Sun, 16 Feb 2014 06:51:28 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 476F823E2D48; Sun, 16 Feb 2014 14:51:20 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gyYtgSZbJGyu; Sun, 16 Feb 2014 15:51:18 +0100 (CET)
Received: from kopoli (g225015008.adsl.alicedsl.de [92.225.15.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 80A4F23E2B25; Sun, 16 Feb 2014 15:51:18 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Marc Buijsman'" <Marc.Buijsman@os3.nl>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl> <003a01cf2b0c$067d2360$13776a20$@rozanak.com> <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com> <5300B6C6.8030903@os3.nl>
In-Reply-To: <5300B6C6.8030903@os3.nl>
Date: Sun, 16 Feb 2014 15:51:16 +0100
Message-ID: <005c01cf2b26$8b895aa0$a29c0fe0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQOKWVpFurMI2Qzh8V0RHyHseiUo8gI85gZYAcBsuHoCE4W3igGmux4JlwPGjTA=
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/CpSSbpBxsEj8_wxn3oPyEgwWxPY
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 14:51:31 -0000

Dear Marc,

Thanks again for your message.
> Let me first react to your first email of today. CGA uses the
> RSASSA-PKCS1-v1_5 signature algorithm to sign the message. The way I
> understand it as explained at
> http://tools.ietf.org/html/rfc3447#section-8.2.1 is that the length of the
> output signature S only depends on the length k of the RSA modulus n, and
> not on the length of the input message M. The algorithm accomplishes this
by
> using a hash function on message M, SHA-1 in case of CGA. So provided that
> the RSA key has been determined, it does not matter how many fields you
> concatenate and take as input message M (although there is a maximum
> depending on the chosen hash function); the output will always be a
signature
> of length k. The signature field is variable because the RSA key size is
variable;
> not because the message is variable.

You're right I guess I was confused two different things -- data encryption
and  signature generation. I re-checked the signature generation algorithm.
Since first the data is hashed using SHA function and then the digest is
encrypted using a private key, this will lead to having the same length
signature.

But I need to update the document that the signature should be generated
based on the standard RSASSA-PKCS1-v1_5 or for ECC (as a future replacement
of RSA) there should be a standard way. Because I think it is necessary to
also consider other SHA algorithms since SHA1 is no longer consider a very
strong hash function and CGA-TSIG needs to support any future changes to
other algorithms.


> I was not aware that SEND actually encodes groups of 8 bytes. I thought
you
> meant that the value set in the length field should be a multiple of 8,
but now I
> see you mean that the length of the data itself should be a multiple of 8.
It is
> then logical that you might need padding to be able to make whole
> 'octobytes'. However, I don't believe that this padding is needed for the
> signature operation since the hash function takes a variable amount of
input
> bytes anyway. You also didn't mention anything about padding in your draft
> (nor does the CGA RFC), so I assumed the encoded length to be in bytes
just
> like the other length-encoding fields in the TSIG RR. I'm also not sure if
you
> save more space by using 1 byte for the length-encoding field and
additional
> padding, instead of 2 bytes for the length-encoding field without padding.

IMHO, we do not really need two bytes and no padding is also needed. Because
I think if the encryption is on hash function, then it always generates the
same values that is multiple of 8. To have a proof of concept, I checked RSA
signature a few minutes ago with different key sizes (1024bits , 1280bits,
1536bits, 1792bits,2048bits, 3072bits) and the result was always the
multiple of 8. 


> Regarding the old signature, I think you could even leave out the
timestamp
> from the old signature operation. As long as you sign the new public key
with
> the old public key (with the old signature as ouput) in order to
authenticate
> the new public key, it is also possible to authenticate the timestamp and
fudge
> field provided that they have been signed with the new public key (as
> required by TSIG, which recommends a fudge value of 300 seconds i.e. 5
> minutes, a bit more than a few seconds).

Hum... I guess you're right. Signing only the new public key is enough and
in this case no timestamp is needed for the old signature (not new
signature).  I know the attacker only has a small period of time to do this
attack and if it cannot do it, since the new public key is replaced with the
old one on the DNS server, it cannot do this attack anymore or this attack
is not effective as there is no old public key anymore valid.
So I assume this scenario can be like this:
The original node wants to change its IP address or public key. It signs all
DNS message excluding the signature fields using its own new private key and
sign the new public key using its own old private key. Then submit this
packet including the TSIG RR with CGA-TSIG  DATA

The attacker eavesdrops and copy only the old public key and old signature
from the packet and sign the DNS message using its own private key and
submit this value... But the verification of the old signature fails since
the attacker cannot copy the new public key of the original node. If it does
this, the CGA verification will be failed and the node cannot prove the
owner of this public key.

So,
By assuming such failure in the attack scenario. I guess only signing the
new public key for old signature is enough. For this purpose no more
authentication is needed since the time has been already checked for the new
signature.

Thanks,
Best,
Hosnieh


From nobody Sun Feb 16 07:53:08 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60F41A025B for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 07:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.047
X-Spam-Level: 
X-Spam-Status: No, score=-1.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iUXrXzgJlmgr for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 07:53:05 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id AD64A1A00B4 for <dnsop@ietf.org>; Sun, 16 Feb 2014 07:53:05 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s1GFqvZh054422 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 16 Feb 2014 08:52:59 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: multipart/signed; boundary="Apple-Mail=_D7D40732-1110-49D5-B6B0-F3CB956D6453"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <53006595.5010207@frobbit.se>
Date: Sun, 16 Feb 2014 07:52:55 -0800
Message-Id: <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/3lqy5QU8aNlxs_XHSrzmOpwzVJ8
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 15:53:07 -0000

--Apple-Mail=_D7D40732-1110-49D5-B6B0-F3CB956D6453
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Feb 15, 2014, at 11:15 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:

> On 2014-02-16 03:04, David Conrad wrote:
>> Perhaps DNSOP actually is the DNS innovation WG (if perhaps only as a =
seeding ground)?
>=20
> The largest problem for IETF and DNS innovation is that the consensus =
in
> IETF seems to be that innovation of DNS is not possible unless it
> involves reuse of the TXT resource record.

Sorry, friend, but this is trolling. Or do you believe that DANE is not =
an innovation?

--Paul Hoffman

--Apple-Mail=_D7D40732-1110-49D5-B6B0-F3CB956D6453
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJTAN7aAAoJEJz/fXByZmLZ+XkH/1L3wSpFyhkXKB8oS9IcNy6l
+dw0ID5ZQx2US83ubzsQ7iWkLDvTsCgbJ4w1DGmPEBqFQnHkunPxUpkcjQ38mRE3
WR2uOJKr0SnwKE4UAMmx8VKT3kodJ/CWszwFuuZnMfk5hquB7XgJKedjUB8j+4sK
VK/kFJbdB50NYojYnzfmG1Q0MNBZLOSG31mM1uKI/MoonSXxh25MfLPKdDZEnlSt
FS3ZjZXxGz2mblLjmBxqJw1KI54K2pG/T4r43ChNy9bodmZbx72gsRJ76xMJMqg3
BX9aMndgILpSP53Up3kbR4DRaVZxL10Ra/HRxG285Wr5ht4uFUfKrygDuxbhinI=
=d2vX
-----END PGP SIGNATURE-----

--Apple-Mail=_D7D40732-1110-49D5-B6B0-F3CB956D6453--


From nobody Sun Feb 16 08:03:14 2014
Return-Path: <christian@grothoff.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E02AF1A0081 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:03:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6FRK6EoqtXW for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:03:09 -0800 (PST)
Received: from smtp1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) by ietfa.amsl.com (Postfix) with ESMTP id AAD921A002C for <dnsop@ietf.org>; Sun, 16 Feb 2014 08:03:09 -0800 (PST)
Received: from [192.168.178.20] (pd95c0f92.dip0.t-ipconnect.de [217.92.15.146]) by mail.net.in.tum.de (Postfix) with ESMTPSA id DDADF188E03C for <dnsop@ietf.org>; Sun, 16 Feb 2014 17:03:05 +0100 (CET)
Message-ID: <5300E136.5070901@grothoff.org>
Date: Sun, 16 Feb 2014 17:03:02 +0100
From: Christian Grothoff <christian@grothoff.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: dnsop WG <dnsop@ietf.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org>
In-Reply-To: <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/sH6ekBr3VfV0S8CBBbj6biTWCcM
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 16:03:12 -0000

On 02/16/2014 04:52 PM, Paul Hoffman wrote:
> Sorry, friend, but this is trolling. Or do you believe that DANE is not an innovation?

Well, I personally am not so sure that the delta to CERT records (RFC
4398) is all that big,
so is this really the best example you have? ;-).


From nobody Sun Feb 16 08:11:39 2014
Return-Path: <dhc2@dcrocker.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCFB1A0081 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:11:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drK4GD4O3I3F for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:11:35 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 467D21A002C for <dnsop@ietf.org>; Sun, 16 Feb 2014 08:11:35 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1GGBO2K003536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 16 Feb 2014 08:11:28 -0800
Message-ID: <5300E26B.4030301@dcrocker.net>
Date: Sun, 16 Feb 2014 08:08:11 -0800
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, David Conrad <drc@virtualized.org>, Paul Wouters <paul@nohats.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se>
In-Reply-To: <5300C52A.9050802@frobbit.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 16 Feb 2014 08:11:28 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/WNbaIoiJYFY_rsYGZN1jNAM6oeg
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 16:11:37 -0000

On 2/16/2014 6:03 AM, Patrik Fältström wrote:
> I think this email make exactly my point.


Please explain.

By way of anticipating your response, I should not have removed your key 
conclusion:

      "Unless that is put to rest, we can not do much at all."

That is demonstrably not true, as well as the claim of consensus about 
not being able to do anything being wrong.

But even at the simple fact level, are you under the impression that SRV 
uses TXT?

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Feb 16 08:39:44 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C85341A002C for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:39:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Y6UeEmAHUyo for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:39:41 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id C6F031A00F0 for <dnsop@ietf.org>; Sun, 16 Feb 2014 08:39:37 -0800 (PST)
Received: from ix-2.local (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 979701FF55; Sun, 16 Feb 2014 17:39:33 +0100 (CET)
Message-ID: <5300E9C5.9090702@frobbit.se>
Date: Sun, 16 Feb 2014 17:39:33 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org>
In-Reply-To: <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fs1tR17aUmxgV8HWN3p3JbgXEwrXQBTci"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/oQPq3j7AoAtjsIQ5oJoniECslqY
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 16:39:43 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--fs1tR17aUmxgV8HWN3p3JbgXEwrXQBTci
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-16 16:52, Paul Hoffman wrote:
> On Feb 15, 2014, at 11:15 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wro=
te:
>=20
>> > On 2014-02-16 03:04, David Conrad wrote:
>>> >> Perhaps DNSOP actually is the DNS innovation WG (if perhaps only a=
s a seeding ground)?
>> >=20
>> > The largest problem for IETF and DNS innovation is that the consensu=
s in
>> > IETF seems to be that innovation of DNS is not possible unless it
>> > involves reuse of the TXT resource record.
>
> Sorry, friend, but this is trolling. Or do you believe that DANE is not=
 an innovation?

I think so, and I like DANE, I am all in favor of innovation, but I see
strong forces against DANE, inside IETF.

Yes, I am just starting to investigate and try to mitigate, but the
forces against are the ones I see too often:

- We can not use new RR Types, lets use A and TXT
- DNSSEC will never take off
- Lets just use HTTP for transport

My point is that to get innovation, we have to over and over and over
again address these issues.

Ok, I take Daves point that there is no consensus from a process
definition of consensus in the IETF, but the _feeling_ is that there is
consensus as there is no consensus that we CAN add new RR-Types etc.

Just look at the SPF discussion, or the cert-for-secure-xmpp which is
what I refer to regarding "we can not use DANE as DNSSEC is not deployed"=
=2E

I see too many similarities between the two.

And as I wrote, I claim those views block innovation more than anything
else in IETF at the moment.

   Patrik



--fs1tR17aUmxgV8HWN3p3JbgXEwrXQBTci
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTAOnFrMabGguI180RAsitAJsGLVirzAi7wT7O21gNh/SdNyWIZwCeKmMw
y19YDxwUiQhdq8fTMbFA3Uw=
=E353
-----END PGP SIGNATURE-----

--fs1tR17aUmxgV8HWN3p3JbgXEwrXQBTci--


From nobody Sun Feb 16 08:41:14 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549131A0105 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:41:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ga7OjxOUooCa for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:41:11 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id A19D31A00F0 for <dnsop@ietf.org>; Sun, 16 Feb 2014 08:41:11 -0800 (PST)
Received: from ix-2.local (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id DD4E02032D; Sun, 16 Feb 2014 17:41:08 +0100 (CET)
Message-ID: <5300EA24.7090301@frobbit.se>
Date: Sun, 16 Feb 2014 17:41:08 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org> <5300E9C5.9090702@frobbit.se>
In-Reply-To: <5300E9C5.9090702@frobbit.se>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5CjqvXKuwxpS5kBmnRwvp7i0mpJGFuUR5"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/pP_OTEDSMsg7009-m6mgb3wllu4
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 16:41:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--5CjqvXKuwxpS5kBmnRwvp7i0mpJGFuUR5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-16 17:39, Patrik F=E4ltstr=F6m wrote:
> On 2014-02-16 16:52, Paul Hoffman wrote:
>> On Feb 15, 2014, at 11:15 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wr=
ote:
>>
>>>> On 2014-02-16 03:04, David Conrad wrote:
>>>>>> Perhaps DNSOP actually is the DNS innovation WG (if perhaps only a=
s a seeding ground)?
>>>>
>>>> The largest problem for IETF and DNS innovation is that the consensu=
s in
>>>> IETF seems to be that innovation of DNS is not possible unless it
>>>> involves reuse of the TXT resource record.
>>
>> Sorry, friend, but this is trolling. Or do you believe that DANE is no=
t an innovation?
>=20
> I think so,

What I mean is that I *DO* think DANE is an innovation!

> and I like DANE, I am all in favor of innovation, but I see
> strong forces against DANE, inside IETF.
>=20
> Yes, I am just starting to investigate and try to mitigate, but the
> forces against are the ones I see too often:
>=20
> - We can not use new RR Types, lets use A and TXT
> - DNSSEC will never take off
> - Lets just use HTTP for transport
>=20
> My point is that to get innovation, we have to over and over and over
> again address these issues.
>=20
> Ok, I take Daves point that there is no consensus from a process
> definition of consensus in the IETF, but the _feeling_ is that there is=

> consensus as there is no consensus that we CAN add new RR-Types etc.
>=20
> Just look at the SPF discussion, or the cert-for-secure-xmpp which is
> what I refer to regarding "we can not use DANE as DNSSEC is not deploye=
d".
>=20
> I see too many similarities between the two.
>=20
> And as I wrote, I claim those views block innovation more than anything=

> else in IETF at the moment.
>=20
>    Patrik
>=20
>=20
>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20



--5CjqvXKuwxpS5kBmnRwvp7i0mpJGFuUR5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTAOokrMabGguI180RAkxKAJwL16Cd22ApGATm2hCYVKOY9JpyWACff+lv
26NsvCDAvr9QWUlSX/9pMBo=
=EHaP
-----END PGP SIGNATURE-----

--5CjqvXKuwxpS5kBmnRwvp7i0mpJGFuUR5--


From nobody Sun Feb 16 08:48:41 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABD91A03FD for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:48:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.701
X-Spam-Level: 
X-Spam-Status: No, score=-1.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GfuSmWcEX9Qc for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 08:48:38 -0800 (PST)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 8E8FA1A03FE for <dnsop@ietf.org>; Sun, 16 Feb 2014 08:48:38 -0800 (PST)
Received: by mail-ig0-f180.google.com with SMTP id m12so3725008iga.1 for <dnsop@ietf.org>; Sun, 16 Feb 2014 08:48:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=hoy8lIzu4c/26J9UaSj7C9cGT9GZl7eHA+GZ7ylGxhg=; b=oEk8AIskzHRck39OJR+vh8hlYNpxa94o9aDwWNvP8FlqO+nbVZyQP+gHqq/P1EBtfG uqVykAzgFEZF1kEgrw6LYpF7Ls36YGZNJay6We0sp7yxwwq2+2xs/GZnUDVd+vbHfXdC 6I/Oa1ifBoYKTKhqBHR/62fkuewDgUrlGMADs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=hoy8lIzu4c/26J9UaSj7C9cGT9GZl7eHA+GZ7ylGxhg=; b=PQQo1x/1I1Xzno2H+DBgdmyslMTGSmPOgmYCUuxG6cnOar8XY/nNovRJpZ4qd6FltW lugNbXNlmQvM08YN71aw4phMHpiXYtJm6NbcRESrvgTBgJEjY5YUKmMPvaNRq5wjfZDW Bq5+97I+BLm9opyLKgg+V2v23CMQ5suIEx0cAHLW56Wq3YorltjukpSxSYp16pIec36a Qdh/urpsXJZdHujL6xPYC2JSiQ2DWPcTkzafB5LV21LvaqyX6fMTQhW80KWAy2wHL9Y+ ZyTp9YwOA1ec4P1yTNG3L3ywDSRJLwmboBkNDlNyL5QDQLzH9+ubQHSaZMMY/xXfejI6 T64g==
X-Gm-Message-State: ALoCoQlbHJ9NPfG7QmFdZIJAwPCtTh0KLWk11TJLrUMVRpuagNXSpLqSuSVzVjFQb+nAB1IwioWb
X-Received: by 10.43.153.138 with SMTP id la10mr14597763icc.10.1392569316098;  Sun, 16 Feb 2014 08:48:36 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:6d4a:1c1b:df6d:b7b9? ([2001:4900:1042:1:6d4a:1c1b:df6d:b7b9]) by mx.google.com with ESMTPSA id vu3sm23634942igc.6.2014.02.16.08.48.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Feb 2014 08:48:34 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_C81CFD78-ED2C-4B3B-9C62-615CCBC099F2"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <5300E9C5.9090702@frobbit.se>
Date: Sun, 16 Feb 2014 11:48:32 -0500
Message-Id: <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org> <5300E9C5.9090702@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/0MLMtHFpfFBTmOE6oUDiES1Fv7g
Cc: dnsop <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 16:48:40 -0000

--Apple-Mail=_C81CFD78-ED2C-4B3B-9C62-615CCBC099F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 2014-02-16, at 11:39, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:

> - We can not use new RR Types, lets use A and TXT
> - DNSSEC will never take off
> - Lets just use HTTP for transport

I think we are suffering from a knee-jerk instinct to say no to ideas =
that we assume will never work in the real world.

We can't add more transports (e.g. SCTP), because even if implemented =
there's just too much middleware in the world that will interact badly.

We can't add more resource records, because there are nameserver =
implementations that don't deal with opaque types properly, and won't =
allow the new resource records to be published.

We can't do anything that will cause larger responses, because EDNS =
support is not widespread, and in any case the network can't reliably =
deliver fragments.

If we believe all these problems are intractable, then we might as well =
just accept that overloading TXT records and reflection attacks are a =
fact of life, and stop worrying about them.

What I would prefer, though, is a more entrepreneurial approach where =
the likelihood of short-term operational problems (or even long-term =
failure of the work) should not stop us from trying. Rich people are the =
ones that realise that you only need one out of ten business ventures to =
succeed to get a pay out.

So, how about a starting point where we assume that if a particular =
extension has value to anybody, the operators (the market) will adjust =
to allow it to work, and if it doesn't, then adjustments are not =
necessary?

Anybody else feel like working on the specification for SCTP transport? =
:-)


Joe


--Apple-Mail=_C81CFD78-ED2C-4B3B-9C62-615CCBC099F2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlMA6+AACgkQNI8MvYZSOiz0hQCgjo2V7CoPa8LoYcdl45c9w68z
2zAAnjbfR7tPqmALWiEQDZUgSBAwkV+Y
=Qvzq
-----END PGP SIGNATURE-----

--Apple-Mail=_C81CFD78-ED2C-4B3B-9C62-615CCBC099F2--


From nobody Sun Feb 16 11:44:38 2014
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C571A03EE for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 11:44:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPvrN_tJfGfr for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 11:44:36 -0800 (PST)
Received: from ss.vix.su (ss.vix.su [24.104.150.2]) by ietfa.amsl.com (Postfix) with ESMTP id 40D1F1A0276 for <dnsop@ietf.org>; Sun, 16 Feb 2014 11:44:36 -0800 (PST)
Received: from [IPv6:2001:559:8000:c9:e06b:8433:a508:56ec] (unknown [IPv6:2001:559:8000:c9:e06b:8433:a508:56ec]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ss.vix.su (Postfix) with ESMTPSA id B286FEBDA4; Sun, 16 Feb 2014 19:44:33 +0000 (UTC) (envelope-from paul@redbarn.org)
Message-ID: <5301152A.2090800@redbarn.org>
Date: Sun, 16 Feb 2014 11:44:42 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.9 (Windows/20140128)
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org> <5300E9C5.9090702@frobbit.se> <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca>
In-Reply-To: <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tWR8BPNk_d1rMaPgv7mWPO6ssXU
Cc: dnsop <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 19:44:38 -0000

Joe Abley wrote:
> ...
> If we believe all these problems are intractable, then we might as well just accept that overloading TXT records and reflection attacks are a fact of life, and stop worrying about them.

reflection attacks aren't a fact of life. DNS RRL does not require a
forklift upgrade of the infrastructure, isn't stopped by middleboxes,
and does not change the protocol. i think you should discriminate more
finely as to what we ought and ought not give up about.

> What I would prefer, though, is a more entrepreneurial approach where the likelihood of short-term operational problems (or even long-term failure of the work) should not stop us from trying. ...

those were my exact words upon the publication of RFC 2671. it's been
fifteen years. i think if any change to the dns protocol was going to be
useful enough to overcome edge corruption and edge inertia, it would be
EDNS0.

however, it's heartening to see another generation of cannon fodder
lining up to enter the trenches. you go, joe. i'll cheer you on. but
i'll be working on a RESTful/JSON API to hide DNS edge traffic inside
TLS, in sessions not managed by any X.509 CA, while cheering you on.

> So, how about a starting point where we assume that if a particular extension has value to anybody, the operators (the market) will adjust to allow it to work, and if it doesn't, then adjustments are not necessary?
>
> Anybody else feel like working on the specification for SCTP transport? :-)

go, joe, go!

vixie


From nobody Sun Feb 16 13:11:31 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D824C1A041B; Sun, 16 Feb 2014 13:11:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kN0evIwLRFyv; Sun, 16 Feb 2014 13:11:25 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7F41A02E5; Sun, 16 Feb 2014 13:11:25 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 7DDC223E2D48; Sun, 16 Feb 2014 21:11:21 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mngg6NlyLpWw; Sun, 16 Feb 2014 22:11:20 +0100 (CET)
Received: from kopoli (g225015008.adsl.alicedsl.de [92.225.15.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 1A2B923E2B25; Sun, 16 Feb 2014 22:11:20 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Marc Buijsman'" <Marc.Buijsman@os3.nl>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl> <003a01cf2b0c$067d2360$13776a20$@rozanak.com> <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com> <5300B6C6.8030903@os3.nl> <005c01cf2b26$8b895aa0$a29c0fe0$@rozanak.com> <53011AE3.20102@os3.nl>
In-Reply-To: <53011AE3.20102@os3.nl>
Date: Sun, 16 Feb 2014 22:11:17 +0100
Message-ID: <000f01cf2b5b$a26b6800$e7423800$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQOKWVpFurMI2Qzh8V0RHyHseiUo8gI85gZYAcBsuHoCE4W3igGmux4JAfAtHs4C/eRXQpbc0RYg
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/oFqyOfO5sL7rRMbddV7cWpYLLYg
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 21:11:30 -0000

Dear Marc,


> Yes, that's what I thought too, so that's why I proposed to use
> 1.2.840.113549.1.1.5 (note the last 5 instead of 1) for RSA+SHA1.
> 
> > IMHO, we do not really need two bytes and no padding is also needed.
> > Because I think if the encryption is on hash function, then it always
> > generates the same values that is multiple of 8. To have a proof of
> > concept, I checked RSA signature a few minutes ago with different key
> > sizes (1024bits , 1280bits, 1536bits, 1792bits,2048bits, 3072bits) and
> > the result was always the multiple of 8.
> 
> This is indeed true for the signature fields. However, you also defined
single-
> byte length fields for the complete CGA-TSIG DATA field, the Parameters
field
> and the Old PK field (not in the table in section 4.1 of draft 07, but you
do in
> the figure in section 4.2). The Parameters field includes the public key,
which
> consists of (for example) an 1024-bit modulus, but also of a variably
sized
> exponent (say 3 bytes), PLUS the bytes of the encapsulating DER encoding.
> According to my calculations, this requires a minimum of 161 bytes for the
> complete DER-encoded public key. If you then add the 16-byte modifier, the
> 8-byte prefix, the 1-byte collision count, and 0 bytes for the extension
fields
> (but this one is variable as well), then you get a total size of 186 for
the
> Parameters field, which is not a multiple of 8. You would then need
> 6 bytes of additional padding, or fiddle with the padding inside the DER
> structure (but I don't think this is desirable).
> 
> Assuming that the Old PK is also a DER-encoded ASN.1 structure and that an
> Old PK of similar size is added to the packet (161 + 7 bytes padding),
then the
> complete CGA-TSIG DATA field would be of size 660 (including 22 bytes for
> the encoding of 1.2.840.113549.1.1.5 in domain name syntax and two
> signatures of length 128), which requires an additional padding of 4 bytes
to
> make it a multiple of 8.

> So the total padding in this case would be 6 + 7 + 4 = 17 bytes.
> However, if you would use 2 bytes for all five length fields then you
don't
> need padding and you would actually spare 17 - 5 = 12 bytes. To be honest,
I
> don't think the difference is significant enough with respect to the total
size of
> 664 bytes to make it a strong argument for using 2-byte length fields, but
I do
> think that it makes implementing CGA-TSIG much more straightforward
> without having the hassle of adding paddings to each variably sized field.
It
> would also be in line with the size of the length fields defined by TSIG,
which
> are also 2 bytes.


Agreed. For CGA-TSIG data structure, I will change it but for signatures, I
will let it to be only 8 bits since it does not need it.

 
> Agreed. That only leaves the problem of how you notify your clients of
your
> new IPv6 address. :)

It is also not a problem. I addressed it in the new version. The client
receives the IP address of the DNS server from the option of the router
advertisement (if it wants to be secure) and this is the recommended way.
So, the routers usually sends the RA message in a frequent intervals. This
also inform the clients about any changes of the DNS information such as the
DNS IP addresses. 

I just explain a possible attack scenario here

A node receives a RA message and after verification accepts that router
prefix and also sets its DNS IP address (resolver A). Whenever it wants to
resolve any domain names, it asks the resolver A to translate a domain to an
iP address.

Now consider a case where resolver A changes its IP address for whatever
reason. If we say that the RA message interval is 10 minutes. The node now
wants to resolve a name and since it hasn't yet received any new RA message,
it sends a message to the old resolver. We assume that the attacker can
eavesdrop this message. He immediately answers instead of legitimate
resolver (since there is no resolver using that old IP address). The
resolver, according to CGA-TSIG document, needs to include the CGA-TSIG data
structure that enables the other nodes to verify it. Since the attacker does
not have the private key of the legitimate resolver, it cannot spoof the old
IP address of the legitimate resolver since the CGA verification will fails
and signature is not valid if the time signed is an old time.  So, this
attack fails. But only the problem is that the node needs to either wait for
another RA message to receive the new information about the resolver or can
send a RS message and ask for a new RA message to save time. This can happen
after the node does not receive any response from the legitimate resolver.
It then assumes that the legitimate resolver is not alive anymore. 

The other way to solve this problem is that. The resolver announce the nodes
who wants to communicate, about the changes in its IP address. But this is
more complicated than the first solution. Because, the node should know when
the resolver wants to change its IP address. However, we can decrease the
complexity by having a default standard value. Say something like 10
minutes. So, if the resolver receives any query request 10 minutes before
changing its IP address, it will include the its old IP address as mentioned
in CGA-TSIG document. This inform the nodes that the resolver's old IP
address will not be valid after 10 minutes and they need to replace this IP
for further communication in their cache.

The last solution would be using both approach to ensure the client can
translate the names to IP without any delay to go through sending RS and
receiving RA, etc.

Thanks,
Best,
Hosnieh


From nobody Sun Feb 16 15:45:13 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79E681A0128 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 15:45:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6we-WhBA-Jv for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 15:45:10 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 9AEBA1A00CB for <dnsop@ietf.org>; Sun, 16 Feb 2014 15:45:10 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 918E9C9422; Sun, 16 Feb 2014 23:44:55 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1392594308; bh=uc5BgLCiNwAI02J7bR7LuFDLd90VULr0GtwWrq5FQZY=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=sQ6XMt4a6gtBVYptfxdra7PiRTxoJ3dM98mKPzTQwAWQpGX6cxaxsFBLMayxPtsBB Pg4ZcymoV51+jqberq9JkKIWmo0zcyR+IWw3lmQFZQZRNaySf2KsQWWeiPVUq/r6dU oKoUgV+wilOsYw/uL/d1EFP2jTuqEV3sbc6jgKT0=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Sun, 16 Feb 2014 23:44:55 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 14BEA160059; Sun, 16 Feb 2014 23:45:42 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id D260E16004E; Sun, 16 Feb 2014 23:45:41 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 3F399F63F40; Mon, 17 Feb 2014 10:44:54 +1100 (EST)
To: "William F. Maton Sotomayor" <wmaton@ottix.net>
From: Mark Andrews <marka@isc.org>
References: <20140214134610.15238.66099.idtracker@ietfa.amsl.com> <F0F8E35F-4ED7-4D8D-8860-BB1D6D97CB85@hopcount.ca> <alpine.LSU.2.00.1402141456450.14957@hermes-1.csi.cam.ac.uk> <alpine.DEB.2.03.1402141618310.14904@iskra.ottix.net>
In-reply-to: Your message of "Fri, 14 Feb 2014 16:25:46 -0500." <alpine.DEB.2.03.1402141618310.14904@iskra.ottix.net>
Date: Mon, 17 Feb 2014 10:44:53 +1100
Message-Id: <20140216234454.3F399F63F40@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/KTl0L-P9kLRZO2H14Ta7Gtu0l1E
Cc: Tony Finch <dot@dotat.at>, dnsop <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] AS112 bits and pieces
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 23:45:12 -0000

In message <alpine.DEB.2.03.1402141618310.14904@iskra.ottix.net>, "William F. Maton Sotomayor" writes:
> On Fri, 14 Feb 2014, Tony Finch wrote:
> 
> > Joe Abley <jabley@hopcount.ca> wrote:
> >>
> >> Reactions and reviews of the two documents would be most welcome!
> >
> > The as112-dname draft still does not mention the glibc DNAME logging bug.
> 
> Which Linux distro, or a set of Linux distros?  Some seaches yield various 
> bug reports related to DNAME over the last few years in a couple of 
> distros.

Really does it matter?  The answer gets correctly processed and a
little syslog noise is produced.  If you have the problem upgrade
/ report it.

B.T.W. FreeBSD cleaned this up in 2007.
http://svnweb.freebsd.org/base/release/10.0.0/lib/libc/net/gethostbydns.c?r1=188315&r2=188316&

> > https://www.ietf.org/mail-archive/web/dnsop/current/msg10638.html
> >
> > Typo: "flexibl"
> >
> > Apart from that, looks OK :-)
> 
> +1
> 
> >
> > Tony.
> > -- 
> > f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> > Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
> > Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
> > occasionally poor at first.
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
> >
> 
> wfms
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Sun Feb 16 18:03:46 2014
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45A661A030C for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 18:03:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5tTUYIn0ScPD for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 18:03:42 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE801A02E3 for <dnsop@ietf.org>; Sun, 16 Feb 2014 18:03:42 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 50A30800AA; Sun, 16 Feb 2014 21:03:39 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1392602619; bh=IO8UHz3CB2Y2Yol5wd+XNrHDn9cC//v3NlHUkcMR2u4=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=LSrzhORNPoiyhFgOu7j7BrUKvVyqoivQqXmjqB+3vLN4H0wVwXR0B2uTwOYcnl9di ValYxst3ECeYZy70y76ee6cxogQa8PWfmvIv1h7ouUqno2MxhEcg3iRK32VF+APL/I W0Esc95mifKcLUHzWBZe6VzmQAIQWbMx4bRtuu5c=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s1H23bHw001743; Sun, 16 Feb 2014 21:03:37 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Sun, 16 Feb 2014 21:03:37 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: dcrocker@bbiw.net
In-Reply-To: <5300E26B.4030301@dcrocker.net>
Message-ID: <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=ISO-8859-15
Content-Transfer-Encoding: 8BIT
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/d8rcFbbArfff9kEK5rcf8ZqmcUk
Cc: dnsop <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 02:03:44 -0000

On Sun, 16 Feb 2014, Dave Crocker wrote:

> On 2/16/2014 6:03 AM, Patrik Fältström wrote:
>> I think this email make exactly my point.
>
> Please explain.
>
> By way of anticipating your response, I should not have removed your key 
> conclusion:
>
>     "Unless that is put to rest, we can not do much at all."
>
> That is demonstrably not true, as well as the claim of consensus about not 
> being able to do anything being wrong.

Needing TXT records is really a red herring. For instance, look at

http://tools.ietf.org/html/draft-wouters-dane-openpgp-02

and the implementation in:

https://github.com/letoams/openpgpkey-milter

(with supporting https://github.com/letoams/hash-slinger/blob/master/openpgpkey )

It uses a private use RRtype of 65280 and helps you create an RFC 3597
Generic Record type for records. At any time can now, I can ask for
an IANA registration - I've just waited a bit for a discussion and
WG adoption.

At no point in time did I need to use TXT records and at no point in
time did I need to modify DNS software. So yes, innovation via TXT record
has been put to rest a long long time ago.

The problem we have now is purely in process. During the last few IETF
meetings, I was always told I was a "guest" at DNSOPs, that it is the
wrong place for discussion about new RRtypes or EDNS options, and I've
been forced to use the DNSEXT mailing list of a closed WG. DNSOP needs
to broaden its charter, or we need to revive some kind of DNSEXT group.

So let's discuss WG scope and not TXT records.

Thanks,

Paul


From nobody Sun Feb 16 18:16:25 2014
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD39F1A0325 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 18:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DwPTdmQKFE1m for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 18:16:17 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 0837E1A0317 for <dnsop@ietf.org>; Sun, 16 Feb 2014 18:16:16 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id w8so20771018qac.22 for <dnsop@ietf.org>; Sun, 16 Feb 2014 18:16:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rlXy+Q2FW0rU51xR0vH7FeVm2UqVCqQCOKJurFg/HZQ=; b=e0U9NH0jMqnaU0qrdxqAWPC5uaQnxJIMorAFWGoJhqQf2jLIvRfhTSB/FumkJN20Xn jxO9wjaR2qC3SbQxYxePwscGWQ5gC1aTwoclblxznBoCUs80Fby2M0C2Y1c3j/EPwLFC o7O5blm99SZS13afDPuQEE4/X0ljOmqnROtAHZQuBHxdgBenNg2VIi0sMY9py7id5Upg hlXH7Uc3o0hr5Tz9ZbyVDRLT1qhsAIDYZgTtFtkFbEBwuTfyFjQDC1s45/fg5C9DBaF0 xPfnxjO6OHpLiOP3mCrYUEiuSboHDgdyjNXoyKJHkUZpFPoTiVZaFDnGjKuaHXzIqHAj UVJg==
X-Received: by 10.224.172.133 with SMTP id l5mr31684138qaz.25.1392603374573; Sun, 16 Feb 2014 18:16:14 -0800 (PST)
Received: from still.local (184-19-89-76.drr03.clbg.wv.frontiernet.net. [184.19.89.76]) by mx.google.com with ESMTPSA id 110sm19848775qgv.19.2014.02.16.18.16.13 for <dnsop@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Feb 2014 18:16:14 -0800 (PST)
Message-ID: <530170EC.7080305@gmail.com>
Date: Sun, 16 Feb 2014 21:16:12 -0500
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: dnsop <dnsop@ietf.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org>
In-Reply-To: <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/2TVdI2dSs5Egq63F8LRNuMCxXIk
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 02:16:21 -0000

On 2/15/14, 9:04 PM, David Conrad wrote:
> [perpass dropped from ccs]
>
> On Feb 15, 2014, at 11:57 AM, Paul Wouters <paul@nohats.ca> wrote:
>> At ietf87 it was planned to  have a discussion at dnsop about this
>> continued problem of drafts that fall between operations and extensions
>> and the fact that dnsext closed down. Nothing happened at ietf87 or
>> ietf88. I hope to see this as agenda item for dnsop this meeting.
>>
>> We need a WG to discuss DNS innovation.
> At the Vancouver DNSOP meeting when there was some discussion I thought was protocol development related, I got up to the mike asked if DNSOP was the right place for that discussion, being righteously indignant that DNSOP would discuss something non-operational.  However, after sitting down someone pointed out to me that one of the common recurrent complaints about the IETF is that operators tend to get excluded and that maybe DNSOP is actually the best place to discuss DNS protocol development since that's where operators go.
>
> Perhaps DNSOP actually is the DNS innovation WG (if perhaps only as a seeding ground)?
>
>
As the co-chair or DNSOP who took this rather liberal view of our 
charter, I attempted to use the focus be the 'operational impacts' of 
several of the proposals, such at Mr. Wouter's too on tcp keepalives and 
query chaining.  I do believe it was the right thing to do, and I 
continue to do so.  We had great discussion on the topic and while 
nothing could be agreed on, there was some solid advice to take back on 
the issues.

One of the things we've been discussing internally (and have been 
negligent in bringing forward to the group) with our glorious ADs is 
expanding the charter.

tim


From nobody Sun Feb 16 18:51:59 2014
Return-Path: <watsonbladd@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10EDF1A015F; Sat, 15 Feb 2014 08:44:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p8RqPDljYiy2; Sat, 15 Feb 2014 08:44:29 -0800 (PST)
Received: from mail-yh0-x22a.google.com (mail-yh0-x22a.google.com [IPv6:2607:f8b0:4002:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 280051A0151; Sat, 15 Feb 2014 08:44:29 -0800 (PST)
Received: by mail-yh0-f42.google.com with SMTP id a41so12954194yho.29 for <multiple recipients>; Sat, 15 Feb 2014 08:44:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=18N+ranM0ekuYBHJFBUWL9Cvl+tr7p8mdnsBf4AzZiU=; b=XYYcg+JnKYkyGLKhVJFKb8lPoHNyYz1jGA2KOkOSMtU8BZ5DYVca3J56VMtkMiyTgK 7C+D8uVLqstmSNsK3anIn7As5ZyvnacTYqXSnqdTO/vi/okpvR6b9igswf8CK2RIAKPq aI0Re6vwu2Nqjq7gXlXzR5nqX118Dt96Y3B9d9AhxzVWQAw/zylaGTEBRjpGG9+g746F vSvsjmeQqQprhUHAqt7aSkAJGgF43g/YCXR/4NxHTycXOfJbqw0vULtVBYOIU/HG7bPf 40WSuvmmCxEt5PNhGt00Gt6f0bg+Ewi6lOzUzcSG6pUGPvBGJ+N3Xeej7pQ2USgic9SQ e+JQ==
MIME-Version: 1.0
X-Received: by 10.236.94.243 with SMTP id n79mr9849734yhf.46.1392482667133; Sat, 15 Feb 2014 08:44:27 -0800 (PST)
Received: by 10.170.164.212 with HTTP; Sat, 15 Feb 2014 08:44:27 -0800 (PST)
In-Reply-To: <20140215140133.GA6990@sources.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org>
Date: Sat, 15 Feb 2014 08:44:27 -0800
Message-ID: <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/AM-qa9zFX59DBdxoxT6gepJu3W4
X-Mailman-Approved-At: Sun, 16 Feb 2014 18:51:54 -0800
Cc: dnsop@ietf.org, Paul Vixie <paul@redbarn.org>, perpass@ietf.org, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] [perpass] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 16:44:31 -0000

Dear all,
This proposal has multiple shortcomings compared to DNSCurve.

First off, it says that the rationale for TLS over DNSCurve is simply
to "take advantage of TLS". I would respectfully submit that DJB can
do a better job than the TLS committee, and did. Merely adding bolts
and nuts onto a design is not improving it.

Secondly, this proposal only works on TCP. This imposes latency and
state requirements that most people would rather avoid. The use of
keepalive only addresses computational burden, not state burden, and
with the DH speed records we have today unnecessary.

Thirdly, this proposal ignores entirely how to validate the server
over the TLS connection. Does it need a certificate? Who should be
allowed to sign it? How should it be validated? DNSSEC provides a PKI,
and this proposal provides another one. Their interactions will not be
fun.

Fourthly, there is substantial operational knowledge and deployed,
working, code implementing DNSCurve. This does not hold for this
proposal.

Sincerely,
Watson Ladd


From nobody Sun Feb 16 18:52:01 2014
Return-Path: <paul.hoffman@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76DA71A0272; Sat, 15 Feb 2014 10:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rse3HJgFkTjq; Sat, 15 Feb 2014 10:36:38 -0800 (PST)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 0F84B1A026E; Sat, 15 Feb 2014 10:36:37 -0800 (PST)
Received: by mail-vc0-f180.google.com with SMTP id ks9so10158172vcb.39 for <multiple recipients>; Sat, 15 Feb 2014 10:36:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r0g6PT4e4OChPqvC0bbwKKMKUvmgpC9Org/zXxNCk3A=; b=ldHiAgXndv1s/jeyvpSSyp09Kh4mkvGaYTKnkx/0VwucGup40CRrOurRCH698dL9dP VDbro1ydKkC6FIOltN55SSZ8R4BNfuqzOmpVH74fi83ZB8vhhkhsadf0cBV82hg8dyYe BGfTCJckeeQ532c6bJOLv7/xtkRP74Ntx9KgTm+0o7IkMEUGk3UBai9McFBjWNVItxT9 abp2tApu7XHJY8GJ0vhjxo8WDNepvqfBbSEXDZ53tHHLphyavfaPx4eBFgBALBK3aXul FI1MuYxSwDpuLyr/IyLlTgUGkxtbcenvEE3nzrzt2BJBlAlp4245xIsR8nWyF4C+IxNj 4y4A==
MIME-Version: 1.0
X-Received: by 10.52.243.102 with SMTP id wx6mr8701267vdc.12.1392489395897; Sat, 15 Feb 2014 10:36:35 -0800 (PST)
Received: by 10.220.104.8 with HTTP; Sat, 15 Feb 2014 10:36:35 -0800 (PST)
In-Reply-To: <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com>
Date: Sat, 15 Feb 2014 10:36:35 -0800
Message-ID: <CAPik8yatYVBPGV8ObXrqWBkni303Vbk6b=OtMvOUeZvA0gbZ6A@mail.gmail.com>
From: Paul Hoffman <paul.hoffman@gmail.com>
To: Watson Ladd <watsonbladd@gmail.com>
Content-Type: multipart/alternative; boundary=001a1133ec96cbc96c04f276336c
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/xSfelBz87NIhpz5E6-FJqodz2fM
X-Mailman-Approved-At: Sun, 16 Feb 2014 18:51:55 -0800
Cc: Paul Vixie <paul@redbarn.org>, dnsop@ietf.org, perpass <perpass@ietf.org>, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] [perpass] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 18:36:40 -0000

--001a1133ec96cbc96c04f276336c
Content-Type: text/plain; charset=UTF-8

On Sat, Feb 15, 2014 at 8:44 AM, Watson Ladd <watsonbladd@gmail.com> wrote:

> Dear all,
> This proposal has multiple shortcomings compared to DNSCurve.
>

And some advantages over DNSCurve.


> First off, it says that the rationale for TLS over DNSCurve is simply
> to "take advantage of TLS". I would respectfully submit that DJB can
> do a better job than the TLS committee, and did. Merely adding bolts
> and nuts onto a design is not improving it.
>

That is a value judgement that cannot be measured. While DJB's crypto
algorithms have been widely adopted, his crypto protocols have not.

Secondly, this proposal only works on TCP. This imposes latency and
> state requirements that most people would rather avoid. The use of
> keepalive only addresses computational burden, not state burden, and
> with the DH speed records we have today unnecessary.
>

That is a measureable criticism. Note that DNSCurve trades latency and
state for massive amounts more computation by parties who might not care to
do any. Even after many years, there has been no noticeable interest in
DNSCurve from those whom that protocol would hit the hardest.


> Thirdly, this proposal ignores entirely how to validate the server
> over the TLS connection.


True.


> Does it need a certificate?


No.


> Who should be
> allowed to sign it?


"Allowed"? Are we now the identity police?


> How should it be validated?


Using TLS authentication.


> DNSSEC provides a PKI,
> and this proposal provides another one. Their interactions will not be
> fun.
>

They in fact might be fun; they have barely been explored.


> Fourthly, there is substantial operational knowledge and deployed,
> working, code implementing DNSCurve. This does not hold for this
> proposal.
>
>
>
I question "substantial" and  "operational" at the level that is expected
for this protocol. Regardless, there is substantial operational knowledge
of TLS that dwarfs whatever has been done for DNSCurve.

--Paul Hoffman

--001a1133ec96cbc96c04f276336c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Feb 15, 2014 at 8:44 AM, Watson Ladd <span dir=3D"=
ltr">&lt;<a href=3D"mailto:watsonbladd@gmail.com" target=3D"_blank">watsonb=
ladd@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dear all,<br>
This proposal has multiple shortcomings compared to DNSCurve.<br></blockquo=
te><div><br></div><div>And some advantages over DNSCurve.<br>=C2=A0<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">

First off, it says that the rationale for TLS over DNSCurve is simply<br>
to &quot;take advantage of TLS&quot;. I would respectfully submit that DJB =
can<br>
do a better job than the TLS committee, and did. Merely adding bolts<br>
and nuts onto a design is not improving it.<br></blockquote><div><br></div>=
<div>That is a value judgement that cannot be measured. While DJB&#39;s cry=
pto algorithms have been widely adopted, his crypto protocols have not.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
Secondly, this proposal only works on TCP. This imposes latency and<br>
state requirements that most people would rather avoid. The use of<br>
keepalive only addresses computational burden, not state burden, and<br>
with the DH speed records we have today unnecessary.<br></blockquote><div><=
br></div><div>That is a measureable criticism. Note that DNSCurve trades la=
tency and state for massive amounts more computation by parties who might n=
ot care to do any. Even after many years, there has been no noticeable inte=
rest in DNSCurve from those whom that protocol would hit the hardest.<br>
=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
Thirdly, this proposal ignores entirely how to validate the server<br>
over the TLS connection. </blockquote><div><br></div><div>True.<br></div><d=
iv>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Does it need a certificate? <=
/blockquote>
<div><br></div><div>No.<br>=C2=A0<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">W=
ho should be<br>
allowed to sign it? </blockquote><div><br></div><div>&quot;Allowed&quot;? A=
re we now the identity police?<br></div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
How should it be validated? </blockquote><div><br></div><div>Using TLS auth=
entication.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">DNSSEC=
 provides a PKI,<br>

and this proposal provides another one. Their interactions will not be<br>
fun.<br></blockquote><div><br></div><div>They in fact might be fun; they ha=
ve barely been explored.<br></div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">

Fourthly, there is substantial operational knowledge and deployed,<br>
working, code implementing DNSCurve. This does not hold for this<br>
proposal.<br>
<br><br></blockquote><div><br></div><div>I question &quot;substantial&quot;=
 and=C2=A0 &quot;operational&quot; at the level that is expected for this p=
rotocol. Regardless, there is substantial operational knowledge of TLS that=
 dwarfs whatever has been done for DNSCurve.<br>
<br></div><div>--Paul Hoffman<br></div></div><br></div></div>

--001a1133ec96cbc96c04f276336c--


From nobody Sun Feb 16 18:52:03 2014
Return-Path: <paul.hoffman@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECB01A0274; Sat, 15 Feb 2014 10:38:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 800xsc-XpHFU; Sat, 15 Feb 2014 10:38:36 -0800 (PST)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1FAAC1A026E; Sat, 15 Feb 2014 10:38:36 -0800 (PST)
Received: by mail-vc0-f180.google.com with SMTP id ks9so10055996vcb.25 for <multiple recipients>; Sat, 15 Feb 2014 10:38:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4Kb8fL1PsJv5jjlXkrxe2b2Ziby4dm9GhfrSo1bCPaM=; b=h6kaMvJLVyWqniK4j21FFupnf103zH+V+t4uk8ro3M3ETUyVNDXilUMAnVJMiSe6RG IDbohCVwOUyMgpJ0ky4jJkmzi/QywtZ0Ql8f5qEo1HFe7kO84abKCqSj18WCvXvVW8Q/ Z2YzdYre6D9CIJCcBONweArLiewtQ4Ed10o5E4LMjin4EWztEVMjmc4gIrwdkjUgbVqK VMAJYdKCXajMrjisRma5wTdH21uixbZ20Ep0p21Uk33SOc92mRUFDgV8Rv8pUsK+UT1o 8DQDnePj5cFtVWFl565nkw5lLwnwlTDLOLgvhLCnrWCHOzNqm8VPZPEC32FEQpoiurEu +Qhw==
MIME-Version: 1.0
X-Received: by 10.52.191.9 with SMTP id gu9mr5161882vdc.37.1392489514064; Sat, 15 Feb 2014 10:38:34 -0800 (PST)
Received: by 10.220.104.8 with HTTP; Sat, 15 Feb 2014 10:38:34 -0800 (PST)
In-Reply-To: <52FFAD1E.1040509@redbarn.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <CACsn0cn=B201xpoMLhEpwhj_NRtG64zQQyoS7eCf_8-0cmeHFQ@mail.gmail.com> <52FFAD1E.1040509@redbarn.org>
Date: Sat, 15 Feb 2014 10:38:34 -0800
Message-ID: <CAPik8ybjFoG7WAjEmR5Gpe0GXt2qECBws0QNPu3DQ7uSOOWG0A@mail.gmail.com>
From: Paul Hoffman <paul.hoffman@gmail.com>
To: Paul Vixie <paul@redbarn.org>
Content-Type: multipart/alternative; boundary=089e013a00cad6e27d04f2763a65
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/CQi6ZDQoDJiA8uBGNMxy7x_4bAQ
X-Mailman-Approved-At: Sun, 16 Feb 2014 18:51:55 -0800
Cc: Watson Ladd <watsonbladd@gmail.com>, dnsop@ietf.org, perpass <perpass@ietf.org>, Zi Hu <zihu@usc.edu>
Subject: Re: [DNSOP] [perpass] draft-hzhwm-start-tls-for-dns-00: Starting TLS over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 18:38:38 -0000

--089e013a00cad6e27d04f2763a65
Content-Type: text/plain; charset=UTF-8

Cherry-picking the worst of the assertions...


On Sat, Feb 15, 2014 at 10:08 AM, Paul Vixie <paul@redbarn.org> wrote:

> has mr. bernstein's Curve25519 (see
> http://en.wikipedia.org/wiki/Curve25519) been explicitly validated by
> other crypto experts?


Yes.


> last i knew he was the only one claiming it was
> correct and strong enough for production use.


It has been widely discussed with no papers showing any flaws at all.

The crypto is not in question: the rest of the protocol is.

--Paul Hoffman

--089e013a00cad6e27d04f2763a65
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Cherry-picking the worst of the assertions...<br><div><div=
 class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, Feb 15, 2=
014 at 10:08 AM, Paul Vixie <span dir=3D"ltr">&lt;<a href=3D"mailto:paul@re=
dbarn.org" target=3D"_blank">paul@redbarn.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">has mr. bernstein&#39;s Curve25519 (see<br>
<a href=3D"http://en.wikipedia.org/wiki/Curve25519" target=3D"_blank">http:=
//en.wikipedia.org/wiki/Curve25519</a>) been explicitly validated by<br>
other crypto experts?</blockquote><div><br></div><div>Yes.<br>=C2=A0<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"> last i knew he was the only one claiming=
 it was<br>

correct and strong enough for production use. </blockquote><div><br></div><=
div>It has been widely discussed with no papers showing any flaws at all.<b=
r><br>The crypto is not in question: the rest of the protocol is.<br>=C2=A0=
<br>
</div>--Paul Hoffman<br></div></div></div></div>

--089e013a00cad6e27d04f2763a65--


From nobody Sun Feb 16 18:52:06 2014
Return-Path: <Marc.Buijsman@os3.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0AD71A01B6; Sun, 16 Feb 2014 03:12:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.353
X-Spam-Level: 
X-Spam-Status: No, score=-0.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.548] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQhIm56oy9rQ; Sun, 16 Feb 2014 03:12:01 -0800 (PST)
Received: from mail.serv.os3.nl (mail.serv.os3.nl [IPv6:2001:610:158:960::25]) by ietfa.amsl.com (Postfix) with ESMTP id 54EBC1A0199; Sun, 16 Feb 2014 03:12:01 -0800 (PST)
Received: from smtp.os3.nl (smtp.os3.nl [IPv6:2001:610:158:960::119]) by mail.serv.os3.nl (Postfix) with ESMTP id 6FFD617B9A8; Sun, 16 Feb 2014 12:11:58 +0100 (CET)
Received: from [192.168.1.2] (178-84-162-64.dynamic.upc.nl [178.84.162.64]) by smtp.os3.nl (Postfix) with ESMTPSA id 6132817B99E; Sun, 16 Feb 2014 12:11:58 +0100 (CET)
Message-ID: <53009CFE.9030900@os3.nl>
Date: Sun, 16 Feb 2014 12:11:58 +0100
From: Marc Buijsman <Marc.Buijsman@os3.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com>
In-Reply-To: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/ckWbxIH5wk0-vSlsceQbbatWFeg
X-Mailman-Approved-At: Sun, 16 Feb 2014 18:51:55 -0800
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 11:12:04 -0000

Dear Hosnieh,

First of all, I'm glad I could be of help and to see that a number of my
suggestions have been adopted!

Regarding the size of the length fields, however, I'm still confused by
what you are trying to say. I did not consider the number of bits, I
really considered the number of bytes (octets). If I wanted to encode
the length in bits (and I don't), I would have set the value to 2048.
But I'm dividing by 8 and set the value to 256 instead, which is the
length in *bytes* as you said yourself. The reason why you divide by 8 a
second time is a mystery to me. The outcome would then be the number of
groups of 8 bytes, but I've never seen a length encoding before that
counts such 'octobytes' (which is not a byte, but 8 bytes). So you are
counting 32 octobytes, while I am counting 256 bytes (as usual).

Also, I don't understand what you mean to say by "multiple of 8". If the
encoding would be in bits (and again, it's not) and the data is always a
number of whole bytes, then yes the value would be a multiple of 8. But
we are talking about an encoding in bytes here, which do not necessarily
come in groups of 8 (and is therefore not necessarily a multiple of 8).
I also don't know what checksum fields you mean or how their length is
relevant here, but the IPv4 header checksum field and UDP checksum field
in a regular DNS packet are two bytes each.

With regard to the old signature: how would including more fields in the
digest operation increase the packet size? No matter how many fields you
digest, the resulting signature is always of the same length. And the
fields I was referring to are already part of the packet. In order to be
able to authenticate the new public key, you MUST at least include the
new public key in the digest operation. Otherwise the packet could be
intercepted and the new public key could be replaced without notice.

Kind regards,

Marc Buijsman

Hosnieh Rafiee schreef op 15-2-2014 0:07:
> Thanks for the information you've provided, I improved the document
> according to comments and found out that the report also has a few problems
> which is due to the fact that it misinterpreted the of CGA-TSIG document.
>
> Here I explain the problems or the reasons of choices:
>
> - CGA-TSIG cannot use MAC as a signature field. The purpose was that to have
> all the CGA data in one section instead of trying to find them in different
> sections of TSIG. 
>
> - sizes of length encoding: It is one byte. It is enough for any key sizes.
> If you also check the "checksum" field in the packets, you will find out
> that it is only 8 bits or one byte. In the emails I explained to you that it
> is the multiple of 8. In no RFC you can find out that the value is the
> length of data in bits. It is always the length of data in bytes. But how
> you showed in your report is that you consider the number of bits and not
> bytes so you had the following example
> 2048/8=256 (now you only converted the number of bits to bytes) so you
> needed to divide it by another 8 that is 256/8=32 and this is the value you
> set to length. If you even consider the key size 7680, then the length will
> be only 120.
> nd
> - old signature only contains time signed. The reason is to avoid increasing
> the packet length 
>
> I appreciate further comments and would like more people review it so that
> we can go ahead with this document.
>
> Thanks,
> Hosnieh
>
>
>
> A new version of I-D, draft-rafiee-intarea-cga-tsig-07.txt
> has been successfully submitted by Hosnieh Rafiee and posted to the IETF
> repository.
>
> Name:		draft-rafiee-intarea-cga-tsig
> Revision:	07
> Title:		Secure DNS Authentication using CGA/SSAS Algorithm in IPv6
> Document date:	2014-02-15
> Group:		Individual Submission
> Pages:		26
> URL:
> http://www.ietf.org/internet-drafts/draft-rafiee-intarea-cga-tsig-07.txt
> Status:
> https://datatracker.ietf.org/doc/draft-rafiee-intarea-cga-tsig/
> Htmlized:       http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-07
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-rafiee-intarea-cga-tsig-07
>
> Abstract:
>    This document describes a new mechanism that can be used to reduce
>    the need for human intervention during DNS authentication and secure
>    DNS authentication in various scenarios such as the DNS
>    authentication of resolvers to stub resolvers, authentication during
>    zone transfers, authentication of root DNS servers to recursive DNS
>    servers, and authentication during the FQDN (RFC 4703) update.
>
>    Especially in the last scenario, i.e., FQDN, if the node uses the
>    Neighbor Discovery Protocol (NDP) (RFC 4861, RFC 4862), unlike the
>    Dynamic Host Configuration Protocol (DHCP) (RFC 3315), the node has
>    no way of updating his FQDN records on the DNS and has no means for a
>    secure authentication with the DNS server. While this is a major
>    problem in NDP-enabled networks, this is a minor problem in DHCPv6.
>    This is because the DHCP server updates the FQDN records on behalf of
>    the nodes on the network. This document also introduces a possible
>    algorithm for DNS data confidentiality.
>
>
>
>
>
>  
>
>
>> -----Original Message-----
>> From: dnsext [mailto:dnsext-bounces@ietf.org] On Behalf Of Marc Buijsman
>> Sent: Thursday, January 16, 2014 3:45 PM
>> To: dnsext@ietf.org
>> Cc: Jeroen van der Ham
>> Subject: [dnsext] CGA-TSIG research report
>>
>> Dear working group members,
>>
>> For my master's thesis I have performed an investigation at NLnet Labs on
>> CGA-TSIG as a solution to the last mile problem of DNS. The version of the
>> CGA-TSIG proposal that I reviewed is the current latest version at
>> http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-06. During the
> course of
>> my research I have already had some contact with Ms. Rafiee.
>>
>> In order to do a verification of the CGA-TSIG proposal I have created a
> proof
>> of concept implementation in NLnet Labs' "ldns" library. Since the scope
> of
>> the project was limited to the last mile problem it only includes the code
>> required for this purpose, but the implementation could easily be extended
>> to support other applications (like zone transfers). I have found that
> CGA-TSIG
>> has potential to be an adequate solution to the last mile problem on IPv6
>> networks, although some future research is needed with regard to
>> bootstrapping the authentication.
>>
>> As a result, I would hereby like to refer you to my report which can be
> found
>> at http://www.nlnetlabs.nl/downloads/publications/report-rp2-buijsman.pdf.
>> I have outlined my results in section 4.2 which contains suggestions on
> how I
>> believe the CGA-TSIG draft could be clarified and otherwise improved. I
> hope
>> my suggestions will be adopted in the next version of the draft. The PoC
> code
>> can be found in the online Git repository of NLnet Labs at
>> http://git.nlnetlabs.nl/ldns/?h=cga-tsig.
>>
>> I hope my work will be helpful in standardising CGA-TSIG.
>>
>> Yours sincerely,
>>
>> Marc Buijsman
>> _______________________________________________
>> dnsext mailing list
>> dnsext@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsext


From nobody Sun Feb 16 18:52:08 2014
Return-Path: <Marc.Buijsman@os3.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF4581A01C7; Sun, 16 Feb 2014 05:02:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.353
X-Spam-Level: 
X-Spam-Status: No, score=-0.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.548] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aVp5uV1hJQV; Sun, 16 Feb 2014 05:02:01 -0800 (PST)
Received: from mail.serv.os3.nl (mail.serv.os3.nl [IPv6:2001:610:158:960::25]) by ietfa.amsl.com (Postfix) with ESMTP id 0723E1A002B; Sun, 16 Feb 2014 05:02:01 -0800 (PST)
Received: from smtp.os3.nl (smtp.os3.nl [IPv6:2001:610:158:960::119]) by mail.serv.os3.nl (Postfix) with ESMTP id 7C1C417BA76; Sun, 16 Feb 2014 14:01:58 +0100 (CET)
Received: from [192.168.1.2] (178-84-162-64.dynamic.upc.nl [178.84.162.64]) by smtp.os3.nl (Postfix) with ESMTPSA id 5595D17BA75; Sun, 16 Feb 2014 14:01:58 +0100 (CET)
Message-ID: <5300B6C6.8030903@os3.nl>
Date: Sun, 16 Feb 2014 14:01:58 +0100
From: Marc Buijsman <Marc.Buijsman@os3.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl> <003a01cf2b0c$067d2360$13776a20$@rozanak.com> <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com>
In-Reply-To: <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/kl-hqNOQvTmHmrQUg-PqSX3mfn4
X-Mailman-Approved-At: Sun, 16 Feb 2014 18:51:55 -0800
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 13:02:04 -0000

Dear Hosnieh,

Let me first react to your first email of today. CGA uses the
RSASSA-PKCS1-v1_5 signature algorithm to sign the message. The way I
understand it as explained at
http://tools.ietf.org/html/rfc3447#section-8.2.1 is that the length of
the output signature S only depends on the length k of the RSA modulus
n, and not on the length of the input message M. The algorithm
accomplishes this by using a hash function on message M, SHA-1 in case
of CGA. So provided that the RSA key has been determined, it does not
matter how many fields you concatenate and take as input message M
(although there is a maximum depending on the chosen hash function); the
output will always be a signature of length k. The signature field is
variable because the RSA key size is variable; not because the message
is variable.

I was not aware that SEND actually encodes groups of 8 bytes. I thought
you meant that the value set in the length field should be a multiple of
8, but now I see you mean that the length of the data itself should be a
multiple of 8. It is then logical that you might need padding to be able
to make whole 'octobytes'. However, I don't believe that this padding is
needed for the signature operation since the hash function takes a
variable amount of input bytes anyway. You also didn't mention anything
about padding in your draft (nor does the CGA RFC), so I assumed the
encoded length to be in bytes just like the other length-encoding fields
in the TSIG RR. I'm also not sure if you save more space by using 1 byte
for the length-encoding field and additional padding, instead of 2 bytes
for the length-encoding field without padding.

Regarding the old signature, I think you could even leave out the
timestamp from the old signature operation. As long as you sign the new
public key with the old public key (with the old signature as ouput) in
order to authenticate the new public key, it is also possible to
authenticate the timestamp and fudge field provided that they have been
signed with the new public key (as required by TSIG, which recommends a
fudge value of 300 seconds i.e. 5 minutes, a bit more than a few seconds).

Kind regards,

Marc Buijsman

Hosnieh Rafiee schreef op 16-2-2014 13:10:
> Follow up,
>
> I thought again about the possible attacks scenarios. I concluded that I
> also need to include the new public key in the content of the old signature.
> This means the old signature should be "new public key + timestamp",
> otherwise the attacker might have a possibility (a few seconds) to do the
> replay attack by copying the old public key and oldsignature.  So, you're
> right, it still might cause the attacker to attack. But to avoid increasing
> packet size, it is only enough for the two values that is new public key and
> timestamp. Since the new public key is verified by both CGA verification
> process and also the new signature and the old public key is verified by old
> signature.
>
> I will correct this in the next version of the document.
>
> Thanks,
> Best,
> Hosnieh
>
>
>> -----Original Message-----
>> From: dnsext [mailto:dnsext-bounces@ietf.org] On Behalf Of Hosnieh Rafiee
>> Sent: Sunday, February 16, 2014 12:41 PM
>> To: 'Marc Buijsman'
>> Cc: 'Jeroen van der Ham'; DNSOP@ietf.org; dnsext@ietf.org
>> Subject: Re: [dnsext] CGA-TSIG - new version
>>
>> Dear Marc,
>>
>> Thanks for your comments.
>>
>>> Regarding the size of the length fields, however, I'm still confused
>>> by
>> what you
>>> are trying to say. I did not consider the number of bits, I really
>> considered the
>>> number of bytes (octets). If I wanted to encode the length in bits
>>> (and I
>> don't),
>>> I would have set the value to 2048.
>>> But I'm dividing by 8 and set the value to 256 instead, which is the
>> length in
>>> *bytes* as you said yourself. The reason why you divide by 8 a second
>>> time
>> is
>>> a mystery to me. The outcome would then be the number of groups of 8
>>> bytes, but I've never seen a length encoding before that counts such
>>> 'octobytes' (which is not a byte, but 8 bytes). So you are counting 32
>>> octobytes, while I am counting 256 bytes (as usual).
>>
>>> Also, I don't understand what you mean to say by "multiple of 8". If
>>> the encoding would be in bits (and again, it's not) and the data is
>>> always a
>> number
>>> of whole bytes, then yes the value would be a multiple of 8. But we
>>> are
>> talking
>>> about an encoding in bytes here, which do not necessarily come in
>>> groups
>> of
>>> 8 (and is therefore not necessarily a multiple of 8).
>>> I also don't know what checksum fields you mean or how their length is
>>> relevant here, but the IPv4 header checksum field and UDP checksum
>>> field
>> in
>>> a regular DNS packet are two bytes each.
>> http://tools.ietf.org/html/rfc3971#section-5.1
>> maybe my wording is not correct. Check the length field here. 8 bits is
> really
>> not enough for that. So, If you check the implementation of SeNDs (Docomo,
>> etc). what they do is they shift the values or easier way is to divide by
> 8.
>>> With regard to the old signature: how would including more fields in
>>> the digest operation increase the packet size? No matter how many
>>> fields you digest, the resulting signature is always of the same
>>> length. And the
>> fields I was
>>> referring to are already part of the packet. In order to be able to
>> authenticate
>>> the new public key, you MUST at least include the new public key in
>>> the
>> digest
>>> operation. Otherwise the packet could be intercepted and the new
>>> public
>> key
>>> could be replaced without notice.
>> You're not talking about SHA1 digest, you're talking about digital
> signature. It
>> depends on the input data. This is why , for example, in SeND they
> included
>> padding at the end that this value can be the multiple of 8.
>> If this value had a fixed size, they would not include any length to it.
> In RFCs
>> they usually include lengths when the length of value is variable and
> without
>> length field, one cannot determine the length.
>> http://tools.ietf.org/html/rfc3971#section-5.2
>> So, this value is not actually the same size and depends on the plain text
> that
>> one wants to sign.
>> Secondly, if you check the content of the signature, you will notice that
> I
>> included all the DNS message and it is not like before. Because the new
>> signature is verified before old signature, no replay attack can be
> happened
>> since the new signature verification will be failed. So no need to sign a
> large
>> data for old signature field and only timestamp or a small value is enough
> just
>> to show that this node is the owner of this public key. To avoid replay
> attack
>> again, I consider to sign the timestamp.
>>
>> I hope this answer your questions.
>>
>>
>> Thanks,
>> Best,
>> Hosnieh
>>
>>> Kind regards,
>>>
>>> Marc Buijsman
>>>
>>> Hosnieh Rafiee schreef op 15-2-2014 0:07:
>>>> Thanks for the information you've provided, I improved the document
>>>> according to comments and found out that the report also has a few
>>>> problems which is due to the fact that it misinterpreted the of
>>>> CGA-TSIG
>>> document.
>>>> Here I explain the problems or the reasons of choices:
>>>>
>>>> - CGA-TSIG cannot use MAC as a signature field. The purpose was that
>>>> to have all the CGA data in one section instead of trying to find
>>>> them in different sections of TSIG.
>>>>
>>>> - sizes of length encoding: It is one byte. It is enough for any key
>> sizes.
>>>> If you also check the "checksum" field in the packets, you will find
>>>> out that it is only 8 bits or one byte. In the emails I explained to
>>>> you that it is the multiple of 8. In no RFC you can find out that
>>>> the value is the length of data in bits. It is always the length of
>>>> data in bytes. But how you showed in your report is that you
>>>> consider the number of bits and not bytes so you had the following
>>>> example
>>>> 2048/8=256 (now you only converted the number of bits to bytes) so
>>>> you needed to divide it by another 8 that is 256/8=32 and this is
>>>> the value you set to length. If you even consider the key size 7680,
>>>> then the length will be only 120.
>>>> nd
>>>> - old signature only contains time signed. The reason is to avoid
>>>> increasing the packet length
>>>>
>>>> I appreciate further comments and would like more people review it
>>>> so that we can go ahead with this document.
>>>>
>>>> Thanks,
>>>> Hosnieh
>>>>
>>>>
>>>>
>>>> A new version of I-D, draft-rafiee-intarea-cga-tsig-07.txt
>>>> has been successfully submitted by Hosnieh Rafiee and posted to the
>>>> IETF repository.
>>>>
>>>> Name:		draft-rafiee-intarea-cga-tsig
>>>> Revision:	07
>>>> Title:		Secure DNS Authentication using CGA/SSAS Algorithm
>> in IPv6
>>>> Document date:	2014-02-15
>>>> Group:		Individual Submission
>>>> Pages:		26
>>>> URL:
>>>> http://www.ietf.org/internet-drafts/draft-rafiee-intarea-cga-tsig-07
>>>> .t
>>>> xt
>>>> Status:
>>>> https://datatracker.ietf.org/doc/draft-rafiee-intarea-cga-tsig/
>>>> Htmlized:
>> http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-07
>>>> Diff:
>>>> http://www.ietf.org/rfcdiff?url2=draft-rafiee-intarea-cga-tsig-07
>>>>
>>>> Abstract:
>>>>    This document describes a new mechanism that can be used to reduce
>>>>    the need for human intervention during DNS authentication and
> secure
>>>>    DNS authentication in various scenarios such as the DNS
>>>>    authentication of resolvers to stub resolvers, authentication
> during
>>>>    zone transfers, authentication of root DNS servers to recursive DNS
>>>>    servers, and authentication during the FQDN (RFC 4703) update.
>>>>
>>>>    Especially in the last scenario, i.e., FQDN, if the node uses the
>>>>    Neighbor Discovery Protocol (NDP) (RFC 4861, RFC 4862), unlike the
>>>>    Dynamic Host Configuration Protocol (DHCP) (RFC 3315), the node has
>>>>    no way of updating his FQDN records on the DNS and has no means for
> a
>>>>    secure authentication with the DNS server. While this is a major
>>>>    problem in NDP-enabled networks, this is a minor problem in DHCPv6.
>>>>    This is because the DHCP server updates the FQDN records on behalf
> of
>>>>    the nodes on the network. This document also introduces a possible
>>>>    algorithm for DNS data confidentiality.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: dnsext [mailto:dnsext-bounces@ietf.org] On Behalf Of Marc
>>>>> Buijsman
>>>>> Sent: Thursday, January 16, 2014 3:45 PM
>>>>> To: dnsext@ietf.org
>>>>> Cc: Jeroen van der Ham
>>>>> Subject: [dnsext] CGA-TSIG research report
>>>>>
>>>>> Dear working group members,
>>>>>
>>>>> For my master's thesis I have performed an investigation at NLnet
>>>>> Labs on CGA-TSIG as a solution to the last mile problem of DNS. The
>>>>> version of the CGA-TSIG proposal that I reviewed is the current
>>>>> latest version at
>>>>> http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig-06. During
>>>>> the
>>>> course of
>>>>> my research I have already had some contact with Ms. Rafiee.
>>>>>
>>>>> In order to do a verification of the CGA-TSIG proposal I have
>>>>> created a
>>>> proof
>>>>> of concept implementation in NLnet Labs' "ldns" library. Since the
>>>>> scope
>>>> of
>>>>> the project was limited to the last mile problem it only includes
>>>>> the code required for this purpose, but the implementation could
>>>>> easily be extended to support other applications (like zone
>>>>> transfers). I have found that
>>>> CGA-TSIG
>>>>> has potential to be an adequate solution to the last mile problem
>>>>> on
>>>>> IPv6 networks, although some future research is needed with regard
>>>>> to bootstrapping the authentication.
>>>>>
>>>>> As a result, I would hereby like to refer you to my report which
>>>>> can be
>>>> found
>>>>> at http://www.nlnetlabs.nl/downloads/publications/report-rp2-
>>> buijsman.pdf.
>>>>> I have outlined my results in section 4.2 which contains
>>>>> suggestions on
>>>> how I
>>>>> believe the CGA-TSIG draft could be clarified and otherwise improved.
>>>>> I
>>>> hope
>>>>> my suggestions will be adopted in the next version of the draft.
>>>>> The PoC
>>>> code
>>>>> can be found in the online Git repository of NLnet Labs at
>>>>> http://git.nlnetlabs.nl/ldns/?h=cga-tsig.
>>>>>
>>>>> I hope my work will be helpful in standardising CGA-TSIG.
>>>>>
>>>>> Yours sincerely,
>>>>>
>>>>> Marc Buijsman
>>>>> _______________________________________________
>>>>> dnsext mailing list
>>>>> dnsext@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dnsext
>> _______________________________________________
>> dnsext mailing list
>> dnsext@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsext


From nobody Sun Feb 16 18:52:11 2014
Return-Path: <Marc.Buijsman@os3.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98AC71A027D; Sun, 16 Feb 2014 12:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.353
X-Spam-Level: 
X-Spam-Status: No, score=-0.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.548] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkdmOHm__2FF; Sun, 16 Feb 2014 12:09:12 -0800 (PST)
Received: from mail.serv.os3.nl (mail.serv.os3.nl [IPv6:2001:610:158:960::25]) by ietfa.amsl.com (Postfix) with ESMTP id B875F1A0208; Sun, 16 Feb 2014 12:09:11 -0800 (PST)
Received: from smtp.os3.nl (smtp.os3.nl [145.100.96.119]) by mail.serv.os3.nl (Postfix) with ESMTP id CE43917B5D1; Sun, 16 Feb 2014 21:09:07 +0100 (CET)
Received: from [192.168.1.2] (178-84-162-64.dynamic.upc.nl [178.84.162.64]) by smtp.os3.nl (Postfix) with ESMTPSA id 9924E17B5BB; Sun, 16 Feb 2014 21:09:07 +0100 (CET)
Message-ID: <53011AE3.20102@os3.nl>
Date: Sun, 16 Feb 2014 21:09:07 +0100
From: Marc Buijsman <Marc.Buijsman@os3.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl> <003a01cf2b0c$067d2360$13776a20$@rozanak.com> <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com> <5300B6C6.8030903@os3.nl> <005c01cf2b26$8b895aa0$a29c0fe0$@rozanak.com>
In-Reply-To: <005c01cf2b26$8b895aa0$a29c0fe0$@rozanak.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/FUdLjp7LaSBlixOLwYkOVH7yKE4
X-Mailman-Approved-At: Sun, 16 Feb 2014 18:51:55 -0800
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2014 20:09:14 -0000

Dear Hosnieh,

> You're right I guess I was confused two different things -- data encryption
> and  signature generation. I re-checked the signature generation algorithm.
> Since first the data is hashed using SHA function and then the digest is
> encrypted using a private key, this will lead to having the same length
> signature.

I'm glad you agree. :)

> But I need to update the document that the signature should be generated
> based on the standard RSASSA-PKCS1-v1_5 or for ECC (as a future replacement
> of RSA) there should be a standard way. Because I think it is necessary to
> also consider other SHA algorithms since SHA1 is no longer consider a very
> strong hash function and CGA-TSIG needs to support any future changes to
> other algorithms.

Yes, that's what I thought too, so that's why I proposed to use
1.2.840.113549.1.1.5 (note the last 5 instead of 1) for RSA+SHA1.

> IMHO, we do not really need two bytes and no padding is also needed. Because
> I think if the encryption is on hash function, then it always generates the
> same values that is multiple of 8. To have a proof of concept, I checked RSA
> signature a few minutes ago with different key sizes (1024bits , 1280bits,
> 1536bits, 1792bits,2048bits, 3072bits) and the result was always the
> multiple of 8. 

This is indeed true for the signature fields. However, you also defined
single-byte length fields for the complete CGA-TSIG DATA field, the
Parameters field and the Old PK field (not in the table in section 4.1
of draft 07, but you do in the figure in section 4.2). The Parameters
field includes the public key, which consists of (for example) an
1024-bit modulus, but also of a variably sized exponent (say 3 bytes),
PLUS the bytes of the encapsulating DER encoding. According to my
calculations, this requires a minimum of 161 bytes for the complete
DER-encoded public key. If you then add the 16-byte modifier, the 8-byte
prefix, the 1-byte collision count, and 0 bytes for the extension fields
(but this one is variable as well), then you get a total size of 186 for
the Parameters field, which is not a multiple of 8. You would then need
6 bytes of additional padding, or fiddle with the padding inside the DER
structure (but I don't think this is desirable).

Assuming that the Old PK is also a DER-encoded ASN.1 structure and that
an Old PK of similar size is added to the packet (161 + 7 bytes
padding), then the complete CGA-TSIG DATA field would be of size 660
(including 22 bytes for the encoding of 1.2.840.113549.1.1.5 in domain
name syntax and two signatures of length 128), which requires an
additional padding of 4 bytes to make it a multiple of 8.

So the total padding in this case would be 6 + 7 + 4 = 17 bytes.
However, if you would use 2 bytes for all five length fields then you
don't need padding and you would actually spare 17 - 5 = 12 bytes. To be
honest, I don't think the difference is significant enough with respect
to the total size of 664 bytes to make it a strong argument for using
2-byte length fields, but I do think that it makes implementing CGA-TSIG
much more straightforward without having the hassle of adding paddings
to each variably sized field. It would also be in line with the size of
the length fields defined by TSIG, which are also 2 bytes.

> Hum... I guess you're right. Signing only the new public key is enough and
> in this case no timestamp is needed for the old signature (not new
> signature).  I know the attacker only has a small period of time to do this
> attack and if it cannot do it, since the new public key is replaced with the
> old one on the DNS server, it cannot do this attack anymore or this attack
> is not effective as there is no old public key anymore valid.
> So I assume this scenario can be like this:
> The original node wants to change its IP address or public key. It signs all
> DNS message excluding the signature fields using its own new private key and
> sign the new public key using its own old private key. Then submit this
> packet including the TSIG RR with CGA-TSIG  DATA
>
> The attacker eavesdrops and copy only the old public key and old signature
> from the packet and sign the DNS message using its own private key and
> submit this value... But the verification of the old signature fails since
> the attacker cannot copy the new public key of the original node. If it does
> this, the CGA verification will be failed and the node cannot prove the
> owner of this public key.
>
> So,
> By assuming such failure in the attack scenario. I guess only signing the
> new public key for old signature is enough. For this purpose no more
> authentication is needed since the time has been already checked for the new
> signature.

Agreed. That only leaves the problem of how you notify your clients of
your new IPv6 address. :)

Thank you!

Kind regards,
Marc Buijsman


From nobody Sun Feb 16 19:41:47 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0942D1A042E for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 19:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3IbuGX8mOm7N for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 19:41:44 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 671811A0332 for <dnsop@ietf.org>; Sun, 16 Feb 2014 19:41:44 -0800 (PST)
Received: (qmail 67572 invoked from network); 17 Feb 2014 03:41:40 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 17 Feb 2014 03:41:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=530184f1.xn--i8sz2z.k1402; i=johnl@user.iecc.com; bh=HNfBWDDyqC/52WEkX+zsJMDba7drkm9NoEvwIDVGCCo=; b=HheaA60CVa5bVYPATnkxv+uuZeCsAVNnL1wMxPwmzlEJ4CHIoiQYEEIZcEi/C3dMYEm/EmBC+dHZ8gH72kQYdjr/9zxxMGDFYvBDOTKYDIjIX7NqUBk4EiFUKEOQajPrXNO3y8CqXVnRPFHUI02g6sWwrrHlt1JN2kyOT3FBhueZdLaCdlfikawSOKV3j89IIt1lD60eY6PMuRcbOMF5JL95Qy27XspcGnwXw/TpVZmx5zqk+4r0Q3331GIjBzdt
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=530184f1.xn--i8sz2z.k1402; bh=HNfBWDDyqC/52WEkX+zsJMDba7drkm9NoEvwIDVGCCo=;  b=lRshPSmNTin0kC6pC6m0VQun/HU38kEgHH/oNcVTASus24X1JAsKPdTzhaI4hVrkRKOFNW11v57CS2NABwHRJ0OikWl/+yG/mU50Y2Olc7DWS3uta2dn6Ic13IgatiwoWSNsCsXDfhtIwglqSTjk8XqHRZpxx5vTCkYCV64OhFvMNlkpsC9cYsyKGnE0JSQREU8Rl3nBlcOJzTPs/GW/Ex7O/N2j7pV16RQxEdZ6/y86kmfHql4p+f6r5e6SK8//
Date: 17 Feb 2014 03:41:14 -0000
Message-ID: <20140217034114.64447.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <53006595.5010207@frobbit.se>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/UvYpCrm9xNKMKCIxszrD4wNdVfM
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 03:41:46 -0000

>The largest problem for IETF and DNS innovation is that the consensus in
>IETF seems to be that innovation of DNS is not possible unless it
>involves reuse of the TXT resource record.

Yes, sort of.  The consensus in one part of the IETF is that adding
new RR types is too hard due to DNS server upgrades and particularly
to the web crudware that most people use to provision their DNS.  The
consensus in another part of the IETF is that adding new RR types is
trivial, and anyone who thinks otherwise is stupid.  (I oversimplify
but not by much.)

I've had a draft kicking around for a while, with recent additions
from Vixie, of an RR config language to allow the DNS to be largely
self-describing, with most new RR types having names and formats
published in a well known place so the servers and crudware can handle
new RRs without software upgrades (after a one-off upgrade to handle
the config language itself) or config changes.

The responses to the draft have been most educational.

R's,
John


From nobody Sun Feb 16 22:39:17 2014
Return-Path: <jay@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAEF91A0375 for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 22:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2woykkwTjD0X for <dnsop@ietfa.amsl.com>; Sun, 16 Feb 2014 22:39:09 -0800 (PST)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC8A1A036E for <dnsop@ietf.org>; Sun, 16 Feb 2014 22:39:09 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id 6D1C54B9819; Mon, 17 Feb 2014 19:39:04 +1300 (NZDT)
X-Virus-Scanned: Debian amavisd-new at srsomail.office.nzrs.net.nz
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNjQZOnrsVds; Mon, 17 Feb 2014 19:38:55 +1300 (NZDT)
Received: from [192.168.1.231] (121-74-106-209.telstraclear.net [121.74.106.209]) (Authenticated sender: jay) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id 6E9D04B9818; Mon, 17 Feb 2014 19:38:55 +1300 (NZDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Jay Daley <jay@nzrs.net.nz>
In-Reply-To: <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca>
Date: Mon, 17 Feb 2014 19:38:53 +1300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3DD4822-CFD3-479C-9C68-45A7EBDA0D4A@nzrs.net.nz>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org> <5300E9C5.9090702@frobbit.se> <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/VSJwIh5ZEGlOcRSBzSBYdhpPc7o
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 06:39:13 -0000

On 17/02/2014, at 5:48 am, Joe Abley <jabley@hopcount.ca> wrote:

>=20
> On 2014-02-16, at 11:39, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:
>=20
>> - We can not use new RR Types, lets use A and TXT
>> - DNSSEC will never take off
>> - Lets just use HTTP for transport
>=20
> I think we are suffering from a knee-jerk instinct to say no to ideas =
that we assume will never work in the real world.
>=20
> We can't add more transports (e.g. SCTP), because even if implemented =
there's just too much middleware in the world that will interact badly.
>=20
> We can't add more resource records, because there are nameserver =
implementations that don't deal with opaque types properly, and won't =
allow the new resource records to be published.
>=20
> We can't do anything that will cause larger responses, because EDNS =
support is not widespread, and in any case the network can't reliably =
deliver fragments.
>=20
> If we believe all these problems are intractable, then we might as =
well just accept that overloading TXT records and reflection attacks are =
a fact of life, and stop worrying about them.
>=20
> What I would prefer, though, is a more entrepreneurial approach where =
the likelihood of short-term operational problems (or even long-term =
failure of the work) should not stop us from trying. Rich people are the =
ones that realise that you only need one out of ten business ventures to =
succeed to get a pay out.
>=20
> So, how about a starting point where we assume that if a particular =
extension has value to anybody, the operators (the market) will adjust =
to allow it to work, and if it doesn't, then adjustments are not =
necessary?

Very well put indeed.

The default position currently seems to be that consensus is so hard to =
achieve because it demands so much that very little can pass.  A =
particular symptom of that is the increasing calls for a "requirements =
draft" or "problem statement" (which is obviously wider than DNSOP).

We'd do well from turning that on its head and making the default =
position that everything passes unless consensus is that it shouldn't, =
which would generally be because it is truly awful, duplicative, nobody =
understands it, etc.

As Henry Ford probably didn't say "If I had asked people what they =
wanted, they would have said faster horses.=94.  Or better still a =
genuine quote from Steve Crocker in the final ICANN board vote on new =
TLDs:  "The case for new TLDs is a little harder to pin down.  But one =
of the most important principles in the creation of the Internet from a =
very long time ago was not to stifle or prejudge what the paths for =
innovation are.  So the default has to be that, absent a strong case =
that such things will cause harm, we must move forward.  And I strongly =
support this."

Jay

>=20
> Anybody else feel like working on the specification for SCTP =
transport? :-)
>=20
>=20
> Joe
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--=20
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley


From nobody Mon Feb 17 02:31:22 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 299F71A0480 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 02:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6L32pY0ODL6 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 02:31:16 -0800 (PST)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 1567F1A038D for <dnsop@ietf.org>; Mon, 17 Feb 2014 02:31:15 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:50712) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1WFLTb-0003Jo-9F (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 17 Feb 2014 10:31:03 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WFLTb-00065M-Qu (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 17 Feb 2014 10:31:03 +0000
Date: Mon, 17 Feb 2014 10:31:03 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Mark Andrews <marka@isc.org>
In-Reply-To: <20140216234454.3F399F63F40@rock.dv.isc.org>
Message-ID: <alpine.LSU.2.00.1402171024220.18502@hermes-1.csi.cam.ac.uk>
References: <20140214134610.15238.66099.idtracker@ietfa.amsl.com> <F0F8E35F-4ED7-4D8D-8860-BB1D6D97CB85@hopcount.ca> <alpine.LSU.2.00.1402141456450.14957@hermes-1.csi.cam.ac.uk> <alpine.DEB.2.03.1402141618310.14904@iskra.ottix.net> <20140216234454.3F399F63F40@rock.dv.isc.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/0vXUZ4hPYoowWcx9UeN3EE3RJWE
Cc: dnsop <dnsop@ietf.org>, "William F. Maton Sotomayor" <wmaton@ottix.net>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] AS112 bits and pieces
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 10:31:19 -0000

Mark Andrews <marka@isc.org> wrote:
> In message <alpine.DEB.2.03.1402141618310.14904@iskra.ottix.net>, "William F. Maton Sotomayor" writes:
> > On Fri, 14 Feb 2014, Tony Finch wrote:
> >
> > > Joe Abley <jabley@hopcount.ca> wrote:
> > >>
> > >> Reactions and reviews of the two documents would be most welcome!
> > >
> > > The as112-dname draft still does not mention the glibc DNAME logging bug.
> >
> > Which Linux distro, or a set of Linux distros?  Some seaches yield various
> > bug reports related to DNAME over the last few years in a couple of
> > distros.
>
> Really does it matter?  The answer gets correctly processed and a
> little syslog noise is produced.  If you have the problem upgrade
> / report it.

Whether it matters depends on the quantity of reverse DNS lookups you are
doing and the completeness of your locally-served zone setup, so I think
it is worth including the warning. And I think wfms's question is worth
answering but I don't have time to dig through historical versions right
now, sorry.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rockall, Malin: Cyclonic 5 to 7, occasionally gale 8 at first in Rockall,
decreasing 3 or 4 except in north Rockall. Moderate or rough, becoming rough
or very rough. Rain or showers. Moderate or good.


From nobody Mon Feb 17 08:22:27 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF85A1A051E for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:22:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2hEN39fzGt3N for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:22:24 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9441A050F for <dnsop@ietf.org>; Mon, 17 Feb 2014 08:22:24 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 31B691B80AD for <dnsop@ietf.org>; Mon, 17 Feb 2014 08:22:22 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 20FD0190043; Mon, 17 Feb 2014 08:22:22 -0800 (PST)
Received: from [10.0.1.29] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 08:22:21 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca>
Date: Mon, 17 Feb 2014 11:22:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/psNTSt5oWpjW2kUzXyaOPQwWUgk
Cc: dnsop <dnsop@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 16:22:26 -0000

On Feb 16, 2014, at 9:03 PM, Paul Wouters <paul@nohats.ca> wrote:
> DNSOP needs
> to broaden its charter, or we need to revive some kind of DNSEXT =
group.

We would need to find some volunteers to act as co-chair.   I don't =
think adding the work to the DNSOP charter is the right thing to do, =
although I am not wedded to that position.   I just suspect that (a) it =
will make life in DNSOP harder and (b) we will get better review in an =
intarea working group.   But that's a fairly artificial point to be =
making, so argue away!   :)


From nobody Mon Feb 17 08:44:23 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF96F1A00B4 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:44:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aoMnadKf1EUx for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:44:21 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E5C801A0509 for <dnsop@ietf.org>; Mon, 17 Feb 2014 08:44:20 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E90768A031 for <dnsop@ietf.org>; Mon, 17 Feb 2014 16:44:17 +0000 (UTC)
Date: Mon, 17 Feb 2014 11:44:15 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140217164408.GC27215@mx1.yitter.info>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/q9LrB1kHoFlmUMmEPIKc7iSS-aQ
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 16:44:23 -0000

I am not convinced that DNS belongs in the Internet area.  It's an
application.  I think if we need a place to discuss broader DNS
innovation, then it should be in Applications.

But I also have pretty strong doubts that "DNS innovation" needs a
place for such discussion, on the grounds that when we _had_ such a WG
nobody did any work.  It was just a mailing list and WG for people to
say, "Get off my lawn."  Document reviews languished for months or
years.  LCs resulted in no comments. 

Why shouldn't that work go on in the WGs that want the innovations in
question?  Why shouldn't people who know about the DNS involve
themselves in the protocols that want to use these innovations so
that, instead of being Defenders of the Protocol Faith, they are
engineers trying to solve practical engineering problems that others
have, but in a way consistent with the deployed architecture?

Best regards,

A

On Mon, Feb 17, 2014 at 11:22:19AM -0500, Ted Lemon wrote:
> On Feb 16, 2014, at 9:03 PM, Paul Wouters <paul@nohats.ca> wrote:
> > DNSOP needs
> > to broaden its charter, or we need to revive some kind of DNSEXT group.
> 
> We would need to find some volunteers to act as co-chair.   I don't think adding the work to the DNSOP charter is the right thing to do, although I am not wedded to that position.   I just suspect that (a) it will make life in DNSOP harder and (b) we will get better review in an intarea working group.   But that's a fairly artificial point to be making, so argue away!   :)
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Feb 17 08:59:03 2014
Return-Path: <joelja@bogus.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D931E1A04C1 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trLB9HhlAWFW for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:58:59 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A824C1A040C for <dnsop@ietf.org>; Mon, 17 Feb 2014 08:58:59 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s1HGwn82051204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 17 Feb 2014 16:58:49 GMT (envelope-from joelja@bogus.com)
Message-ID: <53023FC3.8060103@bogus.com>
Date: Mon, 17 Feb 2014 08:58:43 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org> <5300E9C5.9090702@frobbit.se> <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca>
In-Reply-To: <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s9T6WtJx9ommgQ3HtKULLgxf5jEgBB4Cc"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Mon, 17 Feb 2014 16:58:50 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/TA_MOUwfFhlIKSBis5guXJ8ePVw
Cc: dnsop <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 16:59:03 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--s9T6WtJx9ommgQ3HtKULLgxf5jEgBB4Cc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2/16/14, 8:48 AM, Joe Abley wrote:

>=20
> We can't do anything that will cause larger responses, because EDNS
> support is not widespread, and in any case the network can't reliably
> deliver fragments.

in the context of reflection attacks (next paragraph) more packets is
perhaps not the most helpful thing.

> If we believe all these problems are intractable, then we might as
> well just accept that overloading TXT records and reflection attacks
> are a fact of life, and stop worrying about them.
>=20


--s9T6WtJx9ommgQ3HtKULLgxf5jEgBB4Cc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMCP8QACgkQ8AA1q7Z/VrIyBwCdEBvSsdA0FeY2KLLEnNhpoHUJ
xYUAnRByLEQV3J8yl1piFPSfgCQ5u8sk
=ZRWv
-----END PGP SIGNATURE-----

--s9T6WtJx9ommgQ3HtKULLgxf5jEgBB4Cc--


From nobody Mon Feb 17 09:25:17 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9D041A00EE for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 09:25:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mM9_BLpWfw-C for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 09:25:11 -0800 (PST)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id 07DC81A00E6 for <dnsop@ietf.org>; Mon, 17 Feb 2014 09:25:10 -0800 (PST)
Received: by mail-ig0-f176.google.com with SMTP id r2so4304378igi.3 for <dnsop@ietf.org>; Mon, 17 Feb 2014 09:25:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=BqBbtQT6ro+6YCJml2ST0KOoGJdsLJNUu0VwzoELDfc=; b=B26/hUUCzTH8BQvSNB1yzp5ug95qTMljbuSa+/RG0Ww2BXWOHwCcotKc2FCcW+xruJ zQNhJ2O49lvPoiKexWiAH9C0tUh+4fA0BqpHFqVQYk1vtWVkm0pvN3Bx8FwnPO8/y5lM rfsEWDQ9MXTM/8B2Bw/RlLazFJItSQFp1KbWA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=BqBbtQT6ro+6YCJml2ST0KOoGJdsLJNUu0VwzoELDfc=; b=d3wsfHT09z6twJmB9J+TOqR2fjTzLh3Elrz7IEJsjvuXZEeWcdscO0xJTPa+b7JztO CY0Fo0XItUNFXl910Cg01bPHu0bbG2TMGkUvlbIEvhV0zgnFfvm/jDibfJ9D2ASobJYV 64SVOkQqOhN3VwdGRJvWNEaxRQ364B9nO8lQrsJiwtTcWM8R1MAfx6YRxg4YTvSRhRHW EaSIwjiNgEP4tbVUeFriTh12jXSxx/lkIrZzbgShh0EQiNsN1Tnx8Xe89fpi4i5GTNTA WcaIAKYUGvhM6C1iIhwrNvw+c2I0Jv1mgDNIUL9B2LZncF0X3Dce6M277NNjDVjUzEpG G9eA==
X-Gm-Message-State: ALoCoQkpZ4ngMW5af6XPCVpxx0C9WUZhgojZG0A7KJPRHtIZW39MPI34j9bLrpJBedu0RFHCQyov
X-Received: by 10.43.146.69 with SMTP id jx5mr2457757icc.42.1392657908391; Mon, 17 Feb 2014 09:25:08 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:48b3:650a:3c8f:5c5b? ([2001:4900:1042:1:48b3:650a:3c8f:5c5b]) by mx.google.com with ESMTPSA id r6sm32911146igg.10.2014.02.17.09.25.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Feb 2014 09:25:07 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_3A2287EA-6526-4D33-970A-9AD5D9BF8E1F"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <53023FC3.8060103@bogus.com>
Date: Mon, 17 Feb 2014 12:25:05 -0500
Message-Id: <925D6E92-99AE-4F78-AD83-2FE819600E6F@hopcount.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <784CF51A-937B-4131-85BC-AED579FA746D@vpnc.org> <5300E9C5.9090702@frobbit.se> <DB47354C-AEBA-4861-8177-94993377E3E8@hopcount.ca> <53023FC3.8060103@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/XiqcHzcS86qTX7LMdfEAq2mQY08
Cc: dnsop <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 17:25:13 -0000

--Apple-Mail=_3A2287EA-6526-4D33-970A-9AD5D9BF8E1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 2014-02-17, at 11:58, joel jaeggli <joelja@bogus.com> wrote:

> On 2/16/14, 8:48 AM, Joe Abley wrote:
>=20
>> We can't do anything that will cause larger responses, because EDNS
>> support is not widespread, and in any case the network can't reliably
>> deliver fragments.
>=20
> in the context of reflection attacks (next paragraph) more packets is
> perhaps not the most helpful thing.

The problem to solve at the DNS end of the equation boils down to good =
enough client authentication to be able to distinguish between attack =
traffic and legitimate queries. The problem is not "how to stop putting =
things in the DNS".

Waiting for the universal implementation of the recommendations in BCP38 =
doesn't seem like the most proactive approach.


Joe


--Apple-Mail=_3A2287EA-6526-4D33-970A-9AD5D9BF8E1F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlMCRfEACgkQNI8MvYZSOixJ/wCeJNAQkIoshoXSygjOB5njNmK+
acAAmwYOB1arDMfbIOnZ7JVBBxGO5fIo
=FoHz
-----END PGP SIGNATURE-----

--Apple-Mail=_3A2287EA-6526-4D33-970A-9AD5D9BF8E1F--


From nobody Mon Feb 17 09:57:47 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 842071A0239 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 09:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wGU0u3uOq_F0 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 09:57:45 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id EB1D41A0177 for <dnsop@ietf.org>; Mon, 17 Feb 2014 09:57:44 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AA60E1B80E5 for <dnsop@ietf.org>; Mon, 17 Feb 2014 09:57:42 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A3A2D190052; Mon, 17 Feb 2014 09:57:42 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 09:57:42 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140217164408.GC27215@mx1.yitter.info>
Date: Mon, 17 Feb 2014 12:57:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/anTZWgDBqnafQirJkTWUZMEB3ak
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 17:57:46 -0000

On Feb 17, 2014, at 11:44 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
> Why shouldn't that work go on in the WGs that want the innovations in
> question?  Why shouldn't people who know about the DNS involve
> themselves in the protocols that want to use these innovations so
> that, instead of being Defenders of the Protocol Faith, they are
> engineers trying to solve practical engineering problems that others
> have, but in a way consistent with the deployed architecture?

Sure.   If dnsop wants to do this work, that's fine.

As for the dysfunction of the dnsext working group, I agreed to close it =
because as an incoming AD I wasn't entirely clear on what to do when the =
chairs requested that it be closed.   If I had it to do over, I would =
probably instead have solicited new chairs and tried to fix the =
dysfunction, which I agree existed there.

Unfortunately, the dysfunction will arise wherever DNS improvements are =
suggested, so not trying to fix it is not an option.   And of course I =
realize that many good IETF contributors have been ground to a nubbin =
trying to fix the aforementioned dysfunction, and have no particular =
reason to think I would have been more able to fix it than my =
predecessors.


From nobody Mon Feb 17 10:15:26 2014
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F00A1A0103 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VUJFrn14imyH for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:15:23 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 650731A012E for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:15:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 2319784B42; Mon, 17 Feb 2014 13:15:20 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 01442-08; Mon, 17 Feb 2014 13:15:19 -0500 (EST)
Received: from [10.0.1.3] (c-67-169-100-133.hsd1.ca.comcast.net [67.169.100.133]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 1190B8445C; Mon, 17 Feb 2014 13:15:18 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_44B1F99B-3B08-41FB-BB13-517A4DB93C41"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
Date: Mon, 17 Feb 2014 10:15:16 -0800
Message-Id: <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/PSjkCe9xaGSJVGwsLUqzSDrFowo
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:15:25 -0000

--Apple-Mail=_44B1F99B-3B08-41FB-BB13-517A4DB93C41
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Ted,

On Feb 17, 2014, at 9:57 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> If dnsop wants to do this work, that's fine.

Given the various topics being discussed in DNSOP and the relatively =
high interest/reviews/comments/etc being shown, I think DNSOP is working =
fine.

> Unfortunately, the dysfunction will arise wherever DNS improvements =
are suggested, so not trying to fix it is not an option.   And of course =
I realize that many good IETF contributors have been ground to a nubbin =
trying to fix the aforementioned dysfunction, and have no particular =
reason to think I would have been more able to fix it than my =
predecessors.

Given experiences, I have to wonder if the whole idea of a long-term =
working group just leads to dysfunction -- perhaps the IETF version of =
an echo chamber (or perhaps even inbreeding).  Perhaps a better approach =
would be to use something like DNSOP which has an operations bent is use =
to see if there are ideas/interest in particular topics that can drive =
the creation of working groups that focus on the specific DNS-related =
issues?

Regards,
-drc


--Apple-Mail=_44B1F99B-3B08-41FB-BB13-517A4DB93C41
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTAlG0AAoJENV6ebf0/4rXvVYH/2H1uWsgQFMmAdpu/Vyy26lL
GGE41n+2/MF9X5/XRmJntVJoFYfGlr2QCkrlszKQrNrUmcHxRfhYYtzLiNb0LtcU
Ey1WuUYSy0ZJJs3kLLxOWXaLI+gjMh89WKKN58lSbCkTfi+m/1vbQQsSaINHmFD6
d/62UU2KWyI1VNmg+K6o6CzOycmhqKn3F7sO0oePjQ7Vr6Unh7p1zdo9pnG2SrS+
WCIi8bx2kaNKgpalXzZRnGZojN8+HO0Q1QyFNwwZSpIqjZ6GaKO1VgkzZsQVd14w
aePfwTvyR0pEZ3Iss81ZTt6oiiihP8mxWAwiggPXtt/bJN072K9yRxFsFVPv3vE=
=6fS2
-----END PGP SIGNATURE-----

--Apple-Mail=_44B1F99B-3B08-41FB-BB13-517A4DB93C41--


From nobody Mon Feb 17 10:35:57 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B3B1A054D for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0BNp7RDGaUUk for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:35:53 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 4356F1A0549 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:35:53 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CEE2E1B80E5 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:35:50 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id B499C190052; Mon, 17 Feb 2014 10:35:50 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 10:35:50 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org>
Date: Mon, 17 Feb 2014 13:35:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <DDBEF38A-CEA1-4816-BD2E-931AA2728A9B@nominum.com>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/53gAHLGIgEM4MbZaYBxx_SaFEl8
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:35:56 -0000

On Feb 17, 2014, at 1:15 PM, David Conrad <drc@virtualized.org> wrote:
> Given experiences, I have to wonder if the whole idea of a long-term =
working group just leads to dysfunction -- perhaps the IETF version of =
an echo chamber (or perhaps even inbreeding).  Perhaps a better approach =
would be to use something like DNSOP which has an operations bent is use =
to see if there are ideas/interest in particular topics that can drive =
the creation of working groups that focus on the specific DNS-related =
issues?

Yup.   However, creating working groups is a pretty heavyweight =
process=97I think that's what motivates the long-term model for =
protocols where frequent extensions are likely.   Possibly rotating =
working group chairs more frequently would work in such cases.


From nobody Mon Feb 17 10:39:00 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A071A1A054C for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fU48fdtynYYW for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:38:57 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 735561A053A for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:38:46 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s1HIcf50011139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 17 Feb 2014 11:38:43 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
Date: Mon, 17 Feb 2014 10:38:41 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3327F09A-8A9E-4F07-A093-8551DBF87067@vpnc.org>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/JLMyCZAir8_AsJfgq3RIfaUiOlc
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:38:58 -0000

On Feb 17, 2014, at 9:57 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Feb 17, 2014, at 11:44 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
>> Why shouldn't that work go on in the WGs that want the innovations in
>> question?  Why shouldn't people who know about the DNS involve
>> themselves in the protocols that want to use these innovations so
>> that, instead of being Defenders of the Protocol Faith, they are
>> engineers trying to solve practical engineering problems that others
>> have, but in a way consistent with the deployed architecture?
>=20
> Sure.   If dnsop wants to do this work, that's fine.
>=20
> As for the dysfunction of the dnsext working group, I agreed to close =
it because as an incoming AD I wasn't entirely clear on what to do when =
the chairs requested that it be closed.   If I had it to do over, I =
would probably instead have solicited new chairs and tried to fix the =
dysfunction, which I agree existed there.
>=20
> Unfortunately, the dysfunction will arise wherever DNS improvements =
are suggested, so not trying to fix it is not an option.   And of course =
I realize that many good IETF contributors have been ground to a nubbin =
trying to fix the aforementioned dysfunction, and have no particular =
reason to think I would have been more able to fix it than my =
predecessors.

Given your second paragraph, why create a new WG which will be an =
attractive nuisance? Andrew's proposal of letting WGs that want the =
innovations seems less likely to rekindle the dysfunction.

(Disclaimer: I an co-chair of a non-DNS WG that is fully manifesting the =
"lack of interest to even review WG items that people said they wanted" =
dysfunction that we are speaking of. And I want to shut it down.)

--Paul Hoffman=


From nobody Mon Feb 17 10:42:44 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 334821A054C for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:42:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Edz7VJYcdovR for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:42:41 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 820EB1A04F0 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:42:41 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2F0C01B80DF for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:42:39 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 2475D190052; Mon, 17 Feb 2014 10:42:39 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 10:42:38 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <3327F09A-8A9E-4F07-A093-8551DBF87067@vpnc.org>
Date: Mon, 17 Feb 2014 13:42:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <075E8E46-9277-43D2-B66D-0AADB50AE39C@nominum.com>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <3327F09A-8A9E-4F07-A093-8551DBF87067@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/PMiZLtolzCdfQ_u9N88PlkwpxrY
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:42:43 -0000

On Feb 17, 2014, at 1:38 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> Given your second paragraph, why create a new WG which will be an =
attractive nuisance? Andrew's proposal of letting WGs that want the =
innovations seems less likely to rekindle the dysfunction.

Then you're just moving the dysfunction to the IETF mailing list, as =
we've seen in the recent past.   I'm not convinced that that's a win.


From nobody Mon Feb 17 10:44:35 2014
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F5A1A0520 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:44:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XmNvCVMg3qWJ for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:44:30 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 2B1551A0554 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:44:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 8404284B42; Mon, 17 Feb 2014 13:44:27 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 02095-05; Mon, 17 Feb 2014 13:44:27 -0500 (EST)
Received: from [10.0.1.3] (c-67-169-100-133.hsd1.ca.comcast.net [67.169.100.133]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 9739D8445C; Mon, 17 Feb 2014 13:44:26 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_E5B8C5C1-330A-4758-B12A-3E9E983AE60A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <DDBEF38A-CEA1-4816-BD2E-931AA2728A9B@nominum.com>
Date: Mon, 17 Feb 2014 10:44:24 -0800
Message-Id: <142F23D3-9EB9-451D-B7EF-AE1B7E104DF1@virtualized.org>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org> <DDBEF38A-CEA1-4816-BD2E-931AA2728A9B@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/KesHryvYNPdskg1vaur8ahYZ9FU
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:44:32 -0000

--Apple-Mail=_E5B8C5C1-330A-4758-B12A-3E9E983AE60A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Feb 17, 2014, at 10:35 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> However, creating working groups is a pretty heavyweight process

Perhaps this is the problem that should be solved?

> Possibly rotating working group chairs more frequently would work in =
such cases.

This seems to imply the working group chairs have a larger role than I =
suspect is healthy (either for the WG chairs or the IETF as a whole).

Regards,
-drc


--Apple-Mail=_E5B8C5C1-330A-4758-B12A-3E9E983AE60A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTAliIAAoJENV6ebf0/4rXnvYIAJp6hgr28fg59BMNGndLKwEE
Rc6jDoBVEYk5d2een6opXWSBvHEsF37dWVq+KXBZp/Qo5KGQq7bV11OHi7gz/A5N
60VbXHE5aDDiNHnkcmwH9pF7LLwH2cip5NjzHPavccpHBzWdsZHNuJ19WqDJh2ew
+Sik9cOzBzmO05wEtJWx/3LC6VnNiVlBjFfXghenes+BBhTCA0wyCEw9kU+DXVS6
oQUNUGM2b/9q+PToKRiyXduqtCs2p6R/PpTCMpMOemkgpRTulTn0VOhpJs831UD6
kpOfpRhtU/bfrygZg6CLg22rEh/4BaaAbavmq7Ng7w5DlxfcKPjZWNvl16O3xBU=
=kncS
-----END PGP SIGNATURE-----

--Apple-Mail=_E5B8C5C1-330A-4758-B12A-3E9E983AE60A--


From nobody Mon Feb 17 10:45:07 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEEF51A0539 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ipuNXVGNWqcZ for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:45:02 -0800 (PST)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id DFC101A0520 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:45:01 -0800 (PST)
Received: by mail-qg0-f48.google.com with SMTP id a108so5469542qge.7 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:44:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=y644nO5AVY0zqQYb0VaREjRgtXjHUw8ON/zF9Z7Fopg=; b=qqaH8sqkKx52mdjDwabuYzxQINLDQnrwKewWbHWyXdVQGfUpSZHICk/02OW7G7mqv+ BwWjhzOYQYmz/nKFxQNj8dokiuAfJ5P8XllOsuh/07Q4rYOBWpTACADeDkF0SgN6zclM rViEH136oIWrZb+x/HhnfLhonUUVCMSDiO23NYAuLLfLAFbjeDcseS2aYZDTf/3d3K+j kr22Amj7+fCg/wLvxEX8dWwkBE/QTnh+cEe7Gn4YecPky71obNalhoHmKSYeK2aCf6eV caXeOR17lZBYfHcqXrmAi7ago6iXID+BHAjApAR8jGMRMNRaARgHqVuTjOWveFfT83uq hBbw==
X-Received: by 10.224.166.210 with SMTP id n18mr29873933qay.32.1392662699186;  Mon, 17 Feb 2014 10:44:59 -0800 (PST)
Received: from [10.0.0.15] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id i7sm47546232qan.0.2014.02.17.10.44.55 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Feb 2014 10:44:55 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org>
Date: Mon, 17 Feb 2014 13:45:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <51F20B86-AB72-4AAC-9223-3C4DE2B6084E@gmail.com>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org>
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/bnzbUkjh6DbDKA39ZAjfx10qwYo
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:45:04 -0000

On Feb 17, 2014, at 1:15 PM, David Conrad <drc@virtualized.org> wrote:

> Ted,
>=20
> On Feb 17, 2014, at 9:57 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>> If dnsop wants to do this work, that's fine.
>=20
> Given the various topics being discussed in DNSOP and the relatively =
high interest/reviews/comments/etc being shown, I think DNSOP is working =
fine.

This hasn't always been the case. At the moment, we've got a couple of =
high-profile issues by the tail and we're working to get some items that =
had gone dormant in front of the WG again. I hope the current level of =
interest can be sustained as needed to get work meaningfully defined and =
completed. Ask me in Toronto how I think we're doing :)
>=20
>> Unfortunately, the dysfunction will arise wherever DNS improvements =
are suggested, so not trying to fix it is not an option.   And of course =
I realize that many good IETF contributors have been ground to a nubbin =
trying to fix the aforementioned dysfunction, and have no particular =
reason to think I would have been more able to fix it than my =
predecessors.
>=20
> Given experiences, I have to wonder if the whole idea of a long-term =
working group just leads to dysfunction -- perhaps the IETF version of =
an echo chamber (or perhaps even inbreeding).  Perhaps a better approach =
would be to use something like DNSOP which has an operations bent is use =
to see if there are ideas/interest in particular topics that can drive =
the creation of working groups that focus on the specific DNS-related =
issues?

This seems to me to be the function v6ops has in its charter as "Solicit =
input from network operators and users to identify operational issues =
with the IPv4/IPv6 Internet [for us, with DNS], and determine solutions =
or workarounds to those issues=85.This work should primarily be =
conducted by those areas and WGs which are responsible and best fit to =
analyze these problems, but v6ops may also cooperate in focusing such =
work."

In preliminary discussion of the re-chartering that will be on the =
agenda for London, we've already stumbled on the possibility that what's =
really needed here is something similar to what v6ops does-- a way to =
support getting a feedback loop closed between DNS operators and the =
assorted DNS users elsewhere in the IETF. The actual mechanism of that =
interaction may well include "problem statement" documents to be handed =
off to other WGs, but I think that's not necessarily a bad thing; the =
work should go where there are people motivated and able to do it, but =
still should be informed by focused expertise on the infrastructure, =
including DNS.

MHO (no hat): The balancing act is not only between operators and =
vendors/implementors, but also between DNS as an application that needs =
to evolve with the uses of the Internet and DNS as infrastructure that =
everyone relies upon and therefore should probably maintain some level =
of predictability and consistency. If DNSOP can't do anything useful =
towards managing that balance under its current charter, or a new =
charter that can get consensus support and action, we can and should =
shut it down.


Suzanne





From nobody Mon Feb 17 10:46:50 2014
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE97E1A0543 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2K_ZAs3iM23z for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:46:45 -0800 (PST)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id D99881A053E for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:46:44 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id x13so24372079qcv.33 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:46:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hcM4mpJ7R7L1tdcKeyGEPwxI5j0sIx5NcWR5hJmR6mI=; b=I9Otun8X6ZDs2lKgPxk4gt8N2kjFMctE6jqfRyPaugYkvcDtJO3tsuSw5bCbmUURnH S9NetmDG+NW+mtmkK505WHNsc9S+0sjdILDRJpd0iWg911NevlnOZb+CcIxO3rmB/twK gL8LEbakSoCCsPtyegcDPMxupmICpstm7Q8/HQQoB7ShcLTlK3CU0XZObpwBuo9Yhtnk 6mVuDNDoZXL1HqzI7rG5qa0Z/Kox3WmhNhwA32QTOviSylJR4EvL4GpuO2+U/Nfdr0oa xsKkVuydaWbaRGxbZ81I9vtMvegA9iVVWeEKtcpxqoxZCxNBQPwRPTIz3J30grM0OfSd aI0g==
X-Received: by 10.224.22.3 with SMTP id l3mr4322630qab.103.1392662802186; Mon, 17 Feb 2014 10:46:42 -0800 (PST)
Received: from still.local (184-19-89-76.drr03.clbg.wv.frontiernet.net. [184.19.89.76]) by mx.google.com with ESMTPSA id b12sm47441200qag.23.2014.02.17.10.46.41 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Feb 2014 10:46:41 -0800 (PST)
Message-ID: <53025910.7010105@gmail.com>
Date: Mon, 17 Feb 2014 13:46:40 -0500
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, David Conrad <drc@virtualized.org>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org> <DDBEF38A-CEA1-4816-BD2E-931AA2728A9B@nominum.com>
In-Reply-To: <DDBEF38A-CEA1-4816-BD2E-931AA2728A9B@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/fFzKOCgbTQxuhz6kawcVJMqD-sU
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:46:49 -0000

On 2/17/14, 1:35 PM, Ted Lemon wrote:
> On Feb 17, 2014, at 1:15 PM, David Conrad <drc@virtualized.org> wrote:
>> Given experiences, I have to wonder if the whole idea of a long-term working group just leads to dysfunction -- perhaps the IETF version of an echo chamber (or perhaps even inbreeding).  Perhaps a better approach would be to use something like DNSOP which has an operations bent is use to see if there are ideas/interest in particular topics that can drive the creation of working groups that focus on the specific DNS-related issues?
> Yup.   However, creating working groups is a pretty heavyweight process—I think that's what motivates the long-term model for protocols where frequent extensions are likely.   Possibly rotating working group chairs more frequently would work in such cases.
>

The two dnsext releated items we covered in DNSOP were EDNS0 options.  
Since OPT codes are now assigned by expert review, putting some of that 
discussion where the largest collection of DNS experts reside has some 
logic to it.

tim


From nobody Mon Feb 17 10:58:49 2014
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDB11A0275 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmQ56tA6Wic7 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:58:45 -0800 (PST)
Received: from smtp85.ord1c.emailsrvr.com (smtp85.ord1c.emailsrvr.com [108.166.43.85]) by ietfa.amsl.com (Postfix) with ESMTP id 714E21A012E for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:58:45 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 16EA550150; Mon, 17 Feb 2014 13:58:42 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 5DBF650089;  Mon, 17 Feb 2014 13:58:37 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
Date: Mon, 17 Feb 2014 13:58:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B97E8E9-9E8A-4374-B65A-4BFA64A10801@ogud.com>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/_-4RR6ujO0m0oz8u5IjeqIHRsBA
Cc: dnsop WG <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, Dave Crocker <dcrocker@bbiw.net>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:58:47 -0000

On Feb 17, 2014, at 11:22 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 16, 2014, at 9:03 PM, Paul Wouters <paul@nohats.ca> wrote:
>> DNSOP needs
>> to broaden its charter, or we need to revive some kind of DNSEXT =
group.
>=20
> We would need to find some volunteers to act as co-chair.   I don't =
think adding the work to the DNSOP charter is the right thing to do, =
although I am not wedded to that position.   I just suspect that (a) it =
will make life in DNSOP harder and (b) we will get better review in an =
intarea working group.   But that's a fairly artificial point to be =
making, so argue away!   :)


I think recreating DNS WG is a bad idea.=20
We have a few ideas on the table in various that are related to=20
	a) DNS transport TCP, SCTP, "tree answer: give me all records =
need to answer/validate X starting from point above X",=20
	Zone transfer improvements=20
	aa) DNS "privacy" ie. channel encryption/authentication=20
	b) Operational Automation=20
	c) Keeping noise out of DNS (AS112) and name spaces/meta-tld/alt =
TLD.
	d) New protocols adopting DANE
	e) Name server control protocols=20


a) and aa) should have its own short term WG=20
b) Belongs in DNSOP=20
c) is above DNSEXT and DNSOP wg it is more of an intersection of many =
different areas like RAI, APPS,=20
OPS and SECURITY  =3D=3D> a special WG=20
d) DANE WG is handling that=20
d) Domain boundaries BOF may turn into a WG.=20
e) Belongs in DNSOP=20

So Yes I see a need for a focused DNS protocol wg at this time.
The problem with long lived groups is you never know when new useful =
work will show up,
killing groups or just the threat of killing a WG seems to bring out =
innovation.=20

	Olafur




From nobody Mon Feb 17 11:04:53 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF8971A0231 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 11:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PRRjQk4La5ma for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 11:04:51 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 36FED1A01F9 for <dnsop@ietf.org>; Mon, 17 Feb 2014 11:04:51 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id DA09C1B80DF for <dnsop@ietf.org>; Mon, 17 Feb 2014 11:04:48 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D3B7D190052; Mon, 17 Feb 2014 11:04:48 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 11:04:48 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <142F23D3-9EB9-451D-B7EF-AE1B7E104DF1@virtualized.org>
Date: Mon, 17 Feb 2014 14:04:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <22D872A8-33F8-402F-99C8-571D930BEF9E@nominum.com>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org> <DDBEF38A-CEA1-4816-BD2E-931AA2728A9B@nominum.com> <142F23D3-9EB9-451D-B7EF-AE1B7E104DF1@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/XlCooj8FvGvEqqSOsfjV-_uubjQ
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 19:04:52 -0000

On Feb 17, 2014, at 1:44 PM, David Conrad <drc@virtualized.org> wrote:
> Perhaps this is the problem that should be solved?

I don't know how practical that is.   Brian and I have talked about =
doing one-off meetings when we want to discuss DNS extensions at IETF =
meetings, since we have the dnsext mailing list for email discussions.   =
But that leads to AD-sponsored documents, which probably isn't the right =
thing to do on a large scale.

>> Possibly rotating working group chairs more frequently would work in =
such cases.
>=20
> This seems to imply the working group chairs have a larger role than I =
suspect is healthy (either for the WG chairs or the IETF as a whole).


Working group chairs are responsible for determining working group =
consensus.   It's really important (IMHO) for working group chairs to =
take action when mailing list discussions start to tube on =
non-consensus-affecting tangents.   I've seen numerous working groups =
fail when chairs don't do this.

So I really don't know what you mean by "larger role than is healthy."  =
Chairs are not secretaries.   They have real work to do, and a real =
leadership role.   They do not decide what the output of the working =
group should be=97they determine consensus based on working group =
discussions.   But this is a difficult task to do well, and I think it's =
a pretty large role.


From nobody Mon Feb 17 11:07:12 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 569F31A021A for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 11:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ueVzf7qq6mi2 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 11:07:09 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id CC5DC1A0152 for <dnsop@ietf.org>; Mon, 17 Feb 2014 11:07:09 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7AB8A1B80E5 for <dnsop@ietf.org>; Mon, 17 Feb 2014 11:07:07 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6B1DF190052; Mon, 17 Feb 2014 11:07:07 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 11:07:07 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <9B97E8E9-9E8A-4374-B65A-4BFA64A10801@ogud.com>
Date: Mon, 17 Feb 2014 14:07:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <5712A671-6073-493F-9108-F300AC8E571D@nominum.com>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <9B97E8E9-9E8A-4374-B65A-4BFA64A10801@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/PxEL77DO6rmmzqPqnWtKodJ1lYA
Cc: dnsop WG <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, Dave Crocker <dcrocker@bbiw.net>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 19:07:11 -0000

On Feb 17, 2014, at 1:58 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
> The problem with long lived groups is you never know when new useful =
work will show up,
> killing groups or just the threat of killing a WG seems to bring out =
innovation.=20

Yup, that's how DNSIND turned into DNSEXT.   :}


From nobody Tue Feb 18 06:40:23 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1E11A067F; Tue, 18 Feb 2014 06:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OTuB1VQf7YM2; Tue, 18 Feb 2014 06:40:18 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BEFCD1A04DB; Tue, 18 Feb 2014 06:40:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140218144018.16179.57609.idtracker@ietfa.amsl.com>
Date: Tue, 18 Feb 2014 06:40:18 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/SHu-bLcES3UWOt9JJ3hFIjMkSIc
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-child-syncronization-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 14:40:21 -0000

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

        Title           : Child To Parent Synchronization in DNS
        Author          : Wes Hardaker
	Filename        : draft-ietf-dnsop-child-syncronization-00.txt
	Pages           : 12
	Date            : 2014-02-14

Abstract:
   This document specifies how a child zone in the DNS can publish a
   record to indicate to a parental agent that it may copy and process
   certain records from the child zone.  The existence and change of the
   record may be monitored by a parental agent, after which the parent
   may act on the data appropriately.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-child-syncronization-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Feb 18 08:10:25 2014
Return-Path: <sm@resistor.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB2CD1A06A7 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 08:10:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Level: 
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, MIME_8BIT_HEADER=0.3, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHcYBQMX7Xya for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 08:10:21 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C96391A04FB for <dnsop@ietf.org>; Tue, 18 Feb 2014 08:10:21 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1IG9wJg007233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Feb 2014 08:10:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392739812; bh=flT90q4UL7wTOtIxyNxBR8sQJaAOHiiaz6k4Sd9Lpa8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3Rdm87zbe/CJCpO9yhJZo7T+2GD+5K6VRQCHP0EWYuBrLgNhgPTPZPEHOiK+5R5j+ DWVPSULffTULuaumgVdHiZNMGaOpvSKjHdCtVdh7DjFPg8YoR3UTwqJwvYiwHuYk17 W+TD5jZ3QtzXdnYogrK1ROOrabS/iuZeCDo4yLl4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1392739812; i=@resistor.net; bh=flT90q4UL7wTOtIxyNxBR8sQJaAOHiiaz6k4Sd9Lpa8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jJGxOi77Xq394i1KoYciwaw1weN8A6fC6KXph7obrxqyZ4b8m8UwkBIwpQFito6Ae ccsLWkU29zArt1lyrlw9Ak8tmQ4TPLS3wk3mtE0x4PNETCxuX20zACIBlmBok1hz3g blPrX7kSv+J+CFC9wGFkEHrk4dL8FXU2uGxzZEI8=
Message-Id: <6.2.5.6.2.20140218074550.0c380cc8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 18 Feb 2014 07:54:52 -0800
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>, David Conrad <drc@virtualized.org>, Paul Wouters <paul@nohats.ca>
From: SM <sm@resistor.net>
In-Reply-To: <53006595.5010207@frobbit.se>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/aKLfb51lfyVXsWofYlrKzP8V1fU
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 16:10:23 -0000

Hi Patrik,
At 23:15 15-02-2014, Patrik F=E4ltstr=F6m wrote:
>The largest problem for IETF and DNS innovation is that the consensus in
>IETF seems to be that innovation of DNS is not possible unless it
>involves reuse of the TXT resource record.

In other words, it is only possible to use one of=20
the code points as the people being part of the=20
consensus do not work on getting code running. :-)

Seriously, it may take some effort to get things=20
deployed but that is not an insurmountable task=20
[1].  One of the problems is that there isn't any money in doing that.

>Unless that is put to rest, we can not do much at all.

Yes.

Regards,
-sm

1. I actually looked into it some time back.=20


From nobody Tue Feb 18 08:57:25 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8C0D1A0510 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 08:57:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiSBiYbw8Gnu for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 08:57:15 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 74BD41A0228 for <dnsop@ietf.org>; Tue, 18 Feb 2014 08:57:15 -0800 (PST)
Received: from mx1.yitter.info (nat-01-mht.dyndns.com [216.146.45.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B51F68A031 for <dnsop@ietf.org>; Tue, 18 Feb 2014 16:57:10 +0000 (UTC)
Date: Tue, 18 Feb 2014 11:57:10 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140218165710.GD27482@mx1.yitter.info>
References: <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/lgXviO6UVOzjJvkpx4YSEP4Kc2w
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 16:57:19 -0000

On Mon, Feb 17, 2014 at 12:57:40PM -0500, Ted Lemon wrote:
> 
> Sure.   If dnsop wants to do this work, that's fine.

No.  This was precisely my point.  For most of the stuff people want,
the work should be in a WG that does not have "DNS" in its name.
That's the _key_ point.  We protocol weenies need to get out of our
comfy chair and go learn why in the world people want to put
_anything_ in the DNS.  Our failure to do that is how we ended up with
the situation we have: we keep stamping our feet and saying that the
DNS works _just fine_ with new RRTYPEs, for instance, except that many
who want to use them cannot.

My view was that if there was something that was DNS-specific that
needed attention, people should have a BoF.  And look!  We have 2 BoFs
on specific DNS topics in London.  The questions are narrow and
focussed, not big floppy "gee, this looks like DNS, so it should be
swatted over to the DNS weenies" ones.  

If the goal is a "Get off my lawn" working group, then big generic
questions are in order.  But I think we can do better.

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Feb 18 09:10:44 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AFFB1A0653 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 09:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id myBPhB7edjGr for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 09:10:37 -0800 (PST)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 413641A06A0 for <dnsop@ietf.org>; Tue, 18 Feb 2014 09:10:36 -0800 (PST)
Received: by mail-qc0-f175.google.com with SMTP id x13so25584588qcv.6 for <dnsop@ietf.org>; Tue, 18 Feb 2014 09:10:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gAUgoa9WMInQ84hXKxk2VUdvgZIOmuX9o98AiiFToQM=; b=pMeeWsGDhN+25MCCaZhmnqCltRRWrxvqUDXYTya3WKdIiSR9WWbeOcggmeOCzEguAp 4avbh+HjQfkd3gHm/sqF8F1p9CLeT2lsUSnLIkdLlcW2po9M3cJDMGu/5gAnSZkbPMtw upPBScOsND+jlZ40erDMrQTZXrUufU+J3ygClp9J9KrbnZMBRyv1Um2RJxGsLgD170mS y6XNILUbNZ+2VzCwBycCHpDBzqVVkeL/RunGQLKq0GqPUyDgHe68ft8tcU5Dil/jZdsz sTcTjbC39kvgcMTiLxZZXi0OPBNIuopHU+wA7gi8BUHbxezJNE8rPneAaG3rvZ8C549z p1HA==
X-Received: by 10.224.169.11 with SMTP id w11mr12295257qay.71.1392743433224; Tue, 18 Feb 2014 09:10:33 -0800 (PST)
Received: from [10.0.0.15] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id z18sm16053092qab.5.2014.02.18.09.10.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 09:10:31 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20140218165710.GD27482@mx1.yitter.info>
Date: Tue, 18 Feb 2014 12:10:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3F1600A-55DA-40E3-8CA1-F133A7A88966@gmail.com>
References: <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <20140218165710.GD27482@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/cOOYDaY0hePhNAF7BY2VCneLXcg
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 17:10:39 -0000

On Feb 18, 2014, at 11:57 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:

> No.  This was precisely my point.  For most of the stuff people want,
> the work should be in a WG that does not have "DNS" in its name.
> That's the _key_ point.  We protocol weenies need to get out of our
> comfy chair and go learn why in the world people want to put
> _anything_ in the DNS.  Our failure to do that is how we ended up with
> the situation we have: we keep stamping our feet and saying that the
> DNS works _just fine_ with new RRTYPEs, for instance, except that many
> who want to use them cannot.
>=20
> My view was that if there was something that was DNS-specific that
> needed attention, people should have a BoF.  And look!  We have 2 BoFs
> on specific DNS topics in London.  The questions are narrow and
> focussed, not big floppy "gee, this looks like DNS, so it should be
> swatted over to the DNS weenies" ones. =20

I'm sympathetic to this view, assuming I actually understand it, but not =
entirely sure what it says in terms of our charter discussion: should =
DNSOP go away, continue to address specific topics per the current =
charter, or add some kind of v6ops-like =
requirements/coordination-with-the-people-who-really-have-the-problem =
function?=20

As I see it, we have another problem, complementary to the one you're =
highlighting, which is the number of situations arising where working =
groups across the IETF want to do something that makes certain =
assumptions about, or demands upon, the DNS, without DNS protocol =
weenies in the room at all. This strikes me as=85.suboptimal.

Is that a problem you (generically, not just Andrew) see as a concern? =
If so, do you see any general principles for navigating it?=20


thanks,
Suzanne=


From nobody Tue Feb 18 09:15:29 2014
Return-Path: <sm@resistor.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A87E81A0400 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 09:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDTqjtvWuGGw for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 09:15:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C9D51A03CE for <dnsop@ietf.org>; Tue, 18 Feb 2014 09:15:25 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1IHFEEL017139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Feb 2014 09:15:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392743720; bh=zd5jjUtNu0Z4BCK2UZLM4jFjuHFKQjAaUZmrVLkmTaA=; h=Date:To:From:Subject:In-Reply-To:References; b=Lg7cN8ZxUIz7ZWqPJTZXarqnrSR9Uf6GTE8uzfE8O/XnfOacJxOTzqityh2y95pCn StvyI/iCGYSVLrjFtwBr5QuNWHMrIbg2k3lFT1z9qDdntjQNWScvg0YTqk1d0831+D FbQOTMacFkTn28i5iG9j8zuP9vInGPwKb2y1rFPU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1392743720; i=@resistor.net; bh=zd5jjUtNu0Z4BCK2UZLM4jFjuHFKQjAaUZmrVLkmTaA=; h=Date:To:From:Subject:In-Reply-To:References; b=2TAPcw6YuEJQoEXrFpRwgY33gSMWkqM8XAZjrsavPeGKwripoLkEBsiasn+UPd7SI HgdphkIpTqhOC5aOjvO0IrsDZOcwNBtEb/aEHfFMo2iHwqZJx+I9JzK3ak5uulZYtQ rTcM/s72gffJUlJA5/pWAfLzdBZ7Q4dXNKsvVjsY=
Message-Id: <6.2.5.6.2.20140218081053.0c37dad0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 18 Feb 2014 08:19:23 -0800
To: Andrew Sullivan <ajs@anvilwalrusden.com>, dnsop@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <20140217164408.GC27215@mx1.yitter.info>
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/U61ORkC7qznqw7Wq98vnl8Sl2eE
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 17:15:26 -0000

Hi Andrew,
At 08:44 17-02-2014, Andrew Sullivan wrote:
>I am not convinced that DNS belongs in the Internet area.  It's an
>application.  I think if we need a place to discuss broader DNS
>innovation, then it should be in Applications.

To say it differently, DNS has a higher impact on applications work 
than work in other areas.  My guess is that things won't get any 
better if DNS is in the Applications Area.  The issue is cross-area 
reviews.  It is a problem when reviews are not being done [1].

Regards,
-sm

1. There are likely good reasons for that. 


From nobody Tue Feb 18 10:18:42 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA8F21A04C1 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 10:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jl67G4d44N4F for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 10:18:39 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id BB6931A0101 for <dnsop@ietf.org>; Tue, 18 Feb 2014 10:18:39 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E67EA1B81D8 for <dnsop@ietf.org>; Tue, 18 Feb 2014 10:18:36 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id C587A190052; Tue, 18 Feb 2014 10:18:36 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 18 Feb 2014 10:18:36 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <B3F1600A-55DA-40E3-8CA1-F133A7A88966@gmail.com>
Date: Tue, 18 Feb 2014 13:18:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <6585245C-D54A-4068-8615-37188BD1D4D0@nominum.com>
References: <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <20140218165710.GD27482@mx1.yitter.info> <B3F1600A-55DA-40E3-8CA1-F133A7A88966@gmail.com>
To: Suzanne Woolf <suzworldwide@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/TudmtoZHdbx3cBQDBJygF99rzAI
Cc: dnsop WG <dnsop@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:18:41 -0000

On Feb 18, 2014, at 12:10 PM, Suzanne Woolf <suzworldwide@gmail.com> =
wrote:
> Is that a problem you (generically, not just Andrew) see as a concern? =
If so, do you see any general principles for navigating it?=20

I certainly think it's an important concern.   We have the same problem =
with DHCP, which is a much simpler protocol.


From nobody Tue Feb 18 10:58:17 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3C81A0513 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 10:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4e4dKT1G2Pd for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 10:58:14 -0800 (PST)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 0F70C1A03ED for <dnsop@ietf.org>; Tue, 18 Feb 2014 10:58:14 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id to1so2245114ieb.2 for <dnsop@ietf.org>; Tue, 18 Feb 2014 10:58:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=K/bftl5+AQ1F1sI+gAf6UzOxnmw+0E+slIQG3Nd4754=; b=DUIIgQw2vi1xRVoLKUQk13XJtcagwlMheVosQ6LItlNBS5/h48fOeb/JIkv9gGHT/h EhEJRd2WmAZ+wddDPQW1qKJj9R4q27aeQrTLjRbdXT/bAR8bW5C07Uqqv1OQ0pK6b+l4 5CXF4S6ok6+PFyhAURr6je5p1Yc4TwJ7enx2k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=K/bftl5+AQ1F1sI+gAf6UzOxnmw+0E+slIQG3Nd4754=; b=VYoph9uw1rI8hu60DlZsI6oGVWYbaitUxzQQ5cbVIpp/AaETrst53z6GwU0UnLuthd a1oyAgoqppoAsRxkIRlaEyrCFf6jsh/P1XmaenR1Ozk7md9/RfO5uLPiNr/1LpKgcEVJ CgpMy3S1wY0KXvTrzp97oYewSPwshUBJHjbVR/MA7TnDYZReVCm1oq11UVovkrEEccXl SQQyIjhgmPG3n3e5sAljBflaVjgrevfkS1q4v26KcgpHZzOLDHV8CRo1wl+taDhjrTnX aELSY+eBXwYpgOrr8Un0WhwBPrfcgQOXhFF991GtZmCFYodygIOKH8tXtc80aTwG80lZ rqlQ==
X-Gm-Message-State: ALoCoQnz7mF44RDyahAhPi1zbOOZ0vuYHbZddxh/ht/a7nwR3wDKV+K/JxpiI5pBpjU7HM3QqRRL
X-Received: by 10.50.132.66 with SMTP id os2mr23212994igb.33.1392749891021; Tue, 18 Feb 2014 10:58:11 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:2866:4c7e:3e97:d8b7? ([2001:4900:1042:1:2866:4c7e:3e97:d8b7]) by mx.google.com with ESMTPSA id rj10sm42745127igc.8.2014.02.18.10.58.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 10:58:09 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_0422C840-287E-4372-A36E-162DDEB7D20C"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6.2.5.6.2.20140218074550.0c380cc8@resistor.net>
Date: Tue, 18 Feb 2014 13:58:08 -0500
Message-Id: <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/a_uRkmyA681WSrrbNhmrI9u-5b4
Cc: dnsop <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:58:16 -0000

--Apple-Mail=_0422C840-287E-4372-A36E-162DDEB7D20C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 2014-02-18, at 10:54, SM <sm@resistor.net> wrote:

> Seriously, it may take some effort to get things deployed but that is =
not an insurmountable task [1].  One of the problems is that there isn't =
any money in doing that.
>=20
> [...]
>=20
> 1. I actually looked into it some time back.=20

I had some experience with this recently with the document that became =
RFC 7043.

Code-point assignment was swift. Implementation in major nameservers was =
swift (although one or two of them left the types commented out in the =
source until the RFC was published). The RFC publication process was not =
arduous, even given the privacy concerns with this particular proposal.

I appreciate that knowing the process made things easier (mainly; I was =
wrong about some things and had to be educated). But I would not =
describe the process as difficult, and certainly not insurmountable.


Joe

--Apple-Mail=_0422C840-287E-4372-A36E-162DDEB7D20C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlMDrUAACgkQNI8MvYZSOizSqwCgv6s3D94Nuh/RdKp3dZmteUfr
tHgAoL/c6U4NksSer7EaAMD9LcpT3AUN
=Gm19
-----END PGP SIGNATURE-----

--Apple-Mail=_0422C840-287E-4372-A36E-162DDEB7D20C--


From nobody Tue Feb 18 14:20:12 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88DD91A026A for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 14:20:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZn8Ym8PZ2uX for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 14:20:07 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 01F171A02BE for <dnsop@ietf.org>; Tue, 18 Feb 2014 14:20:07 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 5A949C941E; Tue, 18 Feb 2014 22:19:51 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1392762004; bh=2M+T+oOx9aO819AIskfkzO9iWqldH32F2rbQjtWhe2A=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=HSI9q26r0hpBrn6XfdYcDbtdlfe1eYkm9cCviyT+m8myDLyN/5zHSNGQ7NrYIguiL EO29LBFQe/dM/h1RKxD+9gq2v1Zv3osjmTtfDb/rYQ8E2mKyDWdV2pP1pzSZGwGugS vYsrv2CvQ96scWlQ+C+qtiX/s48uWN3r2ziGGtSM=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue, 18 Feb 2014 22:19:51 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4309016005B; Tue, 18 Feb 2014 22:20:38 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 094C716000C; Tue, 18 Feb 2014 22:20:38 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id D7541F9EB9C; Wed, 19 Feb 2014 09:19:48 +1100 (EST)
To: Joe Abley <jabley@hopcount.ca>
From: Mark Andrews <marka@isc.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
In-reply-to: Your message of "Tue, 18 Feb 2014 13:58:08 -0500." <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
Date: Wed, 19 Feb 2014 09:19:48 +1100
Message-Id: <20140218221948.D7541F9EB9C@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/GykD6mJC5nTC2P19ao8GKLFoiKo
Cc: SM <sm@resistor.net>, dnsop <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 22:20:11 -0000

In message <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>, Joe Abley writes
:
> On 2014-02-18, at 10:54, SM <sm@resistor.net> wrote:
>
> > Seriously, it may take some effort to get things deployed but that is
> not an insurmountable task [1].  One of the problems is that there isn't
> any money in doing that.
> >
> > [...]
> >
> > 1. I actually looked into it some time back.
>
> I had some experience with this recently with the document that became
> RFC 7043.
>
> Code-point assignment was swift. Implementation in major nameservers was
> swift (although one or two of them left the types commented out in the
> source until the RFC was published). The RFC publication process was not
> arduous, even given the privacy concerns with this particular proposal.
>
> I appreciate that knowing the process made things easier (mainly; I was
> wrong about some things and had to be educated). But I would not describe
> the process as difficult, and certainly not insurmountable.
>
>
> Joe

The process for getting a new type hasn't been *hard* for a decade
now.

Nameserver developers have been deploying new types quickly for
over a decade now.

Recursive servers have had the bugs w.r.t. handling unknown types
removed over a decade ago.

Being able to lookup a unknown type is a REQUIREMENT of RFC 103[45]
and there have been (stub) resolvers that can do this for the entire
life of DNS (Microsoft just fail to ship one).

We defined how to specify UNKNOWN record types in master files a
decade ago and most nameserver vendors have shipped code that support
unknown types for over a decade now.  Microsoft is the obvious
exception.

There are some load balancers that don't handle unknown types
properly.  Lots of these don't handle anything other than A. Not
AAAA, TXT, SOA, NS. These need to be chased down and removed /
replaced / upgraded with extreme prejudice.

There are the stupid DNS administration panels the don't handle
UNKNOWN types or for that matter anything other that A, NS and maybe
AAAA and TXT.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Feb 18 15:08:54 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B311A02B8 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 15:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hGPNUTh854qm for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 15:08:50 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 753241A02AF for <dnsop@ietf.org>; Tue, 18 Feb 2014 15:08:50 -0800 (PST)
Received: from ix-2.local (unknown [88.131.8.202]) by mail.frobbit.se (Postfix) with ESMTPSA id C7AB0226E9; Wed, 19 Feb 2014 00:08:45 +0100 (CET)
Message-ID: <5303E7FD.9030805@frobbit.se>
Date: Wed, 19 Feb 2014 00:08:45 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>, SM <sm@resistor.net>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
In-Reply-To: <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qS6OgWcuKPDONgWvTgMPC2nDAobM7sjnA"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/iKan6zA2pPZScCR54PLwePRr7lg
Cc: dnsop <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 23:08:51 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qS6OgWcuKPDONgWvTgMPC2nDAobM7sjnA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-18 19:58, Joe Abley wrote:
> I appreciate that knowing the process made things easier (mainly; I
> was wrong about some things and had to be educated). But I would not
> describe the process as difficult, and certainly not insurmountable.

Agree, and correct (I did the same with URI RR-Type). But then to start
to define applications using the RR... :-(

   paf


--qS6OgWcuKPDONgWvTgMPC2nDAobM7sjnA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTA+f9rMabGguI180RAqSWAJ9F/f3OWTYyha8/3GVOdjOV5VTs+gCfWXqJ
bl/cnpq2yTwg+iKrsUXYvv4=
=0MeK
-----END PGP SIGNATURE-----

--qS6OgWcuKPDONgWvTgMPC2nDAobM7sjnA--


From nobody Tue Feb 18 15:49:56 2014
Return-Path: <f4t@november.emu.st>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839A71A02DF for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 15:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H6D5Zw7lsZsz for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 15:49:52 -0800 (PST)
Received: from smtp1.bushwire.net (f5.bushwire.net [199.48.133.46]) by ietfa.amsl.com (Postfix) with SMTP id 17B7D1A02DE for <dnsop@ietf.org>; Tue, 18 Feb 2014 15:49:51 -0800 (PST)
Received: (qmail 10470 invoked by uid 1001); 18 Feb 2014 23:49:46 -0000
Delivered-To: qmda-intercept-dnsop@ietf.org
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=s384; d=november.emu.st;  b=oT/PQss85wjFKDv70P3rjbRDe2njXS5t7sVIB0KwCNU6eN0dwl3XPizljhjNEuKB; 
Comments: DomainKeys? See http://en.wikipedia.org/wiki/DomainKeys
DomainKey-Trace-MD: h=22; b=27; l=C18R71D32M65F41M32T18S70?34R80?29?36?53?55?30?49?51?45M17C39C27I57; 
Comments: QMDA 0.3
Received: (qmail 10462 invoked by uid 1001); 18 Feb 2014 23:49:46 -0000
Date: 18 Feb 2014 23:49:46 +0000
Message-ID: <20140218234946.10461.qmail@f5-external.bushwire.net>
From: "Mark Delany" <f4t@november.emu.st>
Mail-Followup-To: dnsop@ietf.org
To: dnsop@ietf.org
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca> <20140218221948.D7541F9EB9C@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20140218221948.D7541F9EB9C@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/ZT_SGy380LsOOISxzaylbnVUxD0
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 23:49:53 -0000

On 19Feb14, Mark Andrews allegedly wrote:
> The process for getting a new type hasn't been *hard* for a decade
> now.
> 
> Nameserver developers have been deploying new types quickly for
> over a decade now.
> 
> Recursive servers have had the bugs w.r.t. handling unknown types
> removed over a decade ago.

Apart from the web-panels I'd say that the biggest bugbear is CPE such
as DSL/cable modems. Having conducted some experiments recently, my
observation is that some of these** have pretty atrocious cache/proxy
implementations. I had to drop the idea of using PTR for a particular
application because one implementation of dnsproxy assumes that PTR is
only ever valid in in-addr.arpa space (it had plenty of other bugs
too, but that's another story).

I see now that some newer CPE defaults to 8.8.8.8 - at least that
eliminates the local implementation bugs...


Mark.

** The irony won't be lost on you, Mark, that your neighbours are
   probably running with that bug since I found it in a popular DSL
   modem sold in Australia/SE Asia.


From nobody Tue Feb 18 16:09:10 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57FE11A0106 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 16:09:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.449
X-Spam-Level: 
X-Spam-Status: No, score=-7.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Q0URFaF98Z5 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 16:09:06 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 755961A020D for <dnsop@ietf.org>; Tue, 18 Feb 2014 16:09:06 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 05CBE2383B6 for <dnsop@ietf.org>; Wed, 19 Feb 2014 00:09:00 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 3FFB416005C for <dnsop@ietf.org>; Wed, 19 Feb 2014 00:09:47 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 0E142160035 for <dnsop@ietf.org>; Wed, 19 Feb 2014 00:09:47 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 2828AF9FC34 for <dnsop@ietf.org>; Wed, 19 Feb 2014 11:08:57 +1100 (EST)
To: dnsop@ietf.org
From: Mark Andrews <marka@isc.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca> <20140218221948.D7541F9EB9C@rock.dv.isc.org> <20140218234946.10461.qmail@f5-external.bushwire.net>
Mail-Followup-To: dnsop@ietf.org
In-reply-to: Your message of "18 Feb 2014 23:49:46 -0000." <20140218234946.10461.qmail@f5-external.bushwire.net>
Date: Wed, 19 Feb 2014 11:08:57 +1100
Message-Id: <20140219000857.2828AF9FC34@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/MSamdJEx7OFwLzCxfMEksehbBrE
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 00:09:08 -0000

In message <20140218234946.10461.qmail@f5-external.bushwire.net>, "Mark Delany"
 writes:
> On 19Feb14, Mark Andrews allegedly wrote:
> > The process for getting a new type hasn't been *hard* for a decade
> > now.
> > 
> > Nameserver developers have been deploying new types quickly for
> > over a decade now.
> > 
> > Recursive servers have had the bugs w.r.t. handling unknown types
> > removed over a decade ago.
> 
> Apart from the web-panels I'd say that the biggest bugbear is CPE such
> as DSL/cable modems. Having conducted some experiments recently, my
> observation is that some of these** have pretty atrocious cache/proxy
> implementations. I had to drop the idea of using PTR for a particular
> application because one implementation of dnsproxy assumes that PTR is
> only ever valid in in-addr.arpa space (it had plenty of other bugs
> too, but that's another story).
> 
> I see now that some newer CPE defaults to 8.8.8.8 - at least that
> eliminates the local implementation bugs...

And I would have gone ahead and implemented it as Autralian Consumer
Law requires a product to be fit for purpose and this modem clearly
wasn't.  The retailer need to refund or replace at the consumers
discression.  Once these !#!@$ boxes get sent back there will be
supply chain presure to fix the problems.

> Mark.
> 
> ** The irony won't be lost on you, Mark, that your neighbours are
>    probably running with that bug since I found it in a popular DSL
>    modem sold in Australia/SE Asia.
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Feb 18 16:19:58 2014
Return-Path: <f4t@november.emu.st>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB40E1A02AC for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 16:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BgwrGw-NEM6d for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 16:19:55 -0800 (PST)
Received: from smtp1.bushwire.net (f5.bushwire.net [199.48.133.46]) by ietfa.amsl.com (Postfix) with SMTP id 51ABB1A00F6 for <dnsop@ietf.org>; Tue, 18 Feb 2014 16:19:54 -0800 (PST)
Received: (qmail 10616 invoked by uid 1001); 19 Feb 2014 00:19:50 -0000
Delivered-To: qmda-intercept-dnsop@ietf.org
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=s384; d=november.emu.st;  b=rXoTOlCRKTxZNp3MHll3lxxPun0GRz8IKI5p1wTj4lSJ3YcXRbjSFo2bUKnlh5g9; 
Comments: DomainKeys? See http://en.wikipedia.org/wiki/DomainKeys
DomainKey-Trace-MD: h=23; b=15; l=C18R71D32M65F41M32T18S70?34R40?36?53?55?30?49?51?45?54?45M17C39C27I57; 
Comments: QMDA 0.3
Received: (qmail 10609 invoked by uid 1001); 19 Feb 2014 00:19:50 -0000
Date: 19 Feb 2014 00:19:50 +0000
Message-ID: <20140219001950.10608.qmail@f5-external.bushwire.net>
From: "Mark Delany" <f4t@november.emu.st>
Mail-Followup-To: dnsop@ietf.org
To: dnsop@ietf.org
References: <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca> <20140218221948.D7541F9EB9C@rock.dv.isc.org> <20140218234946.10461.qmail@f5-external.bushwire.net> <20140219000857.2828AF9FC34@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20140219000857.2828AF9FC34@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/GdwJiWuO3smFL478wflY6do5M4M
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 00:19:57 -0000

> > I see now that some newer CPE defaults to 8.8.8.8 - at least that
> > eliminates the local implementation bugs...
> 
> And I would have gone ahead and implemented it as Autralian Consumer
> Law

Probably true for most jurisdictions running u-verse modems too as
they too had breakage in my (not very fancy) tests.

I eventually went for a try-this-fall-back-to-that strategy. I won't
say which RR I used as the guaranteed-to-work fallback as I might get
a public flogging :-)


Mark.


From nobody Tue Feb 18 17:29:49 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 242CF1A01FC for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 17:29:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ArsZsxEiFaYO for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 17:29:46 -0800 (PST)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id 504AA1A0166 for <dnsop@ietf.org>; Tue, 18 Feb 2014 17:29:46 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id ld10so17590177pab.38 for <dnsop@ietf.org>; Tue, 18 Feb 2014 17:29:43 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=J0kcHQYoT4zPR1Ll+HW0TshyQujt/NNHOz5QznCrQdw=; b=cc00CJ5bdjIuFWRdl2sxGQ/V+oPhk7N6hT3MXOu3E3LWxKeumTAe5shATZOOCu2ZX0 9NBQ4fipRrMo4d7ENXRN/djM6Pji4NMNFYXFPKdPJkghivga/0T1GPE6X1bCiVWXfENS gSomMf9lQiiTUeuoKQtw9yq702+EE5lYcRkl/T/mHoudgEV4ZohRMsjeg7tuvpAdRgP0 CPp8ENdSKtZW9W+i57s0rKG+wMZU2TN9E9OAhKRZ7TJUKjFzScpnOXlK+UXkhzGe47A4 bEwkdQUCHC31C0zVjHKvv6h1kqhbxN/JVIHBxRvjvGe7IjrcJyraTECH7N9ghYntkJht py1Q==
X-Gm-Message-State: ALoCoQnpk+OWMMXH/oPMlBa1xRLeAng1etoHczsG8ulnJ14tOJtZTaCooUxBHw6ID6Hrh6t6jIdL
MIME-Version: 1.0
X-Received: by 10.68.201.226 with SMTP id kd2mr13432923pbc.157.1392773383319;  Tue, 18 Feb 2014 17:29:43 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Tue, 18 Feb 2014 17:29:43 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:9d8d:b63a:d95f:d2a0]
In-Reply-To: <20140218234946.10461.qmail@f5-external.bushwire.net>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca> <20140218221948.D7541F9EB9C@rock.dv.isc.org> <20140218234946.10461.qmail@f5-external.bushwire.net>
Date: Wed, 19 Feb 2014 11:29:43 +1000
Message-ID: <CAKr6gn3FSNEterut_mMtWBzoEPPjoi-EFbiEjcP9UG6n7f9qiw@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8ff1c37ac40f1104f2b8522f
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/xFcG4eZrF2apFvJNJhi3C-Uu8rM
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 01:29:48 -0000

--e89a8ff1c37ac40f1104f2b8522f
Content-Type: text/plain; charset=ISO-8859-1

in OID space, It was my experience that Russ ran the registry pretty
open-minded. Its a classic dewey-decimal growing numberfield, so the cost
burden of carving out a new OID is low, and he was minded to ask basic
questions, steer you, but in the end, assign a unique value for the wider
public benefit.

is there a quality to the RR registry that it HAS TO HAVE a high barrier to
entry? I've never tried proposing a new RR. I don't understand if, compared
to OID, it has a higher compliance, consequence, risk-side..

-G

--e89a8ff1c37ac40f1104f2b8522f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">in OID space, It was my experience that Russ ran the regis=
try pretty open-minded. Its a classic dewey-decimal growing numberfield, so=
 the cost burden of carving out a new OID is low, and he was minded to ask =
basic questions, steer you, but in the end, assign a unique value for the w=
ider public benefit.<div>
<br></div><div>is there a quality to the RR registry that it HAS TO HAVE a =
high barrier to entry? I&#39;ve never tried proposing a new RR. I don&#39;t=
 understand if, compared to OID, it has a higher compliance, consequence, r=
isk-side..</div>
<div><br></div><div>-G</div></div>

--e89a8ff1c37ac40f1104f2b8522f--


From nobody Tue Feb 18 18:25:13 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3D51A03CF for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 18:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mKhiOo_k_JsK for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 18:25:09 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 198F11A031B for <dnsop@ietf.org>; Tue, 18 Feb 2014 18:25:09 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 187ACC9423; Wed, 19 Feb 2014 02:24:52 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1392776706; bh=xkcJ9VTPZn/amj/yTRpZDggpi1PXbB3hihwhMhhWAq8=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=kluze480JLm8PluahYvbB5fTz/+rLBzordSX9W9IcOlGdAX4bReit117mOHRJJLot WMObKSYhDtsFnVtMdy2dKaGPVFOh+L2zTzq0KCzfXOISfhPASC2S1IAvJd+D8rl+HY VzLrlytMj9ij1JI1eNPrYJ52wlqt2rIYyxxUrHvE=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 19 Feb 2014 02:24:52 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id E276116005C; Wed, 19 Feb 2014 02:25:39 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id B4408160035; Wed, 19 Feb 2014 02:25:39 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 056ADFA91E9; Wed, 19 Feb 2014 13:24:50 +1100 (EST)
To: George Michaelson <ggm@algebras.org>
From: Mark Andrews <marka@isc.org>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca> <20140218221948.D7541F9EB9C@rock.dv.isc.org> <20140218234946.10461.qmail@f5-external.bushwire.net> <CAKr6gn3FSNEterut_mMtWBzoEPPjoi-EFbiEjcP9UG6n7f9qiw@mail.gmail.com>
In-reply-to: Your message of "Wed, 19 Feb 2014 11:29:43 +1000." <CAKr6gn3FSNEterut_mMtWBzoEPPjoi-EFbiEjcP9UG6n7f9qiw@mail.gmail.com>
Date: Wed, 19 Feb 2014 13:24:50 +1100
Message-Id: <20140219022450.056ADFA91E9@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/E1wL1_O6Ajz4tC04Y_TXOSIVmA0
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 02:25:11 -0000

In message <CAKr6gn3FSNEterut_mMtWBzoEPPjoi-EFbiEjcP9UG6n7f9qiw@mail.gmail.com>
, George Michaelson writes:
> 
> in OID space, It was my experience that Russ ran the registry pretty
> open-minded. Its a classic dewey-decimal growing numberfield, so the cost
> burden of carving out a new OID is low, and he was minded to ask basic
> questions, steer you, but in the end, assign a unique value for the wider
> public benefit.
> 
> is there a quality to the RR registry that it HAS TO HAVE a high barrier to
> entry? I've never tried proposing a new RR. I don't understand if, compared
> to OID, it has a higher compliance, consequence, risk-side..

What high barrier to entry?  Fill out a form and you get it basically
provided you meet the minimal criteria.  You can choose a experimental
type to test code with while you are waiting to the value to be assigned.

	http://tools.ietf.org/html/rfc6895
 
> -G
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Feb 18 20:25:06 2014
Return-Path: <sm@resistor.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21F2C1A030F for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 20:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0iRQaM0WaqkC for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 20:25:03 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F301A0129 for <dnsop@ietf.org>; Tue, 18 Feb 2014 20:25:03 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1J4OeGw006431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Feb 2014 20:24:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392783891; bh=3oCdE7q9Km10nhsRCBWg2WUSKYevHTDI6GPEouGoi64=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MXXa1RsJ0WsXqsHcuIncrNQOSmk6diY2OPICf3J+766KHVc7MiuC+1BGd2r2Arcek K+3vF5WUhc0CqCnvYz+IAeT0js6dPvxqR69N4yMy9tmc8xKD2v50xxoB4SNsOJsqvr E+GT2lwznWSpyp5mtwYhbT7a2g6wkHNDyprbpWpw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1392783891; i=@resistor.net; bh=3oCdE7q9Km10nhsRCBWg2WUSKYevHTDI6GPEouGoi64=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=g21AFKoFp1E3RyT87vLlsAAA4nYMwMg+rv2NnV1vtR0DavVfIraL1G0C7BH7gx8FV vC7j2/HF/mqYBUbeovbiCe1KBPPkhBDW91F1u8b0y7Z63kpBtlogBpeamar3hqzpQ/ k9ySxj4MJ9YOtzWO5L0OWAlhgonWiyTb9GXsDbd0=
Message-Id: <6.2.5.6.2.20140218192425.0b333900@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 18 Feb 2014 19:41:09 -0800
To: Joe Abley <jabley@hopcount.ca>
From: SM <sm@resistor.net>
In-Reply-To: <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net> <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/dTL2VrOetmHzqDFKrsBMo0WkEOE
Cc: dnsop <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 04:25:05 -0000

Hi Joe,
At 10:58 18-02-2014, Joe Abley wrote:
>I had some experience with this recently with the document that 
>became RFC 7043.
>
>Code-point assignment was swift. Implementation in major nameservers 
>was swift (although one or two of them left the types commented out 
>in the source until the RFC was published). The RFC publication 
>process was not arduous, even given the privacy concerns with this 
>particular proposal.
>
>I appreciate that knowing the process made things easier (mainly; I 
>was wrong about some things and had to be educated). But I would not 
>describe the process as difficult, and certainly not insurmountable.

I was not thinking of the IETF process.  Mark Andrews covered what I 
was thinking of in a message at 
http://www.ietf.org/mail-archive/web/dnsop/current/msg11173.html

Regards,
-sm 


From john@johnbond.org  Thu Feb 20 13:18:45 2014
Return-Path: <john@johnbond.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49F7F1A02FF for <dnsop@ietfa.amsl.com>; Thu, 20 Feb 2014 13:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EN0Bgu7y7qu9 for <dnsop@ietfa.amsl.com>; Thu, 20 Feb 2014 13:18:42 -0800 (PST)
Received: from ns.johnbond.org (ns.johnbond.org [IPv6:2a00:d1e0:1000:a00::53]) by ietfa.amsl.com (Postfix) with ESMTP id D71951A02F3 for <dnsop@ietf.org>; Thu, 20 Feb 2014 13:18:41 -0800 (PST)
Received: from [109.129.211.92] (helo=[192.168.1.32]) by ns.johnbond.org with esmtpsa (TLSv1:DES-CBC3-SHA:168) (Exim 4.80.1 (FreeBSD)) (envelope-from <john@johnbond.org>) id 1WGb0g-000A21-U5; Thu, 20 Feb 2014 16:18:23 -0500
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Thu, 20 Feb 2014 22:18:09 +0100
From: John Bond <mail@johnbond.org>
To: David Conrad <drc@virtualized.org>, George Michaelson <ggm@algebras.org>
Message-ID: <CF2C2E77.67FD%mail@johnbond.org>
Thread-Topic: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com> <24C0A347-0230-4760-9E49-05F701A11AE2@virtualized.org>
In-Reply-To: <24C0A347-0230-4760-9E49-05F701A11AE2@virtualized.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Sender: john@johnbond.org
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/PtVLgjRADmhGEN0sWehmhoUfrds
X-Mailman-Approved-At: Thu, 20 Feb 2014 14:29:04 -0800
Cc: draft-wkumari-dnsop-alt-tld@tools.ietf.org, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 21:19:58 -0000

-----Original Message-----
From: David Conrad <drc@virtualized.org>
Date: Thursday 13 February 2014 02:48
To: George Michaelson <ggm@algebras.org>
Cc: <draft-wkumari-dnsop-alt-tld@tools.ietf.org>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt

>
>Has anyone asked the folks coding .ONION (or others) if they're willing
>to migrate, pointing out the downsides if they choose not to?
Hopefully this response will help.

https://lists.torproject.org/pipermail/tor-dev/2014-February/006238.html



From nobody Thu Feb 20 14:36:45 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEEF81A0105 for <dnsop@ietfa.amsl.com>; Thu, 20 Feb 2014 14:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O_ymnxJDprfA for <dnsop@ietfa.amsl.com>; Thu, 20 Feb 2014 14:36:41 -0800 (PST)
Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by ietfa.amsl.com (Postfix) with ESMTP id 568EA1A0215 for <dnsop@ietf.org>; Thu, 20 Feb 2014 14:36:41 -0800 (PST)
Received: by mail-pb0-f46.google.com with SMTP id um1so2550791pbc.33 for <dnsop@ietf.org>; Thu, 20 Feb 2014 14:36:37 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=5bF+zpWDCB+mNrB2h1bckhsWwtHxGKxpsvUb67uy+gw=; b=L11LaFkXN6JoG0KDt0IXaIuhuooBtXWT/0KVgwjKjpKPCmqBsUquAJGcPJxCUY0h0k ofe0w0b/Lp0g/qPHrq1fAQ6osopcs1Aa4XbOLMlE7OV/9Atm8jmr1NLVgH4K57i7v+9m Wdj73yxXwRYZoqB0FV3GTHLpNTw8kmrvNGf/diN5T7gxjNvpJksxELHNysaSE5y1wycl wcVj/ax/dnkNg+6MIrhCeR/Z5NWjbiHs7qGG9NDu23fwlO2wWciYQT1mPFc6fhBVX5Jy o0u3KqciLdV59s94Xm00mc6OCX1fSnklBZqL2+a545Nx5Dd3HkGjWpol5PxRqONUqCJy SGmQ==
X-Gm-Message-State: ALoCoQkZDQogFdWCffQkp5oVXui6KMRCHIZe4Fy5Vxl4FjF+uBrtXG/2vHfgqH2sSlYT3wW3rTmz
MIME-Version: 1.0
X-Received: by 10.67.23.135 with SMTP id ia7mr4873951pad.5.1392935797690; Thu, 20 Feb 2014 14:36:37 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Thu, 20 Feb 2014 14:36:37 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:900d:45f8:cc65:b46c]
In-Reply-To: <CF2C2E77.67FD%mail@johnbond.org>
References: <20140210205838.15973.63281.idtracker@ietfa.amsl.com> <E63B37B9-EFA0-43A5-9AC5-81CEC23C342C@viagenie.ca> <00BDA580-984F-41D1-8659-04278737A526@hopcount.ca> <CAKr6gn1fjJG=pgYbu7oDEOo+g1PQruRid5HRD3NTRiXVUFmSHw@mail.gmail.com> <24C0A347-0230-4760-9E49-05F701A11AE2@virtualized.org> <CF2C2E77.67FD%mail@johnbond.org>
Date: Fri, 21 Feb 2014 08:36:37 +1000
Message-ID: <CAKr6gn3YSJOnX0Np3Z4kZZZ1g=9=4UUY8bxD6MqZ9Kvdte7MAg@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: John Bond <mail@johnbond.org>
Content-Type: multipart/alternative; boundary=001a1134519a6aaf0404f2de2354
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/OuNX9PtZlmyAVClco_uN9bNmvqc
Cc: draft-wkumari-dnsop-alt-tld@tools.ietf.org, dnsop <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 22:36:44 -0000

--001a1134519a6aaf0404f2de2354
Content-Type: text/plain; charset=ISO-8859-1

I suspect both sides of the argument about the tractability of change in
systems will be saying SEE I TOLD YOU SO.

It will be clear from my input, that I see this as a positive signal the
.onion community understand the problem, understand the migration and are
prepared in principle to discuss it.

HELL NO and WE CAN'T aren't words in that post.

-G



On Fri, Feb 21, 2014 at 7:18 AM, John Bond <mail@johnbond.org> wrote:

>
>
> -----Original Message-----
> From: David Conrad <drc@virtualized.org>
> Date: Thursday 13 February 2014 02:48
> To: George Michaelson <ggm@algebras.org>
> Cc: <draft-wkumari-dnsop-alt-tld@tools.ietf.org>, dnsop <dnsop@ietf.org>
> Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
>
> >
> >Has anyone asked the folks coding .ONION (or others) if they're willing
> >to migrate, pointing out the downsides if they choose not to?
> Hopefully this response will help.
>
> https://lists.torproject.org/pipermail/tor-dev/2014-February/006238.html
>
>
>

--001a1134519a6aaf0404f2de2354
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I suspect both sides of the argument about the tractabilit=
y of change in systems will be saying SEE I TOLD YOU SO.=A0<div><br></div><=
div>It will be clear from my input, that I see this as a positive signal th=
e .onion community understand the problem, understand the migration and are=
 prepared in principle to discuss it.</div>
<div><br></div><div>HELL NO and WE CAN&#39;T aren&#39;t words in that post.=
</div><div><br></div><div>-G</div><div><br></div></div><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">On Fri, Feb 21, 2014 at 7:18 AM, =
John Bond <span dir=3D"ltr">&lt;<a href=3D"mailto:mail@johnbond.org" target=
=3D"_blank">mail@johnbond.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
-----Original Message-----<br>
From: David Conrad &lt;<a href=3D"mailto:drc@virtualized.org">drc@virtualiz=
ed.org</a>&gt;<br>
Date: Thursday 13 February 2014 02:48<br>
To: George Michaelson &lt;<a href=3D"mailto:ggm@algebras.org">ggm@algebras.=
org</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:draft-wkumari-dnsop-alt-tld@tools.ietf.org">draft=
-wkumari-dnsop-alt-tld@tools.ietf.org</a>&gt;, dnsop &lt;<a href=3D"mailto:=
dnsop@ietf.org">dnsop@ietf.org</a>&gt;<br>
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt<br>
<br>
&gt;<br>
&gt;Has anyone asked the folks coding .ONION (or others) if they&#39;re wil=
ling<br>
&gt;to migrate, pointing out the downsides if they choose not to?<br>
Hopefully this response will help.<br>
<br>
<a href=3D"https://lists.torproject.org/pipermail/tor-dev/2014-February/006=
238.html" target=3D"_blank">https://lists.torproject.org/pipermail/tor-dev/=
2014-February/006238.html</a><br>
<br>
<br>
</blockquote></div><br></div>

--001a1134519a6aaf0404f2de2354--


From nobody Fri Feb 21 08:41:40 2014
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E901A01EC for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 08:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.739
X-Spam-Level: 
X-Spam-Status: No, score=-1.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXICXMqbIVlM for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 08:41:34 -0800 (PST)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 49CC91A01BF for <dnsop@ietf.org>; Fri, 21 Feb 2014 08:41:34 -0800 (PST)
Received: by mail-qg0-f43.google.com with SMTP id f51so8162166qge.2 for <dnsop@ietf.org>; Fri, 21 Feb 2014 08:41:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=rIx1qHtAcnxOr0w3B6I+3E2s9tXLqtpfteHl59c/J2c=; b=eWWKKakJj5znT/N74diUT0PkKcgZrtM+/W1R4v/f3SPhJKRCP5yjMR1bTdbxgavdKq tp1KzmmhuQZLd7rLaAn93NowM/NR/ipfNdwDGjpY5l45JjDs2kXDL55Ctat2v396gSf+ rIgzNYwKO8g2kbw4Edgaz5J/qHa+JHuiKP1YJMLfpgFB3J+pS7dViFhkMjHDb8KXUEZx aUKk38IG1physqvYcwY3m1qeGpRJUhHkyxZvRCZaz8+yesYiIJAl7OYgS4ZIZFm8frjB 1gzJ6fMxJpvfa5+b2XInlCtlHb273glyNC+gLeZYGKPzY07JEzy7xU5cKf+F5WS29NoP DIvw==
X-Received: by 10.140.26.240 with SMTP id 103mr10734973qgv.92.1393000890149; Fri, 21 Feb 2014 08:41:30 -0800 (PST)
Received: from [10.33.0.214] ([204.14.236.215]) by mx.google.com with ESMTPSA id p10sm23202133qag.8.2014.02.21.08.41.29 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Feb 2014 08:41:29 -0800 (PST)
Message-ID: <530781B9.7070004@gmail.com>
Date: Fri, 21 Feb 2014 11:41:29 -0500
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dnsop@ietf.org
Content-Type: multipart/alternative; boundary="------------070100010307010802020901"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Mwz-fCFkm_sT4OdZGD2yXvHL1VI
Subject: [DNSOP] Preliminary agenda for IETF89, London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 16:41:38 -0000

This is a multi-part message in MIME format.
--------------070100010307010802020901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Note, this is a draft and we've been shuffling around the format some.  
If we left you off we did so out of error so drop us a note. Even with 
the longer time, the first rule of meetings does seem to apply: the 
talking will be expanded to fill the allotted time.

http://www.ietf.org/proceedings/89/agenda/agenda-89-dnsop

-------

WG:                     DNS Operations (dnsop)
Meeting:                IETF 89, London
Location:               Hilton Metropole, Sovereign
Date:                   Friday, 7 March 2014
Time:                   0900-1130 GMT
Chairs:                 Tim Wicinski <tjw.ietf@gmail.com>
                         Suzanne Woolf <suzworldwide@gmail.com>




0)        Introduction


1)        Administrivia, Blue Sheets, etc. (10min)


         Overview of meeting structure        (chairs)


2)         Status Updates (30 minutes)
         (Business we need to move along)


         2.1) AS112 updates,  Abley (10 min)
                 draft-ietf-dnsop-as112-dname
		draft-jabley-dnsop-rfc6304bis
                         *Reviewers Needed*


         2.2) DNSSEC Key Exchanges, Hardaker, Kumari, et. al (10 min)
                 draft-ietf-dnsop-child-syncronization
                 draft-ietf-dnsop-delegation-trust-maintainance


         2.3) DNS Referral Response Size Issues (5)
                 draft-ietf-dnsop-respsize
                         *open questions* *Reviewers Needed*


         2.4) Initializing a DNS Resolver with Priming Queries, Koch (5)
                 draft-ietf-dnsop-resolver-priming
                         *open questions* *Reviewers Needed*


3)        New Business


         3.1) Privacy and Confidentiality of DNS.


         	DNSE BOF summary, Bortzmeyer (5 min)


		a) Requirements (10 min)
		draft-bortzmeyer-dnsop-dns-privacy
		draft-koch-perpass-dns-confidentiality
		draft-wijngaards-dnsop-confidentialdns



		b) Solution Space  (10 min)
		draft-rafiee-intarea-cga-tsig
		draft-wijngaards-dnsop-confidentialdns
		draft-bortzmeyer-dnsop-privacy-sol


		c) Next Steps?
         	Not entirely inside *current* charter, but we do have a contribution to make....


	3.2) Special Names (15 min)


         	Chairs' summary (5 min)
         	Discussion: DNSOP role
                 existing requests/RFC 6761 process:
                         draft-grothoff-iesg-special-use-p2p-names
                         draft-chapin-additional-reserved-tlds
                 new drafts:
			draft-wkumari-dnsop-alt-tld
			draft-ogud-appsawg-multiple-namespaces
                 room for improvement?




4)         Non Actionable DNS Extensions
		(The Andrew Sullivan Memorial)


         4.1) TLS over DNS, Zi, (10 min)
                 draft-hzhwm-start-tls-for-dns


         4.2) EDNS Option updates, Wouters (5min)
                 draft-wouters-edns-tcp-keepalive
                 draft-wouters-edns-tcp-chain-query


         4.3) DNS Cookies, Eastlake
                 draft-eastlake-dnsext-cookies




5) Charter Discussion  (30 min)


         Watch this space for content


6) New Business


	6.1) Passive DNS,  (5 min)
		draft-dulaunoy-kaplan-passive-dns-cof


	6.2) DNSSEC Validator Requirements (5 min)
		draft-mglt-dnsop-dnssec-validator-requirements




7) After Meeting Reading



--------------070100010307010802020901
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>Note, this is a draft and we've been shuffling around the </tt><tt>format
      some.&nbsp; If we left you off we did so out of error so drop us a note</tt><tt>.&nbsp;&nbsp;
      Even with the longer time, the first rule of </tt><tt>meetings </tt><tt>does
      seem to apply</tt><tt>: </tt><tt>the t</tt><tt>al</tt><tt>king
      will be expanded to fi</tt><tt>ll the a</tt><tt>llot</tt><tt>ted
      tim</tt><tt>e. </tt><tt><br>
    </tt><tt><br>
    </tt><tt><a class="moz-txt-link-freetext" href="http://www.ietf.org/proceedings/89/agenda/agenda-89-dnsop">http://www.ietf.org/proceedings/89/agenda/agenda-89-dnsop</a></tt><tt><br>
    </tt><tt><br>
      -------<br>
    </tt>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre>WG:                     DNS Operations (dnsop)
Meeting:                IETF 89, London
Location:               Hilton Metropole, Sovereign
Date:                   Friday, 7 March 2014
Time:                   0900-1130 GMT
Chairs:                 Tim Wicinski <a class="moz-txt-link-rfc2396E" href="mailto:tjw.ietf@gmail.com">&lt;tjw.ietf@gmail.com&gt;</a>
                        Suzanne Woolf <a class="moz-txt-link-rfc2396E" href="mailto:suzworldwide@gmail.com">&lt;suzworldwide@gmail.com&gt;</a>




0)        Introduction


1)        Administrivia, Blue Sheets, etc. (10min)


        Overview of meeting structure        (chairs)


2)         Status Updates (30 minutes)
        (Business we need to move along)


        2.1) AS112 updates,  Abley (10 min)
                draft-ietf-dnsop-as112-dname
		draft-jabley-dnsop-rfc6304bis
                        *Reviewers Needed*


        2.2) DNSSEC Key Exchanges, Hardaker, Kumari, et. al (10 min)
                draft-ietf-dnsop-child-syncronization
                draft-ietf-dnsop-delegation-trust-maintainance


        2.3) DNS Referral Response Size Issues (5)
                draft-ietf-dnsop-respsize
                        *open questions* *Reviewers Needed*


        2.4) Initializing a DNS Resolver with Priming Queries, Koch (5)
                draft-ietf-dnsop-resolver-priming
                        *open questions* *Reviewers Needed*


3)        New Business 


        3.1) Privacy and Confidentiality of DNS. 


        	DNSE BOF summary, Bortzmeyer (5 min)


		a) Requirements (10 min)
		draft-bortzmeyer-dnsop-dns-privacy
		draft-koch-perpass-dns-confidentiality
		draft-wijngaards-dnsop-confidentialdns



		b) Solution Space  (10 min)
		draft-rafiee-intarea-cga-tsig 
		draft-wijngaards-dnsop-confidentialdns
		draft-bortzmeyer-dnsop-privacy-sol


		c) Next Steps?
        	Not entirely inside *current* charter, but we do have a contribution to make&#8230;.


	3.2) Special Names (15 min)


        	Chairs&#8217; summary (5 min)
        	Discussion: DNSOP role
                existing requests/RFC 6761 process:
                        draft-grothoff-iesg-special-use-p2p-names
                        draft-chapin-additional-reserved-tlds
                new drafts: 
			draft-wkumari-dnsop-alt-tld
			draft-ogud-appsawg-multiple-namespaces
                room for improvement?




4)         Non Actionable DNS Extensions
		(The Andrew Sullivan Memorial)


        4.1) TLS over DNS, Zi, (10 min)
                draft-hzhwm-start-tls-for-dns


        4.2) EDNS Option updates, Wouters (5min)
                draft-wouters-edns-tcp-keepalive
                draft-wouters-edns-tcp-chain-query


        4.3) DNS Cookies, Eastlake
                draft-eastlake-dnsext-cookies




5) Charter Discussion  (30 min)


        Watch this space for content


6) New Business


	6.1) Passive DNS,  (5 min)
		draft-dulaunoy-kaplan-passive-dns-cof


	6.2) DNSSEC Validator Requirements (5 min)
		draft-mglt-dnsop-dnssec-validator-requirements




7) After Meeting Reading</pre>
    <tt><br>
    </tt>
  </body>
</html>

--------------070100010307010802020901--


From nobody Fri Feb 21 09:17:57 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A857C1A02D0 for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 09:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3AvN67SDFuvg for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 09:17:52 -0800 (PST)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D118F1A01BF for <dnsop@ietf.org>; Fri, 21 Feb 2014 09:17:51 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id c9so6117291qcz.15 for <dnsop@ietf.org>; Fri, 21 Feb 2014 09:17:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:message-id:date:to:mime-version; bh=Q+5ORYs8ajnIrFxvUkZZTeSjnvU/UGCbnH4WA/awh6o=; b=PeLyAlz4Hv+RF/EXYhoSwSG6Dw5xdBL36rFjoi2QawDp+aFt4z0LRk3x9FGrjmwMIK waKqUOlBlE2bYVrWfFGc2Pb8BgCB0/NS1FW2irvrluJFtWXGPcMxFRU6EyaNyLAcHoCl UGYK9yl2ODtXC+0NDDxaHCJXbO++1YpV5YFl00FM7NHz+X0wRe6Oq6UtUS3tqvnRCSTB aWB/FK8VnuKLasmTURWWWPf9fwc40K+JyVKsKgwP3atT+uHmPSkbMnpl3F2qajC/cNAx t9U81MQelKqQvWSCACCmtU2z+WhGmNfxf1L5S2Eco48ROKzxM1ynA7LEfrrHtI834NN/ d/1w==
X-Received: by 10.140.91.228 with SMTP id z91mr11129041qgd.32.1393003067738; Fri, 21 Feb 2014 09:17:47 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id z18sm23459804qab.5.2014.02.21.09.17.46 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Feb 2014 09:17:46 -0800 (PST)
From: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_75454918-A9F3-4FAB-A010-E403C1C7D1CD"
Message-Id: <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>
Date: Fri, 21 Feb 2014 12:17:50 -0500
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/e154LBSsSfXNgxb1O1zZAcjQeuM
Subject: [DNSOP] summary of WG current status
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 17:17:55 -0000

--Apple-Mail=_75454918-A9F3-4FAB-A010-E403C1C7D1CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dear Colleagues,

As we look towards the meeting in London, we have several items in =
progress, which we've organized here from the most specific and =
administratively simple tasks to the broadest discussion topics.

Not everything called out here is on the London agenda, but we=92ve =
tried to round up everything that=92s in progress as work for the WG, =
formally or (in a few cases) informally. We expect to send this out =
periodically, not least so people have a chance to call us on it if we =
drop stuff.

thanks,
Your Chairs


=46rom our existing charter:

1. RESPSIZE draft =
(http://datatracker.ietf.org/doc/draft-ietf-dnsop-respsize/)
    This item has been in our charter for a very long time, and was at =
one time considered almost ready for publication but stalled there. =
There's been recent interest in dusting it off and getting it shipped, =
and with the help of the previous authors and a new volunteer, a new =
version has been published. It=92s been suggested  we might want to add =
some more material on DNSSEC and EDNS0, since the previous version only =
dealt extensively with the impact on referral size of adding AAAA =
records and the bulk of the document was written before the root was =
signed or ICANN's registry contracts were written to require DNSSEC for =
new gTLDs.

Agenda in London: flag open items, get reviewers, get a timeline for =
finishing


2. PRIMING draft =
(http://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/)
    We=92ve also got a new rev of this draft so we can resolve the open =
questions and get this published also. =20

Agenda in London: flag open items, get reviewers, get a timeline for =
finishing

3. AS112 operations:
    http://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/ (WG =
item)
    http://datatracker.ietf.org/doc/draft-jabley-dnsop-rfc6304bis/ (new)

    Some additional =93bits and pieces=94 re: AS112 operations. We need =
reviewers to move forward with the DNAME one, and for 6304bis if we want =
to adopt it.

    Agenda in London: determine momentum for getting these reviewed, =
revised, and published. If not they will be dropped.

4. CDS and related: what are we doing about the topic of DNSSEC in-band =
key maintenance? This has previously been somewhat contentious and seems =
to have stalled without resolution. We now have current versions of two =
drafts and would like to make progress on resolving differences.
=
http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintain=
ance/
http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/

5. 100.64.0.0/10 to reserved list
http://datatracker.ietf.org/doc/draft-andrews-dnsop-rfc6598-rfc6303/
Stalled in WGLC on an administrative issue of overlapping IANA =
registries. Chairs will review discussion and propose a way forward =
soon; no WG action required


NEW TOPICS:
Passive DNS data format: =
http://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/: =
needs review, call for adoption
Authority server placement: no i-d yet; agenda time requested, needs =
review

FOR DISCUSSION, including possible charter revision:

1. Privacy drafts
    There are *at least* four i-ds and a BOF in London specifically for =
discussion of privacy and confidentiality with regards to the protocol =
and operations of DNS:=20

        Stephane Bortzmeyer's problem statement draft =
(http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-dns-privacy/) is =
reasonably on-charter for us.=20
        Stephane's solutions draft =
http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-privacy-sol/)
        Peter Koch's draft on information leakage in the DNS =
(http://datatracker.ietf.org/doc/draft-koch-perpass-dns-confidentiality/)
        Wouter Wijngaards' draft on opportunistic encryption in the DNS =
(http://datatracker.ietf.org/doc/draft-wijngaards-dnsop-confidentialdns/)=20=

(plus a few other documents)

We need to decide what we think a useful contribution on this broad =
topic would be for DNSOP. Stephane's problem statement draft seems =
in-scope and we'd like to call for adoption. Protocol changes as =
described in two of the drafts probably need a new WG. In between, this =
topic provides an opportunity for us to consider reasonable updates to =
our charter given evident demand from the community to examine DNS in =
light of current privacy concerns.=20
	** This is a major item for the agenda in London; please come =
prepared to discuss **

2. Special names
    There are two current drafts requesting additions to the Special Use =
Names registry as per RFC 6761, =
http://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/=
 and =
http://datatracker.ietf.org/doc/draft-chapin-additional-reserved-tlds/. =
The process described in RFC 6761 calls for "IESG action," and the IESG =
has asked for DNSOP input, including that we consider adopting these =
drafts as WG items. We have already had some discussion on these drafts, =
and the current process, based on RFC 6761, makes whether to add these =
names to the registry the IESG=92s decision. We will continue to discuss =
these drafts on the mailing list and provide our advice/observations to =
the IESG.

    There is some interest separately in the broader architectural =
concerns around =93what should we do with requests/needs for namespaces =
that look like DNS names, but aren=92t?=94 As it looks like these uses =
of DNS-like namespaces by non-DNS protocols will continue to evolve, and =
the RFC 6761 process already seems problematic, we need to consider =
whether there=92s work to be done in fine-tuning the IETF=92s response =
to these requests from protocol developers who are trying to do the =
right thing, don=92t want to simply appropriate namespaces a priori, but =
are not actually trying to do DNS protocol or operations and simply want =
to avoid incompatibility.
    http://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/
    =
https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-namespaces/


DNSEXT discussions
- tcp keep-alives
- tcp query-chaining
- DNS cookies
- TLS for DNS

DNS Cookies & TLS for DNS

Donald Eastlake has generated a new version of the DNS Cookies draft, =
which incorporated many comments.  Several other contributors have also =
written a new draft on the use of TLS for DNS over TCP. While these are =
out of scope, we feel with the privacy and confidentiality work =
swirling,  there seems to be room to at least have the discussion.


New charter

DNSOP has been around for awhile, without a recent charter revision even =
as topics including privacy, root zone expansion, and changes in the =
operational environment have become increasingly important. Our Esteemed =
AD has been very open with us pulling things in for discussion, =
especially if there are operational impacts from such things.  We're =
working on a new charter that would include a couple of specific items =
the WG has already adopted or considered, and a shift in scope to allow =
DNSOP to provide a home for problem statements related to DNS in much =
the way v6ops does for the IPv6-related groups and issues. Your =
suggestions are appreciated.

	** This is a major item for the agenda in London; please come =
prepared to discuss **=

--Apple-Mail=_75454918-A9F3-4FAB-A010-E403C1C7D1CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">Dear Colleagues,<br class=3D"kix-line-break"><br =
class=3D"kix-line-break">As we look towards the meeting in London, we =
have several items in progress, which we've organized here from the most =
specific and administratively simple tasks to the broadest discussion =
topics.</span></div><br><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; "></span><div style=3D"line-height: =
1.15; margin-top: 0pt; margin-bottom: 0pt; "><span style=3D"font-size: =
15px; font-family: Arial; vertical-align: baseline; ">Not everything =
called out here is on the London agenda, but we=92ve tried to round up =
everything that=92s in progress as work for the WG, formally or (in a =
few cases) informally. We expect to send this out periodically, not =
least so people have a chance to call us on it if we drop =
stuff.</span></div><br><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; "></span><div style=3D"margin-top: 0pt; =
margin-bottom: 0pt; "><font face=3D"Arial"><span style=3D"font-size: =
15px; line-height: 17px;">thanks,</span></font></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">Your Chairs</span></div><br><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; "></span><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"><br class=3D"kix-line-break">=46rom our existing charter:<br =
class=3D"kix-line-break"><br class=3D"kix-line-break">1. RESPSIZE draft =
(<a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-dnsop-respsize/">http:/=
/datatracker.ietf.org/doc/draft-ietf-dnsop-respsize/</a>)<br =
class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; This item has been in our =
charter for a very long time, and was at one time considered almost =
ready for publication but stalled there. There's been recent interest in =
dusting it off and getting it shipped, and with the help of the previous =
authors and a new volunteer, a new version has been published. It=92s =
been suggested &nbsp;we might want to add some more material on DNSSEC =
and EDNS0, since the previous version only dealt extensively with the =
impact on referral size of adding AAAA records and the bulk of the =
document was written before the root was signed or ICANN's registry =
contracts were written to require DNSSEC for new =
gTLDs.</span></div><br><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; "></span><div style=3D"line-height: =
1.15; margin-top: 0pt; margin-bottom: 0pt; text-indent: 36pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">Agenda in London: flag open items, get reviewers, get a timeline for =
finishing<br class=3D"kix-line-break"><br class=3D"kix-line-break"><br =
class=3D"kix-line-break">2. PRIMING draft (<a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/=
">http://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/</a>)<=
br class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; We=92ve also got a new =
rev of this draft so we can resolve the open questions and get this =
published also. &nbsp;</span></div><br><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; "></span><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; =
text-indent: 36pt; "><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">Agenda in London: flag open items, get =
reviewers, get a timeline for finishing</span></div><br><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"></span><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">3. AS112 operations:</span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">&nbsp;&nbsp;&nbsp; </span><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/" =
style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/</span></a>=
<span style=3D"font-size: 15px; font-family: Arial; vertical-align: =
baseline; "> (WG item)</span></div><div style=3D"line-height: 1.15; =
margin-top: 0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; ">&nbsp;&nbsp;&nbsp; =
</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-jabley-dnsop-rfc6304bis/" =
style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-jabley-dnsop-rfc6304bis/</span></a=
><span style=3D"font-size: 15px; font-family: Arial; vertical-align: =
baseline; "> (new)</span></div><br><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; "></span><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">&nbsp;&nbsp;&nbsp; Some additional =93bits and pieces=94 re: AS112 =
operations. We need reviewers to move forward with the DNAME one, and =
for 6304bis if we want to adopt it. </span></div><br><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"></span><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">&nbsp;&nbsp;&nbsp; Agenda in London: =
determine momentum for getting these reviewed, revised, and published. =
If not they will be dropped.</span></div><div style=3D"line-height: =
1.15; margin-top: 0pt; margin-bottom: 0pt; text-indent: 36pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"><br class=3D"kix-line-break">4. CDS and related: what are we doing =
about the topic of DNSSEC in-band key maintenance? This has previously =
been somewhat contentious and seems to have stalled without resolution. =
We now have current versions of two drafts and would like to make =
progress on resolving differences.</span></div><div style=3D"line-height: =
1.15; margin-top: 0pt; margin-bottom: 0pt; text-indent: 36pt; "><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-=
maintainance/" style=3D"text-decoration:none;"><span style=3D"font-size: =
15px; font-family: Arial; color: rgb(17, 85, 204); text-decoration: =
underline; vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-mainta=
inance/</span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; "></span></div><div style=3D"line-height: =
1.15; margin-top: 0pt; margin-bottom: 0pt; text-indent: 36pt; "><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronizat=
ion/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/</=
span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; "></span></div><br><span style=3D"font-size: =
15px; font-family: Arial; vertical-align: baseline; "></span><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">5. 100.64.0.0/10 to reserved list</span></div><div style=3D"line-height:=
 1.15; margin-top: 0pt; margin-bottom: 0pt; text-indent: 36pt; "><a =
href=3D"http://datatracker.ietf.org/doc/draft-andrews-dnsop-rfc6598-rfc630=
3/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-andrews-dnsop-rfc6598-rfc6303/</sp=
an></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; "></span></div><div style=3D"line-height: =
1.15; margin-top: 0pt; margin-bottom: 0pt; text-indent: 36pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">Stalled in WGLC on an administrative issue of overlapping IANA =
registries. Chairs will review discussion and propose a way forward =
soon; no WG action required</span></div><div style=3D"line-height: 1.15; =
margin-top: 0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; "><br =
class=3D"kix-line-break"><br class=3D"kix-line-break">NEW =
TOPICS:</span></div><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">Passive DNS data format: </span><a =
href=3D"http://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-=
cof/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/</=
span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">: needs review, call for =
adoption</span></div><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">Authority server placement: no i-d =
yet; agenda time requested, needs review</span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"><br class=3D"kix-line-break">FOR DISCUSSION, including possible =
charter revision:<br class=3D"kix-line-break"><br =
class=3D"kix-line-break">1. Privacy drafts<br =
class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; There are *at least* four =
i-ds and a BOF in London specifically for discussion of privacy and =
confidentiality with regards to the protocol and operations of DNS: <br =
class=3D"kix-line-break"><br class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; Stephane Bortzmeyer's problem statement draft =
(</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-dns-privacy=
/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-dns-privacy/</spa=
n></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">) is reasonably on-charter for us. <br =
class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
Stephane's solutions draft</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-privacy-sol=
/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(0, 0, 0); vertical-align: baseline; "> =
</span><span style=3D"font-size: 15px; font-family: Arial; color: =
rgb(17, 85, 204); text-decoration: underline; vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-privacy-sol/</spa=
n></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">)<br =
class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Peter =
Koch's draft on information leakage in the DNS (</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-koch-perpass-dns-confidentia=
lity/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-koch-perpass-dns-confidentiality/<=
/span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">)<br =
class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Wouter =
Wijngaards' draft on opportunistic encryption in the DNS (</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-wijngaards-dnsop-confidentia=
ldns/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-wijngaards-dnsop-confidentialdns/<=
/span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">) <br =
class=3D"kix-line-break"></span></div><div style=3D"line-height: 1.15; =
margin-top: 0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; ">(plus a few other =
documents)</span></div><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; "><br class=3D"kix-line-break">We need =
to decide what we think a useful contribution on this broad topic would =
be for DNSOP. Stephane's problem statement draft seems in-scope and we'd =
like to call for adoption. Protocol changes as described in two of the =
drafts probably need a new WG. In between, this topic provides an =
opportunity for us to consider reasonable updates to our charter given =
evident demand from the community to examine DNS in light of current =
privacy concerns.&nbsp;</span></div><div style=3D"line-height: 1.15; =
margin-top: 0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>** This =
is a major item for the agenda in London; please come prepared to =
discuss **<br class=3D"kix-line-break"><br class=3D"kix-line-break">2. =
Special names<br class=3D"kix-line-break">&nbsp;&nbsp;&nbsp; There are =
two current drafts requesting additions to the Special Use Names =
registry as per RFC 6761,</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2=
p-names/" style=3D"text-decoration:none;"><span style=3D"font-size: =
15px; font-family: Arial; color: rgb(0, 0, 0); vertical-align: baseline; =
"> </span><span style=3D"font-size: 15px; font-family: Arial; color: =
rgb(17, 85, 204); text-decoration: underline; vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-name=
s/</span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; "> and</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-chapin-additional-reserved-t=
lds/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(0, 0, 0); vertical-align: baseline; "> =
</span><span style=3D"font-size: 15px; font-family: Arial; color: =
rgb(17, 85, 204); text-decoration: underline; vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-chapin-additional-reserved-tlds/</=
span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">. The process described in RFC 6761 calls =
for "IESG action," and the IESG has asked for DNSOP input, including =
that we consider adopting these drafts as WG items. We have already had =
some discussion on these drafts, and the current process, based on RFC =
6761, makes whether to add these names to the registry the IESG=92s =
decision. We will continue to discuss these drafts on the mailing list =
and provide our advice/observations to the IESG.</span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"><br></span></div><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">&nbsp;&nbsp;&nbsp; There is some =
interest separately in the broader architectural concerns around =93what =
should we do with requests/needs for namespaces that look like DNS =
names, but aren=92t?=94 As it looks like these uses of DNS-like =
namespaces by non-DNS protocols will continue to evolve, and the RFC =
6761 process already seems problematic, we need to consider whether =
there=92s work to be done in fine-tuning the IETF=92s response to these =
requests from protocol developers who are trying to do the right thing, =
don=92t want to simply appropriate namespaces a priori, but are not =
actually trying to do DNS protocol or operations and simply want to =
avoid incompatibility.</span></div><div style=3D"line-height: 1.15; =
margin-top: 0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; ">&nbsp;&nbsp;&nbsp; =
</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/" =
style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">http://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/</span></a><=
span style=3D"font-size: 15px; font-family: Arial; vertical-align: =
baseline; "></span></div><div style=3D"line-height: 1.15; margin-top: =
0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">&nbsp;&nbsp;&nbsp; </span><a =
href=3D"https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-names=
paces/" style=3D"text-decoration:none;"><span style=3D"font-size: 15px; =
font-family: Arial; color: rgb(17, 85, 204); text-decoration: underline; =
vertical-align: baseline; =
">https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-namespaces/=
</span></a><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; "></span></div><br><span style=3D"font-size: =
15px; font-family: Arial; vertical-align: baseline; "></span><br><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"></span><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">DNSEXT discussions</span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; =
text-indent: 36pt; "><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">- tcp keep-alives</span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; =
margin-left: 36pt; "><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">- tcp query-chaining</span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; =
margin-left: 36pt; "><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">- DNS cookies</span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; =
margin-left: 36pt; "><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; ">- TLS for DNS</span></div><br><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"></span><div style=3D"line-height: 1.15; margin-top: 0pt; =
margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; ">DNS Cookies &amp; TLS for =
DNS</span></div><br><span style=3D"font-size: 15px; font-family: Arial; =
vertical-align: baseline; "></span><div style=3D"line-height: 1.15; =
margin-top: 0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; ">Donald Eastlake has =
generated a new version of the DNS Cookies draft, which incorporated =
many comments. &nbsp;Several other contributors have also written a new =
draft on the use of TLS for DNS over TCP. While these are out of scope, =
we feel with the privacy and confidentiality work swirling, &nbsp;there =
seems to be room to at least have the discussion. =
</span></div><div><br></div><br><span style=3D"font-size: 15px; =
font-family: Arial; vertical-align: baseline; "></span><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
">New charter<br class=3D"kix-line-break"><br =
class=3D"kix-line-break">DNSOP has been around for awhile, without a =
recent charter revision even as topics including privacy, root zone =
expansion, and changes in the operational environment have become =
increasingly important. Our Esteemed AD has been very open with us =
pulling things in for discussion, especially if there are operational =
impacts from such things. &nbsp;We're working on a new charter that =
would include a couple of specific items the WG has already adopted or =
considered, and a shift in scope to allow DNSOP to provide a home for =
problem statements related to DNS in much the way v6ops does for the =
IPv6-related groups and issues. Your suggestions are =
appreciated.</span></div><div style=3D"line-height: 1.15; margin-top: =
0pt; margin-bottom: 0pt; "><span style=3D"font-size: 15px; font-family: =
Arial; vertical-align: baseline; "><br></span></div><div =
style=3D"line-height: 1.15; margin-top: 0pt; margin-bottom: 0pt; "><span =
style=3D"font-size: 15px; font-family: Arial; vertical-align: baseline; =
"><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>** This is a major item for the agenda in London; please come =
prepared to discuss **</span></div></body></html>=

--Apple-Mail=_75454918-A9F3-4FAB-A010-E403C1C7D1CD--


From nobody Fri Feb 21 09:29:48 2014
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6651F1A019C for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 09:29:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YmN0t_W7bAFu for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 09:29:45 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id A8C221A044C for <dnsop@ietf.org>; Fri, 21 Feb 2014 09:29:45 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 73EFE800AA; Fri, 21 Feb 2014 12:29:40 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1393003780; bh=wxccomgy9MvWtcZ9/H6Yo61E/GEecM9u7rRZUCTORps=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=WSSOB7MKGvTdQTG7+7r3Gbwr9aU42+5bWTCcmXdK+EwiRagPebHXQstdNEKocz3e/ 1VTOsWaTVz3rWlGnO9i/S5L7hRkTfU5ztVhqN9p5X03EsT/oh1bvNe9yNIvM6YGIeg 64YwvFsy6xYyBj94H/AqXnbWns3Ep7PL4hc3yb0I=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s1LHTe16028778; Fri, 21 Feb 2014 12:29:40 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Fri, 21 Feb 2014 12:29:40 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Tim Wicinski <tjw.ietf@gmail.com>
In-Reply-To: <530781B9.7070004@gmail.com>
Message-ID: <alpine.LFD.2.10.1402211227190.19817@bofh.nohats.ca>
References: <530781B9.7070004@gmail.com>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/6Q3npyVaGzZktNMwg3ti4GGfJ_Q
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Preliminary agenda for IETF89, London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 17:29:47 -0000

On Fri, 21 Feb 2014, Tim Wicinski wrote:

> 3)        New Business 
>
>         3.1) Privacy and Confidentiality of DNS.

> 		b) Solution Space  (10 min)
> 		draft-rafiee-intarea-cga-tsig
> 		draft-wijngaards-dnsop-confidentialdns
> 		draft-bortzmeyer-dnsop-privacy-sol

> 4)         Non Actionable DNS Extensions
> 		(The Andrew Sullivan Memorial)
>
>         4.1) TLS over DNS, Zi, (10 min)
>                 draft-hzhwm-start-tls-for-dns

Why is TLS for DNS (not 'TLS over DNS') not listed at 3.1?

Paul


From nobody Fri Feb 21 09:54:35 2014
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 577CC1A0225 for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 09:54:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H2wJwFXUJL43 for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 09:54:30 -0800 (PST)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7841A019C for <dnsop@ietf.org>; Fri, 21 Feb 2014 09:54:30 -0800 (PST)
Received: by mail-qa0-f42.google.com with SMTP id k4so3776693qaq.29 for <dnsop@ietf.org>; Fri, 21 Feb 2014 09:54:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5f9pmREOsF+hAlGuOVGe3DUEboFeaiTQLw0Ywd/t/hA=; b=gTxt+ByK91M0dLuElq/yb7GuAyKs9p3k84PwAIvAvHfRN6gg+U+Q+A65jC0pZ8/Ftm rZf4y9EuXwIxogA5/IUpEMCrBETzJDoNZamZg7TXPq3tx3/HdqAzpWc/lu4bx7eIzuek eMH/rhAATtgYc/q5ildO3usy1CgpbBK7n62wtZeYWt7VvI6uvq1SE3uIN2xp2KMZAbWt BVK/T6hx8KdUUmfFkX7SRBDvkLHdWpWGoOld0UPFQDPft6dvg+xG3eh7PwMnu+dmIxme +BBA7Z9yoHsjjK/kU0yc/e5Qms+CDN0hzyqQuWWrQ2WILtF9wKvHhbeSvJSMdGpjGQNZ /qTA==
X-Received: by 10.140.88.180 with SMTP id t49mr11374970qgd.97.1393005266087; Fri, 21 Feb 2014 09:54:26 -0800 (PST)
Received: from [10.33.0.214] ([204.14.236.215]) by mx.google.com with ESMTPSA id q3sm23669372qam.12.2014.02.21.09.54.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Feb 2014 09:54:25 -0800 (PST)
Message-ID: <530792D0.5050409@gmail.com>
Date: Fri, 21 Feb 2014 12:54:24 -0500
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Paul Wouters <paul@nohats.ca>
References: <530781B9.7070004@gmail.com> <alpine.LFD.2.10.1402211227190.19817@bofh.nohats.ca>
In-Reply-To: <alpine.LFD.2.10.1402211227190.19817@bofh.nohats.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/QMQrf1giDvUn9y5Iue0asR8rdDU
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Preliminary agenda for IETF89, London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 17:54:32 -0000

On 2/21/14, 12:29 PM, Paul Wouters wrote:
> On Fri, 21 Feb 2014, Tim Wicinski wrote:
>
>> 3)        New Business
>>         3.1) Privacy and Confidentiality of DNS.
>
>>         b) Solution Space  (10 min)
>>         draft-rafiee-intarea-cga-tsig
>>         draft-wijngaards-dnsop-confidentialdns
>>         draft-bortzmeyer-dnsop-privacy-sol
>
>> 4)         Non Actionable DNS Extensions
>>         (The Andrew Sullivan Memorial)
>>
>>         4.1) TLS over DNS, Zi, (10 min)
>>                 draft-hzhwm-start-tls-for-dns
>
> Why is TLS for DNS (not 'TLS over DNS') not listed at 3.1?
>
> Paul

Paul

While it definitely has privacy implications, it's also involves the 
dreaded 'protocol changes', which chases it into a grey area that while 
I'm very willing to dabble in, leaves some purists with a bad taste in 
their mouth.

Personally, I think its an inspired idea, especially when you look at 
all the tcpm and httpbis work on speeding up connections.   I'm willing 
to push this forward as well,  though I started it there to at least not 
forget it.

tim



From nobody Fri Feb 21 12:07:07 2014
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27E0D1A026C for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 12:07:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M_ulvyFhDc2R for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 12:07:03 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 53EE11A0267 for <dnsop@ietf.org>; Fri, 21 Feb 2014 12:07:03 -0800 (PST)
Received: from ix-2.local (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id B25232270D; Fri, 21 Feb 2014 21:06:58 +0100 (CET)
Message-ID: <5307B1E2.4040004@frobbit.se>
Date: Fri, 21 Feb 2014 21:06:58 +0100
From: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Suzanne Woolf <suzworldwide@gmail.com>,  "dnsop@ietf.org WG" <dnsop@ietf.org>
References: <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>
In-Reply-To: <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8qFP260E8vIrhc9grpStc7LjSWUUiOjwc"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/3D7J0twffxjNk35wdRWIwEAqGH0
Subject: Re: [DNSOP] summary of WG current status
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 20:07:06 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--8qFP260E8vIrhc9grpStc7LjSWUUiOjwc
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

WOW! This could be a week of meetings...

I guess it is not time to fold yet... :-P

   Patrik

On 2014-02-21 18:17, Suzanne Woolf wrote:
> Dear Colleagues,
>=20
> As we look towards the meeting in London, we have several items in
> progress, which we've organized here from the most specific and
> administratively simple tasks to the broadest discussion topics.
>=20
> Not everything called out here is on the London agenda, but we=92ve tri=
ed
> to round up everything that=92s in progress as work for the WG, formall=
y
> or (in a few cases) informally. We expect to send this out periodically=
,
> not least so people have a chance to call us on it if we drop stuff.
>=20
> thanks,
> Your Chairs
>=20
>=20
> From our existing charter:
>=20
> 1. RESPSIZE draft
> (http://datatracker.ietf.org/doc/draft-ietf-dnsop-respsize/)
>     This item has been in our charter for a very long time, and was at
> one time considered almost ready for publication but stalled there.
> There's been recent interest in dusting it off and getting it shipped,
> and with the help of the previous authors and a new volunteer, a new
> version has been published. It=92s been suggested  we might want to add=

> some more material on DNSSEC and EDNS0, since the previous version only=

> dealt extensively with the impact on referral size of adding AAAA
> records and the bulk of the document was written before the root was
> signed or ICANN's registry contracts were written to require DNSSEC for=

> new gTLDs.
>=20
> Agenda in London: flag open items, get reviewers, get a timeline for
> finishing
>=20
>=20
> 2. PRIMING draft
> (http://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/)
>     We=92ve also got a new rev of this draft so we can resolve the open=

> questions and get this published also. =20
>=20
> Agenda in London: flag open items, get reviewers, get a timeline for
> finishing
>=20
> 3. AS112 operations:
>     http://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/(WG it=
em)
>     http://datatracker.ietf.org/doc/draft-jabley-dnsop-rfc6304bis/(new)=

>=20
>     Some additional =93bits and pieces=94 re: AS112 operations. We need=

> reviewers to move forward with the DNAME one, and for 6304bis if we wan=
t
> to adopt it.
>=20
>     Agenda in London: determine momentum for getting these reviewed,
> revised, and published. If not they will be dropped.
>=20
> 4. CDS and related: what are we doing about the topic of DNSSEC in-band=

> key maintenance? This has previously been somewhat contentious and seem=
s
> to have stalled without resolution. We now have current versions of two=

> drafts and would like to make progress on resolving differences.
> http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maint=
ainance/
> http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/
>=20
> 5. 100.64.0.0/10 to reserved list
> http://datatracker.ietf.org/doc/draft-andrews-dnsop-rfc6598-rfc6303/
> Stalled in WGLC on an administrative issue of overlapping IANA
> registries. Chairs will review discussion and propose a way forward
> soon; no WG action required
>=20
>=20
> NEW TOPICS:
> Passive DNS data format:
> http://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/:=

> needs review, call for adoption
> Authority server placement: no i-d yet; agenda time requested, needs re=
view
>=20
> FOR DISCUSSION, including possible charter revision:
>=20
> 1. Privacy drafts
>     There are *at least* four i-ds and a BOF in London specifically for=

> discussion of privacy and confidentiality with regards to the protocol
> and operations of DNS:
>=20
>         Stephane Bortzmeyer's problem statement draft
> (http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-dns-privacy/) i=
s
> reasonably on-charter for us.
>         Stephane's solutions
> drafthttp://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-privacy-sol=
/)
>         Peter Koch's draft on information leakage in the DNS
> (http://datatracker.ietf.org/doc/draft-koch-perpass-dns-confidentiality=
/)
>         Wouter Wijngaards' draft on opportunistic encryption in the DNS=

> (http://datatracker.ietf.org/doc/draft-wijngaards-dnsop-confidentialdns=
/)
> (plus a few other documents)
>=20
> We need to decide what we think a useful contribution on this broad
> topic would be for DNSOP. Stephane's problem statement draft seems
> in-scope and we'd like to call for adoption. Protocol changes as
> described in two of the drafts probably need a new WG. In between, this=

> topic provides an opportunity for us to consider reasonable updates to
> our charter given evident demand from the community to examine DNS in
> light of current privacy concerns.=20
> ** This is a major item for the agenda in London; please come prepared
> to discuss **
>=20
> 2. Special names
>     There are two current drafts requesting additions to the Special Us=
e
> Names registry as per RFC
> 6761,http://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2=
p-names/andhttp://datatracker.ietf.org/doc/draft-chapin-additional-reserv=
ed-tlds/.
> The process described in RFC 6761 calls for "IESG action," and the IESG=

> has asked for DNSOP input, including that we consider adopting these
> drafts as WG items. We have already had some discussion on these drafts=
,
> and the current process, based on RFC 6761, makes whether to add these
> names to the registry the IESG=92s decision. We will continue to discus=
s
> these drafts on the mailing list and provide our advice/observations to=

> the IESG.
>=20
>     There is some interest separately in the broader architectural
> concerns around =93what should we do with requests/needs for namespaces=

> that look like DNS names, but aren=92t?=94 As it looks like these uses =
of
> DNS-like namespaces by non-DNS protocols will continue to evolve, and
> the RFC 6761 process already seems problematic, we need to consider
> whether there=92s work to be done in fine-tuning the IETF=92s response =
to
> these requests from protocol developers who are trying to do the right
> thing, don=92t want to simply appropriate namespaces a priori, but are =
not
> actually trying to do DNS protocol or operations and simply want to
> avoid incompatibility.
>     http://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/
>     https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-namesp=
aces/
>=20
>=20
> DNSEXT discussions
> - tcp keep-alives
> - tcp query-chaining
> - DNS cookies
> - TLS for DNS
>=20
> DNS Cookies & TLS for DNS
>=20
> Donald Eastlake has generated a new version of the DNS Cookies draft,
> which incorporated many comments.  Several other contributors have also=

> written a new draft on the use of TLS for DNS over TCP. While these are=

> out of scope, we feel with the privacy and confidentiality work
> swirling,  there seems to be room to at least have the discussion.
>=20
>=20
> New charter
>=20
> DNSOP has been around for awhile, without a recent charter revision eve=
n
> as topics including privacy, root zone expansion, and changes in the
> operational environment have become increasingly important. Our Esteeme=
d
> AD has been very open with us pulling things in for discussion,
> especially if there are operational impacts from such things.  We're
> working on a new charter that would include a couple of specific items
> the WG has already adopted or considered, and a shift in scope to allow=

> DNSOP to provide a home for problem statements related to DNS in much
> the way v6ops does for the IPv6-related groups and issues. Your
> suggestions are appreciated.
>=20
> ** This is a major item for the agenda in London; please come prepared
> to discuss **
>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20



--8qFP260E8vIrhc9grpStc7LjSWUUiOjwc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTB7HirMabGguI180RAni1AJ97yqQbNCNPM1MRfOUGzvKHeIDnfwCeOzR+
93peYeuywGH7MevI9frbOio=
=xgZ7
-----END PGP SIGNATURE-----

--8qFP260E8vIrhc9grpStc7LjSWUUiOjwc--


From nobody Fri Feb 21 13:06:27 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CF521A023F for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 13:06:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yY6AD1LLEQjI for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 13:06:20 -0800 (PST)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by ietfa.amsl.com (Postfix) with ESMTP id 882E81A01F7 for <dnsop@ietf.org>; Fri, 21 Feb 2014 13:06:20 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id cc10so1275493wib.10 for <dnsop@ietf.org>; Fri, 21 Feb 2014 13:06:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=v4/bG4dP9sbk52ROqvj3tcw1VoUBAKfXOb+caCo6kkU=; b=TAPgoV3GpVuatHaK9QnIsIjJf3y6E2xDAyMs25Pe9uy++U8RSqZ/gEI/qm8vii5cW8 OVnAmZ8uGs3fHvOoyEE1jCh57Elb4NqZGXBioeWd4DWURO4UH+geM7vTPHf3/n0atGkp Hxne0USCfoTSDI7zKbTaBaGtAJQAza0fw9R9kzUAMU54iOBCLz+feMDwP96REj5eSupp hbk5Oi6/X6qNul0tYi8WUJpazYD9ekjGGdsFqd1vtaBsaRKek5zYpOXly4rc4jZssL12 FPMFBDHL/gLWYZUDgp4WEgZ45f6Yl4loRldM3VG6Bpv+l3p1xF/4GQogR+0WfAzYoSTF RvDA==
X-Gm-Message-State: ALoCoQmYJYGtdiVgjuNkH8y631mPRjbGIlHNWSAbEKeydxzGN3HPfTphfwVLNTeO80a6E2dq37NN
MIME-Version: 1.0
X-Received: by 10.195.13.103 with SMTP id ex7mr8843262wjd.3.1393016775925; Fri, 21 Feb 2014 13:06:15 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Fri, 21 Feb 2014 13:06:15 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>
References: <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>
Date: Fri, 21 Feb 2014 16:06:15 -0500
Message-ID: <CAHw9_i+seEcn_CxPF_YHM+AL7iJ9L66fJyCH45tPGSd2KEpq2A@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/ZukAE7FhQS_H77o3ntREhJ9FP7g
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] summary of WG current status
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 21:06:25 -0000

On Fri, Feb 21, 2014 at 12:17 PM, Suzanne Woolf <suzworldwide@gmail.com> wrote:
> Dear Colleagues,
>
> As we look towards the meeting in London, we have several items in progress,
> which we've organized here from the most specific and administratively
> simple tasks to the broadest discussion topics.
>
> Not everything called out here is on the London agenda, but we've tried to
> round up everything that's in progress as work for the WG, formally or (in a
> few cases) informally. We expect to send this out periodically, not least so
> people have a chance to call us on it if we drop stuff.
>
> thanks,
> Your Chairs
>
>
> From our existing charter:
>
> 1. RESPSIZE draft
> (http://datatracker.ietf.org/doc/draft-ietf-dnsop-respsize/)
>     This item has been in our charter for a very long time, and was at one
> time considered almost ready for publication but stalled there. There's been
> recent interest in dusting it off and getting it shipped, and with the help
> of the previous authors and a new volunteer, a new version has been
> published. It's been suggested  we might want to add some more material on
> DNSSEC and EDNS0, since the previous version only dealt extensively with the
> impact on referral size of adding AAAA records and the bulk of the document
> was written before the root was signed or ICANN's registry contracts were
> written to require DNSSEC for new gTLDs.
>
> Agenda in London: flag open items, get reviewers, get a timeline for
> finishing
>
>
> 2. PRIMING draft
> (http://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming/)
>     We've also got a new rev of this draft so we can resolve the open
> questions and get this published also.
>
> Agenda in London: flag open items, get reviewers, get a timeline for
> finishing
>
> 3. AS112 operations:
>     http://datatracker.ietf.org/doc/draft-ietf-dnsop-as112-dname/ (WG item)
>     http://datatracker.ietf.org/doc/draft-jabley-dnsop-rfc6304bis/ (new)
>
>     Some additional "bits and pieces" re: AS112 operations. We need
> reviewers to move forward with the DNAME one, and for 6304bis if we want to
> adopt it.
>
>     Agenda in London: determine momentum for getting these reviewed,
> revised, and published. If not they will be dropped.
>
> 4. CDS and related: what are we doing about the topic of DNSSEC in-band key
> maintenance? This has previously been somewhat contentious and seems to have
> stalled without resolution. We now have current versions of two drafts and
> would like to make progress on resolving differences.
> http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintainance/
> http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/

We don't think that there are differences -- they are *complementary*,
not *competing*.
They solve related, but different problems.

From: http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintainance/
"  The solution described in this document only allows transferring
   information about DNSSEC keys (DS and DNSKEY) from the child to the
   parental agent.  It lists exactly what the parent should publish, and
   allows for publication of stand-by keys.  A different protocol,
   [I-D.csync], can be used to maintain other important delegation
   information, such as NS and glue.  These two protocols have been kept
   as separate solutions because the problems are fundamentally
   different, and a combined solution is overly complex."
and:
   "Special thanks to Wes Hardaker for contributing significant text and
   creating the complementary (CSYNC) solution, and to Paul Hoffman and
   Mukund Sivaraman for text and review."


And from: http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/
   "This specification does not address how to perform bootstrapping
   operations to get the required initial DNSSEC-secured operating
   environment in place.  Additionally, this specification was not
   designed to synchronize DNSSEC security records, such as DS pointers.
   For such a solution, please see the complimentary solution
   [I-D.kumari-ogud-dnsop-cds] for maintaining security delegation
   information."
and:
   "A thank you goes out to Warren Kumari and Olafur Gu[eth]mundsson,
   who's work on the CDS record type helped inspire the work in this
   document, as well as the definition for "Parental Agent" and "DNS
   Publisher" definitions. "

There is no monkey knife fight here -- we are all one big happy family.
The CDS authors believe we have integrated all the suggestions and
addressed the questions and would like to go to WGLC.

W



>
> 5. 100.64.0.0/10 to reserved list
> http://datatracker.ietf.org/doc/draft-andrews-dnsop-rfc6598-rfc6303/
> Stalled in WGLC on an administrative issue of overlapping IANA registries.
> Chairs will review discussion and propose a way forward soon; no WG action
> required
>
>
> NEW TOPICS:
> Passive DNS data format:
> http://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/:
> needs review, call for adoption
> Authority server placement: no i-d yet; agenda time requested, needs review
>
> FOR DISCUSSION, including possible charter revision:
>
> 1. Privacy drafts
>     There are *at least* four i-ds and a BOF in London specifically for
> discussion of privacy and confidentiality with regards to the protocol and
> operations of DNS:
>
>         Stephane Bortzmeyer's problem statement draft
> (http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-dns-privacy/) is
> reasonably on-charter for us.
>         Stephane's solutions draft
> http://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-privacy-sol/)
>         Peter Koch's draft on information leakage in the DNS
> (http://datatracker.ietf.org/doc/draft-koch-perpass-dns-confidentiality/)
>         Wouter Wijngaards' draft on opportunistic encryption in the DNS
> (http://datatracker.ietf.org/doc/draft-wijngaards-dnsop-confidentialdns/)
> (plus a few other documents)
>
> We need to decide what we think a useful contribution on this broad topic
> would be for DNSOP. Stephane's problem statement draft seems in-scope and
> we'd like to call for adoption. Protocol changes as described in two of the
> drafts probably need a new WG. In between, this topic provides an
> opportunity for us to consider reasonable updates to our charter given
> evident demand from the community to examine DNS in light of current privacy
> concerns.
> ** This is a major item for the agenda in London; please come prepared to
> discuss **
>
> 2. Special names
>     There are two current drafts requesting additions to the Special Use
> Names registry as per RFC 6761,
> http://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/
> and http://datatracker.ietf.org/doc/draft-chapin-additional-reserved-tlds/.
> The process described in RFC 6761 calls for "IESG action," and the IESG has
> asked for DNSOP input, including that we consider adopting these drafts as
> WG items. We have already had some discussion on these drafts, and the
> current process, based on RFC 6761, makes whether to add these names to the
> registry the IESG's decision. We will continue to discuss these drafts on
> the mailing list and provide our advice/observations to the IESG.
>
>     There is some interest separately in the broader architectural concerns
> around "what should we do with requests/needs for namespaces that look like
> DNS names, but aren't?" As it looks like these uses of DNS-like namespaces
> by non-DNS protocols will continue to evolve, and the RFC 6761 process
> already seems problematic, we need to consider whether there's work to be
> done in fine-tuning the IETF's response to these requests from protocol
> developers who are trying to do the right thing, don't want to simply
> appropriate namespaces a priori, but are not actually trying to do DNS
> protocol or operations and simply want to avoid incompatibility.
>     http://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/
>     https://datatracker.ietf.org/doc/draft-ogud-appsawg-multiple-namespaces/
>
>
> DNSEXT discussions
> - tcp keep-alives
> - tcp query-chaining
> - DNS cookies
> - TLS for DNS
>
> DNS Cookies & TLS for DNS
>
> Donald Eastlake has generated a new version of the DNS Cookies draft, which
> incorporated many comments.  Several other contributors have also written a
> new draft on the use of TLS for DNS over TCP. While these are out of scope,
> we feel with the privacy and confidentiality work swirling,  there seems to
> be room to at least have the discussion.
>
>
> New charter
>
> DNSOP has been around for awhile, without a recent charter revision even as
> topics including privacy, root zone expansion, and changes in the
> operational environment have become increasingly important. Our Esteemed AD
> has been very open with us pulling things in for discussion, especially if
> there are operational impacts from such things.  We're working on a new
> charter that would include a couple of specific items the WG has already
> adopted or considered, and a shift in scope to allow DNSOP to provide a home
> for problem statements related to DNS in much the way v6ops does for the
> IPv6-related groups and issues. Your suggestions are appreciated.
>
> ** This is a major item for the agenda in London; please come prepared to
> discuss **
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>


From nobody Fri Feb 21 13:41:14 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E2311A0293 for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 13:41:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYL1e0jDW26e for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2014 13:41:11 -0800 (PST)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id C5C4A1A02CF for <dnsop@ietf.org>; Fri, 21 Feb 2014 13:41:10 -0800 (PST)
Received: by mail-qa0-f52.google.com with SMTP id j15so3973280qaq.39 for <dnsop@ietf.org>; Fri, 21 Feb 2014 13:41:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MEaWf0dLsvlZH1FYjNwk03CSnZDCJpjGCYX1XPhCYnw=; b=C5ul/h33+oiMQVcSFqsK1rFsBJt77r9MiUTah4L9vBLSdG4CHQovAwM2KnVsePpomh mbX+r2NerSzDNgjZrPpblMN/2cd3zbcd0q5nqf356vpUMBoZJ//MxKlfLPCY+AuwHs+R P2+s8FEVmkEDY8LNMkgspZEfsAqATTTcRUMQoYNhJLoZTMkB+D54ElDew3HndRPCWYXB oUCAT5IVwmLcqE8mIQPhP3BuSGmk+wYLGjphAz3dgoG/sX2/wmrl7axZDizqyhXQlwBj 5C7fxXIeg7DMsLcdvosl84aeAlB6fnF6NZT/c56e+957mgiItCJNER8SCVdh13UYmrwx zQEA==
X-Received: by 10.140.83.203 with SMTP id j69mr12683338qgd.42.1393018866694; Fri, 21 Feb 2014 13:41:06 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id g36sm558573qge.7.2014.02.21.13.41.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Feb 2014 13:41:04 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <CAHw9_i+seEcn_CxPF_YHM+AL7iJ9L66fJyCH45tPGSd2KEpq2A@mail.gmail.com>
Date: Fri, 21 Feb 2014 16:41:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E93C2D1-477A-4E6D-8FA2-D74FDA94CA3F@gmail.com>
References: <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com> <CAHw9_i+seEcn_CxPF_YHM+AL7iJ9L66fJyCH45tPGSd2KEpq2A@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/YQCsfPnzagU1U-MKlsy-o-mF4l8
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] summary of WG current status
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 21:41:13 -0000

Warren,

You're right-- our apologies for a misunderstanding combined with a bad =
edit in the summary as sent.

Both drafts are on the agenda for London, so you (all the authors) can =
do an update if you feel it's necessary, and we'll move them ahead for =
final review/WGLC.

Thanks for your attention and helping us get it right :)

best,
Your Chairs

On Feb 21, 2014, at 4:06 PM, Warren Kumari <warren@kumari.net> wrote:

> On Fri, Feb 21, 2014 at 12:17 PM, Suzanne Woolf =
<suzworldwide@gmail.com> wrote:
>> Dear Colleagues,
>>=20
>> 4. CDS and related: what are we doing about the topic of DNSSEC =
in-band key
>> maintenance? This has previously been somewhat contentious and seems =
to have
>> stalled without resolution. We now have current versions of two =
drafts and
>> would like to make progress on resolving differences.
>> =
http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintain=
ance/
>> =
http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/
>=20
> We don't think that there are differences -- they are *complementary*,
> not *competing*.
> They solve related, but different problems.
>=20
> From: =
http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintain=
ance/
> "  The solution described in this document only allows transferring
>   information about DNSSEC keys (DS and DNSKEY) from the child to the
>   parental agent.  It lists exactly what the parent should publish, =
and
>   allows for publication of stand-by keys.  A different protocol,
>   [I-D.csync], can be used to maintain other important delegation
>   information, such as NS and glue.  These two protocols have been =
kept
>   as separate solutions because the problems are fundamentally
>   different, and a combined solution is overly complex."
> and:
>   "Special thanks to Wes Hardaker for contributing significant text =
and
>   creating the complementary (CSYNC) solution, and to Paul Hoffman and
>   Mukund Sivaraman for text and review."
>=20
>=20
> And from: =
http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/
>   "This specification does not address how to perform bootstrapping
>   operations to get the required initial DNSSEC-secured operating
>   environment in place.  Additionally, this specification was not
>   designed to synchronize DNSSEC security records, such as DS =
pointers.
>   For such a solution, please see the complimentary solution
>   [I-D.kumari-ogud-dnsop-cds] for maintaining security delegation
>   information."
> and:
>   "A thank you goes out to Warren Kumari and Olafur Gu[eth]mundsson,
>   who's work on the CDS record type helped inspire the work in this
>   document, as well as the definition for "Parental Agent" and "DNS
>   Publisher" definitions. "
>=20
> There is no monkey knife fight here -- we are all one big happy =
family.
> The CDS authors believe we have integrated all the suggestions and
> addressed the questions and would like to go to WGLC.
>=20
> W


From nobody Sat Feb 22 13:43:16 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7F461A0198 for <dnsop@ietfa.amsl.com>; Sat, 22 Feb 2014 13:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHnoOnDXBEfj for <dnsop@ietfa.amsl.com>; Sat, 22 Feb 2014 13:43:12 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by ietfa.amsl.com (Postfix) with ESMTP id 8CEF91A0180 for <dnsop@ietf.org>; Sat, 22 Feb 2014 13:43:12 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 4B0DE3B7EE; Sat, 22 Feb 2014 21:43:05 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 41AD5190736; Sat, 22 Feb 2014 22:39:10 +0100 (CET)
Date: Sat, 22 Feb 2014 22:39:10 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Paul Wouters <paul@nohats.ca>
Message-ID: <20140222213910.GA14475@sources.org>
References: <530781B9.7070004@gmail.com> <alpine.LFD.2.10.1402211227190.19817@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.10.1402211227190.19817@bofh.nohats.ca>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 7.3
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/_BIKSUVRdTEiWbzP5ZQavo492sk
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop@ietf.org
Subject: Re: [DNSOP] Preliminary agenda for IETF89, London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Feb 2014 21:43:15 -0000

On Fri, Feb 21, 2014 at 12:29:40PM -0500,
 Paul Wouters <paul@nohats.ca> wrote 
 a message of 25 lines which said:

> >		draft-bortzmeyer-dnsop-privacy-sol
...
> Why is TLS for DNS (not 'TLS over DNS') not listed at 3.1?

Following on Tim's response, I draw your attention on the fact that
one of the solutions mentioned in draft-bortzmeyer-dnsop-privacy-sol,
"QNAME minimization", is not a protocol change at all and can
therefore be discussed even by the most charter-strict members of
DNSOP :-)


From nobody Mon Feb 24 12:33:21 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144821A0202; Mon, 24 Feb 2014 12:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.253
X-Spam-Level: 
X-Spam-Status: No, score=0.253 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1TsaGAWGo1l; Mon, 24 Feb 2014 12:33:15 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 585CB1A02E1; Mon, 24 Feb 2014 12:33:15 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id C143E23E2D51; Mon, 24 Feb 2014 20:33:13 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jF-RQx93clJU; Mon, 24 Feb 2014 21:33:09 +0100 (CET)
Received: from kopoli (g225058231.adsl.alicedsl.de [92.225.58.231]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id EF72523E24C1; Mon, 24 Feb 2014 21:33:08 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Marc Buijsman'" <Marc.Buijsman@os3.nl>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl> <003a01cf2b0c$067d2360$13776a20$@rozanak.com> <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com> <5300B6C6.8030903@os3.nl> <005c01cf2b26$8b895aa0$a29c0fe0$@rozanak.com> <53011AE3.20102@os3.nl> <000f01cf2b5b$a26b6800$e7423800$@rozanak.com>
In-Reply-To: <000f01cf2b5b$a26b6800$e7423800$@rozanak.com>
Date: Mon, 24 Feb 2014 21:33:03 +0100
Message-ID: <00ba01cf319f$a10e6530$e32b2f90$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQOKWVpFurMI2Qzh8V0RHyHseiUo8gI85gZYAcBsuHoCE4W3igGmux4JAfAtHs4C/eRXQgH21IMfltmoiXA=
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/uOhEmgWxzI_BRTCNNTnrIXQXSkM
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 20:33:20 -0000

Dear Marc,
Do you have any other comments or I could address your concerns?

Thanks,

Best,
Hosnieh

> -----Original Message-----
> From: DNSOP [mailto:dnsop-bounces@ietf.org] On Behalf Of Hosnieh Rafiee
> Sent: Sunday, February 16, 2014 10:11 PM
> To: 'Marc Buijsman'
> Cc: 'Jeroen van der Ham'; DNSOP@ietf.org; dnsext@ietf.org
> Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
> 
> Dear Marc,
> 
> 
> > Yes, that's what I thought too, so that's why I proposed to use
> > 1.2.840.113549.1.1.5 (note the last 5 instead of 1) for RSA+SHA1.
> >
> > > IMHO, we do not really need two bytes and no padding is also needed.
> > > Because I think if the encryption is on hash function, then it
> > > always generates the same values that is multiple of 8. To have a
> > > proof of concept, I checked RSA signature a few minutes ago with
> > > different key sizes (1024bits , 1280bits, 1536bits,
> > > 1792bits,2048bits, 3072bits) and the result was always the multiple of
8.
> >
> > This is indeed true for the signature fields. However, you also
> > defined
> single-
> > byte length fields for the complete CGA-TSIG DATA field, the
> > Parameters
> field
> > and the Old PK field (not in the table in section 4.1 of draft 07, but
> > you
> do in
> > the figure in section 4.2). The Parameters field includes the public
> > key,
> which
> > consists of (for example) an 1024-bit modulus, but also of a variably
> sized
> > exponent (say 3 bytes), PLUS the bytes of the encapsulating DER
encoding.
> > According to my calculations, this requires a minimum of 161 bytes for
> > the complete DER-encoded public key. If you then add the 16-byte
> > modifier, the 8-byte prefix, the 1-byte collision count, and 0 bytes
> > for the extension
> fields
> > (but this one is variable as well), then you get a total size of 186
> > for
> the
> > Parameters field, which is not a multiple of 8. You would then need
> > 6 bytes of additional padding, or fiddle with the padding inside the
> > DER structure (but I don't think this is desirable).
> >
> > Assuming that the Old PK is also a DER-encoded ASN.1 structure and
> > that an Old PK of similar size is added to the packet (161 + 7 bytes
> > padding),
> then the
> > complete CGA-TSIG DATA field would be of size 660 (including 22 bytes
> > for the encoding of 1.2.840.113549.1.1.5 in domain name syntax and two
> > signatures of length 128), which requires an additional padding of 4
> > bytes
> to
> > make it a multiple of 8.
> 
> > So the total padding in this case would be 6 + 7 + 4 = 17 bytes.
> > However, if you would use 2 bytes for all five length fields then you
> don't
> > need padding and you would actually spare 17 - 5 = 12 bytes. To be
> > honest,
> I
> > don't think the difference is significant enough with respect to the
> > total
> size of
> > 664 bytes to make it a strong argument for using 2-byte length fields,
> > but
> I do
> > think that it makes implementing CGA-TSIG much more straightforward
> > without having the hassle of adding paddings to each variably sized
field.
> It
> > would also be in line with the size of the length fields defined by
> > TSIG,
> which
> > are also 2 bytes.
> 
> 
> Agreed. For CGA-TSIG data structure, I will change it but for signatures,
I will
> let it to be only 8 bits since it does not need it.
> 
> 
> > Agreed. That only leaves the problem of how you notify your clients of
> your
> > new IPv6 address. :)
> 
> It is also not a problem. I addressed it in the new version. The client
receives
> the IP address of the DNS server from the option of the router
advertisement
> (if it wants to be secure) and this is the recommended way.
> So, the routers usually sends the RA message in a frequent intervals. This
also
> inform the clients about any changes of the DNS information such as the
DNS
> IP addresses.
> 
> I just explain a possible attack scenario here
> 
> A node receives a RA message and after verification accepts that router
prefix
> and also sets its DNS IP address (resolver A). Whenever it wants to
resolve any
> domain names, it asks the resolver A to translate a domain to an iP
address.
> 
> Now consider a case where resolver A changes its IP address for whatever
> reason. If we say that the RA message interval is 10 minutes. The node now
> wants to resolve a name and since it hasn't yet received any new RA
message,
> it sends a message to the old resolver. We assume that the attacker can
> eavesdrop this message. He immediately answers instead of legitimate
> resolver (since there is no resolver using that old IP address). The
resolver,
> according to CGA-TSIG document, needs to include the CGA-TSIG data
> structure that enables the other nodes to verify it. Since the attacker
does not
> have the private key of the legitimate resolver, it cannot spoof the old
IP
> address of the legitimate resolver since the CGA verification will fails
and
> signature is not valid if the time signed is an old time.  So, this attack
fails. But
> only the problem is that the node needs to either wait for another RA
> message to receive the new information about the resolver or can send a RS
> message and ask for a new RA message to save time. This can happen after
the
> node does not receive any response from the legitimate resolver.
> It then assumes that the legitimate resolver is not alive anymore.
> 
> The other way to solve this problem is that. The resolver announce the
nodes
> who wants to communicate, about the changes in its IP address. But this is
> more complicated than the first solution. Because, the node should know
> when the resolver wants to change its IP address. However, we can decrease
> the complexity by having a default standard value. Say something like 10
> minutes. So, if the resolver receives any query request 10 minutes before
> changing its IP address, it will include the its old IP address as
mentioned in
> CGA-TSIG document. This inform the nodes that the resolver's old IP
address
> will not be valid after 10 minutes and they need to replace this IP for
further
> communication in their cache.
> 
> The last solution would be using both approach to ensure the client can
> translate the names to IP without any delay to go through sending RS and
> receiving RA, etc.
> 
> Thanks,
> Best,
> Hosnieh
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Mon Feb 24 13:03:15 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E26E91A0277 for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 13:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSdpF_Mki1wb for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 13:03:10 -0800 (PST)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 136311A018D for <dnsop@ietf.org>; Mon, 24 Feb 2014 13:03:06 -0800 (PST)
Received: by mail-qc0-f182.google.com with SMTP id w7so7498647qcr.41 for <dnsop@ietf.org>; Mon, 24 Feb 2014 13:03:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=cXhxJyE6Se8tPEbORgof9hScvqxwtmXEcO+rWTD9etc=; b=ZpzW8N0kDWvdt92/ehu9fuGPpN2EOM08/Ay5P9CbemyNdGOTRWK5duXKPsJ0Rvwm6q t6JwZ6c7tvJ+T5yNg1wftQVM9ftZbpJnVXrUzM4qG3hbavMrWXTqIV3MkKfmsPNBWvy9 KESsSGmQBpnQc7UE1KDb39vdwDD1uAWTDEhA8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=cXhxJyE6Se8tPEbORgof9hScvqxwtmXEcO+rWTD9etc=; b=S6kRd1pT0RzGh0v7/27YmD6z+E2Zbid77b6eWOqxzQsPJPgmvrU0UmyF/z0hdZZ7Xw BzEhyKnkH3bnNPRCKqwYeR2L/DNqMaGaDcHUGNIm+raGVE2sli3XSGo4zNxMoQQedDQp HPzRbmy0T01msduVLUDxQpA6QnQKFTGWUHURLqxo76gWt37dQlZVOQeCVsmBRxmwVr0D QGOLAKtL3i/g7BcNLK+XB1jozHqUwl8FOmRpyv9g03vARx4H1dfyWlfHGFqbO9LTAC0R XIZqnmDYdg3PFIo0PGDtRh3yHY70SE6ADpn8X6FgePiqZSIV+1O6eKhF3saQUB/U6J8v 778w==
X-Gm-Message-State: ALoCoQnfVxKpTrr/a1t1EbBf9sPnxJKXk20ktJ1jV3E9qpCEw4i4iCfXhRfQ1uvf/m+g/FDSKAAf
X-Received: by 10.224.11.136 with SMTP id t8mr33266390qat.26.1393275786270; Mon, 24 Feb 2014 13:03:06 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:71e9:14e2:dba2:7ffd? ([2001:4900:1042:1:71e9:14e2:dba2:7ffd]) by mx.google.com with ESMTPSA id k61sm27051039qge.12.2014.02.24.13.03.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Feb 2014 13:03:05 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_0E52EFA1-5955-4617-B5F4-18F331FE0C2A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.LSU.2.00.1402141550460.14957@hermes-1.csi.cam.ac.uk>
Date: Mon, 24 Feb 2014 16:02:56 -0500
Message-Id: <73E1A21A-F176-478B-AE94-B1B4DCD08C62@hopcount.ca>
References: <alpine.LSU.2.00.1402132050440.18502@hermes-1.csi.cam.ac.uk> <79F80225-91C0-4185-9FB7-172E643DCE90@hopcount.ca> <alpine.LSU.2.00.1402141550460.14957@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Z3sioUjkpPcmd44uNgE9g4J58hU
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] draft-fanf-dnsop-trust-anchor-witnesses-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 21:03:13 -0000

--Apple-Mail=_0E52EFA1-5955-4617-B5F4-18F331FE0C2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Tony,

On 2014-02-14, at 16:02, Tony Finch <dot@dotat.at> wrote:

> I think it's fairly obvious that I wrote just enough to get the idea
> across in a reasonably complete form, but didn't bother with thorough
> references (in particular not to your previous work, sorry!) or =
thorough
> review of formal terminology.

Right, completely understood. That's how I read it.

>>>   o  The concentration of trust in the root is politically
>>>      uncomfortable.
>>=20
>> This may be true, depending on exactly what you mean, but I doubt =
it's
>> universally true (perhaps not even widely true). I'm not sure I
>> understand the motivation for including that statement has in a
>> technical specification, especially when you consider that the =
intended
>> trust mechanisms were designed to be dispersed amongst multiple (e.g.
>> vendor) authorities.
>=20
> Unfortunately the X.509 signatures do not disperse trust, they =
duplicate
> it. A bootstrapping validator trusts (=3D=3D is vulnerable to =
compromise of)
> any one of its X.509 CAs.
>=20
> The key point of the quorum-of-witnesses idea is that no single =
witness is
> trusted in the way that an X.509 CA is.

I think there's an inherent assumption here that by validating a =
certificate, a bootstrapping validator might be vulnerable against any =
one of the various attacks that have afflicted browsers, the core =
problem there being that of the browser list and not the mechanics of =
validating a certificate.

To be clear, what was imagined was that a codebase which already has the =
ability to validate signatures over (say) software updates would easily =
be able to validate a certificate retrieved from data.iana.org that has =
the same kind of signature.

The IANA people imagined that they would solicit specific signatures =
from specific keys relevant to bootstrapping, not that they would obtain =
signatures from commercial CAs and trust the browser list to do the =
right thing.

Since the security of iOS (to choose an example at random) already =
relies upon the ability to validate signatures made by some Apple =
private key, using that same key to validate the integrity of a trust =
anchor bundle retrieved in the clear seemed like a nice easy way to =
import trust in something for which trust is important.

As I mentioned, no such vendor has done this. This is just for =
clarification, not because I think it's a better mechanism than the one =
you proposed.

>> The existing mechanisms (again, lamentably light on implementation)
>> would also facilitate this. The mechanisms in the validator-bootstrap
>> draft I referred to earlier allow trust anchor retrieval with no =
ability
>> to validate, authenticating the retrieved data using appropriate =
local
>> methods (e.g. the key that signed the code is used to test the =
signature
>> of the data the code retrieved).
>=20
> However the existing mechanisms rely on a lot of infrastructure which =
has
> to be accessed with validation turned off. My root witnesses idea uses
> only the DNS and leaves validation switched on while bootstrapping.

I think validation categorically needs to be off until the validator has =
been bootstrapped (not just for this proposal, but in general). No =
validation is possible before you have a stable sense of time and a =
trusted set of local DNSSEC trust anchors. Acting as though you are =
validating when you can't possibly be seems like a bad idea, since if =
you can game validators to get stuck in that state you've defeated =
DNSSEC.

We tried to spell this out in draft-jabley-dnsop-validator-bootstrap.

It occurs to me that we now have three drafts that speak to an active =
need (and try to fill a gap in DNSSEC deployment that at least some of =
us think needs to be filled):

  draft-jabley-dnsop-validator-bootstrap
  draft-jabley-dnssec-trust-anchor
  draft-fanf-dnsop-trust-anchor-witnesses

It's not entirely obvious that dnsop is the right place for these (maybe =
we should talk to opsec? homenet, in the sense that these mechanisms =
need to be automatable without local operators?). But I think if they =
are going to go anywhere they need thorough working group review, and =
should not proceed as independent submissions -- this is an important =
set of definitions for real-world operation of the IANA root zone, and =
it needs to be as right as we can make it.

Suz/Tim/ADs: opinions on whether this is a useful bundle of work for =
dnsop? (No, I'm not (necessarily) requesting another agenda slot for =
London :-)


Joe


--Apple-Mail=_0E52EFA1-5955-4617-B5F4-18F331FE0C2A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlMLs4AACgkQNI8MvYZSOix7YQCeNH7CMrI3xuEbdcDOLzYS85FZ
/7kAniJ+NuiEIyktP9mRg3ByNExlqwcm
=ixS2
-----END PGP SIGNATURE-----

--Apple-Mail=_0E52EFA1-5955-4617-B5F4-18F331FE0C2A--


From nobody Mon Feb 24 13:44:13 2014
Return-Path: <Marc.Buijsman@os3.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8D931A0277; Mon, 24 Feb 2014 13:37:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.352
X-Spam-Level: 
X-Spam-Status: No, score=-0.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.547] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MpxRu-q3U5YC; Mon, 24 Feb 2014 13:37:25 -0800 (PST)
Received: from mail.serv.os3.nl (mail.serv.os3.nl [IPv6:2001:610:158:960::25]) by ietfa.amsl.com (Postfix) with ESMTP id 56EF01A0193; Mon, 24 Feb 2014 13:37:25 -0800 (PST)
Received: from smtp.os3.nl (smtp.os3.nl [IPv6:2001:610:158:960::119]) by mail.serv.os3.nl (Postfix) with ESMTP id 3C60617B81A; Mon, 24 Feb 2014 22:37:23 +0100 (CET)
Received: from [192.168.1.2] (178-84-162-64.dynamic.upc.nl [178.84.162.64]) by smtp.os3.nl (Postfix) with ESMTPSA id 01F4617B7AE; Mon, 24 Feb 2014 22:37:22 +0100 (CET)
Message-ID: <530BBB92.7010001@os3.nl>
Date: Mon, 24 Feb 2014 22:37:22 +0100
From: Marc Buijsman <Marc.Buijsman@os3.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
References: <021201cf29d9$8a5daa30$9f18fe90$@rozanak.com> <53009CFE.9030900@os3.nl> <003a01cf2b0c$067d2360$13776a20$@rozanak.com> <003b01cf2b10$091fbde0$1b5f39a0$@rozanak.com> <5300B6C6.8030903@os3.nl> <005c01cf2b26$8b895aa0$a29c0fe0$@rozanak.com> <53011AE3.20102@os3.nl> <000f01cf2b5b$a26b6800$e7423800$@rozanak.com> <00ba01cf319f$a10e6530$e32b2f90$@rozanak.com>
In-Reply-To: <00ba01cf319f$a10e6530$e32b2f90$@rozanak.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/IQYTl9ZWPaw14NrTmzWBFmAFvZI
X-Mailman-Approved-At: Mon, 24 Feb 2014 13:44:10 -0800
Cc: 'Jeroen van der Ham' <vdham@uva.nl>, DNSOP@ietf.org, dnsext@ietf.org
Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 21:37:29 -0000

Dear Hosnieh,

I have no further comments at the moment. I did not have the chance to
completely read the new version so I was not aware of Section 10, but I
like that you addressed it!

Overall, it is nice to see that the draft has been improved. I hope
others will have a look at it and help improve it more in order to go
forward.

Thanks for thinking along with me, I appreciate it!

Best regards,

Marc Buijsman

Hosnieh Rafiee schreef op 24-2-2014 21:33:
> Dear Marc,
> Do you have any other comments or I could address your concerns?
>
> Thanks,
>
> Best,
> Hosnieh
>
>> -----Original Message-----
>> From: DNSOP [mailto:dnsop-bounces@ietf.org] On Behalf Of Hosnieh Rafiee
>> Sent: Sunday, February 16, 2014 10:11 PM
>> To: 'Marc Buijsman'
>> Cc: 'Jeroen van der Ham'; DNSOP@ietf.org; dnsext@ietf.org
>> Subject: Re: [DNSOP] [dnsext] CGA-TSIG - new version
>>
>> Dear Marc,
>>
>>
>>> Yes, that's what I thought too, so that's why I proposed to use
>>> 1.2.840.113549.1.1.5 (note the last 5 instead of 1) for RSA+SHA1.
>>>
>>>> IMHO, we do not really need two bytes and no padding is also needed.
>>>> Because I think if the encryption is on hash function, then it
>>>> always generates the same values that is multiple of 8. To have a
>>>> proof of concept, I checked RSA signature a few minutes ago with
>>>> different key sizes (1024bits , 1280bits, 1536bits,
>>>> 1792bits,2048bits, 3072bits) and the result was always the multiple of
> 8.
>>> This is indeed true for the signature fields. However, you also
>>> defined
>> single-
>>> byte length fields for the complete CGA-TSIG DATA field, the
>>> Parameters
>> field
>>> and the Old PK field (not in the table in section 4.1 of draft 07, but
>>> you
>> do in
>>> the figure in section 4.2). The Parameters field includes the public
>>> key,
>> which
>>> consists of (for example) an 1024-bit modulus, but also of a variably
>> sized
>>> exponent (say 3 bytes), PLUS the bytes of the encapsulating DER
> encoding.
>>> According to my calculations, this requires a minimum of 161 bytes for
>>> the complete DER-encoded public key. If you then add the 16-byte
>>> modifier, the 8-byte prefix, the 1-byte collision count, and 0 bytes
>>> for the extension
>> fields
>>> (but this one is variable as well), then you get a total size of 186
>>> for
>> the
>>> Parameters field, which is not a multiple of 8. You would then need
>>> 6 bytes of additional padding, or fiddle with the padding inside the
>>> DER structure (but I don't think this is desirable).
>>>
>>> Assuming that the Old PK is also a DER-encoded ASN.1 structure and
>>> that an Old PK of similar size is added to the packet (161 + 7 bytes
>>> padding),
>> then the
>>> complete CGA-TSIG DATA field would be of size 660 (including 22 bytes
>>> for the encoding of 1.2.840.113549.1.1.5 in domain name syntax and two
>>> signatures of length 128), which requires an additional padding of 4
>>> bytes
>> to
>>> make it a multiple of 8.
>>> So the total padding in this case would be 6 + 7 + 4 = 17 bytes.
>>> However, if you would use 2 bytes for all five length fields then you
>> don't
>>> need padding and you would actually spare 17 - 5 = 12 bytes. To be
>>> honest,
>> I
>>> don't think the difference is significant enough with respect to the
>>> total
>> size of
>>> 664 bytes to make it a strong argument for using 2-byte length fields,
>>> but
>> I do
>>> think that it makes implementing CGA-TSIG much more straightforward
>>> without having the hassle of adding paddings to each variably sized
> field.
>> It
>>> would also be in line with the size of the length fields defined by
>>> TSIG,
>> which
>>> are also 2 bytes.
>>
>> Agreed. For CGA-TSIG data structure, I will change it but for signatures,
> I will
>> let it to be only 8 bits since it does not need it.
>>
>>
>>> Agreed. That only leaves the problem of how you notify your clients of
>> your
>>> new IPv6 address. :)
>> It is also not a problem. I addressed it in the new version. The client
> receives
>> the IP address of the DNS server from the option of the router
> advertisement
>> (if it wants to be secure) and this is the recommended way.
>> So, the routers usually sends the RA message in a frequent intervals. This
> also
>> inform the clients about any changes of the DNS information such as the
> DNS
>> IP addresses.
>>
>> I just explain a possible attack scenario here
>>
>> A node receives a RA message and after verification accepts that router
> prefix
>> and also sets its DNS IP address (resolver A). Whenever it wants to
> resolve any
>> domain names, it asks the resolver A to translate a domain to an iP
> address.
>> Now consider a case where resolver A changes its IP address for whatever
>> reason. If we say that the RA message interval is 10 minutes. The node now
>> wants to resolve a name and since it hasn't yet received any new RA
> message,
>> it sends a message to the old resolver. We assume that the attacker can
>> eavesdrop this message. He immediately answers instead of legitimate
>> resolver (since there is no resolver using that old IP address). The
> resolver,
>> according to CGA-TSIG document, needs to include the CGA-TSIG data
>> structure that enables the other nodes to verify it. Since the attacker
> does not
>> have the private key of the legitimate resolver, it cannot spoof the old
> IP
>> address of the legitimate resolver since the CGA verification will fails
> and
>> signature is not valid if the time signed is an old time.  So, this attack
> fails. But
>> only the problem is that the node needs to either wait for another RA
>> message to receive the new information about the resolver or can send a RS
>> message and ask for a new RA message to save time. This can happen after
> the
>> node does not receive any response from the legitimate resolver.
>> It then assumes that the legitimate resolver is not alive anymore.
>>
>> The other way to solve this problem is that. The resolver announce the
> nodes
>> who wants to communicate, about the changes in its IP address. But this is
>> more complicated than the first solution. Because, the node should know
>> when the resolver wants to change its IP address. However, we can decrease
>> the complexity by having a default standard value. Say something like 10
>> minutes. So, if the resolver receives any query request 10 minutes before
>> changing its IP address, it will include the its old IP address as
> mentioned in
>> CGA-TSIG document. This inform the nodes that the resolver's old IP
> address
>> will not be valid after 10 minutes and they need to replace this IP for
> further
>> communication in their cache.
>>
>> The last solution would be using both approach to ensure the client can
>> translate the names to IP without any delay to go through sending RS and
>> receiving RA, etc.
>>
>> Thanks,
>> Best,
>> Hosnieh
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Mon Feb 24 17:51:39 2014
Return-Path: <cheshire@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCAF41A039B for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 17:51:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.049
X-Spam-Level: 
X-Spam-Status: No, score=-102.049 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6sS0q-G-SS9 for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 17:51:36 -0800 (PST)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 706F81A0235 for <dnsop@ietf.org>; Mon, 24 Feb 2014 17:51:36 -0800 (PST)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from relay7.apple.com ([17.128.113.101]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0N1J006VR3TZ9QH1@mail-out.apple.com> for dnsop@ietf.org; Mon, 24 Feb 2014 17:51:35 -0800 (PST)
X-AuditID: 11807165-f79076d0000015d9-48-530bf7272ac3
Received: from spicerack.apple.com (spicerack.apple.com [17.128.115.40]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay7.apple.com (Apple SCV relay) with SMTP id 90.96.05593.727FB035; Mon, 24 Feb 2014 17:51:35 -0800 (PST)
Received: from chesh1.apple.com (chesh1.apple.com [17.193.13.41]) by spicerack.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0N1J00DE63TZL370@spicerack.apple.com> for dnsop@ietf.org; Mon, 24 Feb 2014 17:51:35 -0800 (PST)
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de>
Date: Mon, 24 Feb 2014 17:51:43 -0800
Content-transfer-encoding: quoted-printable
Message-id: <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de>
To: Ralf Weber <dns@fl1ger.de>
X-Mailer: Apple Mail (2.1510)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUi2FCsoav+nTvYYNpNC4u7by6zODB6LFny kymAMYrLJiU1J7MstUjfLoErY8r2e0wFy3grjtxcytLAeI6ri5GTQ0LARGL3y3vMELaYxIV7 69m6GLk4hAQmM0mcfNgG5axiklj5aw+Qw8HBLKAncf+iFkgDL5C5c+82VhBbWCBXYlrvMjYQ m01AS+LF5ytgNqeArcThi+fYQWwWAVWJ01cOM4HYzALuEo2nDzBD2NoST95dYIWYaSPxv+Ul WL2QQIrE5yUTWUBsEQE5ia2rGqAOlZU4fe45ywRGgVkIF81CctEsJFMXMDKvYhQoSs1JrDTX SywoyEnVS87P3cQIDrvC1B2MjcutDjEKcDAq8fB2FHMHC7EmlhVX5h5ilOBgVhLh/XkCKMSb klhZlVqUH19UmpNafIhRmoNFSZx32leglEB6YklqdmpqQWoRTJaJg1OqgfHQ1MvWeR5+bC7T 4gvDPj0V+J8XdePGgS4Vy8ZoDeMpaX8rLj9xviuVfatZP2qyS4fu7wM1T+YwioQtk2R3Cpm6 WP6L0O7VixdfWCpyda0Tsw3bytdl98KKl+UkS4pEfZx1Lvj4NDcVy/I3coWWx/aExkvuFb64 XfLcJsGwM7M3fnf+52Ol1KTEUpyRaKjFXFScCABotOOSNwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/_UjzwZ_gM1V5joOntsuU3dyL2-Y
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, John Levine <johnl@taugh.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 01:51:38 -0000

On 29 Jan, 2014, at 07:47, Ralf Weber <dns@fl1ger.de> wrote:

> Where shall this stop? How about .LOKALESNETZWERK (german for .LAN). =
How many domains do we want to treat special? I know this draft only =
asks for 8, but some of them are on ICANNs application list.

Currently, with no established procedure for local-use names, the result =
is chaos. Since no DNS equivalent to RFC 1918 exists, people use =
whatever name they feel like. My hope is that if people are offered a =
short list of legitimate pseudo-TLDs for local-use names, the temptation =
to use some other TLD not on that list will be less. Today all NAT =
gateways I know of default to one of the RFC 1918 address ranges. If RFC =
1918 did not exist, would NAT gateways not exist, or would they just =
hijack who-knows-what addresses? I suspect the latter.

If we acknowledge and document the reality, the IETF can have a role in =
guiding it in a sane direction. If we pretend local-use names don=92t =
exist, then the IETF has less relevance in the real world and the real =
world carries on without us.

> I also don't think there are risks in delegation these other than the =
applicants will get lots of traffic.

No, the risk is that the applicants *won=92t* get the traffic they want, =
because some user=92s local DNS is answering those queries.

If we have *some* pseudo-TLDs reserved for local-use names, there=92s a =
stronger argument that local hijacking of other names is illegitimate.

And yes, if you want .LOKALESNETZWERK, then argue for that. Let=92s use =
this IETF discussion process to get some clarity on which names are =
local-use and which ones are not.

Stuart Cheshire


From nobody Mon Feb 24 19:37:34 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB36C1A03C4 for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 19:37:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.949
X-Spam-Level: 
X-Spam-Status: No, score=-4.949 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GD-tNXQRy7ip for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 19:37:27 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id A77D61A03A7 for <dnsop@ietf.org>; Mon, 24 Feb 2014 19:37:26 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 555CF23839C; Tue, 25 Feb 2014 03:37:12 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 3725B16005B; Tue, 25 Feb 2014 03:38:03 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id EBBA516004E; Tue, 25 Feb 2014 03:38:02 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 4BDCB10413A9; Tue, 25 Feb 2014 14:37:08 +1100 (EST)
To: Stuart Cheshire <cheshire@apple.com>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com>
In-reply-to: Your message of "Mon, 24 Feb 2014 17:51:43 -0800." <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com>
Date: Tue, 25 Feb 2014 14:37:08 +1100
Message-Id: <20140225033708.4BDCB10413A9@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Jg2oTfJSaqa6Rdq9OURiPHKLwcA
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, John Levine <johnl@taugh.com>, Ralf Weber <dns@fl1ger.de>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 03:37:32 -0000

In message <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com>, Stuart Cheshire wr
ites:
> On 29 Jan, 2014, at 07:47, Ralf Weber <dns@fl1ger.de> wrote:
>
> > Where shall this stop? How about .LOKALESNETZWERK (german for .LAN).
> > How many domains do we want to treat special? I know this draft only asks
> > for 8, but some of them are on ICANNs application list.
>
> Currently, with no established procedure for local-use names, the result
> is chaos. Since no DNS equivalent to RFC 1918 exists, people use whatever
> name they feel like. My hope is that if people are offered a short list
> of legitimate pseudo-TLDs for local-use names, the temptation to use some
> other TLD not on that list will be less. Today all NAT gateways I know of
> default to one of the RFC 1918 address ranges. If RFC 1918 did not exist,
> would NAT gateways not exist, or would they just hijack who-knows-what
> addresses? I suspect the latter.

There is a slight difference.  There is no restriction on getting
names other than unwillingness or lack of education about how to
get a name.  There is a real restriction on getting enough IPv4
addresses to avoid having to use NAT.

With IPv6 you don't even need split DNS.

They can alway use <name>.10.in-addr.arpa. 10.in-addr.arpa is a
perfectly legal suffix for a hostname and 10.in-addr.arpa has a
insecure delegation so there are no DNSSEC issues.  Additionally
the AS112 server will soak any leaked names.  It's not as
pretty as .home or .lan or .corp or .... but it will work.

Alternatively get home.arpa insecurely delegated to a AS112 style
server.  <hostname>.home.arpa. isn't too bad and matches the hostname
structure of 99% of the corporate work, <hostname>.<label>.<tld>.

This also has the advantage that it doesn't involve root zone
politics.

Mark

> If we acknowledge and document the reality, the IETF can have a role in
> guiding it in a sane direction. If we pretend local-use names don't
> exist, then the IETF has less relevance in the real world and the real
> world carries on without us.
>
> > I also don't think there are risks in delegation these other than the
> applicants will get lots of traffic.
>
> No, the risk is that the applicants *won't* get the traffic they want,
> because some user's local DNS is answering those queries.
>
> If we have *some* pseudo-TLDs reserved for local-use names, there's a
> stronger argument that local hijacking of other names is illegitimate.
>
> And yes, if you want .LOKALESNETZWERK, then argue for that. Let's use
> this IETF discussion process to get some clarity on which names are
> local-use and which ones are not.
>
> Stuart Cheshire
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Feb 24 20:12:47 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E511A03FC for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 20:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jamCbdhvUqHw for <dnsop@ietfa.amsl.com>; Mon, 24 Feb 2014 20:12:43 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id BBB601A03EE for <dnsop@ietf.org>; Mon, 24 Feb 2014 20:12:43 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id B4F6A2383A8; Tue, 25 Feb 2014 04:12:30 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id B5BEF16004E; Tue, 25 Feb 2014 04:13:21 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id C6B55160048; Tue, 25 Feb 2014 04:13:20 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 5482E1041B60; Tue, 25 Feb 2014 15:12:27 +1100 (EST)
To: Suzanne Woolf <suzworldwide@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>
In-reply-to: Your message of "Fri, 21 Feb 2014 12:17:50 -0500." <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>
Date: Tue, 25 Feb 2014 15:12:27 +1100
Message-Id: <20140225041227.5482E1041B60@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/b--pzlQnKuGfPNCsCf1TtK8tJlk
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] summary of WG current status
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 04:12:45 -0000

In message <8AA00477-DFDA-4A7A-9A30-76AFB88BE4CA@gmail.com>, Suzanne Woolf writ
es:
> 4. CDS and related: what are we doing about the topic of DNSSEC in-band
> key maintenance? This has previously been somewhat contentious and seems
> to have stalled without resolution. We now have current versions of two
> drafts and would like to make progress on resolving differences.
> http://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintain
> ance/
> http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/

add to that
 http://datatracker.ietf.org/doc/draft-andrews-dnsop-update-parent-zones/

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Feb 25 19:59:57 2014
Return-Path: <cheshire@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7711A03D4 for <dnsop@ietfa.amsl.com>; Tue, 25 Feb 2014 19:59:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.749
X-Spam-Level: 
X-Spam-Status: No, score=-104.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrdqSiiStkFd for <dnsop@ietfa.amsl.com>; Tue, 25 Feb 2014 19:59:54 -0800 (PST)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 252FA1A03DA for <dnsop@ietf.org>; Tue, 25 Feb 2014 19:59:54 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay8.apple.com ([17.128.113.102]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0N1L005D84EM1HE0@mail-out.apple.com> for dnsop@ietf.org; Tue, 25 Feb 2014 19:59:31 -0800 (PST)
X-AuditID: 11807166-f79c26d000001623-09-530d66a3f8f8
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay8.apple.com (Apple SCV relay) with SMTP id 6F.C2.05667.3A66D035; Tue, 25 Feb 2014 19:59:31 -0800 (PST)
Received: from [10.0.1.3] (173-164-252-149-SFBA.hfc.comcastbusiness.net [173.164.252.149]) by jimbu.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0N1L0036J4F6D330@jimbu.apple.com> for dnsop@ietf.org; Tue, 25 Feb 2014 19:59:31 -0800 (PST)
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <20140225033708.4BDCB10413A9@rock.dv.isc.org>
Date: Tue, 25 Feb 2014 19:59:29 -0800
Message-id: <1E762167-609B-4463-B6F4-357512C71FBE@apple.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <20140225033708.4BDCB10413A9@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1827)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsUiON1OVXdxGm+wwebnXBZ331xmcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxr/J/1gKnjBXrL93j6WBsYm5i5GTQ0LARGLFyylsELaYxIV7 64FsLg4hgQYmieOHnzFBOHuZJFonvALrYBbQkli/8zgTiM0roCexcd5ssLiwQK7EtN5lYJPY gGpefL4CZHNwcApYScx9JQMSZhFQlVh0fgE7xJhUiZYXX6BGaks8eXeBFWKkjcTsjqlQRxxn lDi+9wAjSEJEQEGi7e0rJpCZEgKyEvNPl05gFJiF5KJZSC6ahWTsAkbmVYwCRak5iZUWeokF BTmpesn5uZsYQYHXUJi2g7FpudUhRgEORiUe3gAW3mAh1sSy4srcQ4wSHMxKIrwW33iChXhT EiurUovy44tKc1KLDzFKc7AoifPyxgFVC6QnlqRmp6YWpBbBZJk4OKUaGPf2nqtQeep8cO31 aSuFJhVvfNQVZW827eKRezxn/v1zf+b3SW6NylqT5q4Hx9ZGqs2b0/Kwfu6s6fwuS8/Oja04 Ufwx4Nbc50XqZ/PK9q5fvyFVPIHrv9GBuf5PQ9hkDe7aznr08ZOTbbe+9lwP1Wk1vn7VRpNF f/jUbLggvu/Mm+P/DNVd7BYqsRRnJBpqMRcVJwIAp4MAOjgCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/uSSuMgMLj95mgklGGl7_asQu_MU
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, John Levine <johnl@taugh.com>, Ralf Weber <dns@fl1ger.de>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 03:59:55 -0000

On 24 Feb, 2014, at 19:37, Mark Andrews <marka@isc.org> wrote:

> There is a slight difference.  There is no restriction on getting
> names other than unwillingness or lack of education about how to
> get a name.

Good point. A document to help this education aspect would be good.

> They can alway use <name>.10.in-addr.arpa.

I think human-interface factors make such names a non-starter. The people doing this want memorable easy-to-type names.

Stuart Cheshire


From nobody Tue Feb 25 20:50:42 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17001A0216 for <dnsop@ietfa.amsl.com>; Tue, 25 Feb 2014 20:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T5EelrQHCcsj for <dnsop@ietfa.amsl.com>; Tue, 25 Feb 2014 20:50:38 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 8F40E1A040B for <dnsop@ietf.org>; Tue, 25 Feb 2014 20:50:38 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 3960BC94DB; Wed, 26 Feb 2014 04:50:24 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1393390237; bh=0St2ZSL5Ngh7vJ4t1/IPT826WJm6ulvAeyDKxlH01aU=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=NczRddqZzghgbj3+OJVhMOgs6uu2f1U/FU/TQNjL9roTxn5MLd0Qaa1D8+WfeCz/s XGJDWm30MGuvaDg76d4BtrUStCgf8CL8f6V8vpuXz4F6GIxKFtF4K5RDD7LnHDKH/C rBWz5s1EPmbBHXJ4cKKGPzSPhgibvSlcI4F6EXkE=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 26 Feb 2014 04:50:24 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 59B77160059; Wed, 26 Feb 2014 04:51:16 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 27F61160031; Wed, 26 Feb 2014 04:51:16 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 59E1A106685B; Wed, 26 Feb 2014 15:50:20 +1100 (EST)
To: Stuart Cheshire <cheshire@apple.com>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <20140225033708.4BDCB10413A9@rock.dv.isc.org> <1E762167-609B-4463-B6F4-357512C71FBE@apple.com>
In-reply-to: Your message of "Tue, 25 Feb 2014 19:59:29 -0800." <1E762167-609B-4463-B6F4-357512C71FBE@apple.com>
Date: Wed, 26 Feb 2014 15:50:20 +1100
Message-Id: <20140226045020.59E1A106685B@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/OXrK-Vbgvdt5vV7BoREgUObhLlQ
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, John Levine <johnl@taugh.com>, Ralf Weber <dns@fl1ger.de>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 04:50:40 -0000

In message <1E762167-609B-4463-B6F4-357512C71FBE@apple.com>, Stuart Cheshire wr
ites:
> On 24 Feb, 2014, at 19:37, Mark Andrews <marka@isc.org> wrote:
> 
> > There is a slight difference.  There is no restriction on getting
> > names other than unwillingness or lack of education about how to
> > get a name.
> 
> Good point. A document to help this education aspect would be good.
> 
> > They can alway use <name>.10.in-addr.arpa.
> 
> I think human-interface factors make such names a non-starter. The people doi
> ng this want memorable easy-to-type names.

<name>.10.in-addr.arpa. was a bit tongue in cheek, but <name>.home.arpa
I think could be a viable alternative for those that refuse to get
their own domain.  It would require a education process but I think
it would be possible.

> Stuart Cheshire
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Feb 26 00:16:52 2014
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61CC51A0063 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 00:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCKrZcAiMLXC for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 00:16:46 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 2AABA1A0075 for <dnsop@ietf.org>; Wed, 26 Feb 2014 00:16:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 280B686719; Wed, 26 Feb 2014 03:16:37 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 27755-08; Wed, 26 Feb 2014 03:16:36 -0500 (EST)
Received: from 30.145.dhcp.conference.apricot.net (unknown [220.247.145.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 40A3C866C8; Wed, 26 Feb 2014 03:16:34 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_D20AA91E-9E0F-4BBD-BCB5-B43388A0F7F8"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com>
Date: Wed, 26 Feb 2014 16:16:30 +0800
Message-Id: <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com>
To: Stuart Cheshire <cheshire@apple.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/67xSJvGUzae-oWwrvliLFjX7zq8
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 08:16:48 -0000

--Apple-Mail=_D20AA91E-9E0F-4BBD-BCB5-B43388A0F7F8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Feb 25, 2014, at 9:51 AM, Stuart Cheshire <cheshire@apple.com> wrote:
> If we have *some* pseudo-TLDs reserved for local-use names,

I would think =
http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#User-assigned_code_element=
s would be appropriate for this purpose.

Regards,
-drc


--Apple-Mail=_D20AA91E-9E0F-4BBD-BCB5-B43388A0F7F8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTDaLeAAoJENV6ebf0/4rXXU4IALszQd7rc0PssoxKtuL+DN/g
0wG4weHr4kc8i+Y/ta9RIm1qFmsR1hNH7Kg6Hn5uxgTPn10hzAlmln3qrQNu4TjX
n+DJAgjRm343w7m3y1C898oZCaxmgH1h3UkoP3qfmlvEoKgowmUd14NSTbHOiH57
clKbUVENnBhduk0/LtCiOrE9tRj64lmv9Jci9hDAsWq26vXKvV3paBtaDqr+paFZ
9EiSx6uG8pDyOzXulTdRAKe41lqBKVn6+oLsCGFI7mbMgqt26kmeFISxHTgiPimo
WpbWHHth6v2LUFMoUyGI31OQUGOcq2wA5uCOOUytE6mg5BoCdvePj4tX1Pc3tPI=
=642r
-----END PGP SIGNATURE-----

--Apple-Mail=_D20AA91E-9E0F-4BBD-BCB5-B43388A0F7F8--


From nobody Wed Feb 26 02:03:36 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B05851A01C7 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 02:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k43fXK4V_pbI for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 02:03:27 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0881A01C6 for <dnsop@ietf.org>; Wed, 26 Feb 2014 02:03:27 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 5F68CC94D2; Wed, 26 Feb 2014 10:03:14 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1393409006; bh=a+M+rtFWOWmmwgWkNyQfeCiX62E8NkqmMmuQ1gkbSrA=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=l3Qjk34ojhlV8oov3AuGBD3IUMO0BZyiNtXt1dIJeAlnXWhv4z7nMHU/DXS74T4DJ 0KlDe7A3kK3LEG7QZS9+4sK3egI68/5iEEyUQZqdsZN0sAz2X2CiinZgLDyHkrD1Pa EhILdsJoS3+zLybjXdbPxH2CtEj0c4z4G7dVlq/0=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 26 Feb 2014 10:03:14 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 94D29160066; Wed, 26 Feb 2014 10:04:06 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 5844B160060; Wed, 26 Feb 2014 10:04:06 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id E73CA1069B39; Wed, 26 Feb 2014 21:03:11 +1100 (EST)
To: David Conrad <drc@virtualized.org>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org>
In-reply-to: Your message of "Wed, 26 Feb 2014 16:16:30 +0800." <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org>
Date: Wed, 26 Feb 2014 21:03:11 +1100
Message-Id: <20140226100311.E73CA1069B39@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/6DLrmUsFu2IDbuM37LaXUxIkqBI
Cc: Stuart Cheshire <cheshire@apple.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 10:03:31 -0000

In message <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org>, David Conrad
 writes:
> 
> On Feb 25, 2014, at 9:51 AM, Stuart Cheshire <cheshire@apple.com> wrote:
> > If we have *some* pseudo-TLDs reserved for local-use names,
> 
> I would think =
> http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#User-assigned_code_element=
> s would be appropriate for this purpose.
> 
> Regards,
> -drc

Whatever is used needs to be insecurely delegated so that in app
validation will work.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Feb 26 06:34:21 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCD31A0424 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 06:34:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Euo69h9ExvVt for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 06:34:07 -0800 (PST)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id E8FB41A0390 for <dnsop@ietf.org>; Wed, 26 Feb 2014 06:34:06 -0800 (PST)
Received: by mail-qc0-f178.google.com with SMTP id i8so1388937qcq.37 for <dnsop@ietf.org>; Wed, 26 Feb 2014 06:34:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E13LCSQrzhKMc4pxsOuCIN/fFVm5Tv0hq/wpj5NtZZ4=; b=jKsWxvT+qJPQezC2myCV0E6td01hghlMmO5PFJ0xtlPeZdg8f/VsJIfYHOuRYyy3ZJ cHuH0keCDqvrmXvhNlKKF+5y5JLky980i8iV5vE2WufWOkjjfw2a10Hez1MJ7QyFxBRy Kc+MMh2xrPzB/eND1Ye7cqilSHjQi4jBS5t8c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=E13LCSQrzhKMc4pxsOuCIN/fFVm5Tv0hq/wpj5NtZZ4=; b=HttY7pOvtbfxIXuR3XZPX5sWhytsOGWUi25XVFqys9V7neK2yn31njFm3+/6fq5Ib7 pGtQTO7RFhX93rDlYsNdb8kN7pmMlNzBR1ymlOkoXSBzrXnLeevVbbb3DS8oCODr1cj4 mN+E1LNGt+ypj4zSU13A2Avo4y2OqXWg+3OjI9pkhFC8YvK8/fiEERsq+oOomlmGYCJB Pksht+6wTuA6LtRRkgLTygktaMAQLbmlsHndwjdQBuF966ai+VO2DxKpbWoOpnxFyys5 KE0C43tD53/uCPoB/iE6MfkVIloB+G4pl6uPZ+SOBQ+4ilHu/WR0uhwVXv4lomcqCt26 gkAQ==
X-Gm-Message-State: ALoCoQlPb8NwveON4uBtYiHuovBAyk0ydmcHIZqM+TBkHX15eB/ADQy7gMupYrfru+OAwRKkbon0
X-Received: by 10.224.160.83 with SMTP id m19mr8229009qax.21.1393425245459; Wed, 26 Feb 2014 06:34:05 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:6179:ce53:5e0:2f2b? ([2001:4900:1042:1:6179:ce53:5e0:2f2b]) by mx.google.com with ESMTPSA id t5sm3029788qat.6.2014.02.26.06.34.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Feb 2014 06:34:04 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20140226100311.E73CA1069B39@rock.dv.isc.org>
Date: Wed, 26 Feb 2014 09:34:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/kRS48EVg8rv5NRkMngbFQt1_ews
Cc: Stuart Cheshire <cheshire@apple.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 14:34:09 -0000

On 26 Feb 2014, at 5:03, Mark Andrews <marka@isc.org> wrote:

> In message <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org>, =
David Conrad
> writes:
>=20
>> On Feb 25, 2014, at 9:51 AM, Stuart Cheshire <cheshire@apple.com> =
wrote:
>>> If we have *some* pseudo-TLDs reserved for local-use names,
>>=20
>> I would think =3D
>> =
http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#User-assigned_code_element=
=3D
>> s would be appropriate for this purpose.
>>=20
>> Regards,
>> -drc
>=20
> Whatever is used needs to be insecurely delegated so that in app
> validation will work.

I still don=92t see why we need a TLD, or a delegation/reservation under =
ARPA.

There are many, many TLDs under which an application/protocol =
implementer can reserve some namespace for their exclusive use at low =
cost ($10/year, say). Why is this approach not preferred for a new =
application/protocol? It seems far simpler.

Perhaps all that is missing is some guidance that says =93you shouldn=92t =
hijack namespaces that you don=92t control, even for non-DNS =
applications; register a domain instead=94.


Joe=


From nobody Wed Feb 26 07:29:08 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F121A065D for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 07:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAEUdPXPMRKj for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 07:29:02 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id BB9911A0660 for <dnsop@ietf.org>; Wed, 26 Feb 2014 07:28:59 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s1QFSut8064858 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Wed, 26 Feb 2014 08:28:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca>
Date: Wed, 26 Feb 2014 07:28:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3ED0C133-B1F4-48DD-83C2-D26E26764F42@vpnc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/6mv9WrtGxU3EmguvbScFCCYFVps
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 15:29:04 -0000

On Feb 26, 2014, at 6:34 AM, Joe Abley <jabley@hopcount.ca> wrote:

> Perhaps all that is missing is some guidance that says =93you =
shouldn=92t hijack namespaces that you don=92t control, even for non-DNS =
applications; register a domain instead=94.

+1, with a short list of things that can go wrong if you hijack. I'd be =
willing to write that up (maybe with Joe; his sardonic humor is more fun =
than mine) if people here think it would move forward as an update to =
RFC 6761.

--Paul Hoffman=


From nobody Wed Feb 26 07:45:04 2014
Return-Path: <pspacek@redhat.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8221A042B for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 07:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TC0lpQC_xSKg for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 07:44:54 -0800 (PST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by ietfa.amsl.com (Postfix) with ESMTP id A442F1A0037 for <dnsop@ietf.org>; Wed, 26 Feb 2014 07:44:54 -0800 (PST)
Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s1QFiqlw020652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <dnsop@ietf.org>; Wed, 26 Feb 2014 10:44:53 -0500
Received: from pspacek.brq.redhat.com (vpn1-4-54.ams2.redhat.com [10.36.4.54]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id s1QFinn9031778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Wed, 26 Feb 2014 10:44:51 -0500
Message-ID: <530E0BF1.4010008@redhat.com>
Date: Wed, 26 Feb 2014 16:44:49 +0100
From: Petr Spacek <pspacek@redhat.com>
Organization: Red Hat
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dnsop@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 10.5.11.11
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/w48C0JDw-jJ89Vvp0KN-TGnjWFU
Subject: [DNSOP] DNSSEC AD bit handling in stub-resolvers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 15:45:00 -0000

Greetings,

I'm Petr Spacek from Red Hat's Identity Management group. We plan to extend 
support for DNSSEC (including DANE and others) in open-source software and we 
would like to discuss the right implementation approach with you.

We can see two very basic approaches:
A) Do DNSSEC response validation in each application.
B) Let recursive resolver do the validation and use AD bit in the application.

We consider the first approach (i.e. each application doing response 
validation) too heavy-weight and hard to administer for various reasons:
- Response validation is sensitive operation and application programmers 
should not do it themselves.
- A variant where every application calls validation library is still not 
optimal. Experience with crypto libraries shows that there are many 
opportunities to use a library incorrectly (in a way which works but is not 
secure).
- This approach has potential to create administrative nightmare if each 
application decides to maintain own set of trust anchors etc. We can see 
results of such approach in PKI world ...


We believe that better approach is to centralize validation in local 
system-wide recursive resolver and use AD bit for signaling that data are 
trustworthy to applications. An application should use stub-resolver to talk 
to local recursive resolver and use received AD bit to decide e.g. if it is 
possible to trust TLSA records or not.

Unfortunately, there are use cases where neither a locally running validating 
resolver nor a trusted path to a remote resolver are available and deployment 
of such is unacceptable.

It seems that existing stub-resolvers unconditionally trust recursive 
resolvers and just forward the AD bit back and forth. This behavior is okay 
only if no application relays on the AD bit. In other words, supporting DANE 
with current stub-resolvers practically requires to add a configuration option 
'recursive resolver is un/trusted' to each and every DANE-enabled application 
and library. (This is exactly what OpenSSH client does. An additional problem 
is that this value has to be maintained as network configuration changes over 
time.)


We would like to make DNSSEC implementation in applications as simple and 
secure as possible. That is a reason why we are looking for a solution for a 
case where AD bit can't be trusted because validating resolver is not 
available for whatever reason. It would allow applications to use AD bit 
without explicit configuration per-application if we solve this case somehow.

Is there any 'standard' way to handle described situation?


We have the following proposal (some people say it is controversial):
- Extend stub-resolvers with a new call for resolver initialization: In case 
of ldns it would be something like: ldns_resolver_new_frm_file_trusted() or 
for glibc res_init_trusted().
- The new call will initialize library as usual + read some system-wide 
configuration (it can be whatever, imagine for example a new file 
/etc/resolv.trusted).
- Client applications will use the same API (except the initialization) to do 
DNS queries.
- When a DNS answer is received from network the stub-resolver will consult 
configuration read from /etc/resolv.trusted:
-- If the particular recursive resolver is listed as trusted - pass AD bit to 
the application.
-- *Otherwise: Clear AD bit and pass the answer with AD=0 to the application.*

This allows an administrator to configure system-wide policy. In case with 
locally running validating resolver or e.g. IPSec tunnel to trusted resolver 
admin can declare it as trusted and nothing changes. However, this mechanism 
allows the system to be safe even in configurations *without* validating 
resolver. No explicit configuration in application is need, just one 
system-wide setting.

It could seem like a minor improvement or a hack, but it allows applications 
to trust the AD bit unconditionally and as a result it significantly 
simplifies DNSSEC implementation and configuration on client machines. We hope 
that this simple approach will allow us to implement and deploy DANE and 
similar technologies widely.

This proposal can be seen as temporary solution before secure transport 
mechanisms like IPSec or CGA-TSIG are widely available and used. The main 
advantage is that it is easy to implement and it doesn't require any new 
technology so we can use it in applications today.

We would like to hear your opinions and recommendations for this area.

Thank you for your time.

-- 
Petr Spacek
Software Engineer
Red Hat


From nobody Wed Feb 26 08:02:59 2014
Return-Path: <gwiley@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62A61A0454 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 08:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRiQzHcGu0za for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 08:02:47 -0800 (PST)
Received: from exprod6og120.obsmtp.com (exprod6og120.obsmtp.com [64.18.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id 1732C1A0699 for <dnsop@ietf.org>; Wed, 26 Feb 2014 08:02:45 -0800 (PST)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob120.postini.com ([64.18.5.12]) with SMTP ID DSNKUw4QI2oqf1lya/d23k2O1RAhTYMkYf1v@postini.com; Wed, 26 Feb 2014 08:02:46 PST
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s1QG2gvb011937 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Feb 2014 11:02:43 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0123.003; Wed, 26 Feb 2014 11:02:41 -0500
From: "Wiley, Glen" <gwiley@verisign.com>
To: Petr Spacek <pspacek@redhat.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] DNSSEC AD bit handling in stub-resolvers
Thread-Index: AQHPMwm90JqcSVg1Qkyoc2fHUuWuKprHskSA
Date: Wed, 26 Feb 2014 16:02:41 +0000
Message-ID: <CF337945.35ABA%gwiley@verisign.com>
References: <530E0BF1.4010008@redhat.com>
In-Reply-To: <530E0BF1.4010008@redhat.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <96AACE91EDC9074781DAF495475FFBCC@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/wBsuVZ1biCJ8FFom7tIUf3I5W6o
Subject: Re: [DNSOP] DNSSEC AD bit handling in stub-resolvers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 16:02:52 -0000

Petr,

Have you taken a look at the getdns API specification that Paul Hoffman
put together at http://www.vpnc.org/getdns-api/ ?

This addresses many of your points for both stub resolvers and a recursive
resolver that would run on a platform local to the applications.
--=20
Glen Wiley
KK4SFV

Sr. Engineer
The Hive, Verisign, Inc.




On 2/26/14 10:44 AM, "Petr Spacek" <pspacek@redhat.com> wrote:

>Greetings,
>
>I'm Petr Spacek from Red Hat's Identity Management group. We plan to
>extend=20
>support for DNSSEC (including DANE and others) in open-source software
>and we=20
>would like to discuss the right implementation approach with you.
>
>We can see two very basic approaches:
>A) Do DNSSEC response validation in each application.
>B) Let recursive resolver do the validation and use AD bit in the
>application.
>
>We consider the first approach (i.e. each application doing response
>validation) too heavy-weight and hard to administer for various reasons:
>- Response validation is sensitive operation and application programmers
>should not do it themselves.
>- A variant where every application calls validation library is still not
>optimal. Experience with crypto libraries shows that there are many
>opportunities to use a library incorrectly (in a way which works but is
>not=20
>secure).
>- This approach has potential to create administrative nightmare if each
>application decides to maintain own set of trust anchors etc. We can see
>results of such approach in PKI world ...
>
>
>We believe that better approach is to centralize validation in local
>system-wide recursive resolver and use AD bit for signaling that data are
>trustworthy to applications. An application should use stub-resolver to
>talk=20
>to local recursive resolver and use received AD bit to decide e.g. if it
>is=20
>possible to trust TLSA records or not.
>
>Unfortunately, there are use cases where neither a locally running
>validating=20
>resolver nor a trusted path to a remote resolver are available and
>deployment=20
>of such is unacceptable.
>
>It seems that existing stub-resolvers unconditionally trust recursive
>resolvers and just forward the AD bit back and forth. This behavior is
>okay=20
>only if no application relays on the AD bit. In other words, supporting
>DANE=20
>with current stub-resolvers practically requires to add a configuration
>option=20
>'recursive resolver is un/trusted' to each and every DANE-enabled
>application=20
>and library. (This is exactly what OpenSSH client does. An additional
>problem=20
>is that this value has to be maintained as network configuration changes
>over=20
>time.)
>
>
>We would like to make DNSSEC implementation in applications as simple and
>secure as possible. That is a reason why we are looking for a solution
>for a=20
>case where AD bit can't be trusted because validating resolver is not
>available for whatever reason. It would allow applications to use AD bit
>without explicit configuration per-application if we solve this case
>somehow.
>
>Is there any 'standard' way to handle described situation?
>
>
>We have the following proposal (some people say it is controversial):
>- Extend stub-resolvers with a new call for resolver initialization: In
>case=20
>of ldns it would be something like: ldns_resolver_new_frm_file_trusted()
>or=20
>for glibc res_init_trusted().
>- The new call will initialize library as usual + read some system-wide
>configuration (it can be whatever, imagine for example a new file
>/etc/resolv.trusted).
>- Client applications will use the same API (except the initialization)
>to do=20
>DNS queries.
>- When a DNS answer is received from network the stub-resolver will
>consult=20
>configuration read from /etc/resolv.trusted:
>-- If the particular recursive resolver is listed as trusted - pass AD
>bit to=20
>the application.
>-- *Otherwise: Clear AD bit and pass the answer with AD=3D0 to the
>application.*
>
>This allows an administrator to configure system-wide policy. In case
>with=20
>locally running validating resolver or e.g. IPSec tunnel to trusted
>resolver=20
>admin can declare it as trusted and nothing changes. However, this
>mechanism=20
>allows the system to be safe even in configurations *without* validating
>resolver. No explicit configuration in application is need, just one
>system-wide setting.
>
>It could seem like a minor improvement or a hack, but it allows
>applications=20
>to trust the AD bit unconditionally and as a result it significantly
>simplifies DNSSEC implementation and configuration on client machines. We
>hope=20
>that this simple approach will allow us to implement and deploy DANE and
>similar technologies widely.
>
>This proposal can be seen as temporary solution before secure transport
>mechanisms like IPSec or CGA-TSIG are widely available and used. The main
>advantage is that it is easy to implement and it doesn't require any new
>technology so we can use it in applications today.
>
>We would like to hear your opinions and recommendations for this area.
>
>Thank you for your time.
>
>--=20
>Petr Spacek
>Software Engineer
>Red Hat
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop


From nobody Wed Feb 26 08:03:17 2014
Return-Path: <pspacek@redhat.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 353E41A06A3 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 08:03:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.449
X-Spam-Level: 
X-Spam-Status: No, score=-7.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMhlay23aaDC for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 08:03:11 -0800 (PST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by ietfa.amsl.com (Postfix) with ESMTP id E6DDF1A0683 for <dnsop@ietf.org>; Wed, 26 Feb 2014 08:03:10 -0800 (PST)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s1QG38mB009330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <dnsop@ietf.org>; Wed, 26 Feb 2014 11:03:08 -0500
Received: from pspacek.brq.redhat.com (vpn1-4-54.ams2.redhat.com [10.36.4.54]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s1QG2uuG004497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Wed, 26 Feb 2014 11:03:02 -0500
Message-ID: <530E1030.6060300@redhat.com>
Date: Wed, 26 Feb 2014 17:02:56 +0100
From: Petr Spacek <pspacek@redhat.com>
Organization: Red Hat
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dnsop@ietf.org
References: <530E0BF1.4010008@redhat.com>
In-Reply-To: <530E0BF1.4010008@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/oc-hJh_EvWgmc1gHgc3Il590O6Y
Subject: Re: [DNSOP] DNSSEC AD bit handling in stub-resolvers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 16:03:15 -0000

Greetings,

Paul Wouters and me have accidentally open threads about the same topic on 
this list and also on dane-list. I guess that this discussion fits better to 
dane-list so please discuss there.

I'm sorry for the noise.

Petr Spacek

On 26.2.2014 16:44, Petr Spacek wrote:
> Greetings,
>
> I'm Petr Spacek from Red Hat's Identity Management group. We plan to extend
> support for DNSSEC (including DANE and others) in open-source software and we
> would like to discuss the right implementation approach with you.
>
> We can see two very basic approaches:
> A) Do DNSSEC response validation in each application.
> B) Let recursive resolver do the validation and use AD bit in the application.
>
> We consider the first approach (i.e. each application doing response
> validation) too heavy-weight and hard to administer for various reasons:
> - Response validation is sensitive operation and application programmers
> should not do it themselves.
> - A variant where every application calls validation library is still not
> optimal. Experience with crypto libraries shows that there are many
> opportunities to use a library incorrectly (in a way which works but is not
> secure).
> - This approach has potential to create administrative nightmare if each
> application decides to maintain own set of trust anchors etc. We can see
> results of such approach in PKI world ...
>
>
> We believe that better approach is to centralize validation in local
> system-wide recursive resolver and use AD bit for signaling that data are
> trustworthy to applications. An application should use stub-resolver to talk
> to local recursive resolver and use received AD bit to decide e.g. if it is
> possible to trust TLSA records or not.
>
> Unfortunately, there are use cases where neither a locally running validating
> resolver nor a trusted path to a remote resolver are available and deployment
> of such is unacceptable.
>
> It seems that existing stub-resolvers unconditionally trust recursive
> resolvers and just forward the AD bit back and forth. This behavior is okay
> only if no application relays on the AD bit. In other words, supporting DANE
> with current stub-resolvers practically requires to add a configuration option
> 'recursive resolver is un/trusted' to each and every DANE-enabled application
> and library. (This is exactly what OpenSSH client does. An additional problem
> is that this value has to be maintained as network configuration changes over
> time.)
>
>
> We would like to make DNSSEC implementation in applications as simple and
> secure as possible. That is a reason why we are looking for a solution for a
> case where AD bit can't be trusted because validating resolver is not
> available for whatever reason. It would allow applications to use AD bit
> without explicit configuration per-application if we solve this case somehow.
>
> Is there any 'standard' way to handle described situation?
>
>
> We have the following proposal (some people say it is controversial):
> - Extend stub-resolvers with a new call for resolver initialization: In case
> of ldns it would be something like: ldns_resolver_new_frm_file_trusted() or
> for glibc res_init_trusted().
> - The new call will initialize library as usual + read some system-wide
> configuration (it can be whatever, imagine for example a new file
> /etc/resolv.trusted).
> - Client applications will use the same API (except the initialization) to do
> DNS queries.
> - When a DNS answer is received from network the stub-resolver will consult
> configuration read from /etc/resolv.trusted:
> -- If the particular recursive resolver is listed as trusted - pass AD bit to
> the application.
> -- *Otherwise: Clear AD bit and pass the answer with AD=0 to the application.*
>
> This allows an administrator to configure system-wide policy. In case with
> locally running validating resolver or e.g. IPSec tunnel to trusted resolver
> admin can declare it as trusted and nothing changes. However, this mechanism
> allows the system to be safe even in configurations *without* validating
> resolver. No explicit configuration in application is need, just one
> system-wide setting.
>
> It could seem like a minor improvement or a hack, but it allows applications
> to trust the AD bit unconditionally and as a result it significantly
> simplifies DNSSEC implementation and configuration on client machines. We hope
> that this simple approach will allow us to implement and deploy DANE and
> similar technologies widely.
>
> This proposal can be seen as temporary solution before secure transport
> mechanisms like IPSec or CGA-TSIG are widely available and used. The main
> advantage is that it is easy to implement and it doesn't require any new
> technology so we can use it in applications today.
>
> We would like to hear your opinions and recommendations for this area.
>
> Thank you for your time.


From nobody Wed Feb 26 10:46:52 2014
Return-Path: <gwiley@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 873641A0139 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 10:46:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrTuyDxfQduq for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 10:46:42 -0800 (PST)
Received: from exprod6og114.obsmtp.com (exprod6og114.obsmtp.com [64.18.1.33]) by ietfa.amsl.com (Postfix) with ESMTP id 099481A0111 for <dnsop@ietf.org>; Wed, 26 Feb 2014 10:46:42 -0800 (PST)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob114.postini.com ([64.18.5.12]) with SMTP ID DSNKUw42kHTbVKZdwKR/nn1XN+uUsT4kVIWk@postini.com; Wed, 26 Feb 2014 10:46:41 PST
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s1QIkePx017720 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dnsop@ietf.org>; Wed, 26 Feb 2014 13:46:40 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0123.003; Wed, 26 Feb 2014 13:46:39 -0500
From: "Wiley, Glen" <gwiley@verisign.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: beta release of getdns stub resolver
Thread-Index: AQHPMyMVJ6Rc0KhHfEGJKBnHArSIPg==
Date: Wed, 26 Feb 2014 18:46:38 +0000
Message-ID: <CF33A0BD.35B11%gwiley@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.173.152.4]
Content-Type: multipart/alternative; boundary="_000_CF33A0BD35B11gwileyverisigncom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/NqIBbXpysaNFxHvlTVnqPYoVyD4
Subject: [DNSOP] beta release of getdns stub resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 18:46:44 -0000

--_000_CF33A0BD35B11gwileyverisigncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Verisign and NLnet Labs are pleased to announce the first beta release (0.1=
.0) of an open source implementation of the getdns API specification.  The =
project's home page is at http://getdnsapi.net<http://getdnsapi.net/>.

getdns is a modern asynchronous DNS API. It implements DNS entry points fro=
m a design developed and vetted by application developers, in the specifica=
tion at http://www.vpnc.org/getdns-api/ edited by Paul Hoffman. With the de=
velopment of this API, we intend to offer application developers a moderniz=
ed and flexible way to access DNS security (DNSSEC) and other powerful new =
DNS features; a particular hope is to inspire application developers toward=
s innovative security solutions in their applications.

We invite everyone to take a look at the project and to provide feedback to=
 us and even contribute back to the project!  We expect to have successive =
releases over the next few months that move us toward a more complete imple=
mentation and includes ports to even more platforms.

Signed=85the getdns core team:

Craig Despeaux, Verisign, Inc.
Neel Goyal, Verisign, Inc.
Olaf Kolkman, NLnet Labs
Allison Mankin, Verisign Labs.
Melinda Shore, No Mountain Software LLC
Willem Toorop, NLnet Labs
Wouter Wijngaards, NLnet Labs
Glen Wiley, Verisign, Inc.

--_000_CF33A0BD35B11gwileyverisigncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <C0056A8EE986D3428C8D06018C28D2DB@verisign.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div><span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Verisign and NLnet =
Labs are pleased to announce the first beta release (0.1.0) of an open sour=
ce implementation of the getdns API specification. &nbsp;The project's home=
 page is at&nbsp;<a href=3D"http://getdnsapi.net/">http://getdnsapi.net</a>=
.</font></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; "><br>
</font></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">getdns is a modern =
asynchronous DNS API. It implements DNS entry points from a design develope=
d and vetted by application developers, in the specification at&nbsp;<a hre=
f=3D"http://www.vpnc.org/getdns-api/">http://www.vpnc.org/getdns-api/</a>&n=
bsp;edited
 by Paul Hoffman. With the development of this API, we intend to offer appl=
ication developers a modernized and flexible way to access DNS security (DN=
SSEC) and other powerful new DNS features; a particular hope is to inspire =
application developers towards innovative
 security solutions in their applications.&nbsp;</font></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; "><br>
</font></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">We invite everyone =
to take a look at the project and to provide feedback to us and even contri=
bute back to the project! &nbsp;We expect to have successive releases over =
the next few months that move us toward a
 more complete implementation and includes ports to even more platforms.</f=
ont></div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Signed=85the getdns=
 core team:</font></div>
<div>
<ul>
</ul>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Craig Despeaux, Ver=
isign, Inc.</font></div>
<div></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Neel Goyal, Verisig=
n, Inc.</font></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Olaf Kolkman,&nbsp;=
NLnet Labs</font></div>
<div></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Allison Mankin, Ver=
isign Labs.</font></div>
<div></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Melinda Shore, No M=
ountain Software LLC</font></div>
<div></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Willem Toorop, NLne=
t Labs</font></div>
<div></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Wouter Wijngaards, =
NLnet Labs</font></div>
<div></div>
<div><font face=3D"Courier" style=3D"font-size: 12px; ">Glen Wiley, Verisig=
n, Inc.</font></div>
</div>
</div>
</div>
</div>
</span></div>
</body>
</html>

--_000_CF33A0BD35B11gwileyverisigncom_--


From nobody Wed Feb 26 11:02:53 2014
Return-Path: <richard.lamb@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B08801A015E for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 11:02:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level: 
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maHpkHq7Yz7q for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 11:02:37 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id 180DA1A00F2 for <dnsop@ietf.org>; Wed, 26 Feb 2014 11:02:37 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Wed, 26 Feb 2014 11:02:35 -0800
From: Richard Lamb <richard.lamb@icann.org>
To: "Wiley, Glen" <gwiley@verisign.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Date: Wed, 26 Feb 2014 11:02:28 -0800
Thread-Topic: beta release of getdns stub resolver
Thread-Index: AQHPMyMVJ6Rc0KhHfEGJKBnHArSIPprH4vlA
Message-ID: <5648A8908CCB564EBF46E2BC904A75B19684A12AD8@EXVPMBX100-1.exc.icann.org>
References: <CF33A0BD.35B11%gwiley@verisign.com>
In-Reply-To: <CF33A0BD.35B11%gwiley@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5648A8908CCB564EBF46E2BC904A75B19684A12AD8EXVPMBX1001ex_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/SrBEf4qgjU_rcMNSpegYXM-7ikQ
Subject: Re: [DNSOP] beta release of getdns stub resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 19:02:43 -0000

--_000_5648A8908CCB564EBF46E2BC904A75B19684A12AD8EXVPMBX1001ex_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thank you guys!

This is exactly the kind of leadership the rest of the IT industry needs to=
 help take DNSSEC to the next level.  Many of us were just going to hack up=
 some code for Windows out of frustration but were stymied by what sort of =
interface would be the most attractive to developers (and therefore widespr=
ead DNSSEC adoption).  So we were waiting for someone else to take the firs=
t step.  You did it.

Thanks !!
-Rick Lamb (with entrepreneur hat on)



From: DNSOP [mailto:dnsop-bounces@ietf.org] On Behalf Of Wiley, Glen
Sent: Wednesday, February 26, 2014 10:47 AM
To: dnsop@ietf.org
Subject: [DNSOP] beta release of getdns stub resolver

Verisign and NLnet Labs are pleased to announce the first beta release (0.1=
.0) of an open source implementation of the getdns API specification.  The =
project's home page is at http://getdnsapi.net<http://getdnsapi.net/>.

getdns is a modern asynchronous DNS API. It implements DNS entry points fro=
m a design developed and vetted by application developers, in the specifica=
tion at http://www.vpnc.org/getdns-api/ edited by Paul Hoffman. With the de=
velopment of this API, we intend to offer application developers a moderniz=
ed and flexible way to access DNS security (DNSSEC) and other powerful new =
DNS features; a particular hope is to inspire application developers toward=
s innovative security solutions in their applications.

We invite everyone to take a look at the project and to provide feedback to=
 us and even contribute back to the project!  We expect to have successive =
releases over the next few months that move us toward a more complete imple=
mentation and includes ports to even more platforms.

Signed...the getdns core team:
Craig Despeaux, Verisign, Inc.
Neel Goyal, Verisign, Inc.
Olaf Kolkman, NLnet Labs
Allison Mankin, Verisign Labs.
Melinda Shore, No Mountain Software LLC
Willem Toorop, NLnet Labs
Wouter Wijngaards, NLnet Labs
Glen Wiley, Verisign, Inc.

--_000_5648A8908CCB564EBF46E2BC904A75B19684A12AD8EXVPMBX1001ex_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:481236316;
	mso-list-template-ids:437953948;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you=
 guys!<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif";color:#1F497D'>This is exactly the kind of leadership=
 the rest of the IT industry needs to help take DNSSEC to the next level.&n=
bsp; Many of us were just going to hack up some code for Windows out of fru=
stration but were stymied by what sort of interface would be the most attra=
ctive to developers (and therefore widespread DNSSEC adoption).&nbsp; So we=
 were waiting for someone else to take the first step.&nbsp; You did it.&nb=
sp; <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'>Thanks !!<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>&#8211;Rick Lamb (with entrepreneur hat on)<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:soli=
d #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b>=
<span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> DNSOP [=
mailto:dnsop-bounces@ietf.org] <b>On Behalf Of </b>Wiley, Glen<br><b>Sent:<=
/b> Wednesday, February 26, 2014 10:47 AM<br><b>To:</b> dnsop@ietf.org<br><=
b>Subject:</b> [DNSOP] beta release of getdns stub resolver<o:p></o:p></spa=
n></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div>=
<div><div><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:C=
ourier;color:black'>Verisign and NLnet Labs are pleased to announce the fir=
st beta release (0.1.0) of an open source implementation of the getdns API =
specification. &nbsp;The project's home page is at&nbsp;<a href=3D"http://g=
etdnsapi.net/">http://getdnsapi.net</a>.</span><span style=3D'font-size:10.=
5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p><=
/div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:=
"Calibri","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p></div><div>=
<p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:Courier;col=
or:black'>getdns is a modern asynchronous DNS API. It implements DNS entry =
points from a design developed and vetted by application developers, in the=
 specification at&nbsp;<a href=3D"http://www.vpnc.org/getdns-api/">http://w=
ww.vpnc.org/getdns-api/</a>&nbsp;edited by Paul Hoffman. With the developme=
nt of this API, we intend to offer application developers a modernized and =
flexible way to access DNS security (DNSSEC) and other powerful new DNS fea=
tures; a particular hope is to inspire application developers towards innov=
ative security solutions in their applications.&nbsp;</span><span style=3D'=
font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt=
;font-family:"Calibri","sans-serif";color:black'><o:p>&nbsp;</o:p></span></=
p></div><div><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-famil=
y:Courier;color:black'>We invite everyone to take a look at the project and=
 to provide feedback to us and even contribute back to the project! &nbsp;W=
e expect to have successive releases over the next few months that move us =
toward a more complete implementation and includes ports to even more platf=
orms.</span><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-ser=
if";color:black'><o:p></o:p></span></p></div></div></div></div><div><p clas=
s=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-s=
erif";color:black'><o:p>&nbsp;</o:p></span></p></div><div><div><div><div><p=
 class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:Courier;color=
:black'>Signed&#8230;the getdns core team:</span><span style=3D'font-size:1=
0.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p=
></div><div><div><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-f=
amily:Courier;color:black'>Craig Despeaux, Verisign, Inc.</span><span style=
=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p><=
/o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:9.=
0pt;font-family:Courier;color:black'>Neel Goyal, Verisign, Inc.</span><span=
 style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>=
<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-s=
ize:9.0pt;font-family:Courier;color:black'>Olaf Kolkman,&nbsp;NLnet Labs</s=
pan><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";colo=
r:black'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=
=3D'font-size:9.0pt;font-family:Courier;color:black'>Allison Mankin, Verisi=
gn Labs.</span><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-=
serif";color:black'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><=
span style=3D'font-size:9.0pt;font-family:Courier;color:black'>Melinda Shor=
e, No Mountain Software LLC</span><span style=3D'font-size:10.5pt;font-fami=
ly:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:Courier;color:=
black'>Willem Toorop, NLnet Labs</span><span style=3D'font-size:10.5pt;font=
-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><di=
v><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:Courier;c=
olor:black'>Wouter Wijngaards, NLnet Labs</span><span style=3D'font-size:10=
.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p>=
</div><div><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:=
Courier;color:black'>Glen Wiley, Verisign, Inc.</span><span style=3D'font-s=
ize:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></spa=
n></p></div></div></div></div></div></div></div></body></html>=

--_000_5648A8908CCB564EBF46E2BC904A75B19684A12AD8EXVPMBX1001ex_--


From nobody Wed Feb 26 11:21:18 2014
Return-Path: <gwiley@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACF81A072F for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 11:21:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VUtSxp1k8z9w for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 11:21:08 -0800 (PST)
Received: from exprod6og117.obsmtp.com (exprod6og117.obsmtp.com [64.18.1.39]) by ietfa.amsl.com (Postfix) with ESMTP id 752C61A084B for <dnsop@ietf.org>; Wed, 26 Feb 2014 11:20:47 -0800 (PST)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob117.postini.com ([64.18.5.12]) with SMTP ID DSNKUw4+jrJoXLnCcnnQwr5W4FvC5bovKqwU@postini.com; Wed, 26 Feb 2014 11:21:06 PST
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s1QJKjOv018764 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Feb 2014 14:20:45 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0123.003; Wed, 26 Feb 2014 14:20:45 -0500
From: "Wiley, Glen" <gwiley@verisign.com>
To: Richard Lamb <richard.lamb@icann.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: beta release of getdns stub resolver
Thread-Index: AQHPMyMVJ6Rc0KhHfEGJKBnHArSIPprH4vlAgAAGb4A=
Date: Wed, 26 Feb 2014 19:20:44 +0000
Message-ID: <CF33A822.35B57%gwiley@verisign.com>
References: <CF33A0BD.35B11%gwiley@verisign.com> <5648A8908CCB564EBF46E2BC904A75B19684A12AD8@EXVPMBX100-1.exc.icann.org>
In-Reply-To: <5648A8908CCB564EBF46E2BC904A75B19684A12AD8@EXVPMBX100-1.exc.icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.173.152.4]
Content-Type: multipart/alternative; boundary="_000_CF33A82235B57gwileyverisigncom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/czbcP37C3O_2t0K-Kd0LTcQ7bJY
Subject: Re: [DNSOP] beta release of getdns stub resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 19:21:10 -0000

--_000_CF33A82235B57gwileyverisigncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Thanks Rick.

Paul's original commission to write the spec was I think largely motivated =
by the need for an API that non-DNS expert application developers could liv=
e with.  I am hoping that by building a fully open (BSD licensed) implement=
ation that is willing to accept contributions from the community we will en=
d up with something that will move DNSSEC adoption to the next level.

--
Glen Wiley
KK4SFV
Sr. Engineer
The Hive, Verisign, Inc.

From: Richard Lamb <richard.lamb@icann.org<mailto:richard.lamb@icann.org>>
Date: Wednesday, February 26, 2014 2:02 PM
To: "Wiley, Glen" <gwiley@verisign.com<mailto:gwiley@verisign.com>>, "dnsop=
@ietf.org<mailto:dnsop@ietf.org>" <dnsop@ietf.org<mailto:dnsop@ietf.org>>
Subject: RE: beta release of getdns stub resolver

Thank you guys!

This is exactly the kind of leadership the rest of the IT industry needs to=
 help take DNSSEC to the next level.  Many of us were just going to hack up=
 some code for Windows out of frustration but were stymied by what sort of =
interface would be the most attractive to developers (and therefore widespr=
ead DNSSEC adoption).  So we were waiting for someone else to take the firs=
t step.  You did it.

Thanks !!
=96Rick Lamb (with entrepreneur hat on)



From: DNSOP [mailto:dnsop-bounces@ietf.org] On Behalf Of Wiley, Glen
Sent: Wednesday, February 26, 2014 10:47 AM
To: dnsop@ietf.org<mailto:dnsop@ietf.org>
Subject: [DNSOP] beta release of getdns stub resolver

Verisign and NLnet Labs are pleased to announce the first beta release (0.1=
.0) of an open source implementation of the getdns API specification.  The =
project's home page is at http://getdnsapi.net<http://getdnsapi.net/>.

getdns is a modern asynchronous DNS API. It implements DNS entry points fro=
m a design developed and vetted by application developers, in the specifica=
tion at http://www.vpnc.org/getdns-api/ edited by Paul Hoffman. With the de=
velopment of this API, we intend to offer application developers a moderniz=
ed and flexible way to access DNS security (DNSSEC) and other powerful new =
DNS features; a particular hope is to inspire application developers toward=
s innovative security solutions in their applications.

We invite everyone to take a look at the project and to provide feedback to=
 us and even contribute back to the project!  We expect to have successive =
releases over the next few months that move us toward a more complete imple=
mentation and includes ports to even more platforms.

Signed=85the getdns core team:
Craig Despeaux, Verisign, Inc.
Neel Goyal, Verisign, Inc.
Olaf Kolkman, NLnet Labs
Allison Mankin, Verisign Labs.
Melinda Shore, No Mountain Software LLC
Willem Toorop, NLnet Labs
Wouter Wijngaards, NLnet Labs
Glen Wiley, Verisign, Inc.

--_000_CF33A82235B57gwileyverisigncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <71DA5FAAF4236E41A9BC1657AAA3665C@verisign.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>
<div>Thanks Rick.</div>
<div><br>
</div>
<div>Paul's original commission to write the spec was I think largely motiv=
ated by the need for an API that non-DNS expert application developers coul=
d live with. &nbsp;I am hoping that by building a fully open (BSD licensed)=
 implementation that is willing to accept
 contributions from the community we will end up with something that will m=
ove DNSSEC adoption to the next level.</div>
<div><br>
</div>
<div>
<div>
<div>--&nbsp;</div>
<div>Glen Wiley</div>
<div>KK4SFV</div>
</div>
<div>Sr. Engineer</div>
<div>The Hive, Verisign, Inc.</div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Richard Lamb &lt;<a href=3D"m=
ailto:richard.lamb@icann.org">richard.lamb@icann.org</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, February 26, 2014 =
2:02 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;Wiley, Glen&quot; &lt;<a =
href=3D"mailto:gwiley@verisign.com">gwiley@verisign.com</a>&gt;, &quot;<a h=
ref=3D"mailto:dnsop@ietf.org">dnsop@ietf.org</a>&quot; &lt;<a href=3D"mailt=
o:dnsop@ietf.org">dnsop@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: beta release of getdns=
 stub resolver<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:481236316;
	mso-list-template-ids:437953948;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">Thank you guys!<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">This is exactly the kind of leader=
ship the rest of the IT industry needs to help take DNSSEC to the next leve=
l.&nbsp; Many of us were just going to hack
 up some code for Windows out of frustration but were stymied by what sort =
of interface would be the most attractive to developers (and therefore wide=
spread DNSSEC adoption).&nbsp; So we were waiting for someone else to take =
the first step.&nbsp; You did it.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">Thanks !!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">=96Rick Lamb (with entrepreneur ha=
t on)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; font-fami=
ly: Tahoma, sans-serif; "> DNSOP [<a href=3D"mailto:dnsop-bounces@ietf.org"=
>mailto:dnsop-bounces@ietf.org</a>]
<b>On Behalf Of </b>Wiley, Glen<br>
<b>Sent:</b> Wednesday, February 26, 2014 10:47 AM<br>
<b>To:</b> <a href=3D"mailto:dnsop@ietf.org">dnsop@ietf.org</a><br>
<b>Subject:</b> [DNSOP] beta release of getdns stub resolver<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Verisign and NLnet Labs are pleased to announce the first beta =
release (0.1.0) of an open source implementation of the getdns API specific=
ation. &nbsp;The project's home page is at&nbsp;<a href=3D"http://getdnsapi=
.net/">http://getdnsapi.net</a>.</span><span style=3D"font-size: 10.5pt; fo=
nt-family: Calibri, sans-serif; color: black; "><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">getdns is a modern asynchronous DNS API. It implements DNS entr=
y points from a design developed and vetted by application developers, in t=
he specification at&nbsp;<a href=3D"http://www.vpnc.org/getdns-api/">http:/=
/www.vpnc.org/getdns-api/</a>&nbsp;edited
 by Paul Hoffman. With the development of this API, we intend to offer appl=
ication developers a modernized and flexible way to access DNS security (DN=
SSEC) and other powerful new DNS features; a particular hope is to inspire =
application developers towards innovative
 security solutions in their applications.&nbsp;</span><span style=3D"font-=
size: 10.5pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">We invite everyone to take a look at the project and to provide=
 feedback to us and even contribute back to the project! &nbsp;We expect to=
 have successive releases over the next few
 months that move us toward a more complete implementation and includes por=
ts to even more platforms.</span><span style=3D"font-size: 10.5pt; font-fam=
ily: Calibri, sans-serif; color: black; "><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Signed=85the getdns core team:</span><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span=
></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Craig Despeaux, Verisign, Inc.</span><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Neel Goyal, Verisign, Inc.</span><span style=3D"font-size: 10.5=
pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Olaf Kolkman,&nbsp;NLnet Labs</span><span style=3D"font-size: 1=
0.5pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Allison Mankin, Verisign Labs.</span><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Melinda Shore, No Mountain Software LLC</span><span style=3D"fo=
nt-size: 10.5pt; font-family: Calibri, sans-serif; color: black; "><o:p></o=
:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Willem Toorop, NLnet Labs</span><span style=3D"font-size: 10.5p=
t; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Wouter Wijngaards, NLnet Labs</span><span style=3D"font-size: 1=
0.5pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Courier;c=
olor:black">Glen Wiley, Verisign, Inc.</span><span style=3D"font-size: 10.5=
pt; font-family: Calibri, sans-serif; color: black; "><o:p></o:p></span></p=
>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CF33A82235B57gwileyverisigncom_--


From nobody Wed Feb 26 14:03:37 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7621A0749 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 14:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.103
X-Spam-Level: 
X-Spam-Status: No, score=-100.103 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsbCsQtZrQ4F for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 14:03:24 -0800 (PST)
Received: from winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5DC1A0733 for <dnsop@ietf.org>; Wed, 26 Feb 2014 14:03:23 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1590; t=1393452197; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=/82WYEafpFy1ORSQfMJAxUinAKk=; b=dKe0Gr9UGSxd9cXdGydd Q1bNk6SFV26nb2rsoQh/zivdXEQFnsowsUoiub4p8u3g0RT/ZqHC/6nJmbfu/FVo TfXmF8gcJRmbLtuEDKAUVUuTT/G+VFAPt1d5guofi3ZB5UY1mrdxYJ8VHwOVWL/i YcCEEqXuay/dGU+0fz0onGU=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for dnsop@ietf.org; Wed, 26 Feb 2014 17:03:17 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2734657645.20363.1340; Wed, 26 Feb 2014 17:03:17 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1590; t=1393451557; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=oVSa0Kw 9GTwk5TN57UpAlVbE/MhZewGdwMBWAJSvIOQ=; b=BlKgFfBEPJB/r19McQNKjY1 P29lnk6kzelXIH0GBQlfC5fyoe4e+jL1vhsB7lt2KtvcOQAC3alKDs3N0n0RP4Y1 GAB7JxzsgpHTmii4xPuKzPtwL190/oEc00t6fe2QYO13Xsf89Euov6N3N441tZxQ Yab/VoitzazZyXtlokUw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for dnsop@ietf.org; Wed, 26 Feb 2014 16:52:37 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2180935787.9.7688; Wed, 26 Feb 2014 16:52:36 -0500
Message-ID: <530E64A4.2070607@isdg.net>
Date: Wed, 26 Feb 2014 17:03:16 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Wiley, Glen" <gwiley@verisign.com>,  "dnsop@ietf.org" <dnsop@ietf.org>
References: <CF33A0BD.35B11%gwiley@verisign.com>
In-Reply-To: <CF33A0BD.35B11%gwiley@verisign.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/9hi351h0y2NR3bMsWfV1mdz6sZs
Subject: Re: [DNSOP] beta release of getdns stub resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 22:03:31 -0000

Is there is a plug and play 32 bit and/or 64 bit Windows version?

On 2/26/2014 1:46 PM, Wiley, Glen wrote:
> Verisign and NLnet Labs are pleased to announce the first beta release (0.1.0) of an open source implementation of the getdns API specification.  The project's home page is at http://getdnsapi.net<http://getdnsapi.net/>.
>
> getdns is a modern asynchronous DNS API. It implements DNS entry points from a design developed and vetted by application developers, in the specification at http://www.vpnc.org/getdns-api/ edited by Paul Hoffman. With the development of this API, we intend to offer application developers a modernized and flexible way to access DNS security (DNSSEC) and other powerful new DNS features; a particular hope is to inspire application developers towards innovative security solutions in their applications.
>
> We invite everyone to take a look at the project and to provide feedback to us and even contribute back to the project!  We expect to have successive releases over the next few months that move us toward a more complete implementation and includes ports to even more platforms.
>
> Signedï¿½the getdns core team:
>
> Craig Despeaux, Verisign, Inc.
> Neel Goyal, Verisign, Inc.
> Olaf Kolkman, NLnet Labs
> Allison Mankin, Verisign Labs.
> Melinda Shore, No Mountain Software LLC
> Willem Toorop, NLnet Labs
> Wouter Wijngaards, NLnet Labs
> Glen Wiley, Verisign, Inc.
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

-- 
HLS



From nobody Wed Feb 26 14:05:22 2014
Return-Path: <glen.wiley@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF4E81A075A for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 14:05:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6gKMbhLvu5er for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 14:05:14 -0800 (PST)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0531A074D for <dnsop@ietf.org>; Wed, 26 Feb 2014 14:05:14 -0800 (PST)
Received: by mail-qc0-f181.google.com with SMTP id c9so2260191qcz.40 for <dnsop@ietf.org>; Wed, 26 Feb 2014 14:05:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8MD4UeeTPMzo+TlSmgjauZH3H5kUA1+tPmXMuewGg9A=; b=OdkB1Rew4f4Rl7RK2uQWAM2tomG6lknu9YKbHZdopfCrZkik6wQC2NEbWLdLeLLYEg 1F8lXpW1qo0+ByDtRZ2A5wC5Kh/btWo0htBB3WpNO7GW0X8rojCkSRobS2Y3GjenxniM Z02rcvqkbjKRrJuk1YYkS8yIgffEqhWKCHk8+C3pxViow7LN42sdfMZTIYpKGX1lZYrK UZZw7M8HPe55seSAYOX9ciBSa2gkPgQISn7ELzw1VsCfzcsT3rIgFuj0S7kazrk3BLej JuOUeiStqlLgGfBcgI5TRB4k2rF1YXsplHlK5+OwEwi4kf2Wevo+Qeupu23iS6RJHO9f q/pQ==
MIME-Version: 1.0
X-Received: by 10.224.79.19 with SMTP id n19mr11441094qak.99.1393452312923; Wed, 26 Feb 2014 14:05:12 -0800 (PST)
Received: by 10.96.58.202 with HTTP; Wed, 26 Feb 2014 14:05:12 -0800 (PST)
In-Reply-To: <530E64A4.2070607@isdg.net>
References: <CF33A0BD.35B11%gwiley@verisign.com> <530E64A4.2070607@isdg.net>
Date: Wed, 26 Feb 2014 17:05:12 -0500
Message-ID: <CANqeWyOpeLRT1fOwomgQkP-17Rau+BVcKAdEmP6cpJrJ06D=OQ@mail.gmail.com>
From: Glen Wiley <glen.wiley@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=047d7bdc80401f94eb04f3566611
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Lou-0hb0BtjxBi9UJxhGsH23JUY
Cc: "Wiley, Glen" <gwiley@verisign.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] beta release of getdns stub resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 22:05:19 -0000

--047d7bdc80401f94eb04f3566611
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Not yet, but that us on the hit list for us.

On Wednesday, February 26, 2014, Hector Santos <hsantos@isdg.net> wrote:

> Is there is a plug and play 32 bit and/or 64 bit Windows version?
>
> On 2/26/2014 1:46 PM, Wiley, Glen wrote:
>
>> Verisign and NLnet Labs are pleased to announce the first beta release
>> (0.1.0) of an open source implementation of the getdns API specification=
.
>>  The project's home page is at http://getdnsapi.net<http://getdnsapi.net=
/
>> >.
>>
>> getdns is a modern asynchronous DNS API. It implements DNS entry points
>> from a design developed and vetted by application developers, in the
>> specification at http://www.vpnc.org/getdns-api/ edited by Paul Hoffman.
>> With the development of this API, we intend to offer application develop=
ers
>> a modernized and flexible way to access DNS security (DNSSEC) and other
>> powerful new DNS features; a particular hope is to inspire application
>> developers towards innovative security solutions in their applications.
>>
>> We invite everyone to take a look at the project and to provide feedback
>> to us and even contribute back to the project!  We expect to have
>> successive releases over the next few months that move us toward a more
>> complete implementation and includes ports to even more platforms.
>>
>> Signed=EF=BF=BDthe getdns core team:
>>
>> Craig Despeaux, Verisign, Inc.
>> Neel Goyal, Verisign, Inc.
>> Olaf Kolkman, NLnet Labs
>> Allison Mankin, Verisign Labs.
>> Melinda Shore, No Mountain Software LLC
>> Willem Toorop, NLnet Labs
>> Wouter Wijngaards, NLnet Labs
>> Glen Wiley, Verisign, Inc.
>>
>>
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>>
> --
> HLS
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>


--=20
Glen Wiley
KK4SFV

"A designer knows he has achieved perfection not when there is nothing left
to add, but when there is nothing left to take away." - Antoine de
Saint-Exupery

--047d7bdc80401f94eb04f3566611
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Not yet, but that us on the hit list for us. =C2=A0<span></span><br><br>On =
Wednesday, February 26, 2014, Hector Santos &lt;<a href=3D"mailto:hsantos@i=
sdg.net">hsantos@isdg.net</a>&gt; wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there is a plug and play 32 bit and/or 64 bit Windows version?<br>
<br>
On 2/26/2014 1:46 PM, Wiley, Glen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Verisign and NLnet Labs are pleased to announce the first beta release (0.1=
.0) of an open source implementation of the getdns API specification. =C2=
=A0The project&#39;s home page is at <a href=3D"http://getdnsapi.net" targe=
t=3D"_blank">http://getdnsapi.net</a>&lt;<a href=3D"http://getdnsapi.net/" =
target=3D"_blank">http://<u></u>getdnsapi.net/</a>&gt;.<br>

<br>
getdns is a modern asynchronous DNS API. It implements DNS entry points fro=
m a design developed and vetted by application developers, in the specifica=
tion at <a href=3D"http://www.vpnc.org/getdns-api/" target=3D"_blank">http:=
//www.vpnc.org/getdns-<u></u>api/</a> edited by Paul Hoffman. With the deve=
lopment of this API, we intend to offer application developers a modernized=
 and flexible way to access DNS security (DNSSEC) and other powerful new DN=
S features; a particular hope is to inspire application developers towards =
innovative security solutions in their applications.<br>

<br>
We invite everyone to take a look at the project and to provide feedback to=
 us and even contribute back to the project! =C2=A0We expect to have succes=
sive releases over the next few months that move us toward a more complete =
implementation and includes ports to even more platforms.<br>

<br>
Signed=EF=BF=BDthe getdns core team:<br>
<br>
Craig Despeaux, Verisign, Inc.<br>
Neel Goyal, Verisign, Inc.<br>
Olaf Kolkman, NLnet Labs<br>
Allison Mankin, Verisign Labs.<br>
Melinda Shore, No Mountain Software LLC<br>
Willem Toorop, NLnet Labs<br>
Wouter Wijngaards, NLnet Labs<br>
Glen Wiley, Verisign, Inc.<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
DNSOP mailing list<br>
<a>DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/dnsop</a><br>
<br>
</blockquote>
<br>
-- <br>
HLS<br>
<br>
<br>
______________________________<u></u>_________________<br>
DNSOP mailing list<br>
<a>DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/dnsop</a><br>
</blockquote><br><br>-- <br><div dir=3D"ltr">Glen Wiley<div>KK4SFV</div><di=
v><br><span style=3D"font-family:arial,sans-serif;font-size:13px;border-col=
lapse:collapse;color:rgb(34,34,34)">&quot;A designer knows he has achieved =
perfection not when there is nothing left to add, but when there is nothing=
 left to take away.&quot; - Antoine de Saint-Exupery</span></div>
</div><br>

--047d7bdc80401f94eb04f3566611--


From nobody Wed Feb 26 14:53:25 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2824E1A0749 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 14:53:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-4CdkGsGME0 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 14:53:14 -0800 (PST)
Received: from winserver.com (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 208E81A0726 for <dnsop@ietf.org>; Wed, 26 Feb 2014 14:53:14 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2477; t=1393455188; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=MUZFZeLwAs4nz9lGs5MJraCwJtA=; b=sN791jCLlDGmsnzxHz/k P3THMjYQO2DXj/k1K2yJEXuowFFZw3DuLbgQu/vQkqvFzTLd5h5WX/VYKf/PBqyo cbuFEAKSkxUXjCLMCjmezgcRW9v21gCy4N627Pbc6tDDKvlYXNL22nAXC3Y59Al+ 82TjYdX+uvTit25eh+t+THM=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for dnsop@ietf.org; Wed, 26 Feb 2014 17:53:08 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2737647887.20363.4988; Wed, 26 Feb 2014 17:53:07 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2477; t=1393454546; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=N3efEtJ B5gL5n7lN9UB+CP9yFKZx2CcLFc76YMsnm9I=; b=p1hZiwy0mT6ysBAGsKDJQC1 FAY6DbtR1GeA0V8z8WMfvBkWUowHYa8ReNELEDMIKNguSoTQ4qnF5vAHZJDk5s1a AgUBlLNRP53XifKXb+noYjUmda+tZAtXxHuleLRyB6ivY6tTlIRmbFT5IjCFrPtB TFty61vqUOSD4Vh0zaFg=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for dnsop@ietf.org; Wed, 26 Feb 2014 17:42:26 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2183925553.9.668; Wed, 26 Feb 2014 17:42:25 -0500
Message-ID: <530E7052.2000400@isdg.net>
Date: Wed, 26 Feb 2014 17:53:06 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "dnsop@ietf.org" <dnsop@ietf.org>
References: <CF33A0BD.35B11%gwiley@verisign.com>	<530E64A4.2070607@isdg.net> <CANqeWyOpeLRT1fOwomgQkP-17Rau+BVcKAdEmP6cpJrJ06D=OQ@mail.gmail.com>
In-Reply-To: <CANqeWyOpeLRT1fOwomgQkP-17Rau+BVcKAdEmP6cpJrJ06D=OQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/6nPo94goi3ts3c0O6-pYiRNnLN8
Subject: Re: [DNSOP] beta release of getdns stub resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 22:53:17 -0000

I should note that we invested heavy in DNS API development that 
allowed for single sourcing and caching across many applications (DNS 
clients users of the API).  If *local* caching is not part of it, it 
would not help in its consideration (for us).

--
HLS


On 2/26/2014 5:05 PM, Glen Wiley wrote:
> Not yet, but that us on the hit list for us.
>
> On Wednesday, February 26, 2014, Hector Santos <hsantos@isdg.net> wrote:
>
>> Is there is a plug and play 32 bit and/or 64 bit Windows version?
>>
>> On 2/26/2014 1:46 PM, Wiley, Glen wrote:
>>
>>> Verisign and NLnet Labs are pleased to announce the first beta release
>>> (0.1.0) of an open source implementation of the getdns API specification.
>>>   The project's home page is at http://getdnsapi.net<http://getdnsapi.net/
>>>> .
>>>
>>> getdns is a modern asynchronous DNS API. It implements DNS entry points
>>> from a design developed and vetted by application developers, in the
>>> specification at http://www.vpnc.org/getdns-api/ edited by Paul Hoffman.
>>> With the development of this API, we intend to offer application developers
>>> a modernized and flexible way to access DNS security (DNSSEC) and other
>>> powerful new DNS features; a particular hope is to inspire application
>>> developers towards innovative security solutions in their applications.
>>>
>>> We invite everyone to take a look at the project and to provide feedback
>>> to us and even contribute back to the project!  We expect to have
>>> successive releases over the next few months that move us toward a more
>>> complete implementation and includes ports to even more platforms.
>>>
>>> Signedï¿½the getdns core team:
>>>
>>> Craig Despeaux, Verisign, Inc.
>>> Neel Goyal, Verisign, Inc.
>>> Olaf Kolkman, NLnet Labs
>>> Allison Mankin, Verisign Labs.
>>> Melinda Shore, No Mountain Software LLC
>>> Willem Toorop, NLnet Labs
>>> Wouter Wijngaards, NLnet Labs
>>> Glen Wiley, Verisign, Inc.
>>>
>>>
>>>
>>> _______________________________________________
>>> DNSOP mailing list
>>> DNSOP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dnsop
>>>
>>>
>> --
>> HLS
>>
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

-- 
HLS



From nobody Wed Feb 26 15:20:06 2014
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C481A02F3 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 15:19:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TdBwa4mlei5P for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 15:19:53 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 068A01A02F1 for <dnsop@ietf.org>; Wed, 26 Feb 2014 15:19:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 4D3938693E; Wed, 26 Feb 2014 18:19:50 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 40294-02; Wed, 26 Feb 2014 18:19:49 -0500 (EST)
Received: from [10.0.1.2] (unknown [182.173.75.2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 6BA558693D; Wed, 26 Feb 2014 18:19:47 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_196EAF71-9F8C-416D-8D37-7BD2EBF86381"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca>
Date: Thu, 27 Feb 2014 07:19:38 +0800
Message-Id: <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/LWZ7lHJ5nVooxAA0c9gGcT1VhUk
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 23:19:57 -0000

--Apple-Mail=_196EAF71-9F8C-416D-8D37-7BD2EBF86381
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Joe,

On Feb 26, 2014, at 10:34 PM, Joe Abley <jabley@hopcount.ca> wrote:
>>> On Feb 25, 2014, at 9:51 AM, Stuart Cheshire <cheshire@apple.com> =
wrote:
>>>> If we have *some* pseudo-TLDs reserved for local-use names,
> I still don=92t see why we need a TLD, or a delegation/reservation =
under ARPA.

Because if something isn't documented, people tend to squat.

> There are many, many TLDs under which an application/protocol =
implementer can reserve some namespace for their exclusive use at low =
cost ($10/year, say). Why is this approach not preferred for a new =
application/protocol? It seems far simpler.

Why does RFC 1918 address space exist?

Regards,
-drc


--Apple-Mail=_196EAF71-9F8C-416D-8D37-7BD2EBF86381
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTDnaKAAoJENV6ebf0/4rXSUgH/jz+HlRsm7xmjLRg0RP/vHAn
j9WnJB5RASC7wjTmj/KplNQzyMZvmgSwcF8NlZNwE9/L/pUA8bjguj2nMni/irnw
73BA/39fc1vlFNi6n1UuTEjFx9w2fYoxFk2x0Zjf2xd0U/THJhWisggFohXy0T5H
0iGIpAAr07Kj3y1QR0R59TMjZ0usxLDd0V9CZdoZcJzwRyqCFrJJS7twLtDvYWyl
xmUPViNyeRbw8tbnHKFiGukGgeZeccjDF6qiSFlsKP1zPJAScUE4+9PC+JGCDrN+
ScyLGer3DOh5mVvFwENwwXeRHvoBQsml9byI8FkDqGB+r1ChuTqGHs3VP1UcY2Q=
=1Gi3
-----END PGP SIGNATURE-----

--Apple-Mail=_196EAF71-9F8C-416D-8D37-7BD2EBF86381--


From nobody Wed Feb 26 15:39:39 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212121A066B for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 15:39:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.343
X-Spam-Level: **
X-Spam-Status: No, score=2.343 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gqgxUB59doY for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 15:39:29 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 72B861A01EE for <dnsop@ietf.org>; Wed, 26 Feb 2014 15:39:29 -0800 (PST)
Received: (qmail 86789 invoked from network); 26 Feb 2014 23:39:27 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 26 Feb 2014 23:39:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=530e7b31.xn--i8sz2z.k1402; i=johnl@user.iecc.com; bh=yZrgNj8tiwvFP+EAvDvC4p8ql5uNA+scJWGi7ZZhXco=; b=NsoxotlV1Gs+gyVaYHFqU9W2QxJUn7r/umaoF/g1VYbCLILd5QPDgLXGJGhi6Vgp95DwW+7V94ln+uJXkSNMPqsD4IbAsJYmbr7MpJKYip6pUVuBqF2SqJfDzSTPDTMgqEPBG6IZlFjiFNMP/wL/z++wblPpBYeKJlntqefXOqFAwtx0zxBFabnPz8zIxTFQTrb04qpZRl72OLikt1iQGTmc3rDXt9SZK7g4jkty08XguqVRDi7iGAA2pQfVM/J3
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=530e7b31.xn--i8sz2z.k1402; bh=yZrgNj8tiwvFP+EAvDvC4p8ql5uNA+scJWGi7ZZhXco=;  b=oWi4SUje+WvGmt9tTB/gYNcTBItG/n2szsQeyv3uQ1fdXUBHEVXeTIt7Je9qMBbjzzWXpipuho3eFugk4yMidfWYn9Hn+sm3GcowgdwqVm6qVFBUWJBgbT4akBCcJdRZHyv8i0InTY2atWob6+8DWvUKQo4VrCtuFWqDqH4hH1NiG1BL55uJf1ao/9vEPnaE1R3zIIpALidFWZi/9/kburGGNWVQFHS1kU5xbh5/5JcmMzt+ECfoxLhWpUbz7TM6
Date: 26 Feb 2014 23:39:07 -0000
Message-ID: <20140226233907.6214.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/5-_33XYiIUSm2eehPloYTjVHB0w
Cc: jabley@hopcount.ca
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 23:39:32 -0000

>Perhaps all that is missing is some guidance that says “you shouldn’t hijack
>namespaces that you don’t control, even for non-DNS applications; register a
>domain instead”.

That's a relatively high bar for all the residential broadband users
who buy a router at Best Buy (Future Shop to you), plug it in, and set
up the router via the configuration page at http://router.home.

What do they get for their $10/yr and extra config hassle that they
would care about?

R's,
John

PS: Don't miss ICANN's latest on this point:

http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm

They commissioned a report that says to reserve .HOME .CORP and .MAIL,
and to do a 120 day wildcard on new domains that returns 127.0.53.53
to alert people to upcoming problems and see what the traffic is.  It
notably does not suggest how to interpret the results after the 120
days.


From nobody Wed Feb 26 18:15:14 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27B711A02B7 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 18:14:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id De1h_Pnj8qp9 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 18:14:53 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 752D11A01A9 for <dnsop@ietf.org>; Wed, 26 Feb 2014 18:14:53 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 35DC9C944A; Thu, 27 Feb 2014 02:14:39 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1393467292; bh=L7zFv/Hl3gEmI/RZ/PYFuaxuKvyFWonSrDwZ/9Uz8DU=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=Z4IOtky0VVEqklDZYdoW4nb7Jsy+ql7nZDVcdhj4zeeTKieu5QiEdZeJmq2IqKV0g VdHm0OddinQtWCbHq0Mlw2jZI4WKJLvhYww9VejKTLnSXzpNlVvIgGlAjHReNLMvyo rWAdVbrJ57q9YlC1IqE0aeqpsE8MujZFAHYKmOZw=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Thu, 27 Feb 2014 02:14:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id DD9D616005C; Thu, 27 Feb 2014 02:15:31 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id AACF016004A; Thu, 27 Feb 2014 02:15:31 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id E957210702F7; Thu, 27 Feb 2014 13:14:36 +1100 (EST)
To: David Conrad <drc@virtualized.org>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org>
In-reply-to: Your message of "Thu, 27 Feb 2014 07:19:38 +0800." <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org>
Date: Thu, 27 Feb 2014 13:14:36 +1100
Message-Id: <20140227021436.E957210702F7@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/PooTKbtZJ2M0H9SR9ZO5y5mnKEk
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 02:14:59 -0000

In message <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org>, David Conrad
 writes:
>
> Joe,
>
> On Feb 26, 2014, at 10:34 PM, Joe Abley <jabley@hopcount.ca> wrote:
> >>> On Feb 25, 2014, at 9:51 AM, Stuart Cheshire <cheshire@apple.com>
> wrote:
> >>>> If we have *some* pseudo-TLDs reserved for local-use names,
> > I still don't see why we need a TLD, or a delegation/reservation under
> ARPA.
>
> Because if something isn't documented, people tend to squat.
>
> > There are many, many TLDs under which an application/protocol
> implementer can reserve some namespace for their exclusive use at low
> cost ($10/year, say). Why is this approach not preferred for a new
> application/protocol? It seems far simpler.
>
> Why does RFC 1918 address space exist?

Because IPv4 address were and always have been a scarse resource
and RFC 1918 is a reaction to that.  Homes use it because CPE vendors
built it into their devices because

	* Lots of ISP's would only give you one address
	* Those that didn't often charged you a lot
	* Ridiculous ISP terms and conditions that prohibited multiple
	  machines.

> Regards,
> -drc
> 
> 
> --Apple-Mail=_196EAF71-9F8C-416D-8D37-7BD2EBF86381
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
> 	filename=signature.asc
> Content-Type: application/pgp-signature;
> 	name=signature.asc
> Content-Description: Message signed with OpenPGP using GPGMail
> 
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> 
> iQEcBAEBAgAGBQJTDnaKAAoJENV6ebf0/4rXSUgH/jz+HlRsm7xmjLRg0RP/vHAn
> j9WnJB5RASC7wjTmj/KplNQzyMZvmgSwcF8NlZNwE9/L/pUA8bjguj2nMni/irnw
> 73BA/39fc1vlFNi6n1UuTEjFx9w2fYoxFk2x0Zjf2xd0U/THJhWisggFohXy0T5H
> 0iGIpAAr07Kj3y1QR0R59TMjZ0usxLDd0V9CZdoZcJzwRyqCFrJJS7twLtDvYWyl
> xmUPViNyeRbw8tbnHKFiGukGgeZeccjDF6qiSFlsKP1zPJAScUE4+9PC+JGCDrN+
> ScyLGer3DOh5mVvFwENwwXeRHvoBQsml9byI8FkDqGB+r1ChuTqGHs3VP1UcY2Q=
> =1Gi3
> -----END PGP SIGNATURE-----
> 
> --Apple-Mail=_196EAF71-9F8C-416D-8D37-7BD2EBF86381--
> 
> 
> --===============0999451085410326449==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
> 
> --===============0999451085410326449==--
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Feb 26 18:56:42 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA661A0807 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 18:56:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5Gur2BFLoa3 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 18:56:35 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 076141A0369 for <dnsop@ietf.org>; Wed, 26 Feb 2014 18:56:35 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 0E239238400; Thu, 27 Feb 2014 02:56:20 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 3451C16004C; Thu, 27 Feb 2014 02:57:12 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 4772A16004A; Thu, 27 Feb 2014 02:57:11 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 0101A107642C; Thu, 27 Feb 2014 13:56:16 +1100 (EST)
To: "John Levine" <johnl@taugh.com>
From: Mark Andrews <marka@isc.org>
References: <20140226233907.6214.qmail@joyce.lan>
In-reply-to: Your message of "26 Feb 2014 23:39:07 -0000." <20140226233907.6214.qmail@joyce.lan>
Date: Thu, 27 Feb 2014 13:56:16 +1100
Message-Id: <20140227025617.0101A107642C@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/csPftEQlpHdUuovCWjpvXyPCC1g
Cc: dnsop@ietf.org, jabley@hopcount.ca
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 02:56:39 -0000

In message <20140226233907.6214.qmail@joyce.lan>, "John Levine" writes:
> 
> >Perhaps all that is missing is some guidance that says "you shouldn't hijack
> >namespaces that you don't control, even for non-DNS applications; register a
> >domain instead".
> 
> That's a relatively high bar for all the residential broadband users
> who buy a router at Best Buy (Future Shop to you), plug it in, and set
> up the router via the configuration page at http://router.home.

And why wasn't that "http://router.netgear.com" or
"http://router.linksys.com". The router could easily serve the zone
locally and the vendor could have a insecure delegation to it so
it works if there are validating browsers being used.

http://router.home does not work with validating browsers.

If the CPE vendors want to use .home let them pony up the 100K for
it rather than hijack the namespace.

> What do they get for their $10/yr and extra config hassle that they
> would care about?
> 
> R's,
> John
> 
> PS: Don't miss ICANN's latest on this point:
> 
> http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm
> 
> They commissioned a report that says to reserve .HOME .CORP and .MAIL,
> and to do a 120 day wildcard on new domains that returns 127.0.53.53
> to alert people to upcoming problems and see what the traffic is.  It
> notably does not suggest how to interpret the results after the 120
> days.
> 
> 
> --===============4405462344142669891==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
> 
> --===============4405462344142669891==--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Feb 26 19:19:50 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1927D1A01D3 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 19:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7iOFpe-yHEFF for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 19:19:44 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 78B8C1A015C for <dnsop@ietf.org>; Wed, 26 Feb 2014 19:19:44 -0800 (PST)
Received: (qmail 19357 invoked from network); 27 Feb 2014 03:19:42 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 27 Feb 2014 03:19:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=530eaed0.xn--3zv.k1402; i=johnl@user.iecc.com; bh=Z29JYi1DOxkHy8SriE7G/8hUTFpR210N+k9Ony7RvRw=; b=Wa9DS0mzDhE8h0m3GTrmM16VSHIOtDuv12TmnsJj0XiDPTRBgKNgtIdDwwupz47hWnZUMkCqJ/iVueYcmny37mwhCcICXbwPHYvIAeHFyx/5L/6K9ckotrJJsK/ITKvpUlF3Kz9BTWnVPKpjqICDlSG2f4y4osqw9PIPgnKE4a7/+Bs1oDRfRi6qoJ0O3+Ll12Y2vUqWuBbKY2pT/wvN4WLK/QDRwjoIqZNtcWa/34I/iileYbMXomLtcWL1iGDb
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=530eaed0.xn--3zv.k1402; bh=Z29JYi1DOxkHy8SriE7G/8hUTFpR210N+k9Ony7RvRw=; b=E/neH9+eJzgRnr178qPcSbBXWkJx6JsE7ZcV+5XCLl2rEpJ2V9z6jKuDSf7A5EgpCzFCGvi4D/K79HRFgXBVabZK/MR7KNiAP/V3xRcY+b6c6lpyAQoKzkDN0uSyai9B6ZUvtpt9KHJ3YRCW68a/WT2XwiA1Wsc9bYRHSajSbwxXJD+9PCb7XCff681basb5rWCg594ONsA+MNC4Am8L63FhzHht3SlYoGKyAxh58wGKXKV4RwEirGButVS+5t7p
Date: 27 Feb 2014 03:19:21 -0000
Message-ID: <20140227031921.7962.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20140227025617.0101A107642C@rock.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tSm9u1gcl7cByUtm75jrSykkaOw
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 03:19:46 -0000

>> That's a relatively high bar for all the residential broadband users
>> who buy a router at Best Buy (Future Shop to you), plug it in, and set
>> up the router via the configuration page at http://router.home.
>
>And why wasn't that "http://router.netgear.com" or
>"http://router.linksys.com".

I dunno, but that doesn't help much once the network is online and
there are other devices with .home names.

>If the CPE vendors want to use .home let them pony up the 100K for
>it rather than hijack the namespace.

Um, it's a wee bit late for that.

R's,
John


From nobody Wed Feb 26 19:37:43 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558371A0711 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 19:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0LxPMFH52Ct for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 19:37:40 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 17CFF1A0373 for <dnsop@ietf.org>; Wed, 26 Feb 2014 19:37:40 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s1R3ba7l093507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Feb 2014 20:37:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140226233907.6214.qmail@joyce.lan>
Date: Wed, 26 Feb 2014 19:37:35 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DA454DE-5429-4563-8593-0593920CE4EC@vpnc.org>
References: <20140226233907.6214.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/qmIdxMl5hEO-E0CMpygL_g4sBsg
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 03:37:41 -0000

On Feb 26, 2014, at 3:39 PM, John Levine <johnl@taugh.com> wrote:

>> Perhaps all that is missing is some guidance that says =EF=BF=BDyou =
shouldn=EF=BF=BDt hijack
>> namespaces that you don=EF=BF=BDt control, even for non-DNS =
applications; register a
>> domain instead=EF=BF=BD.
>=20
> That's a relatively high bar for all the residential broadband users
> who buy a router at Best Buy (Future Shop to you), plug it in, and set
> up the router via the configuration page at http://router.home.

Ummm, why do those people need to have a unique domain name at all?

> PS: Don't miss ICANN's latest on this point:
>=20
> http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm

That's unrelated to "this point", it seems.

--Paul Hoffman=


From nobody Wed Feb 26 19:43:02 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 589071A0663 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 19:43:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_44=0.6, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2A8GF1A7xzF for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 19:42:59 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 236701A01D3 for <dnsop@ietf.org>; Wed, 26 Feb 2014 19:42:59 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id D66A22383A7; Thu, 27 Feb 2014 03:42:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 112C416004C; Thu, 27 Feb 2014 03:43:36 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id D065D16004A; Thu, 27 Feb 2014 03:43:35 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id A4CB01077146; Thu, 27 Feb 2014 14:42:41 +1100 (EST)
To: "John Levine" <johnl@taugh.com>
From: Mark Andrews <marka@isc.org>
References: <20140227031921.7962.qmail@joyce.lan>
In-reply-to: Your message of "27 Feb 2014 03:19:21 -0000." <20140227031921.7962.qmail@joyce.lan>
Date: Thu, 27 Feb 2014 14:42:41 +1100
Message-Id: <20140227034241.A4CB01077146@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/3BusUrdObqbhwpU7I__bU83yrsM
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 03:43:01 -0000

In message <20140227031921.7962.qmail@joyce.lan>, "John Levine" writes:
> >> That's a relatively high bar for all the residential broadband users
> >> who buy a router at Best Buy (Future Shop to you), plug it in, and set
> >> up the router via the configuration page at http://router.home.
> >
> >And why wasn't that "http://router.netgear.com" or
> >"http://router.linksys.com".
> 
> I dunno, but that doesn't help much once the network is online and
> there are other devices with .home names.

Whether is it router.home or router.vendor.com, both names assume
that the CPE device is in the DNS lookup path to get the correct
address returned for the name.

If the CPE puts out a search list of "home.arpa" rather than "home"
in the DHCP lease and added the machines to home.arpa rather than
home zone I doubt many people would notice.  Most home users would
be using unqualified names and the resolver's search will qualify
them.

This is all about getting sensible defaults in new CPE devices and
have a reserved place for them.  This should already be configurable
if they doing this sort of thing.

> >If the CPE vendors want to use .home let them pony up the 100K for
> >it rather than hijack the namespace.
> 
> Um, it's a wee bit late for that.
> 
> R's,
> John
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Feb 26 22:16:34 2014
Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC221A0412 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 22:16:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zru9n4ROai1z for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 22:16:29 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1F21A039B for <dnsop@ietf.org>; Wed, 26 Feb 2014 22:16:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id A453D86940; Thu, 27 Feb 2014 01:16:27 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 42250-05; Thu, 27 Feb 2014 01:16:27 -0500 (EST)
Received: from 139.146.dhcp.conference.apricot.net (unknown [220.247.146.139]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 9C2E08693F; Thu, 27 Feb 2014 01:16:24 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_B56481B9-34A1-479C-AEDB-5ABD00D94C2B"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20140227021436.E957210702F7@rock.dv.isc.org>
Date: Thu, 27 Feb 2014 14:16:15 +0800
Message-Id: <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/o9pcpjBrDAeBdZpZ5lXL8Z_cYWU
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 06:16:32 -0000

--Apple-Mail=_B56481B9-34A1-479C-AEDB-5ABD00D94C2B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mark,

On Feb 27, 2014, at 10:14 AM, Mark Andrews <marka@isc.org> wrote:
>>> There are many, many TLDs under which an application/protocol =
implementer can reserve some namespace for their exclusive use at low =
cost ($10/year, say). Why is this approach not preferred for a new =
application/protocol? It seems far simpler.
>>=20
>> Why does RFC 1918 address space exist?
>=20
> Because IPv4 address were and always have been a scarse resource and =
RFC 1918 is a reaction to that. =20

Not really.  RFC 1918 was created when IPv4 addresses were still =
relatively plentiful.  Many folks used 1918 space because they didn't =
want to be bothered with putting up with the hassles and cost (even if =
it was trivial) of obtaining space from the registries for a resource =
that was never going to be used on the Internet.

There are a number of potential options for 'private' domain space. I do =
not believe the answer of "buy a domain" will alleviate the problem as =
paying money and wading through web forms, etc., will always be harder =
that simply squatting on a domain name.

Regards,
-drc



--Apple-Mail=_B56481B9-34A1-479C-AEDB-5ABD00D94C2B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTDtgxAAoJENV6ebf0/4rX8d0H/38SbVok8WnMMzTKrd5/74ye
LEZHMyNSSNvI7gefcxtxsh8XCqwj5DqNESuhV8AIodQZj/YHt6vxaIHh2ShPAwAz
ZGqsYs4TClEm35Cxx9zWwCSnmzgaRJ4H0OlsjTN4Ev3wuYRKHRy/oCn/miXmCYml
6vzCgVltidQvV4tpry1ga9uCEbvNNhTfqmJRYtijpIsDDlGyhoy/pYF5PJW4l8nc
01v4DjuGqmN9RCbqhYKNbmoYj1eta+a81+97tRLKkRr1nTPsPievdGJG40z3wUPk
8gS3S2AmNLOPd6vvZNC5FE33kURJAWfp8/VWUA+f/qQoyOmS7lKX2m/CPwIG2jk=
=nCW/
-----END PGP SIGNATURE-----

--Apple-Mail=_B56481B9-34A1-479C-AEDB-5ABD00D94C2B--


From nobody Wed Feb 26 23:43:08 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA041A0005 for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 23:43:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.148
X-Spam-Level: 
X-Spam-Status: No, score=-1.148 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F4orNOfHP0Fe for <dnsop@ietfa.amsl.com>; Wed, 26 Feb 2014 23:43:06 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 093731A0007 for <dnsop@ietf.org>; Wed, 26 Feb 2014 23:43:06 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id ECC25C94DA; Thu, 27 Feb 2014 07:42:51 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1393486984; bh=HQ7Gf+P36TawcAQ2GxmA6XbMsQz/T4fe0U7vOlAnNTk=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=AZvJ33t5VfCpUdHN6uUtFxn21/MmHcj3295WfCeDCo1vx9fqZ28iVOBQiDwWdln7J 1zDIhf2WRntxD9seEu2RNfRh8Zu8wpRoZdu6hrO7V5KNi4I+aHjF5gP8bd+Czx1rH9 zH2diwK2vkTt3C5vNP0DQIAsdY2R1yfAWeJixiDo=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Thu, 27 Feb 2014 07:42:51 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id BBDA216005C; Thu, 27 Feb 2014 07:43:44 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 8276E160056; Thu, 27 Feb 2014 07:43:44 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 2972F107D273; Thu, 27 Feb 2014 18:42:49 +1100 (EST)
To: David Conrad <drc@virtualized.org>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org> <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org>
In-reply-to: Your message of "Thu, 27 Feb 2014 14:16:15 +0800." <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org>
Date: Thu, 27 Feb 2014 18:42:49 +1100
Message-Id: <20140227074249.2972F107D273@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/5sn0TPdvzOIVysXSPf32Z3ELg74
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 07:43:08 -0000

In message <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org>, David Conrad
 writes:
>
> Mark,
>
> On Feb 27, 2014, at 10:14 AM, Mark Andrews <marka@isc.org> wrote:
> >>> There are many, many TLDs under which an application/protocol
> implementer can reserve some namespace for their exclusive use at low
> cost ($10/year, say). Why is this approach not preferred for a new
> application/protocol? It seems far simpler.
> >>
> >> Why does RFC 1918 address space exist?
> >
> > Because IPv4 address were and always have been a scarse resource and
> RFC 1918 is a reaction to that.
>
> Not really.  RFC 1918 was created when IPv4 addresses were still
> relatively plentiful.  Many folks used 1918 space because they didn't
> want to be bothered with putting up with the hassles and cost (even if it
> was trivial) of obtaining space from the registries for a resource that
> was never going to be used on the Internet.

While there are multiple reasons, RFC 1918 does actually state that address
space is a scare resource.  

   The Internet has grown beyond anyone's expectations. Sustained
   exponential growth continues to introduce new challenges.  One
   challenge is a concern within the community that globally unique
   address space will be exhausted. A separate and far more pressing
   concern is that the amount of routing overhead will grow beyond the
   capabilities of Internet Service Providers. Efforts are in progress
   within the community to find long term solutions to both of these
   problems. Meanwhile it is necessary to revisit address allocation
   procedures, and their impact on the Internet routing system.

> There are a number of potential options for 'private' domain space. I do
> not believe the answer of "buy a domain" will alleviate the problem as
> paying money and wading through web forms, etc., will always be harder
> that simply squatting on a domain name.

Well hopefully DNSSEC will eventually be on by default and squatting
like this will have negative consequences.  There may be a need for
a reserved suffix.  It doesn't have to be .HOME.  Rewarding bad
behaviour leads to more bad behaviour.

> Regards,
> -drc
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Feb 27 03:46:03 2014
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0B121A0256 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 03:46:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.548
X-Spam-Level: 
X-Spam-Status: No, score=-0.548 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fz3lNsPQ8Tda for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 03:45:59 -0800 (PST)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id C5D6E1A024F for <dnsop@ietf.org>; Thu, 27 Feb 2014 03:45:58 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 7673224212ED; Thu, 27 Feb 2014 11:45:53 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20140227074249.2972F107D273@rock.dv.isc.org>
Date: Thu, 27 Feb 2014 11:45:52 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org> <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org> <20140227074249.2972F107D273@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/qwRbrVGseccDN9OnVxD8jXSZsYI
Cc: DNSOP WG <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 11:46:01 -0000

On 27 Feb 2014, at 07:42, Mark Andrews <marka@isc.org> wrote:

> DNSSEC will eventually be on by default and squatting like this will =
have negative consequences.

Er, no. Vendors who pluck domain names out of the ether and use them in =
their products will by definition not have the DNS clue required for =
deploying a viable DNSSEC. Besides, in the case of CPE, they won't even =
*need* DNSSEC because the offending domain names (router.home or =
whatever) get looked up on the internal net. Most likely those names =
will be used by web browsers that do not have a validating resolver and =
are already relying on the CPE for DNS. Those lookups will almost never =
go to the outside, far less validate a signed referral for .whatever =
from the root.

> There may be a need for a reserved suffix.  It doesn't have to be =
.HOME.  Rewarding bad
> behaviour leads to more bad behaviour.

IMO, the draft aims to document existing bad behaviour and explains why =
people should stop doing those bad/stupid/wrong things. Or at least =
appreciate the consequences. This is a Good Thing. It might even mean =
fewer instances of bad behaviour in future. Whether of course the =
writers of CPE crapware will ever read this RFC, let alone act on it, is =
another matter. At least the IETF will have produced a useful document =
on the topic. Which is all it could do.

BTW, the latest thinking (ie as of yesterday) from ICANN is .home will =
be reserved indefinitely: =
http://www.icann.org/en/news/public-comment/name-collision-26feb14-en.htm.=
 It doesn't matter now whether someone wants to call that "rewarding bad =
behaviour" or not. That train left the station a long, long time ago. =
[And I'm long past caring either way.] So it seems to me ICANN is =
acknowledging reality and taking prudent measures for overall security =
and stability of the DNS. Too much stuff is already (ab)using .home so =
this TLD can't go into the public root for the obvious reasons.=


From nobody Thu Feb 27 03:55:42 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8071A018F for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 03:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wriQMFG_tZkP for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 03:55:39 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3BC1A018D for <dnsop@ietf.org>; Thu, 27 Feb 2014 03:55:39 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 657F02383F7; Thu, 27 Feb 2014 11:55:22 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id C0F2916005C; Thu, 27 Feb 2014 11:56:14 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 91592160056; Thu, 27 Feb 2014 11:56:14 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id D4628107FA73; Thu, 27 Feb 2014 22:55:18 +1100 (EST)
To: Jim Reid <jim@rfc1035.com>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org> <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org> <20140227074249.2972F107D273@rock.dv.isc.org> <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com>
In-reply-to: Your message of "Thu, 27 Feb 2014 11:45:52 -0000." <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com>
Date: Thu, 27 Feb 2014 22:55:18 +1100
Message-Id: <20140227115518.D4628107FA73@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/-e-3rURXnbFOF91CeGW53TTF7Ck
Cc: DNSOP WG <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 11:55:41 -0000

In message <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com>, Jim Reid writes:
> On 27 Feb 2014, at 07:42, Mark Andrews <marka@isc.org> wrote:
>
> > DNSSEC will eventually be on by default and squatting like this will
> have negative consequences.
>
> Er, no. Vendors who pluck domain names out of the ether and use them in
> their products will by definition not have the DNS clue required for
> deploying a viable DNSSEC. Besides, in the case of CPE, they won't even
> *need* DNSSEC because the offending domain names (router.home or
> whatever) get looked up on the internal net. Most likely those names will
> be used by web browsers that do not have a validating resolver and are
> already relying on the CPE for DNS. Those lookups will almost never go to
> the outside, far less validate a signed referral for .whatever from the
> root.

And the moment you have a validating brower / app they *will* break.

> > There may be a need for a reserved suffix.  It doesn't have to be
> > .HOME.  Rewarding bad behaviour leads to more bad behaviour.
>
> IMO, the draft aims to document existing bad behaviour and explains why
> people should stop doing those bad/stupid/wrong things. Or at least
> appreciate the consequences. This is a Good Thing. It might even mean
> fewer instances of bad behaviour in future. Whether of course the writers
> of CPE crapware will ever read this RFC, let alone act on it, is another
> matter. At least the IETF will have produced a useful document on the
> topic. Which is all it could do.
>
> BTW, the latest thinking (ie as of yesterday) from ICANN is .home will be
> reserved indefinitely:
> http://www.icann.org/en/news/public-comment/name-collision-26feb14-en.htm.
>  It doesn't matter now whether someone wants to call that "rewarding bad
> behaviour" or not. That train left the station a long, long time ago.
> [And I'm long past caring either way.] So it seems to me ICANN is
> acknowledging reality and taking prudent measures for overall security
> and stability of the DNS. Too much stuff is already (ab)using .home so
> this TLD can't go into the public root for the obvious reasons.

reserved indefinitely != insecurely delegated

10.in-addr.arpa is insecurely delegated deliberately to prevent DNSSEC
breakages.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Feb 27 04:15:38 2014
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14F151A026F for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 04:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SigNEDYBt-Ck for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 04:15:35 -0800 (PST)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id B51931A0210 for <dnsop@ietf.org>; Thu, 27 Feb 2014 04:15:35 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 7A7D624212ED; Thu, 27 Feb 2014 12:15:33 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20140227115518.D4628107FA73@rock.dv.isc.org>
Date: Thu, 27 Feb 2014 12:15:31 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D27FE132-502B-46EE-8B55-CB71908BBEB8@rfc1035.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org> <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org> <20140227074249.2972F107D273@rock.dv.isc.org> <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com> <20140227115518.D4628107FA73@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/c-KQGdHHUpCT5KSQgnrEhv8-uSY
Cc: DNSOP WG <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 12:15:37 -0000

On 27 Feb 2014, at 11:55, Mark Andrews <marka@isc.org> wrote:

>=20
> In message <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com>, Jim =
Reid writes:
>> On 27 Feb 2014, at 07:42, Mark Andrews <marka@isc.org> wrote:
>>=20
>>> DNSSEC will eventually be on by default and squatting like this will
>> have negative consequences.
>>=20
>> Er, no. Vendors who pluck domain names out of the ether and use them =
in
>> their products will by definition not have the DNS clue required for
>> deploying a viable DNSSEC. Besides, in the case of CPE, they won't =
even
>> *need* DNSSEC because the offending domain names (router.home or
>> whatever) get looked up on the internal net. Most likely those names =
will
>> be used by web browsers that do not have a validating resolver and =
are
>> already relying on the CPE for DNS. Those lookups will almost never =
go to
>> the outside, far less validate a signed referral for .whatever from =
the
>> root.
>=20
> And the moment you have a validating brower / app they *will* break.

And this is a problem because... ?

I doubt there will ever be validating browsers/apps for accessing CPE =
from the inside. They have no need for DNSSEC because everything's on =
the local net. But let's assume they do. The Netgear app could have a TA =
for .netgear (say) embedded in it. A more likely scenario is the =
software hard-wires a locally scoped IP address to the device and =
doesn't bother with DNS at all. Most CPE is already doing that as a =
fall-back in case local (unsigned) DNS is broken.

> reserved indefinitely !=3D insecurely delegated

Not delegated at all =3D=3D ???

> 10.in-addr.arpa is insecurely delegated deliberately to prevent DNSSEC
> breakages.

Sure. But that's in a part of the name space where end client behaviour =
is known, stable and predictable.

Are you suggesting IANA has to insert provably insecure delegations for =
every possible string that someone, somewhere might be informally using =
as a TLD? Good luck with that.=


From nobody Thu Feb 27 04:22:02 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43CEE1A0269 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 04:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ADot2TvQAsN for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 04:21:58 -0800 (PST)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f51]) by ietfa.amsl.com (Postfix) with ESMTP id BAD561A0217 for <dnsop@ietf.org>; Thu, 27 Feb 2014 04:21:58 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:52235) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1WIzyA-0008FR-YO (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 12:21:42 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WIzyA-00073Q-I6 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 12:21:42 +0000
Date: Thu, 27 Feb 2014 12:21:42 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Jim Reid <jim@rfc1035.com>
In-Reply-To: <D27FE132-502B-46EE-8B55-CB71908BBEB8@rfc1035.com>
Message-ID: <alpine.LSU.2.00.1402271219440.13302@hermes-1.csi.cam.ac.uk>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org> <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org> <20140227074249.2972F107D273@rock.dv.isc.org> <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com> <20140227115518.D4628107FA73@rock.dv.isc.org> <D27FE132-502B-46EE-8B55-CB71908BBEB8@rfc1035.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/icPvagwfCtBZmgoA3OB5V73Skng
Cc: DNSOP WG <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 12:22:01 -0000

Jim Reid <jim@rfc1035.com> wrote:
> On 27 Feb 2014, at 11:55, Mark Andrews <marka@isc.org> wrote:
> >
> > And the moment you have a validating brower / app they *will* break.
>
> And this is a problem because... ?
>
> I doubt there will ever be validating browsers/apps for accessing CPE
> from the inside. They have no need for DNSSEC because everything's on
> the local net.

The problem occurs when common operating systems start shipping validating
resolvers, then users will not be able to browse to http://router.home to
configure their device.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty, Forth, Tyne, Dogger: Southwest 4 or 5, but south 6 to gale
8 at first in Forties and Dogger. Moderate or rough, occasionally very rough
at first in Forties and Dogger. Showers, rain at first. Moderate or good.


From nobody Thu Feb 27 04:55:37 2014
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7493C1A028E for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 04:55:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_64=0.6, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J1hspOScc4YU for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 04:55:35 -0800 (PST)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC4D1A0256 for <dnsop@ietf.org>; Thu, 27 Feb 2014 04:55:35 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id B34E524212ED; Thu, 27 Feb 2014 12:55:30 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <alpine.LSU.2.00.1402271219440.13302@hermes-1.csi.cam.ac.uk>
Date: Thu, 27 Feb 2014 12:55:30 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC2770FB-A9E7-472D-A16D-2BFE5CA153AD@rfc1035.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org> <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org> <20140227074249.2972F107D273@rock.dv.isc.org> <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com> <20140227115518.D4628107FA73@rock.dv.isc.org> <D27FE132-502B-46EE-8B55-CB71908BBEB8@rfc1035.com> <alpine.LSU.2.00.1402271219440.13302@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/OY6QMgs3S0fsCVHN2nxU7a8SaC4
Cc: DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 12:55:36 -0000

On 27 Feb 2014, at 12:21, Tony Finch <dot@dotat.at> wrote:

> The problem occurs when common operating systems start shipping =
validating
> resolvers, then users will not be able to browse to http://router.home =
to
> configure their device.

An what do these users currently do when router.home or whatever doesn't =
resolve regardless of whether DNSSEC is involved?

IMO there is no actual problem apart from perhaps a minor inconvenience =
that's no different from the current (unsigned) failure mode.

Nothing to see here, move along...


From nobody Thu Feb 27 05:17:13 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C5A1A027F for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 05:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_64=0.6, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFwr7Gu8jKLg for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 05:17:09 -0800 (PST)
Received: from ppsw-40.csi.cam.ac.uk (ppsw-40-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f40]) by ietfa.amsl.com (Postfix) with ESMTP id D2B351A021A for <dnsop@ietf.org>; Thu, 27 Feb 2014 05:17:08 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:52454) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1WJ0pm-0005JW-kt (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 13:17:06 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WJ0pm-0004DK-Ex (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 13:17:06 +0000
Date: Thu, 27 Feb 2014 13:17:06 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Jim Reid <jim@rfc1035.com>
In-Reply-To: <DC2770FB-A9E7-472D-A16D-2BFE5CA153AD@rfc1035.com>
Message-ID: <alpine.LSU.2.00.1402271315430.18502@hermes-1.csi.cam.ac.uk>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <54BE75D7-E70B-46AB-93C1-042E655BB5E7@apple.com> <D0AC0015-63C3-4C03-A8D0-888C435D2775@virtualized.org> <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <6F605B46-51AD-4A21-BA3E-5723AA843EC6@virtualized.org> <20140227021436.E957210702F7@rock.dv.isc.org> <7E284F2F-1A99-4E57-B7BD-46129AEDDD04@virtualized.org> <20140227074249.2972F107D273@rock.dv.isc.org> <B67B8708-66D9-4372-B3E4-58FBC3297E9D@rfc1035.com> <20140227115518.D4628107FA73@rock.dv.isc.org> <D27FE132-502B-46EE-8B55-CB71908BBEB8@rfc1035.com> <alpine.LSU.2.00.1402271219440.13302@hermes-1.csi.cam.ac.uk> <DC2770FB-A9E7-472D-A16D-2BFE5CA153AD@rfc1035.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/NnJ9xfIdudE2ZzlS4Uq2JVqUmx4
Cc: DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 13:17:11 -0000

Jim Reid <jim@rfc1035.com> wrote:

> On 27 Feb 2014, at 12:21, Tony Finch <dot@dotat.at> wrote:
>
> > The problem occurs when common operating systems start shipping validating
> > resolvers, then users will not be able to browse to http://router.home to
> > configure their device.
>
> An what do these users currently do when router.home or whatever doesn't
> resolve regardless of whether DNSSEC is involved?

They follow the troubleshooting guide and eventually get it to work.

With DNSSEC the only resolution would be to turn off validation on the
user's computer which is NOT what we want.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Fisher, German Bight, Humber: South 6 to gale 8, becoming variable 4 later.
Moderate or rough, occasionally very rough at first in Fisher, becoming slight
later in German Bight and Humber. Rain or showers. Moderate or good.


From nobody Thu Feb 27 06:47:08 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1F881A02DD for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 06:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpoPjoleLqvE for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 06:47:04 -0800 (PST)
Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3701A02CF for <dnsop@ietf.org>; Thu, 27 Feb 2014 06:47:04 -0800 (PST)
Received: by mail-qa0-f41.google.com with SMTP id j5so2944919qaq.28 for <dnsop@ietf.org>; Thu, 27 Feb 2014 06:47:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=LraZVA8xrL7bIfBRoGm3KnEisL9+q/XwxW9IF7lrsXA=; b=XH4VbEGE9DCiFSM+xqR21knye6B7Atak14ZiTIdRAcPLrB04OM3A7Yofo0P9055FLu qLY1A9cYKzrna2tm7g/Ez7ytdm68SVrGaAr45eoAcyECSbyg9UgGMpv8DQDRHhLWhidf EAXD3V44TTgXw5nffkLDLMfuKZn5nruZz9eEHIiqQ8U3/AuNKM71qdwVKhh4RSKyN/0Q Ks54AeLnqaCmKJAkyjO+FAPwhoQ0shC/menlEslK4cfQ67ilzeUrEN043eM6hfjgzoZv NdZ9lK1mpok0so62UJpesGru24xFL/nNLvTl03gJvh2uKB7vC2pgo4yjINAQAIbR7h2A glHw==
X-Received: by 10.224.163.139 with SMTP id a11mr17100515qay.1.1393512422920; Thu, 27 Feb 2014 06:47:02 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id b14sm14237397qac.17.2014.02.27.06.47.01 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Feb 2014 06:47:02 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20140227025617.0101A107642C@rock.dv.isc.org>
Date: Thu, 27 Feb 2014 09:47:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A016D7ED-BB45-490E-B188-0326B2B89A5E@gmail.com>
References: <20140226233907.6214.qmail@joyce.lan> <20140227025617.0101A107642C@rock.dv.isc.org>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/QUY-V5c777TS32jDq4KQfmuS7ps
Subject: [DNSOP] admin note Re: additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 14:47:07 -0000

(chair bit enabled)

On Feb 26, 2014, at 9:56 PM, Mark Andrews <marka@isc.org> wrote:

> In message <20140226233907.6214.qmail@joyce.lan>, "John Levine" =
writes:
>>=20
>>> Perhaps all that is missing is some guidance that says "you =
shouldn't hijack
>>> namespaces that you don't control, even for non-DNS applications; =
register a
>>> domain instead".
>>=20
>> That's a relatively high bar for all the residential broadband users
>> who buy a router at Best Buy (Future Shop to you), plug it in, and =
set
>> up the router via the configuration page at http://router.home.
>=20
> And why wasn't that "http://router.netgear.com" or
> "http://router.linksys.com". The router could easily serve the zone
> locally and the vendor could have a insecure delegation to it so
> it works if there are validating browsers being used.
>=20
> http://router.home does not work with validating browsers.
>=20
> If the CPE vendors want to use .home let them pony up the 100K for
> it rather than hijack the namespace.

There are operational reasons to care whether a name is in the special =
names registry, the production root zone, both, or neither-- regardless =
of who has authority over either or on what terms. We should probably =
focus on those. The DNSSEC issue is one useful set to explore, and =
further focus on it would be helpful. Another set of suggestions for our =
work is beginning to appear around refinements of standards treatment =
for DNS search path processing, on the grounds that much of the =
unpredictability of mixing namespaces and DNS scopes is based on =
unpredictable precedence of search path processes.

We've attempted to suggest now more than once that the special names =
discussions will be more useful if:

*We leave speculation on the economics and other non-technical =
attributes of other entities' decisions about the namespace out of it. =
Speculation on other mechanisms besides the one we in the IETF have =
(roughly, RFC 6761) for getting names into the top level namespace isn't =
productive, as we don't control them. We don't know when or whether =
ICANN will ever conduct another new TLD opening, or what will be =
eligible to be included, or at what price. The root zone change we have =
to consider is only that the old assumptions about its size stopped =
applying, not what the new ones might be beyond the specific commitments =
made by ICANN in its current root zone expansion. This is not an =
endorsement of anyone's actions in this space, or a condemnation either; =
it's an attempt to describe the situation we're actually in.=20

* We separate issues of "what should be done, if anything, in the future =
to enable/support/protect non-DNS-protocol-specific, possibly non-global =
uses of the DNS namespace" from "what should be done, if anything, to =
improve/normalize the situation we're currently in". We have several =
drafts for discussion in London on options for the future, and a =
possible course of action for them that we work on them as refinements =
or replacements to RFC 6761. We also have two drafts requesting more or =
less that we grandfather pseudo-TLDs deployed in the absence of clear =
guidelines and consistent system behavior, in order to mitigate current =
issues caused by "hijacking" names under traditional expectations about =
how the root zone is managed.=20

Regarding the guidance Joe proposed, our question is whether it's good =
guidance for the future, not so much whether it would have been in the =
past. We may also decide there's nothing we can do in the way of such =
guidance, the relevant horses have left the relevant barns, and the =
combination of DNS on-the-wire protocol, system behavior for scoping of =
names, and the policy characteristics of the namespace mean ambiguity, =
collision, or other sub-optimal characteristics of trying to use DNS =
namespace for non-DNS protocols or non-global scopes are a fact of life =
we can't usefully act to prevent in the future. That doesn't tell the =
IESG what to do with the current requests for grandfathering.

Ultimately, these issues do have to be integrated. But at this point we =
will get nowhere in, for example, trying to decide whether to =
grandfather existing names into the special names registry managed under =
the process in RFC 6761 based on an opinion about what a vendor might or =
should do in the future under an ICANN process we don't control.

thanks,
Suzanne





From nobody Thu Feb 27 08:57:20 2014
Return-Path: <Alexandre.Dulaunoy@circl.lu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1618B1A0342 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 08:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.047
X-Spam-Level: 
X-Spam-Status: No, score=-1.047 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OvZUp6BY7JmV for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 08:57:15 -0800 (PST)
Received: from cpb.circl.lu (cpb.circl.lu [IPv6:2001:978:4200:a::5]) by ietfa.amsl.com (Postfix) with ESMTP id 207F51A02A1 for <dnsop@ietf.org>; Thu, 27 Feb 2014 08:57:15 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by cpb.circl.lu (Postfix) with ESMTPS id BFB5AE80608; Thu, 27 Feb 2014 17:57:12 +0100 (CET)
Message-ID: <530F6E68.7080504@circl.lu>
Date: Thu, 27 Feb 2014 17:57:12 +0100
From: Alexandre Dulaunoy <Alexandre.Dulaunoy@circl.lu>
Organization: CIRCL - Computer Incident Response Center Luxembourg
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.28) Gecko/20120313 Lightning/1.0b2 Something
MIME-Version: 1.0
To: "L. Aaron Kaplan" <kaplan@cert.at>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org> <alpine.LSU.2.00.1401161404280.13642@hermes-2.csi.cam.ac.uk> <80FDE505-1ADC-4451-8A74-51CFFE681A1C@cert.at>
In-Reply-To: <80FDE505-1ADC-4451-8A74-51CFFE681A1C@cert.at>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tX8VT7WSZy4JJK9-D7Mar_eZCkc
Cc: Tony Finch <dot@dotat.at>, dnsop@ietf.org
Subject: Re: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 16:57:18 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/27/2014 05:43 PM, L. Aaron Kaplan wrote:

Thanks for feedback and updates.

> So, the changes are currently in our github repository. Waiting for Alexandre to submit them again.

The -02 is now available at

https://github.com/adulau/pdns-qof/blob/master/to-submit/draft-dulaunoy-kaplan-passive-dns-cof-02.txt

It will be pushed to I-D submission when it's back ;-)

""
The cut-off time for the I-D submission was 00h UTC, 2014-02-15.
The I-D submission tool will be reopened at 00h local time at the IETF
meeting location, 2014-03-03.
""

Cheers.

- -- 
Alexandre Dulaunoy
CIRCL - Computer Incident Response Center Luxembourg
41, avenue de la gare L-1611 Luxembourg
info@circl.lu - www.circl.lu
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlMPbmUACgkQCeLNSUTmy80v3ACdEIa4w45ojtz9th/+KpdI+74m
dZ8An2IsqxjDscRGh4KFD4XugCdjeG+0
=aIhd
-----END PGP SIGNATURE-----


From nobody Thu Feb 27 08:57:58 2014
Return-Path: <kaplan@cert.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592071A0234 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 08:44:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.679
X-Spam-Level: 
X-Spam-Status: No, score=-0.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, J_CHICKENPOX_32=0.6, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQsGvzTMjPD7 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 08:44:05 -0800 (PST)
Received: from nuwen.cert.at (nuwen.cert.at [IPv6:2a02:850:5:64::2]) by ietfa.amsl.com (Postfix) with ESMTP id E3F171A0033 for <dnsop@ietf.org>; Thu, 27 Feb 2014 08:44:04 -0800 (PST)
Received: from cleophus.intern.cert.at (cleophus.intern.cert.at [172.21.47.118]) by nuwen.cert.at (Postfix) with ESMTP id F0B5224124; Thu, 27 Feb 2014 17:43:56 +0100 (CET)
Received: from [172.21.48.118] (unknown [172.21.48.118]) by cleophus.intern.cert.at (Postfix) with ESMTPS id C80D23415CA; Thu, 27 Feb 2014 17:43:59 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_F14839A0-F975-4CA0-86F9-C025BAE7233A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: "L. Aaron Kaplan" <kaplan@cert.at>
In-Reply-To: <alpine.LSU.2.00.1401161404280.13642@hermes-2.csi.cam.ac.uk>
Date: Thu, 27 Feb 2014 17:43:51 +0100
Message-Id: <80FDE505-1ADC-4451-8A74-51CFFE681A1C@cert.at>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org> <alpine.LSU.2.00.1401161404280.13642@hermes-2.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1510)
X-CERTat-MailScanner-ID: F0B5224124.A946E
X-CERTat-MailScanner: Found to be clean
X-CERTat-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.9, required 5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90)
X-CERTat-MailScanner-From: kaplan@cert.at
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/-uc-G5Zjny68PFIzrU1p9V_fFRA
X-Mailman-Approved-At: Thu, 27 Feb 2014 08:57:57 -0800
Cc: Dulaunoy Alexandre <Alexandre.Dulaunoy@circl.lu>, dnsop@ietf.org
Subject: Re: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 16:44:07 -0000

--Apple-Mail=_F14839A0-F975-4CA0-86F9-C025BAE7233A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Tony,

Thanks a lot for your very valuable feedback.

On Jan 16, 2014, at 3:27 PM, Tony Finch <dot@dotat.at> wrote:

> Paul Vixie <paul@redbarn.org> wrote:
>=20
>> speaking for the authors of the draft below, i request adoption by
>> dnsop. --vixie
>>=20
>> =
https://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/
>=20
> A few questions / comments:
>=20
> The ws non-terminal isn't defined. I guess it is supposed to be
>=20
> 	ws =3D *( %x10 / %x09 )
>=20
I agree. You probably meant=20

   ws              =3D *(
                       %x20 |              ; Space
                       %x09                ; Horizontal tab
                      )

?

> i.e. no newlines within a JSON object, which is different from the
> definition of ws in RFC 4627. (Maybe use core ABNF WSP instead?)
>=20
Fixed , thanks for pointing this out.

> The ABNF specifies that the field names are not quoted (the quotes are
> part of the ABNF metasyntax not part of the language it specifies) =
which
> is incompatible with JSON and disagrees with the examples in the =
appendix.
>=20
Fixed

> The appendix could do with some rubric to explain the backslashes.
>=20
Fixed

> Are numeric rrtypes represented as JSON numbers? Or a "TYPEnnn" =
string?
>=20
JSON numbers

> I guess time stamps are represented as JSON numbers.
>=20
Yes

> How are sensor_id octet strings encoded as JSON strings?
>=20
Correct.


So, the changes are currently in our github repository. Waiting for =
Alexandre to submit them again.

See you next week.

a.

> Tony.
> --=20
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at =
first.
> Rough, becoming slight or moderate. Showers, rain at first. Moderate =
or good,
> occasionally poor at first.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

---=20
// L. Aaron Kaplan <kaplan@cert.at> - T: +43 1 5056416 78
// CERT Austria - http://www.cert.at/
// Eine Initiative der nic.at GmbH - http://www.nic.at/
// Firmenbuchnummer 172568b, LG Salzburg





--Apple-Mail=_F14839A0-F975-4CA0-86F9-C025BAE7233A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlMPa0sACgkQLXqZes2uTba+2QCgp2nhw8S39Fj1rG6C+4kFFJLK
+O4An1qKX15GUPEYj3MCkyHvekJR2hVg
=AHK0
-----END PGP SIGNATURE-----

--Apple-Mail=_F14839A0-F975-4CA0-86F9-C025BAE7233A--


From nobody Thu Feb 27 09:04:43 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D249D1A0231 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 09:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjXDjhc3Qb_K for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 09:04:40 -0800 (PST)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f51]) by ietfa.amsl.com (Postfix) with ESMTP id D501D1A00B4 for <dnsop@ietf.org>; Thu, 27 Feb 2014 09:04:39 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:35988) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1WJ4Nx-0008Bm-YZ (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 17:04:37 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WJ4Nx-0002K1-KA (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 17:04:37 +0000
Date: Thu, 27 Feb 2014 17:04:37 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: "L. Aaron Kaplan" <kaplan@cert.at>
In-Reply-To: <80FDE505-1ADC-4451-8A74-51CFFE681A1C@cert.at>
Message-ID: <alpine.LSU.2.00.1402271701230.18502@hermes-1.csi.cam.ac.uk>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org> <alpine.LSU.2.00.1401161404280.13642@hermes-2.csi.cam.ac.uk> <80FDE505-1ADC-4451-8A74-51CFFE681A1C@cert.at>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/BmmN2vSGRR1nUWVZ-Ewk9QX4xR8
Cc: Dulaunoy Alexandre <Alexandre.Dulaunoy@circl.lu>, dnsop@ietf.org
Subject: Re: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 17:04:42 -0000

L. Aaron Kaplan <kaplan@cert.at> wrote:

> I agree. You probably meant
>
>    ws              = *(
>                        %x20 |              ; Space
>                        %x09                ; Horizontal tab
>                       )

Er yes, typo :-)

> > How are sensor_id octet strings encoded as JSON strings?
>
> Correct.

I need a bit more clarification than that :-) Section 3.5.1 of the -01
version of your draft says that a sensor_id is an opaque octet string,
which cannot safely be encoded as a JSON string because JSON strings have
to be valid UTF-8.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Plymouth, Biscay, FitzRoy: West, veering northwest, 7 to severe gale 9,
perhaps storm 10 later. Very rough or high, occasionally very high. Rain or
showers. Moderate, occasionally poor.


From nobody Thu Feb 27 09:19:16 2014
Return-Path: <kaplan@cert.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36A741A0415 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 09:15:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.679
X-Spam-Level: 
X-Spam-Status: No, score=-0.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, J_CHICKENPOX_32=0.6, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 539lx5O3EezF for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 09:15:46 -0800 (PST)
Received: from nuwen.cert.at (nuwen.cert.at [IPv6:2a02:850:5:64::2]) by ietfa.amsl.com (Postfix) with ESMTP id 002001A03AB for <dnsop@ietf.org>; Thu, 27 Feb 2014 09:15:45 -0800 (PST)
Received: from cleophus.intern.cert.at (cleophus.intern.cert.at [172.21.47.118]) by nuwen.cert.at (Postfix) with ESMTP id 6CF2324124; Thu, 27 Feb 2014 18:15:34 +0100 (CET)
Received: from [172.21.48.118] (unknown [172.21.48.118]) by cleophus.intern.cert.at (Postfix) with ESMTPS id 3D1D6341764; Thu, 27 Feb 2014 18:15:37 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_C044B48B-B819-4D50-83D6-071FAD8EF4DD"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: "L. Aaron Kaplan" <kaplan@cert.at>
In-Reply-To: <alpine.LSU.2.00.1402271701230.18502@hermes-1.csi.cam.ac.uk>
Date: Thu, 27 Feb 2014 18:15:29 +0100
Message-Id: <22BA26A2-4423-486C-9886-46F6CAFB43A3@cert.at>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org> <alpine.LSU.2.00.1401161404280.13642@hermes-2.csi.cam.ac.uk> <80FDE505-1ADC-4451-8A74-51CFFE681A1C@cert.at> <alpine.LSU.2.00.1402271701230.18502@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1510)
X-CERTat-MailScanner-ID: 6CF2324124.A8CC5
X-CERTat-MailScanner: Found to be clean
X-CERTat-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.9, required 5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90)
X-CERTat-MailScanner-From: kaplan@cert.at
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/JclbACNq8aVLPtTYKcOgh2kLTZo
X-Mailman-Approved-At: Thu, 27 Feb 2014 09:19:15 -0800
Cc: Dulaunoy Alexandre <Alexandre.Dulaunoy@circl.lu>, dnsop@ietf.org
Subject: Re: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 17:15:48 -0000

--Apple-Mail=_C044B48B-B819-4D50-83D6-071FAD8EF4DD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 27, 2014, at 6:04 PM, Tony Finch <dot@dotat.at> wrote:

> L. Aaron Kaplan <kaplan@cert.at> wrote:
>=20
>> I agree. You probably meant
>>=20
>>   ws              =3D *(
>>                       %x20 |              ; Space
>>                       %x09                ; Horizontal tab
>>                      )
>=20
> Er yes, typo :-)
>=20
>>> How are sensor_id octet strings encoded as JSON strings?
>>=20
>> Correct.
>=20
> I need a bit more clarification than that :-)
All right then :)

> Section 3.5.1 of the -01
> version of your draft says that a sensor_id is an opaque octet string,
> which cannot safely be encoded as a JSON string because JSON strings =
have
> to be valid UTF-8.
>=20
Okay, quite a nice catch. I would not have noticed that.

Since I am the only user of the sensor_id field right now, I'd say we =
remove the=20
text:
  "The sensor_id is an opaque byte string as defined by RFC 5001 in
   section 2.3 [RFC5001].  The sensor_id MUST be escaped as defined in
   section 2.6 of RFC4627 [RFC4627]."
and just leave:
  "This field returns the sensor information where the record was seen.=20=

   This field is represented as a JSON [RFC4627] string."


Would that be OK for you?


> Tony.
> --=20
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> Plymouth, Biscay, FitzRoy: West, veering northwest, 7 to severe gale =
9,
> perhaps storm 10 later. Very rough or high, occasionally very high. =
Rain or
> showers. Moderate, occasionally poor.

---=20
// L. Aaron Kaplan <kaplan@cert.at> - T: +43 1 5056416 78
// CERT Austria - http://www.cert.at/
// Eine Initiative der nic.at GmbH - http://www.nic.at/
// Firmenbuchnummer 172568b, LG Salzburg





--Apple-Mail=_C044B48B-B819-4D50-83D6-071FAD8EF4DD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlMPcrUACgkQLXqZes2uTbZ2+QCgs3n00esDqON4QQQH6Qcr+/0d
cFcAn3N8fJ3wRecP7jwM/5T6s0np8K00
=5pHZ
-----END PGP SIGNATURE-----

--Apple-Mail=_C044B48B-B819-4D50-83D6-071FAD8EF4DD--


From nobody Thu Feb 27 09:38:21 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E151A01A6 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 09:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6KVGckJrtIb1 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 09:38:18 -0800 (PST)
Received: from ppsw-40.csi.cam.ac.uk (ppsw-40-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f40]) by ietfa.amsl.com (Postfix) with ESMTP id 57C1C1A015A for <dnsop@ietf.org>; Thu, 27 Feb 2014 09:38:18 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:35157) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1WJ4uV-0004GW-l6 (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 17:38:15 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WJ4uV-0005jC-HA (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 27 Feb 2014 17:38:15 +0000
Date: Thu, 27 Feb 2014 17:38:15 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: "L. Aaron Kaplan" <kaplan@cert.at>
In-Reply-To: <22BA26A2-4423-486C-9886-46F6CAFB43A3@cert.at>
Message-ID: <alpine.LSU.2.00.1402271737240.18502@hermes-1.csi.cam.ac.uk>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org> <alpine.LSU.2.00.1401161404280.13642@hermes-2.csi.cam.ac.uk> <80FDE505-1ADC-4451-8A74-51CFFE681A1C@cert.at> <alpine.LSU.2.00.1402271701230.18502@hermes-1.csi.cam.ac.uk> <22BA26A2-4423-486C-9886-46F6CAFB43A3@cert.at>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/wWRPUUIKBKi2CySRkoGrM5jMfr4
Cc: Dulaunoy Alexandre <Alexandre.Dulaunoy@circl.lu>, dnsop@ietf.org
Subject: Re: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 17:38:20 -0000

L. Aaron Kaplan <kaplan@cert.at> wrote:
>
> Since I am the only user of the sensor_id field right now, I'd say we remove the
> text:
>   "The sensor_id is an opaque byte string as defined by RFC 5001 in
>    section 2.3 [RFC5001].  The sensor_id MUST be escaped as defined in
>    section 2.6 of RFC4627 [RFC4627]."
> and just leave:
>   "This field returns the sensor information where the record was seen.
>    This field is represented as a JSON [RFC4627] string."
>
> Would that be OK for you?

I think that makes sense because I can't see any reason to put non-UTF-8
junk in that field.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Humber: Southwest, backing east, 4. Slight, occasionally moderate. Showers.
Good.


From nobody Thu Feb 27 12:25:22 2014
Return-Path: <sebastian@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A852D1A0665 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 12:25:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.051
X-Spam-Level: 
X-Spam-Status: No, score=0.051 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_42=0.6, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xsr6CvXVP7bK for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 12:25:19 -0800 (PST)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id F23F41A0645 for <dnsop@ietf.org>; Thu, 27 Feb 2014 12:25:17 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id 7827A4B99F9 for <dnsop@ietf.org>; Fri, 28 Feb 2014 09:25:15 +1300 (NZDT)
X-Virus-Scanned: Debian amavisd-new at srsomail.office.nzrs.net.nz
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ri8HbHvRfK2 for <dnsop@ietf.org>; Fri, 28 Feb 2014 09:25:06 +1300 (NZDT)
Received: from [192.168.22.178] (unknown [202.46.183.35]) (Authenticated sender: sebastian) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id A292E4B99F7 for <dnsop@ietf.org>; Fri, 28 Feb 2014 09:25:06 +1300 (NZDT)
Message-ID: <530F9F22.7070300@nzrs.net.nz>
Date: Fri, 28 Feb 2014 09:25:06 +1300
From: Sebastian Castro <sebastian@nzrs.net.nz>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "dnsop@ietf.org" <dnsop@ietf.org>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org>
In-Reply-To: <52D6E0AB.807@redbarn.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/2aANxz8qkJe4X9ZjCQdSgr_n8VU
Subject: Re: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 20:25:21 -0000

On 16/01/14 08:25, Paul Vixie wrote:
> speaking for the authors of the draft below, i request adoption by
> dnsop. --vixie
> 

Hi Paul and the rest of the authors.

> https://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/
> 
> Internet Engineering Task Force                              A. Dulaunoy
> Internet-Draft                                                     CIRCL
> Intended status: Informational                                 A. Kaplan
> Expires: July 11, 2014                                           CERT.at
>                                                                 P. Vixie
>                                                                 H. Stern
>                                                  Farsight Security, Inc.
>                                                          January 7, 2014
> 
>                    Passive DNS - Common Output Format
>                 draft-dulaunoy-kaplan-passive-dns-cof-01
> 
> Abstract
> 
>    This document describes a common output format of Passive DNS Servers
>    which clients can query.  The output format description includes also
>    in addition a common semantic for each Passive DNS system.  By having
>    multiple Passive DNS Systems adhere to the same output format for
>    queries, users of multiple Passive DNS servers will be able to
>    combine result sets easily.
> 

I've read the 02 draft and I have a couple of comments:

- In section 3.3, it reads:
   rdata MAY be an array as defined in JSON [RFC4627].
   Implementors of this draft MUST be able to deal with rdata being
   returned as JSON array or alternatively as a JSON string.

Thinking as a developer, it could be annoying to have to test if rdata
is a string or an array. Given JSON arrays can be empty, wouldn't be
better to express it always as an array?

- In section 3.4.1 count
   Specifies how many authoritative DNS answers were received at the
   Passive DNS Server's collectors with exactly the given set of values
   as answers (i.e. same data in the answer set - compare with the
   uniqueness property in "Mandatory Fields").  The number of requests
   is expressed as a decimal value.

If you collector is sitting in front of a recursor, that uses an
upstream recursor (forwarder), the number of answers you are going to
see it won't be the same of the number of authoritative answers. Given
this, should count be an object like

   { 'total': integer,
     'auth': integer }

or be expressed in different fields?


Finally, is there a reason why TTL are being omitted from the collection
and responses?


Cheers,


> 
> ...
> 
> 
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
> 


-- 
Sebastian Castro
Technical Research Manager
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 495 2337
mobile: +64 21 400535


From nobody Thu Feb 27 20:20:23 2014
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D244E1A06E4 for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 20:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.043
X-Spam-Level: *
X-Spam-Status: No, score=1.043 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zwd0eg5zpO6F for <dnsop@ietfa.amsl.com>; Thu, 27 Feb 2014 20:20:18 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0F2FF1A06C2 for <dnsop@ietf.org>; Thu, 27 Feb 2014 20:20:17 -0800 (PST)
Received: (qmail 13020 invoked from network); 28 Feb 2014 04:20:15 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 28 Feb 2014 04:20:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=53100e81.xn--9vv.k1402; i=johnl@user.iecc.com; bh=5YDdWkbthJWjQn3y3u5lV/t2XINqxYfvRsyfn6omxRs=; b=Fo3kb243ActfKv1U/TNkmCgYqBm+SIn9FqWUDSvM9xp2Do5wzrLTg8JYnFOxe+2WGcMRlUs9PqpEpEmzI535TgvwTGUr3bvtitMBQcvQVteW85m3SE2HLRUTUgqohVPbRyk3ejNTIANdEtt/mXGMGvnIVhcyuZ50hoMdxaT+vGfftu4bEUa1esU/7k0h9wzZl+wKej8/wf6ckJ4g4bLStf9IVFL7M27rXVhwVQGZAOhwpJ6BG2XRBrj5pSEEY8VB
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=53100e81.xn--9vv.k1402; bh=5YDdWkbthJWjQn3y3u5lV/t2XINqxYfvRsyfn6omxRs=; b=exA9oNkUnC3dFe28Kj7syIzDM+sMgLZ8irdw3/F7SInMTzvO9P2MOEqOo7B1+MIowmczaWrcRrHm/wMeXOYLYU8jUXfH/3rRJVPsGBHnjK4/r0qJp2I5JWzPtSfPQ2lzhG24jukKvNGsjHOt+civ2FbezS51TSwD2QfskpdoV0vYjDDWzjAOVjrhosXSYkkL39ghXP9Na8Tk1EURnDUWc/LZdTcGpsk+OrzzEWblVN2SWxs8sm/BCAcq//4oXCXk
Date: 28 Feb 2014 04:19:55 -0000
Message-ID: <20140228041955.24570.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <alpine.LSU.2.00.1402271219440.13302@hermes-1.csi.cam.ac.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/-libECJNZD_Q1VA7r4W9BSPl-4g
Cc: dot@dotat.at
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 04:20:20 -0000

>The problem occurs when common operating systems start shipping validating
>resolvers, then users will not be able to browse to http://router.home to
>configure their device.

Since the device and the browser will not be online when you do the
initial configuration, it seems to me that if you use a validating
resolver you lose no matter what the name is.

R's,
John


From nobody Fri Feb 28 03:31:35 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95F91A01DC for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 03:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ta2LgpmZm6dt for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 03:31:29 -0800 (PST)
Received: from ppsw-40.csi.cam.ac.uk (ppsw-40-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f40]) by ietfa.amsl.com (Postfix) with ESMTP id 7033A1A019D for <dnsop@ietf.org>; Fri, 28 Feb 2014 03:31:29 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:53481) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1WJLf4-0007oA-jU (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 28 Feb 2014 11:31:26 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WJLf4-0007AG-1B (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 28 Feb 2014 11:31:26 +0000
Date: Fri, 28 Feb 2014 11:31:26 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: John Levine <johnl@taugh.com>
In-Reply-To: <20140228041955.24570.qmail@joyce.lan>
Message-ID: <alpine.LSU.2.00.1402281129350.13302@hermes-1.csi.cam.ac.uk>
References: <20140228041955.24570.qmail@joyce.lan>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/3cDSEtsIoK0JpAPh0QSI3A_imCs
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 11:31:31 -0000

John Levine <johnl@taugh.com> wrote:

> Since the device and the browser will not be online when you do the
> initial configuration, it seems to me that if you use a validating
> resolver you lose no matter what the name is.

Hmm yes a very good point :-/

I think this is an argument in favour of registering a special use name
for this purpose which can be configured with a negative trust anchor.

Unless someone has a bright idea for some alternative fix...

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Faeroes, South-east Iceland: Cyclonic 6 to gale 8, occasionally severe gale 9
at first in Faeroes. Very rough, occasionally high. Occasional rain. Moderate
or good.


From nobody Fri Feb 28 06:55:38 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02B461A07B5; Fri, 28 Feb 2014 06:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.081
X-Spam-Level: *
X-Spam-Status: No, score=1.081 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FS_WE_WANT=1.629, RP_MATCHES_RCVD=-0.547] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ImCaNTGse3ep; Fri, 28 Feb 2014 06:55:29 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 12DB31A01E8; Fri, 28 Feb 2014 06:55:29 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 7491523E2D51; Fri, 28 Feb 2014 14:55:26 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyS8AdK2ueB2; Fri, 28 Feb 2014 15:55:23 +0100 (CET)
Received: from kopoli (g225115060.adsl.alicedsl.de [92.225.115.60]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 5F1F123E24C1; Fri, 28 Feb 2014 15:55:23 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <DNSOP@ietf.org>, <dnsext@ietf.org>
Date: Fri, 28 Feb 2014 15:55:21 +0100
Message-ID: <002101cf3495$1ad2d570$50788050$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac80lRjPs+oEPGR+Qe6rhNpf40faRg==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/vD8iptW1WHadzjANXWH8CLoyNik
Subject: [DNSOP] We want to have fruitful discussions - please review
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 14:55:31 -0000

Dear All,

Since we have a timeslot to present
http://tools.ietf.org/html/draft-rafiee-intarea-cga-tsig in DNSOP. I ask you
please review it so that the discussion would be fruitful and we can receive
good comments to improve it and to move ahead.  This draft is not a new one
as many of you already know or heard about it, it was first presented in
IETF 85 and recently in IETF 88 in Int-area. The reason was because it was
more related to DNSEXT and at that time it was going to shut down. It had
several volunteer reviewers and it received some good comments. However, we
would like to receive more comments in case we missed anything that needs to
be addressed or we missed to clarify any section in the draft that needs
more clarifications. Since now the DNS confidentiality is also an important
topic and this proposal could handle it for IPv6 and during data transfer, I
also included a section and explained the required changes to the original
proposal.

Here again I briefly explain the purpose of this document for those who do
not know about it or who do not know the exact purpose of it:

This proposal is for the cases where DNS uses IPv6 and there is a need to
use a security mechanism for DNS authentication or provide the data
confidentiality for the DNS data during transferring data over the network.
It is possible to use this proposal in different DNS scenarios such as DNS
update, updating FQDN and PTR, or DNS resolving. In this case it is enough
that the verifier node only knows the IP address of the DNS server or
resolver. For DNS update, this IP address can be set manually for the first
time in the DNS configuration file and for other times, the CGA-TSIG can
handle the changes with the proposed specifications. For DNS resolver, it
receives this IP address securely via the option in the router advertisement
message. The implementation of this part is also available. one need to use
a suitable solution for secure authentication purposes while at the same
time decrease the human intervention for the configuration.
CGA-TSIG is the combination of the use of SSAS or CGA as an authentication
purpose for DNS protocol and TSIG. SSAS/CGA is the mechanism which provides
the node with the proof of IP address ownership by finding a binding between
the IP address and the nodes' public key. Since this approach prevent IP
spoofing (in network layer), it also ensures the DNS server or the clients
that the one who is talking with is the owner of this IP address without the
need to check the public key to the root to find out that this public key is
really belong to this node with this IP address. 

So, using this approach can eliminate the need for this check. It can be
also integrated with DNSSEC for this purpose and prevent IP spoofing without
the need to check the keys up to the root level and simplify the key
exchange process. This proposal also can be helpful for resolving scenario
that is now a problem. Since for DNSSEC, exchanging the key of the resolver
is the problem because the resolver must answer to anonymous queries, it is
not easy to exchange the keys of this DNSSEC resolver to all the nodes who
wants to ask this resolver. But with using this approach as I explained
earlier, the IP address of the resolver can be obtained in a secure manner
via the RA message and then since there is a binding between the IP address
and the public key, the CGA/SSAS verification helps to verify this resolver.


There is a recent discussion about privacy and data confidentiality.  This
proposal can also handle data confidentiality during the data exchanged
between two nodes (servers or clients). Since the node knows the IP address
of the DNS server, it can ask the DNS  server to send the node, its public
key. Then the node can encrypt a secret key with this public key and then
encrypt the whole message using this secret key and AES or other symmetric
algorithms. The DNS server then decrypt the secret key with its own private
key and decrypt the whole DNS message by using this secret key. This
provides the data confidentiality during DNS updates or also it can be used
during DNS resolving. (if necessary) 

If you don't know anything about CGA, I try to explain it in a very simple
example:

Note that all values are in hexadecimal

CGA parameters= 
e387d788a9e529701ba9baf0bb3694de20051abcab8c7dc000e581e41c6891dd5c06fee6f3ab
149bcf00d18d90534606354b8b8d7511ff90552393f974082732f16b646a97d336190c26d5e1
0347422ebfd6da4036d1e363f9de5c85091448b330ca8b541d246c378de29e9f37b19c072974
2d0a04ac0befe2e5069dd16cea03762b6d621d5d15fbf00131a5ee48f91d5a46396af46d01e6
17010001


Sha1(CGA parameters) = e584448d597e3c927805fc18250598a1d1b71b46
now set bits u and g and sec value so only the first bytes will change

CGA value= 2784448d

Thank you and looking forward to see you all in our talk. Since I cannot
make it and will not be in London, Erik will present in my place but can
answer some questions and I will also follow it in jabber. I hope to see a
fruitful conversations :-)

-----------smile----------
Hosnieh



From nobody Fri Feb 28 07:03:28 2014
Return-Path: <ietf@rozanak.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC201A02BD; Fri, 28 Feb 2014 07:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yq-_6W6i67Yz; Fri, 28 Feb 2014 07:03:25 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id B9E0C1A01E8; Fri, 28 Feb 2014 07:03:25 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 7EE8623E2D51; Fri, 28 Feb 2014 15:03:23 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MSnSx-mj_aw2; Fri, 28 Feb 2014 16:03:22 +0100 (CET)
Received: from kopoli (g225115060.adsl.alicedsl.de [92.225.115.60]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id EE16E23E24C1; Fri, 28 Feb 2014 16:03:21 +0100 (CET)
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <DNSOP@ietf.org>, <dnsext@ietf.org>
Date: Fri, 28 Feb 2014 16:03:20 +0100
Message-ID: <002e01cf3496$3815b840$a84128c0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac80ljcq+IFdQYqNRCGC533InN3wjw==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/JgnReIGnna9bVP-quC36vTO39sE
Subject: [DNSOP] followup - We want to have fruitful discussions - please review
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 15:03:27 -0000

Followup: 

I forgot to mention that what are CGA parameters (that is really important)

The most important parameter is public key. So CGA uses the hash of public
key and after some conditions and settings, set the CGA value as a 64
rightmost bits of an IPv6 address

IIPv6= Subnetprefix + cga value

So, this makes a binding between the IP address and the public key. 

> If you don't know anything about CGA, I try to explain it in a very simple
> example:
> 
> Note that all values are in hexadecimal
> 
> CGA parameters=
> e387d788a9e529701ba9baf0bb3694de20051abcab8c7dc000e581e41c689
> 1dd5c06fee6f3ab
> 149bcf00d18d90534606354b8b8d7511ff90552393f974082732f16b646a97
> d336190c26d5e1
> 0347422ebfd6da4036d1e363f9de5c85091448b330ca8b541d246c378de29
> e9f37b19c072974
> 2d0a04ac0befe2e5069dd16cea03762b6d621d5d15fbf00131a5ee48f91d5a
> 46396af46d01e6
> 17010001
> 
> 
> Sha1(CGA parameters) = e584448d597e3c927805fc18250598a1d1b71b46
> now set bits u and g and sec value so only the first bytes will change
> 
> CGA value= 2784448d
> 
> Thank you and looking forward to see you all in our talk. Since I cannot
> make it and will not be in London, Erik will present in my place but can
> answer some questions and I will also follow it in jabber. I hope to see a
> fruitful conversations :-)
> 





From nobody Fri Feb 28 07:06:27 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132841A0830 for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 07:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCgaKmB75WHy for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 07:06:24 -0800 (PST)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id D9CF61A0837 for <dnsop@ietf.org>; Fri, 28 Feb 2014 07:06:23 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id as1so3009688iec.17 for <dnsop@ietf.org>; Fri, 28 Feb 2014 07:06:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/5sOHQF1JFuSBOQsVSRzvnZp0AQ+4CdDpRq9LWERc78=; b=G/T9Sf0iq7WTERj5CPF6N4cvyIVs4LjR0MQSYiFg+PCFx1kfzn4fYEBpeiifTLKQ3J m29rd1um0i77QeN7risS6kuKHEklfYhROuUAXBH7gw8je3ogLoWpkp6LKo/gNEX2vqUK 5dWMi7F9Z6qeXNJNuDTYQXVQMelVYjf2phiz8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=/5sOHQF1JFuSBOQsVSRzvnZp0AQ+4CdDpRq9LWERc78=; b=Kq3TgAN5KfPULgLa2GnRHhYWORWxTowoGJvG902PCxksG9SjGnQkZ4q4xTn+wlFUlt H4uclpG73MJTsfOcInU+1WuQpluIg4E4Uk1Y3vlcErowtm2/9z0l8y0UOO5CjfworYOg 6D4JUv8qG3DGXnB8JmR72ZH6Ozu0lMeYCyETs4lgbBYauG0mEzBKOhbTEngwVb/p6Hw4 kFuIG69c1A16JbVNV5RCdkbVSXeiOPZ29a18E8ULL2ThVpfKWw1MNiEDghRcM+WzWoYH DkonreubKLhGtL7Uc334LYORLaFGCFCbpAeeo9gBGyxc2fsqhjH8B1M3iMduGkyRkBFK wsGA==
X-Gm-Message-State: ALoCoQnQXgOELXzAHxsiLld8QORR52aAd/MnVJHnVv2RFTOPr3YOnH3DvJwNWDTqlIlvSwWbHMN6
X-Received: by 10.50.176.162 with SMTP id cj2mr4559131igc.7.1393599981899; Fri, 28 Feb 2014 07:06:21 -0800 (PST)
Received: from dh24.r1.hopcount.ca (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id om7sm7796441igb.10.2014.02.28.07.06.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 28 Feb 2014 07:06:21 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.LSU.2.00.1402281129350.13302@hermes-1.csi.cam.ac.uk>
Date: Fri, 28 Feb 2014 10:06:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <71ABA9C6-6B92-40D9-BAED-909EE78D54AC@hopcount.ca>
References: <20140228041955.24570.qmail@joyce.lan> <alpine.LSU.2.00.1402281129350.13302@hermes-1.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/6zeVsfclVSu_cfzsEM2U9CTmONs
Cc: dnsop@ietf.org, John Levine <johnl@taugh.com>
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 15:06:26 -0000

On 28 Feb 2014, at 6:31, Tony Finch <dot@dotat.at> wrote:

> John Levine <johnl@taugh.com> wrote:
>=20
>> Since the device and the browser will not be online when you do the
>> initial configuration, it seems to me that if you use a validating
>> resolver you lose no matter what the name is.
>=20
> Hmm yes a very good point :-/
>=20
> I think this is an argument in favour of registering a special use =
name
> for this purpose which can be configured with a negative trust anchor.
>=20
> Unless someone has a bright idea for some alternative fix=85

Bonjour. It works for every other device in the home that needs a direct =
connection to manage. Nobody assumes that =93http://printer.home=94 is =
going to do anything useful; why is the gateway device different?

(I=92ve never owned a consumer-grade home gateway; whenever I=92ve =
helped out a neighbour with theirs I=92ve always just connected to =
whatever address the gateway=92s DHCP server gave me as a default route. =
I had no idea there was any expectation that =93router.home=94 would do =
anything sensible. It does go some way to explain what I saw at L-Root =
when I last had the opportunity to look, though :-)


Joe


From nobody Fri Feb 28 07:43:05 2014
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 283321A0308 for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 07:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.136
X-Spam-Level: 
X-Spam-Status: No, score=-1.136 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, NORMAL_HTTP_TO_IP=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fRTUgjN07OBE for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 07:43:01 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 78C601A00E2 for <dnsop@ietf.org>; Fri, 28 Feb 2014 07:43:01 -0800 (PST)
Received: (qmail 28678 invoked from network); 28 Feb 2014 15:42:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=7004.5310ae83.k1402; i=johnl-iecc.com@submit.iecc.com; bh=Y2bTYFhVOUCtauSjMpwQ3YaYQpEueCi7aekG0QYgskM=; b=yFerF0czEq09+Tfd+6ZJuEyEeP9LVavP111kySZsBnY7szQekiQHxNS2lDx7HxYC3FZCrecprQ/jh/e0/Pv+DwM7pjHEEU4Pg6QTE/wMk66afWEVeuJ4jfdP6OyYDQtD5Zh1U4VY8xCQf5iG+ihFt0Ua3pe/hfI+RDI56Sh9Hqs7IA7CfcSpRRjR5Jtt6jJrSFSwShICZS5mrSO57nfv5ixuUgpHRo3BU/heMQNeB/hLvV7kzrHwhYhxYKnjzknZ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=7004.5310ae83.k1402; olt=johnl-iecc.com@submit.iecc.com; bh=Y2bTYFhVOUCtauSjMpwQ3YaYQpEueCi7aekG0QYgskM=; b=Wrr9CHI5xdPWKJWyAIq1UOzOnLjRw0942QRp/mqsS+1g4WocUfQ+AfweXqabptKFddxIVAn7Jb84vdBLvugUuzY4B4IUM0LrkW5PiMVJmthU/7PxyQOm0b4Af/kwsylyZslY8sHIdqFYGdYoBffWbrHbJzKOo8JntvNmz3XWB6EHovmJtWD1gdGZucUULQ9TzjkV60T0WARj2LL79MuQo/PSEENpX2+EG5ANrJEy/p5RkP5Hl8z882oOXyX/AnHC
Received: from joyce.lan ([24.59.92.2]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 28 Feb 2014 15:42:58 -0000
Date: 28 Feb 2014 10:43:00 -0500
Message-ID: <alpine.BSF.2.00.1402281035520.31785@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Joe Abley" <jabley@hopcount.ca>
In-Reply-To: <71ABA9C6-6B92-40D9-BAED-909EE78D54AC@hopcount.ca>
References: <20140228041955.24570.qmail@joyce.lan> <alpine.LSU.2.00.1402281129350.13302@hermes-1.csi.cam.ac.uk> <71ABA9C6-6B92-40D9-BAED-909EE78D54AC@hopcount.ca>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-573474667-1393602180=:31785"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/LumT7hvIz1yt4nxg1fbzB1PBgsQ
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 15:43:03 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-573474667-1393602180=:31785
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

> (Iâ€™ve never owned a consumer-grade home gateway; whenever Iâ€™ve helped 
> out a neighbour with theirs Iâ€™ve always just connected to whatever 
> address the gatewayâ€™s DHCP server gave me as a default route. I had no 
> idea there was any expectation that â€œrouter.homeâ€� would do anything 
> sensible. It does go some way to explain what I saw at L-Root when I 
> last had the opportunity to look, though :-)

That's OK when the router self-configures, but some do PPPoE and need for 
you to type user ID info.  Most often they currently tell you to go to 
http://192.168.80.1/ but that's going to be a lot less pleasant when 
people start using IPv6 addresses.

I suppose Bonjour is a reasonable way for the router and the PC to fine 
each other, haven't looked at the details.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
--3825401791-573474667-1393602180=:31785--


From nobody Fri Feb 28 08:46:20 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA1CB1A0059 for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 08:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ar_Sd_WHyzFK for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 08:46:17 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 940BC1A0037 for <dnsop@ietf.org>; Fri, 28 Feb 2014 08:46:17 -0800 (PST)
Received: from mx1.yitter.info (unknown [207.236.136.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 899E88A031 for <dnsop@ietf.org>; Fri, 28 Feb 2014 16:46:14 +0000 (UTC)
Date: Fri, 28 Feb 2014 11:46:12 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140228164612.GI2309@mx1.yitter.info>
References: <20140228041955.24570.qmail@joyce.lan> <alpine.LSU.2.00.1402281129350.13302@hermes-1.csi.cam.ac.uk> <71ABA9C6-6B92-40D9-BAED-909EE78D54AC@hopcount.ca> <alpine.BSF.2.00.1402281035520.31785@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1402281035520.31785@joyce.lan>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/UtJwgsfkoybSlUjMVoRwOe4oiK0
Subject: Re: [DNSOP] DNSSEC, additional special names & draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 16:46:19 -0000

On Fri, Feb 28, 2014 at 10:43:00AM -0500, John R Levine wrote:
> I suppose Bonjour is a reasonable way for the router and the PC to
> fine each other, haven't looked at the details.

This entire discussion sure looks like something that ought to inform
homenet and dnssd, no?

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Fri Feb 28 13:45:21 2014
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66EAE1A034B for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 13:45:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OjUeobxeZurk for <dnsop@ietfa.amsl.com>; Fri, 28 Feb 2014 13:45:18 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC8D1A022D for <dnsop@ietf.org>; Fri, 28 Feb 2014 13:45:18 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id DBD3D80DAB; Fri, 28 Feb 2014 16:45:13 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1393623913; bh=Fm2dwm+bO8Zrh2n1mfNnkXNNXhS8G92h9ZKRzrhywK0=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=cHpag7Eh2ZYWoHfeJa8+cM6JCjJO5lCJgZcZSDULS4PIS6KfHG3kpTOfXyNQ6X9F0 h1F6rZkLNGVQzAtW5Q3rloboXu05hfGokuP0UA6rWGOZmkQ8+OChcXa+wZ8yR3Womr /BOO2XDu65EWA/7nD3IegwSrg9RLpllj3wz7I4LY=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s1SLjD4m026865; Fri, 28 Feb 2014 16:45:13 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Fri, 28 Feb 2014 16:45:13 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Tim Wicinski <tjw.ietf@gmail.com>, Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <530781B9.7070004@gmail.com>
Message-ID: <alpine.LFD.2.10.1402281625490.23628@bofh.nohats.ca>
References: <530781B9.7070004@gmail.com>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/hUWiO4VvrYz3c9A-CXo7CnQtEck
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Preliminary agenda for IETF89, London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 21:45:20 -0000

On Fri, 21 Feb 2014, Tim Wicinski wrote:

>
>         4.2) EDNS Option updates, Wouters (5min)
>                 draft-wouters-edns-tcp-keepalive
>                 draft-wouters-edns-tcp-chain-query

I just noticed teh agenda links to the old tcp-only chain-query draft.
The actual latest version of the document is:


http://datatracker.ietf.org/doc/draft-wouters-edns-chain-query/

Paul

