
From wjhns1@hardakers.net  Wed Jun  5 14:58:51 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3249B21F963F for <dnsop@ietfa.amsl.com>; Wed,  5 Jun 2013 14:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkCoY7xJ2drH for <dnsop@ietfa.amsl.com>; Wed,  5 Jun 2013 14:58:47 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id 9476621F9642 for <dnsop@ietf.org>; Wed,  5 Jun 2013 14:58:43 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:211f:1683:e2b8:8b09]) by mail.hardakers.net (Postfix) with ESMTPSA id 1627524CB4 for <dnsop@ietf.org>; Wed,  5 Jun 2013 14:58:42 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: dnsop@ietf.org
Date: Wed, 05 Jun 2013 14:58:42 -0700
Message-ID: <0lk3m8w771.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Subject: [DNSOP] draft-hardaker-dnsop-csync-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 21:58:51 -0000

I've been thinking about this possibility for a while, but discussions
in Orlando really got me thinking so I've finally written up my thoughts
and a possible direction.  Feedback appreciated.



A new version of I-D, draft-hardaker-dnsop-csync-00.txt
has been successfully submitted by Wes Hardaker and posted to the
IETF repository.

Filename:	 draft-hardaker-dnsop-csync
Revision:	 00
Title:		 Child To Parent Synchronization in DNS
Creation date:	 2013-06-05
Group:		 Individual Submission
Number of pages: 13
URL:             http://www.ietf.org/internet-drafts/draft-hardaker-dnsop-csync-00.txt
Status:          http://datatracker.ietf.org/doc/draft-hardaker-dnsop-csync
Htmlized:        http://tools.ietf.org/html/draft-hardaker-dnsop-csync-00

Abstract:
   This document specifies how a child zone in the DNS can publish a
   record that can indicate that a parental agent may copy and process
   certain records from the child zone.  The existence and change of the
   record may be monitored by a parental agent to either assist in
   transferring or automatically transfer data from the child to the
   parent.

The IETF Secretariat

-- 
Wes Hardaker
Parsons

From fujiwara@jprs.co.jp  Thu Jun  6 23:37:43 2013
Return-Path: <fujiwara@jprs.co.jp>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28E8321F9051 for <dnsop@ietfa.amsl.com>; Thu,  6 Jun 2013 23:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tt5tNFv9OfJ for <dnsop@ietfa.amsl.com>; Thu,  6 Jun 2013 23:37:42 -0700 (PDT)
Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) by ietfa.amsl.com (Postfix) with ESMTP id 3699621F8D16 for <dnsop@ietf.org>; Thu,  6 Jun 2013 23:37:42 -0700 (PDT)
Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id r576beou009846 for <dnsop@ietf.org>; Fri, 7 Jun 2013 15:37:40 +0900
X-AuditID: ac120820-b7f306d00000490a-75-51b17fb48e75
Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 6E.0F.18698.4BF71B15; Fri,  7 Jun 2013 15:37:40 +0900 (JST)
Date: Fri, 07 Jun 2013 15:37:40 +0900 (JST)
Message-Id: <20130607.153740.02261936.fujiwara@jprs.co.jp>
To: dnsop@ietf.org
From: fujiwara@jprs.co.jp
X-Mailer: Mew version 6.3.50 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKIsWRmVeSWpSXmKPExsWyRoiFT3dL/cZAgx87zCzuvrnM4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujIeLuQq28FRM+veRqYFxJlcXIyeHhICJxInjfxghbDGJC/fW s3UxcnEICZxklPj7ehc7SIJFQFti3967zCA2r4CVxNW29ywgtoiAkMTXm0dYQWxhATOJzi09 YDVsApISmz+3MkMMtZM48XwFUA0HUK+gxN8dwiBhZgEtiZ4Zj9khbHmJ7W/nME9g5JmFUDUL SdUsJFULGJlXMcrkp6XpFqfmpRTnphsY6pVU5utlFRQV6yWD6E2M4FDhUNjBOOOUwSFGAQ5G JR5e5tUbAoVYE8uKK3MPMUpyMCmJ8n6q2xgoxJeUn1KZkVicEV9UmpNafIhRgoNZSYR3fRpQ jjclsbIqtSgfJiXNwaIkznv87A4/IYH0xJLU7NTUgtQimKwMB4eSBO8EkKGCRanpqRVpmTkl CGkmDk6Q4TxAwytAaniLCxJzizPTIfKnGCWlxHkXgSQEQBIZpXlwva8YxYFeEOZ9DpLlAcY9 XNcroIFMQAOnv9oAMrAkESEl1cBYNl13i1nHlZPK6xQnRMnaS/oUrzfL+P3ZYkngwj16qybc Se/PnTcr0MPzSXz0h4nCGTd3X8++s9W1LM1xnvjPc4vb9BkC1Iwkv8flVnEmnOZP3B5oeD9G XndDTcSNuE+LFgZxZJr5CU/9bqkjsEgiWnFrj+tdq8lNtTHd1Qv8NwUVfXj4tkGJpTgj0VCL uag4EQAStoGMuAIAAA==
Subject: [DNSOP] draft-fujiwara-dnsop-ds-query-increase-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 06:37:43 -0000

JPRS observed that DS queries for JP registered domain names have been
increasing and 3.5% of queries are qtype DS now.

I make a presentation about it at DNS-OARC 2013 Spring workshop and I
wrote a draft as a DNSSEC side effect.

Presentation material is here:
  https://indico.dns-oarc.net/indico/getFile.py/access?contribId=14&resId=0&materialId=slides&confId=0

Do you observe an increase of DS queries ?

Comments appreciated.

A new version of I-D, draft-fujiwara-dnsop-ds-query-increase-00.txt
has been successfully submitted by Kazunori Fujiwara and posted to the
IETF repository.

Filename:	 draft-fujiwara-dnsop-ds-query-increase
Revision:	 00
Title:		 Side effect of DNSSEC: an increase of DS queries
Creation date:	 2013-06-07
Group:		 Individual Submission
Number of pages: 5
URL:             http://www.ietf.org/internet-drafts/draft-fujiwara-dnsop-ds-query-increase-00.txt
Status:          http://datatracker.ietf.org/doc/draft-fujiwara-dnsop-ds-query-increase
Htmlized:        http://tools.ietf.org/html/draft-fujiwara-dnsop-ds-query-increase-00


Abstract:
   A significant increase of periodic DS queries is observed at top
   level domain (TLD) DNS servers.  Currently, almost all of periodic DS
   queries come from DNSSEC validators and are queries for unsigned
   delegations.  The reason of the increase is low NCACHE TTL value and
   DS nonexistence.  This phenomena is DNSSEC protocol and DNS parameter
   issue.  DS queries will increase as DNSSEC validators will increase.

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>

From jewforice@gmail.com  Fri Jun  7 00:02:40 2013
Return-Path: <jewforice@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F0C21F8BB7 for <dnsop@ietfa.amsl.com>; Fri,  7 Jun 2013 00:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OY20o8cX1pc4 for <dnsop@ietfa.amsl.com>; Fri,  7 Jun 2013 00:02:37 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 7A63A21F8B64 for <dnsop@ietf.org>; Fri,  7 Jun 2013 00:02:36 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id fe20so3373558lab.20 for <dnsop@ietf.org>; Fri, 07 Jun 2013 00:02:34 -0700 (PDT)
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=0l/P2TZpJd07+XYzh8ctJyxozlv7kegWLfwni73eMkc=; b=iHILMZkpy5pEY1hYVj5z0lOb/0JNYGZ8RdUE6Is8NT7+6bq4/HjvbfIClrOqAmuclJ gRuFYMBAPTBm6MggHqKS4DN0GvABupEMK6j1m/3LAYJnUTaYIzRt99IOeEkv7A24GAw9 LVK5XNlXP9C33GK9bHYbqxXb10rhkfmsVklmECCB7kw0C3gfhUj8uQN9c3T/VYzLu0/r ND18pemepgdhkHt/Qt6O+jpTrslJ/Q/9e8GAjReHtqORts+j+CQDTZrSRxPDVvtUKOyj ZD9iDeh1nPlEV2nJHtPnWsPeyUbVmrDF6iU2QIgRpR1My4Zi5OYvjcshAzqDobU05Rf2 eCGw==
MIME-Version: 1.0
X-Received: by 10.112.12.227 with SMTP id b3mr599396lbc.15.1370588554724; Fri, 07 Jun 2013 00:02:34 -0700 (PDT)
Received: by 10.114.92.241 with HTTP; Fri, 7 Jun 2013 00:02:34 -0700 (PDT)
In-Reply-To: <20130607.153740.02261936.fujiwara@jprs.co.jp>
References: <20130607.153740.02261936.fujiwara@jprs.co.jp>
Date: Fri, 7 Jun 2013 15:02:34 +0800
Message-ID: <CAB3ZD+nDZ9+0rfWMdeg0vx2EWWdQpMNOJhyJK4zXaLBGJeHtWA@mail.gmail.com>
From: ice jew <jewforice@gmail.com>
To: fujiwara@jprs.co.jp
Content-Type: multipart/alternative; boundary=001a11c3b9a2f009fd04de8b03dd
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] draft-fujiwara-dnsop-ds-query-increase-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 07:02:40 -0000

--001a11c3b9a2f009fd04de8b03dd
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

There is one confusing point in page 12 "=96 whose RR TTL is smaller than
NCACHE TTL"
Does this really matter? Because the  increased requests are to check the
DS RR's non-existence when NCAHCE for this DS RR exipres, so how is it
related to the RR's TTL?



On Fri, Jun 7, 2013 at 2:37 PM, <fujiwara@jprs.co.jp> wrote:

> JPRS observed that DS queries for JP registered domain names have been
> increasing and 3.5% of queries are qtype DS now.
>
> I make a presentation about it at DNS-OARC 2013 Spring workshop and I
> wrote a draft as a DNSSEC side effect.
>
> Presentation material is here:
>
> https://indico.dns-oarc.net/indico/getFile.py/access?contribId=3D14&resId=
=3D0&materialId=3Dslides&confId=3D0
>
> Do you observe an increase of DS queries ?
>
> Comments appreciated.
>
> A new version of I-D, draft-fujiwara-dnsop-ds-query-increase-00.txt
> has been successfully submitted by Kazunori Fujiwara and posted to the
> IETF repository.
>
> Filename:        draft-fujiwara-dnsop-ds-query-increase
> Revision:        00
> Title:           Side effect of DNSSEC: an increase of DS queries
> Creation date:   2013-06-07
> Group:           Individual Submission
> Number of pages: 5
> URL:
> http://www.ietf.org/internet-drafts/draft-fujiwara-dnsop-ds-query-increas=
e-00.txt
> Status:
> http://datatracker.ietf.org/doc/draft-fujiwara-dnsop-ds-query-increase
> Htmlized:
> http://tools.ietf.org/html/draft-fujiwara-dnsop-ds-query-increase-00
>
>
> Abstract:
>    A significant increase of periodic DS queries is observed at top
>    level domain (TLD) DNS servers.  Currently, almost all of periodic DS
>    queries come from DNSSEC validators and are queries for unsigned
>    delegations.  The reason of the increase is low NCACHE TTL value and
>    DS nonexistence.  This phenomena is DNSSEC protocol and DNS parameter
>    issue.  DS queries will increase as DNSSEC validators will increase.
>
> --
> Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--001a11c3b9a2f009fd04de8b03dd
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">There is one confusing point in page 12 &quot;=96 whose RR=
 TTL is smaller than NCACHE TTL&quot;<div>Does this really matter? Because =
the =A0increased requests are to check the DS RR&#39;s non-existence when N=
CAHCE for this DS RR exipres, so how is it related to the RR&#39;s TTL?<br>
<div><br></div></div></div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Fri, Jun 7, 2013 at 2:37 PM,  <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:fujiwara@jprs.co.jp" target=3D"_blank">fujiwara@jprs.co.jp</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">JPRS observed that DS queries for JP registe=
red domain names have been<br>
increasing and 3.5% of queries are qtype DS now.<br>
<br>
I make a presentation about it at DNS-OARC 2013 Spring workshop and I<br>
wrote a draft as a DNSSEC side effect.<br>
<br>
Presentation material is here:<br>
=A0 <a href=3D"https://indico.dns-oarc.net/indico/getFile.py/access?contrib=
Id=3D14&amp;resId=3D0&amp;materialId=3Dslides&amp;confId=3D0" target=3D"_bl=
ank">https://indico.dns-oarc.net/indico/getFile.py/access?contribId=3D14&am=
p;resId=3D0&amp;materialId=3Dslides&amp;confId=3D0</a><br>

<br>
Do you observe an increase of DS queries ?<br>
<br>
Comments appreciated.<br>
<br>
A new version of I-D, draft-fujiwara-dnsop-ds-query-increase-00.txt<br>
has been successfully submitted by Kazunori Fujiwara and posted to the<br>
IETF repository.<br>
<br>
Filename: =A0 =A0 =A0 =A0draft-fujiwara-dnsop-ds-query-increase<br>
Revision: =A0 =A0 =A0 =A000<br>
Title: =A0 =A0 =A0 =A0 =A0 Side effect of DNSSEC: an increase of DS queries=
<br>
Creation date: =A0 2013-06-07<br>
Group: =A0 =A0 =A0 =A0 =A0 Individual Submission<br>
Number of pages: 5<br>
URL: =A0 =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.ietf.org/internet-drafts=
/draft-fujiwara-dnsop-ds-query-increase-00.txt" target=3D"_blank">http://ww=
w.ietf.org/internet-drafts/draft-fujiwara-dnsop-ds-query-increase-00.txt</a=
><br>
Status: =A0 =A0 =A0 =A0 =A0<a href=3D"http://datatracker.ietf.org/doc/draft=
-fujiwara-dnsop-ds-query-increase" target=3D"_blank">http://datatracker.iet=
f.org/doc/draft-fujiwara-dnsop-ds-query-increase</a><br>
Htmlized: =A0 =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-fujiwa=
ra-dnsop-ds-query-increase-00" target=3D"_blank">http://tools.ietf.org/html=
/draft-fujiwara-dnsop-ds-query-increase-00</a><br>
<br>
<br>
Abstract:<br>
=A0 =A0A significant increase of periodic DS queries is observed at top<br>
=A0 =A0level domain (TLD) DNS servers. =A0Currently, almost all of periodic=
 DS<br>
=A0 =A0queries come from DNSSEC validators and are queries for unsigned<br>
=A0 =A0delegations. =A0The reason of the increase is low NCACHE TTL value a=
nd<br>
=A0 =A0DS nonexistence. =A0This phenomena is DNSSEC protocol and DNS parame=
ter<br>
=A0 =A0issue. =A0DS queries will increase as DNSSEC validators will increas=
e.<br>
<br>
--<br>
Kazunori Fujiwara, JPRS &lt;<a href=3D"mailto:fujiwara@jprs.co.jp">fujiwara=
@jprs.co.jp</a>&gt;<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>
</blockquote></div><br></div>

--001a11c3b9a2f009fd04de8b03dd--

From fujiwara@jprs.co.jp  Fri Jun  7 01:38:21 2013
Return-Path: <fujiwara@jprs.co.jp>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C27621F939E for <dnsop@ietfa.amsl.com>; Fri,  7 Jun 2013 01:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gKORd6qhDp4 for <dnsop@ietfa.amsl.com>; Fri,  7 Jun 2013 01:38:16 -0700 (PDT)
Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9BE21F938E for <dnsop@ietf.org>; Fri,  7 Jun 2013 01:38:16 -0700 (PDT)
Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id r578cDub016839; Fri, 7 Jun 2013 17:38:13 +0900
X-AuditID: ac120820-b7f306d00000490a-95-51b19bf56f06
Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 84.CF.18698.5FB91B15; Fri,  7 Jun 2013 17:38:13 +0900 (JST)
Date: Fri, 07 Jun 2013 17:38:12 +0900 (JST)
Message-Id: <20130607.173812.241943965.fujiwara@jprs.co.jp>
To: jewforice@gmail.com
From: fujiwara@jprs.co.jp
In-Reply-To: <CAB3ZD+nDZ9+0rfWMdeg0vx2EWWdQpMNOJhyJK4zXaLBGJeHtWA@mail.gmail.com>
References: <20130607.153740.02261936.fujiwara@jprs.co.jp> <CAB3ZD+nDZ9+0rfWMdeg0vx2EWWdQpMNOJhyJK4zXaLBGJeHtWA@mail.gmail.com>
X-Mailer: Mew version 6.3.50 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMIsWRmVeSWpSXmKPExsWyRoiFT/fr7I2BBgunslncfXOZxeLWtmss DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfGkheXWAo+sVecXJbTwHiDvYuRk0NCwESi +foLRghbTOLCvfVsXYxcHEICJxkl+t4/YgFJsAhoSzy48QqsiFfAWmLJuc/MILaIgLjErtd3 mUBsZgEhiduNR9lAbGEBJ4kps16D1bMJSEps/twKVs8pECgxYddysMVCAo2MEp0X6yEW20mc eL6CtYuRA2i+oMTfHcIQI9UlPq/+ygxhK0pM6X7IPoGRfxZC1SwkVbOQVC1gZF7FKJOflqZb nJqXUpybbmCoV1KZr5dVUFSslwyiNzGCw5BDYQfjjFMGhxgFOBiVeHiZV28IFGJNLCuuzD3E KMnBpCTKazprY6AQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd6XIDnelMTKqtSifJiUNAeLkjjv 8bM7/IQE0hNLUrNTUwtSi2CyMhwcShK8zSCNgkWp6akVaZk5JQhpJg5OkOE8QMN/zgQZXlyQ mFucmQ6RP8UoKSXOew8kIQCSyCjNg+t9xSgO9IIwbybIaB5gSoHregU0kAlo4PRXG0AGliQi pKQaGNv8o/OaTlxedlrJ0kVHpFSmoMkqfKnho8IS5/aAVq1rs6Z0uT9Z5vXiKPdBtqc/tlqw 2igGPH/N/HfKds6m0Bq77rWhJv9+NoVuXF5mVyh1/c1p6WS52g1RBYprHWWYKw/rcW5Y2OFv 9f6A/eGNl/Qi0+b9LWhh2SN69kCf3RHr9zqlxY/+K7EUZyQaajEXFScCAGwkbJ3mAgAA
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] draft-fujiwara-dnsop-ds-query-increase-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 08:38:21 -0000

PiBGcm9tOiBpY2UgamV3IDxqZXdmb3JpY2VAZ21haWwuY29tPg0KPiBUaGVyZSBpcyBvbmUgY29u
ZnVzaW5nIHBvaW50IGluIHBhZ2UgMTIgIuKAkyB3aG9zZSBSUiBUVEwgaXMgc21hbGxlciB0aGFu
DQo+IE5DQUNIRSBUVEwiDQo+IERvZXMgdGhpcyByZWFsbHkgbWF0dGVyPyBCZWNhdXNlIHRoZSAg
aW5jcmVhc2VkIHJlcXVlc3RzIGFyZSB0byBjaGVjayB0aGUNCj4gRFMgUlIncyBub24tZXhpc3Rl
bmNlIHdoZW4gTkNBSENFIGZvciB0aGlzIERTIFJSIGV4aXByZXMsIHNvIGhvdyBpcyBpdA0KPiBy
ZWxhdGVkIHRvIHRoZSBSUidzIFRUTD8NCg0KQmVjYXVzZSBETlNTRUMgdmFsaWRhdGlvbiBwcm9j
ZXNzIGRvZXMgbm90IHN0YXJ0DQppZiBSUiBvZiBwb3B1bGFyIG5hbWVzIGFyZSBpbiB0aGUgY2Fj
aGUuDQoNCk9uZSBleGFtcGxlIGlzICJ3d3cubmFub2cub3JnIEEiLg0KSXQgaXMgbm90IHNpZ25l
ZCBhbmQgaXRzIFRUTCBpcyAxNDQwMC4NCg0Kd3d3Lm5hbm9nLm9yZy4gICAgICAgICAgMTQ0MDAg
ICBJTiAgICAgIEEgICAgICAgNTAuMzEuMTUxLjY4DQoNCkkgbWFkZSAid3d3Lm5hbm9nLm9yZyBB
IiBwZXJpb2RpYyBxdWVyaWVzIHRvIG15IHZhbGlkYXRvcnMsDQp0aGUgc2VuZGluZyBpbnRlcnZh
bCBvZiAibmFub2cub3JnIERTIiBxdWVyaWVzIGlzIG5vdCBOQ0FDSEUgVFRMIDkwMC4NCg0KLS0N
CkthenVub3JpIEZ1aml3YXJhLCBKUFJTIDxmdWppd2FyYUBqcHJzLmNvLmpwPg0KDQoNCg==

From ed.lewis@neustar.biz  Fri Jun  7 04:34:03 2013
Return-Path: <ed.lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20F4021F9339 for <dnsop@ietfa.amsl.com>; Fri,  7 Jun 2013 04:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.202
X-Spam-Level: 
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id auCADpL3eNTQ for <dnsop@ietfa.amsl.com>; Fri,  7 Jun 2013 04:33:58 -0700 (PDT)
Received: from smtp69.ord1c.emailsrvr.com (smtp69.ord1c.emailsrvr.com [108.166.43.69]) by ietfa.amsl.com (Postfix) with ESMTP id 8629521F92EC for <dnsop@ietf.org>; Fri,  7 Jun 2013 04:33:58 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 081F01480E4; Fri,  7 Jun 2013 07:33:58 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id A215F148096;  Fri,  7 Jun 2013 07:33:57 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_80DC78BD-204D-4C86-A464-DDC66C641DE4"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <20130607.153740.02261936.fujiwara@jprs.co.jp>
Date: Fri, 7 Jun 2013 07:33:57 -0400
Message-Id: <A948312D-9EA0-45EB-945F-FA9F57BD655B@neustar.biz>
References: <20130607.153740.02261936.fujiwara@jprs.co.jp>
To: IETF DNSOP WG <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>
Subject: Re: [DNSOP] draft-fujiwara-dnsop-ds-query-increase-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 11:34:03 -0000

--Apple-Mail=_80DC78BD-204D-4C86-A464-DDC66C641DE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Yes, this is a problem.  But I don't like any of the discussed =
solutions.  I don't think that is surprising, I figure they are just =
ideas and unfortunately they all have bad side effects.

(Possible Solution#) 1 - There are zones that promise new delegations to =
appear in less than X minutes.  Argue whether you think this is an =
abomination of nature or not, but it is a requirement from the business =
world that has been met by DNS for a decade. DNSSEC can't take away a =
"feature" like this anymore that it could take away round-robining =
answers.

2 & 3 - The document hints at this already : impractical.  DNS has got =
to maintain it's loose management nature. A sync'd DNS will sink.

4 -  Add a dummy DS won't work because that kills opt-out.  You can =
throw scaling to 100% out the window.

My thoughts, based on the DNS-OARC presentation, was that this can be =
better treated at the "client" side.

The trouble is we caved in and allowed recursive servers to use the =
NSEC{3} record to infer when they can send back an NXDOMAIN.  Instead of =
allowing a cache to only use the NSEC(3) proof for the (name,class,type) =
- which is what it should be for - we allow recursives to make use is =
the span in the NSEC{3) to say that nothing would be there so I'm not =
going to ask.

What I would suggest is restricting recursive servers to only using the =
proof for the name/class/type and in the case of the DS, in this rare =
case, boost the TTL used for the DS ncache'd answer to that of the NS =
set.  And I mean the remaining TTL of the NS set already in the cache =
(elsewhere).

Listening to the talk, I quickly realized that we have no degrees of =
freedom on the authority side, this has to be solved on the caching =
side.  In the spirit of a quick response, the above is offered as a =
suggestion, it might have holes in it.

On Jun 7, 2013, at 2:37, <fujiwara@jprs.co.jp> <fujiwara@jprs.co.jp> =
wrote:

> JPRS observed that DS queries for JP registered domain names have been
> increasing and 3.5% of queries are qtype DS now.
>=20
> I make a presentation about it at DNS-OARC 2013 Spring workshop and I
> wrote a draft as a DNSSEC side effect.
>=20
> Presentation material is here:
>  =
https://indico.dns-oarc.net/indico/getFile.py/access?contribId=3D14&resId=3D=
0&materialId=3Dslides&confId=3D0
>=20
> Do you observe an increase of DS queries ?
>=20
> Comments appreciated.
>=20
> A new version of I-D, draft-fujiwara-dnsop-ds-query-increase-00.txt
> has been successfully submitted by Kazunori Fujiwara and posted to the
> IETF repository.
>=20
> Filename:	 draft-fujiwara-dnsop-ds-query-increase
> Revision:	 00
> Title:		 Side effect of DNSSEC: an increase of DS =
queries
> Creation date:	 2013-06-07
> Group:		 Individual Submission
> Number of pages: 5
> URL:             =
http://www.ietf.org/internet-drafts/draft-fujiwara-dnsop-ds-query-increase=
-00.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-fujiwara-dnsop-ds-query-increase
> Htmlized:        =
http://tools.ietf.org/html/draft-fujiwara-dnsop-ds-query-increase-00
>=20
>=20
> Abstract:
>   A significant increase of periodic DS queries is observed at top
>   level domain (TLD) DNS servers.  Currently, almost all of periodic =
DS
>   queries come from DNSSEC validators and are queries for unsigned
>   delegations.  The reason of the increase is low NCACHE TTL value and
>   DS nonexistence.  This phenomena is DNSSEC protocol and DNS =
parameter
>   issue.  DS queries will increase as DNSSEC validators will increase.
>=20
> --
> Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_80DC78BD-204D-4C86-A464-DDC66C641DE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Yes, this is a problem. &nbsp;But I don't like any of the =
discussed solutions. &nbsp;I don't think that is surprising, I figure =
they are just ideas and unfortunately they all have bad side =
effects.</div><div><br></div><div>(Possible Solution#) 1 - There are =
zones that promise new delegations to appear in less than X minutes. =
&nbsp;Argue whether you think this is an abomination of nature or not, =
but it is a requirement from the business world that has been met by DNS =
for a decade. DNSSEC can't take away a "feature" like this anymore that =
it could take away round-robining answers.</div><div><br></div><div>2 =
&amp; 3 - The document hints at this already : impractical. &nbsp;DNS =
has got to maintain it's loose management nature. A sync'd DNS will =
sink.</div><div><br></div><div>4 - &nbsp;Add a dummy DS won't work =
because that kills opt-out. &nbsp;You can throw scaling to 100% out the =
window.</div><div><br></div><div>My thoughts, based on the DNS-OARC =
presentation, was that this can be better treated at the "client" =
side.</div><div><br></div><div>The trouble is we caved in and allowed =
recursive servers to use the NSEC{3} record to infer when they can send =
back an NXDOMAIN. &nbsp;Instead of allowing a cache to only use the =
NSEC(3) proof for the (name,class,type) - which is what it should be for =
- we allow recursives to make use is the span in the NSEC{3) to say that =
nothing would be there so I'm not going to =
ask.</div><div><br></div><div>What I would suggest is restricting =
recursive servers to only using the proof for the name/class/type and in =
the case of the DS, in this rare case, boost the TTL used for the DS =
ncache'd answer to that of the NS set. &nbsp;And I mean the remaining =
TTL of the NS set already in the cache =
(elsewhere).</div><div><br></div><div>Listening to the talk, I quickly =
realized that we have no degrees of freedom on the authority side, this =
has to be solved on the caching side. &nbsp;In the spirit of a quick =
response, the above is offered as a suggestion, it might have holes in =
it.</div><br><div><div>On Jun 7, 2013, at 2:37, &lt;<a =
href=3D"mailto:fujiwara@jprs.co.jp">fujiwara@jprs.co.jp</a>&gt; &lt;<a =
href=3D"mailto:fujiwara@jprs.co.jp">fujiwara@jprs.co.jp</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>JPRS observed that DS queries for JP registered =
domain names have been<br>increasing and 3.5% of queries are qtype DS =
now.<br><br>I make a presentation about it at DNS-OARC 2013 Spring =
workshop and I<br>wrote a draft as a DNSSEC side =
effect.<br><br>Presentation material is here:<br> &nbsp;<a =
href=3D"https://indico.dns-oarc.net/indico/getFile.py/access?contribId=3D1=
4&amp;resId=3D0&amp;materialId=3Dslides&amp;confId=3D0">https://indico.dns=
-oarc.net/indico/getFile.py/access?contribId=3D14&amp;resId=3D0&amp;materi=
alId=3Dslides&amp;confId=3D0</a><br><br>Do you observe an increase of DS =
queries ?<br><br>Comments appreciated.<br><br>A new version of I-D, =
draft-fujiwara-dnsop-ds-query-increase-00.txt<br>has been successfully =
submitted by Kazunori Fujiwara and posted to the<br>IETF =
repository.<br><br>Filename:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> =
draft-fujiwara-dnsop-ds-query-increase<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> Side effect of DNSSEC: an increase of DS queries<br>Creation =
date:<span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
2013-06-07<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>Number =
of pages: 5<br>URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a=
 =
href=3D"http://www.ietf.org/internet-drafts/draft-fujiwara-dnsop-ds-query-=
increase-00.txt">http://www.ietf.org/internet-drafts/draft-fujiwara-dnsop-=
ds-query-increase-00.txt</a><br>Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-fujiwara-dnsop-ds-query-incr=
ease">http://datatracker.ietf.org/doc/draft-fujiwara-dnsop-ds-query-increa=
se</a><br>Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-fujiwara-dnsop-ds-query-increase-=
00">http://tools.ietf.org/html/draft-fujiwara-dnsop-ds-query-increase-00</=
a><br><br><br>Abstract:<br> &nbsp;&nbsp;A significant increase of =
periodic DS queries is observed at top<br> &nbsp;&nbsp;level domain =
(TLD) DNS servers. &nbsp;Currently, almost all of periodic DS<br> =
&nbsp;&nbsp;queries come from DNSSEC validators and are queries for =
unsigned<br> &nbsp;&nbsp;delegations. &nbsp;The reason of the increase =
is low NCACHE TTL value and<br> &nbsp;&nbsp;DS nonexistence. &nbsp;This =
phenomena is DNSSEC protocol and DNS parameter<br> &nbsp;&nbsp;issue. =
&nbsp;DS queries will increase as DNSSEC validators will =
increase.<br><br>--<br>Kazunori Fujiwara, JPRS &lt;<a =
href=3D"mailto:fujiwara@jprs.co.jp">fujiwara@jprs.co.jp</a>&gt;<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></div></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></body></html>=

--Apple-Mail=_80DC78BD-204D-4C86-A464-DDC66C641DE4--

From wjhns1@hardakers.net  Thu Jun 13 10:58:33 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC2421F9A35 for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2013 10:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNYv6zrtNxvw for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2013 10:58:33 -0700 (PDT)
Received: from mail.hardakers.net (unknown [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 37B2621F9A2C for <dnsop@ietf.org>; Thu, 13 Jun 2013 10:58:33 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:20c4:ef9:a97f:e8c5]) by mail.hardakers.net (Postfix) with ESMTPSA id 7535D22A69 for <dnsop@ietf.org>; Thu, 13 Jun 2013 10:58:31 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: dnsop@ietf.org
Date: Thu, 13 Jun 2013 10:58:31 -0700
Message-ID: <0lzjutsxiw.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Subject: [DNSOP] request draft-hardaker-dnsop-csync be adopted as a WG item
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:58:33 -0000

Because I think it'll be helpful to the world at large.  That's why.

Thoughts?

A new version of I-D, draft-hardaker-dnsop-csync-00.txt
has been successfully submitted by Wes Hardaker and posted to the
IETF repository.

Filename:	 draft-hardaker-dnsop-csync
Revision:	 00
Title:		 Child To Parent Synchronization in DNS
Creation date:	 2013-06-05
Group:		 Individual Submission
Number of pages: 13
URL:             http://www.ietf.org/internet-drafts/draft-hardaker-dnsop-csync-00.txt
Status:          http://datatracker.ietf.org/doc/draft-hardaker-dnsop-csync
Htmlized:        http://tools.ietf.org/html/draft-hardaker-dnsop-csync-00

Abstract:
   This document specifies how a child zone in the DNS can publish a
   record that can indicate that a parental agent may copy and process
   certain records from the child zone.  The existence and change of the
   record may be monitored by a parental agent to either assist in
   transferring or automatically transfer data from the child to the
   parent.


-- 
Wes Hardaker
Parsons

From joelja@bogus.com  Sat Jun 15 06:29:02 2013
Return-Path: <joelja@bogus.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F08AA21F9D30 for <dnsop@ietfa.amsl.com>; Sat, 15 Jun 2013 06:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id byo8rf696Ay4 for <dnsop@ietfa.amsl.com>; Sat, 15 Jun 2013 06:29:02 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB8E21F9D05 for <dnsop@ietf.org>; Sat, 15 Jun 2013 06:29:02 -0700 (PDT)
Received: from wifi-209-57.mtg.afnog.org (wifi-209-57.mtg.afnog.org [196.200.209.57]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5FDSvLJ002207 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <dnsop@ietf.org>; Sat, 15 Jun 2013 13:29:01 GMT (envelope-from joelja@bogus.com)
Message-ID: <51BC6C18.3020802@bogus.com>
Date: Sat, 15 Jun 2013 15:28:56 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 15 Jun 2013 13:29:01 +0000 (UTC)
Subject: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 13:29:03 -0000

I'm interested in the intersection between the requested payload size 
and the use of the v6 fragmentation header, 6891 I think is missing some 
advice to implementers that might reasonably prevent fragmented replies 
from being dropped and limit the degree of amplification that can be 
achieved with large RRsets.

Are there thoughts about this based on experience?

thanks
joel

From marka@isc.org  Sun Jun 16 23:15:27 2013
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDDA921F9273 for <dnsop@ietfa.amsl.com>; Sun, 16 Jun 2013 23:15:27 -0700 (PDT)
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=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFPC1V15FPcm for <dnsop@ietfa.amsl.com>; Sun, 16 Jun 2013 23:15:26 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 5855421F90FD for <dnsop@ietf.org>; Sun, 16 Jun 2013 23:15:26 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 5C700C94B7; Mon, 17 Jun 2013 06:15:08 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1371449717; bh=+PjwAk+V59eCAaBksdL1bchq9sre7O7UgYkXoxMP/vw=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=XRkuxTeDnzgH/QV9LOQJY9KJt1DNdjw2/2D0FbkdBLsusB5DT6vTkxboPbnkyjsRD RYLIlLb/DUkPG5YCtjt2Cjh5D0VX8cUV3YxOELuTJ2rmL1ts3WnivMG/evKEq12FE3 tLkPfr5NLhLvhmdBPleL9hi5btd/FTaqkR6tA0S8=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Mon, 17 Jun 2013 06:15:08 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 02D0A216C40; Mon, 17 Jun 2013 06:15:08 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id EC19035F6192; Mon, 17 Jun 2013 16:15:03 +1000 (EST)
To: joel jaeggli <joelja@bogus.com>
From: Mark Andrews <marka@isc.org>
References: <51BC6C18.3020802@bogus.com>
In-reply-to: Your message of "Sat, 15 Jun 2013 15:28:56 +0200." <51BC6C18.3020802@bogus.com>
Date: Mon, 17 Jun 2013 16:15:03 +1000
Message-Id: <20130617061503.EC19035F6192@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 06:15:27 -0000

In message <51BC6C18.3020802@bogus.com>, joel jaeggli writes:
> I'm interested in the intersection between the requested payload size 
> and the use of the v6 fragmentation header, 6891 I think is missing some 
> advice to implementers that might reasonably prevent fragmented replies 
> from being dropped and limit the degree of amplification that can be 
> achieved with large RRsets.

Fragments get dropped because of badly configured/designed firewalls
and PMTUD.  Setting IPV6_USE_MIN_MTU to 1 helps with the latter
though it may result in a addition fragment being sent.

If one really wants to play games you set IPV6_USE_MIN_MTU to 1 for
DNS UDP responses bigger than 1432 octets and leave it at -1 for
mesages 1432 octets and less.  1432 octets allows for both a IPv4
and IPv6 header over ethernet without fragmenting.  There is still
a lot of 6in4 and 6to4 tunnels.

TCP should always set IPV6_USE_MIN_MTU to 1 as PMTUD takes too long
for DNS and is unreliable. Except for a zone transfers the most it
will add is 5 additional packets (+ possible acks) to the transaction
and usually no more than 1.

> Are there thoughts about this based on experience?
> 
> thanks
> joel
> _______________________________________________
> 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 warren@kumari.net  Mon Jun 17 10:32:37 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02F921F8825 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 10:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.127
X-Spam-Level: 
X-Spam-Status: No, score=-102.127 tagged_above=-999 required=5 tests=[AWL=0.472, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-3CVwwUyApv for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 10:32:33 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3620021F8887 for <dnsop@ietf.org>; Mon, 17 Jun 2013 10:32:33 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.90]) by vimes.kumari.net (Postfix) with ESMTPSA id 44C7C1B40BB1; Mon, 17 Jun 2013 13:32:32 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
Date: Mon, 17 Jun 2013 13:32:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com>
To: IETF DNSOP WG <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: [DNSOP] Fwd: New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:32:38 -0000

Hi there all,

We have just posted a new version of draft-kumari-ogud-dnsop-cds=20

This incorporates comments from both the list and in person discussions.=20=


The authors believe this version is ready for WG adoption and request =
the DNSOP chairs to kick off an adoption call.

W


Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-kumari-ogud-dnsop-cds-02.txt
> Date: June 17, 2013 12:58:29 PM EDT
> To: Olafur Gudmundsson <ogud@ogud.com>, Warren Kumari =
<warren@kumari.net>, George Barwood <george.barwood@blueyonder.co.uk>
>=20
>=20
> A new version of I-D, draft-kumari-ogud-dnsop-cds-02.txt
> has been successfully submitted by Warren Kumari and posted to the
> IETF repository.
>=20
> Filename:	 draft-kumari-ogud-dnsop-cds
> Revision:	 02
> Title:		 Automating DNSSEC delegation trust maintenance
> Creation date:	 2013-06-17
> Group:		 Individual Submission
> Number of pages: 14
> URL:             =
http://www.ietf.org/internet-drafts/draft-kumari-ogud-dnsop-cds-02.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-kumari-ogud-dnsop-cds
> Htmlized:        =
http://tools.ietf.org/html/draft-kumari-ogud-dnsop-cds-02
> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kumari-ogud-dnsop-cds-02
>=20
> 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.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20

--
"Let's just say that if complete and utter chaos was lightning, he'd be =
the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."

    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)



From paul@cypherpunks.ca  Mon Jun 17 11:28:22 2013
Return-Path: <paul@cypherpunks.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E85321F9CF2 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 11:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zv9sCqn00n8i for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 11:28:16 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id A0F0521F9CB2 for <dnsop@ietf.org>; Mon, 17 Jun 2013 11:28:16 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bZ1Bh3w6bz1wH; Mon, 17 Jun 2013 14:28:12 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id kmwQbNTgnMgV; Mon, 17 Jun 2013 14:28:12 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Mon, 17 Jun 2013 14:28:11 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id A4C3C82C56; Mon, 17 Jun 2013 14:28:12 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 9545982C55; Mon, 17 Jun 2013 14:28:12 -0400 (EDT)
Date: Mon, 17 Jun 2013 14:28:12 -0400 (EDT)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net>
Message-ID: <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 18:28:22 -0000

On Mon, 17 Jun 2013, Warren Kumari wrote:

> We have just posted a new version of draft-kumari-ogud-dnsop-cds
>
> This incorporates comments from both the list and in person discussions.
>
> The authors believe this version is ready for WG adoption and request the DNSOP chairs to kick off an adoption call.

I am in favour of adopting this draft as a WG item.

Some comments:

Section 3.1.1:

I don't think the CDS record should be able to cause a child domain to
go from secure to insecure, or from insecure to secure. That
(infrequent) change should have an additional authentication, eg via EPP
or otherwise)

I strongly prefer the CDS and DS digest algorithms to be identical, so I
am not in favour of some special kind of CDS digest overloading for the
meaning of transition from secure to insecure.

Section 4.2

I think it _is_ able to use a standard validator. It just needs a
non-standard trust anchor loading for confirmation the path of trust
will not break.


Typos:

thus it is not be able -> thus it is not able


If one exits it applies  -> If one exists it applies



From ek@google.com  Mon Jun 17 11:34:10 2013
Return-Path: <ek@google.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 167B121F9D5F for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 11:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MG11wU073ts for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 11:34:05 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7D921F9D01 for <dnsop@ietf.org>; Mon, 17 Jun 2013 11:34:05 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id v20so2842647lbc.3 for <dnsop@ietf.org>; Mon, 17 Jun 2013 11:34:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=BHpSiVIQHOOzJA7xT68jpORUSFa4QDfDXcXbAUD9ytU=; b=FczI5/EuylOdundetCCyFOF1m8oRPPpOQrhoiBMNXv7Tj6RDeCVqtNzFu2hJqCWHRP Pk332n0Eaeqdva3MyAqM/1st6yQ7J2iJb6A8VLkoDmFZ2AuUIZNtXGZ8hbXDhV7rdtnR ozilNQ/m8J2DUtZcM/w4OSQ/soz/YvqoWEMDVdOoM32skshtzRWzlIGm+ivKGI979k7+ JyBx0bxxo8qMDhqwKgH8y/AM3zIoWeu8kUHX08l1tjuV4UHG5X858ojVZMKTz/Yw2ZcE acqraSerjiix88BxMx6ANDZBFgHnKnRoh4SnNhQW5z/kyscIXwuZtB/qBwxaCI05UmEZ 7fAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=BHpSiVIQHOOzJA7xT68jpORUSFa4QDfDXcXbAUD9ytU=; b=FZOa0DsCJ9gyfcnYsogvY3duyVl7H4rQOS1rYOxfW6iLhKrBKT2bE6cMhQUJ5a2qcz XF8zHjrBC1ju4F/PkQfwoOb8XmnZScKaLME1Oudv6c4dbu8ZExUiSaglmpwMTrI4twkG iv/JVych6XUSTfMeM5DfC7Zh+OEZdmhrwqeTFgg/D/9IGwmNrSQ7aRIKGeZ/4u+kKpKf PFW153RKPGQsaQoCCJwvkX2ewQs6cXNWE1N8i70egI+YjUeHM5JWuMrQkgYyjnb6JyPV JyH6MlGsOkKo/P8bBwhoAw1iJt43vzQjUNkR/GMnaRPDrPJjXdvo5IOkPu+k0A7ZgrJv nzUg==
X-Received: by 10.152.2.168 with SMTP id 8mr7224683lav.69.1371494044244; Mon, 17 Jun 2013 11:34:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.73.170 with HTTP; Mon, 17 Jun 2013 11:33:44 -0700 (PDT)
In-Reply-To: <20130617061503.EC19035F6192@drugs.dv.isc.org>
References: <51BC6C18.3020802@bogus.com> <20130617061503.EC19035F6192@drugs.dv.isc.org>
From: Erik Kline <ek@google.com>
Date: Mon, 17 Jun 2013 11:33:44 -0700
Message-ID: <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQl1binMwGyCJByH4+f9rHzMhSW/UhloQaKD9zFYP+31e1TzMZr/B7Pwk5V1qD3lmLvNetbQkEos4FzyQlU0b4cEUufhqbZMT5iubM/uqgPJDlZH7Tw/tL/6w2EDlhLkURNR4msrRGsl87MjBmjjFnuRAvvJtHgZwhQJL6Vjel7YauV6N1OjNYix+XOumzFkzA747sJk
Cc: joel jaeggli <joelja@bogus.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 18:34:10 -0000

On 16 June 2013 23:15, Mark Andrews <marka@isc.org> wrote:
>
> In message <51BC6C18.3020802@bogus.com>, joel jaeggli writes:
>> I'm interested in the intersection between the requested payload size
>> and the use of the v6 fragmentation header, 6891 I think is missing some
>> advice to implementers that might reasonably prevent fragmented replies
>> from being dropped and limit the degree of amplification that can be
>> achieved with large RRsets.
>
> Fragments get dropped because of badly configured/designed firewalls
> and PMTUD.  Setting IPV6_USE_MIN_MTU to 1 helps with the latter
> though it may result in a addition fragment being sent.

Unfortunately the former are far too prevalent.  It's undoubtedly too
late, but unfortunately it might have been better to do the
fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
http://tools.ietf.org/html/rfc5405#section-3.2).

From marka@isc.org  Mon Jun 17 18:26:21 2013
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEA321F9DB6 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 18:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hlb9n4mEGBNi for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 18:26:20 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id C3C7021F9DB4 for <dnsop@ietf.org>; Mon, 17 Jun 2013 18:26:20 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 96609C9422; Tue, 18 Jun 2013 01:26:12 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1371518780; bh=/3j12t7i/7fiYYSraxzzbtyo+vA/UXB8ZRmQSs9gbf8=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=jXGTpuStmpCcp9inuE9B0EoPl8oS46OYgkkM70Kv6o3Qt0wisFExUtAOQ7R2tZ3zj H4C5/XuPmLiNxGdMRwswhaMUtxV6/4Q8GwYT18A5ySh/ud3CmvkGbD5RV+yZIiyEWv /EbeYP3xAx5//tmAl1kW0pBTqT+FAv9ftoUw4D3g=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 18 Jun 2013 01:26:12 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 74972216C40; Tue, 18 Jun 2013 01:25:59 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 4A72A35FF889; Tue, 18 Jun 2013 10:49:05 +1000 (EST)
To: Erik Kline <ek@google.com>
From: Mark Andrews <marka@isc.org>
References: <51BC6C18.3020802@bogus.com> <20130617061503.EC19035F6192@drugs.dv.isc.org> <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com>
In-reply-to: Your message of "Mon, 17 Jun 2013 11:33:44 -0700." <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com>
Date: Tue, 18 Jun 2013 10:49:05 +1000
Message-Id: <20130618004905.4A72A35FF889@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: joel jaeggli <joelja@bogus.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 01:26:21 -0000

In message <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com>, Erik Kline writes:
> On 16 June 2013 23:15, Mark Andrews <marka@isc.org> wrote:
> >
> > In message <51BC6C18.3020802@bogus.com>, joel jaeggli writes:
> >> I'm interested in the intersection between the requested payload size
> >> and the use of the v6 fragmentation header, 6891 I think is missing some
> >> advice to implementers that might reasonably prevent fragmented replies
> >> from being dropped and limit the degree of amplification that can be
> >> achieved with large RRsets.
> >
> > Fragments get dropped because of badly configured/designed firewalls
> > and PMTUD.  Setting IPV6_USE_MIN_MTU to 1 helps with the latter
> > though it may result in a addition fragment being sent.
> 
> Unfortunately the former are far too prevalent.  It's undoubtedly too
> late, but unfortunately it might have been better to do the
> fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
> http://tools.ietf.org/html/rfc5405#section-3.2).

It is *never* too late.  For IPv6 we are still in the very
early days.

Firewalls could just as <src,dest,next header udp,frag!=0> when
they add <src,dest,udp,port,port> tuple today for reply traffic.
This make the hole for fragments a slit rather than wide open.

One could extend IPv6 to add a ignorable hop-by-hop option that
contains a copy the UDP header and add that when fragmentation is
done.  This would reduce the slit to a point.  If the firewall is
reassembling this would be used to protect the reassembly queue.

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

From christopher.morrow@gmail.com  Mon Jun 17 18:31:58 2013
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D7D21F9CD0 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 18:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PBpLfD+kWtL for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 18:31:57 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5878B21F9CCA for <dnsop@ietf.org>; Mon, 17 Jun 2013 18:31:57 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id ec20so3077757lab.27 for <dnsop@ietf.org>; Mon, 17 Jun 2013 18:31:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=sf5RrVQaCGQBTgg8VWd5lexMpDV6eu99X0OGXYD4ThI=; b=hH+sAqPQEaj8IT2vLXbcThkT6kMfRYzNAHSlA4faQnEC9RNOIVPcqPg++NA7c5zm8W R8weVsZjtFjnE7DoWMpbK04AKHmnUC+Mc8Gnhw5IIagpLsAVBXSPyG6d5lfLc5aWlmMe K8SyK0Iym2M8UygZZ9+QxCNptwF1ldeT95KUsBDjtwP13o1qC7jQ5BAVlmDOf2qYYMaa 2IPTJOx05FP490TrbpNzjZ7lbRYPihnQxwOn4MFc1xuxtqK9qUXHuap/szxsm88u4fGG WPeFaImPqbWRh4an8DyTPlJH9gGJd16McPvabZRTApcW28VYGsHfEpe6QziE+S0b4bcQ BMQA==
MIME-Version: 1.0
X-Received: by 10.152.25.135 with SMTP id c7mr7977784lag.39.1371519116104; Mon, 17 Jun 2013 18:31:56 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.22.196 with HTTP; Mon, 17 Jun 2013 18:31:56 -0700 (PDT)
In-Reply-To: <20130618004905.4A72A35FF889@drugs.dv.isc.org>
References: <51BC6C18.3020802@bogus.com> <20130617061503.EC19035F6192@drugs.dv.isc.org> <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com> <20130618004905.4A72A35FF889@drugs.dv.isc.org>
Date: Mon, 17 Jun 2013 21:31:56 -0400
X-Google-Sender-Auth: lwUVpsjXHI3KOf4pK4wwXiI__Bk
Message-ID: <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: joel jaeggli <joelja@bogus.com>, Erik Kline <ek@google.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 01:31:58 -0000

On Mon, Jun 17, 2013 at 8:49 PM, Mark Andrews <marka@isc.org> wrote:
>> Unfortunately the former are far too prevalent.  It's undoubtedly too
>> late, but unfortunately it might have been better to do the
>> fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
>> http://tools.ietf.org/html/rfc5405#section-3.2).
>
> It is *never* too late.  For IPv6 we are still in the very
> early days.

but, what about the 'vast install base'  ?

From marka@isc.org  Mon Jun 17 19:19:40 2013
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4338521F9C8E for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 19:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7K+Yidlkttf2 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 19:19:39 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 6712C21F9C8D for <dnsop@ietf.org>; Mon, 17 Jun 2013 19:19:39 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 64273C9498; Tue, 18 Jun 2013 02:19:31 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1371521979; bh=Z6Ht3fia8irLpHpKzV4I0zZ/lKwhed0RVMDCAmJb3tE=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=p+gnzfinrEzjY9l+HqRsAeYNDMP6Dxg/4V7BKwYPedgabpiUYzqJPoM6xgVD2vuAq +NNkU0sjG6VCutG7OL5g+OHSRC74Xw7AkNy7nmLEycKlGtGuO15eWl4SLhuhM/goJn vE/rp2r0p3aPNqfleRPFvrHnwSOQa5qYZywIJm0s=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 18 Jun 2013 02:19:31 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d4b2:aa83:8f18:7525]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 2BACE216C40; Tue, 18 Jun 2013 02:19:31 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 18AA03600603; Tue, 18 Jun 2013 12:19:29 +1000 (EST)
To: Christopher Morrow <morrowc.lists@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <51BC6C18.3020802@bogus.com> <20130617061503.EC19035F6192@drugs.dv.isc.org> <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com> <20130618004905.4A72A35FF889@drugs.dv.isc.org> <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com>
In-reply-to: Your message of "Mon, 17 Jun 2013 21:31:56 -0400." <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com>
Date: Tue, 18 Jun 2013 12:19:29 +1000
Message-Id: <20130618021929.18AA03600603@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: joel jaeggli <joelja@bogus.com>, Erik Kline <ek@google.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 02:19:40 -0000

In message <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com>, Christopher Morrow writes:
> On Mon, Jun 17, 2013 at 8:49 PM, Mark Andrews <marka@isc.org> wrote:
> >> Unfortunately the former are far too prevalent.  It's undoubtedly too
> >> late, but unfortunately it might have been better to do the
> >> fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
> >> http://tools.ietf.org/html/rfc5405#section-3.2).
> >
> > It is *never* too late.  For IPv6 we are still in the very
> > early days.
> 
> but, what about the 'vast install base'  ?

There isn't a "vast install base" of firewalls (border routers).
If there was we would have 99% IPv6 traffic instead of 1.6% IPv6
traffic.

The key is to get the functionality into firewalls/load balancer
etc. ASAP.  Hosts can happen as they are replaced as part of normal
refresh cycles or apps can use raw sockets if they need the
functionality sooner.  The IPv6 layer will fragment the raw packets
with the hop-by-hop header fine.

Mark

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

From christopher.morrow@gmail.com  Mon Jun 17 20:41:16 2013
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3931221F9C69 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 20:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cMOOGY8TWcZL for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 20:41:15 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7387C21F9C67 for <dnsop@ietf.org>; Mon, 17 Jun 2013 20:41:15 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id er20so3152434lab.31 for <dnsop@ietf.org>; Mon, 17 Jun 2013 20:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=JjHwSZ5ajm67aFhXXeNZDLic+fNtsQbQep2YAWZCkMQ=; b=AUPIcWoYd6ioE5aJXCB8FAXHO9/OCHHa0gskL7LOiyoqd5tGq4ocdmB7Ng815nD5P9 AhWpvrUSFsnFjdktVuXyqlf34BJwPTv67bMzy1tK5OEYRRJijWIc9z7FB+18kiaYe5jo J581FG9YmjTaOHlZBm8nlbyCWryARFHQiUKvVCOv+ZO115jNd0u/zuPThC53GGtLER/G 5onpZHyWbqsZ4yKcj/gw+4SpAZEFYRtC7MCe6gzX2SpWeVcJfM2bSy5SeRAJ2wOej050 nBHay3IRPytPz83nF/JVscoCthBzP7QpZx2+CxgICMmXi3eeQNUxK8vvjQcy+Kb3Dm5g WioA==
MIME-Version: 1.0
X-Received: by 10.152.42.236 with SMTP id r12mr8143126lal.46.1371526874337; Mon, 17 Jun 2013 20:41:14 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.22.196 with HTTP; Mon, 17 Jun 2013 20:41:14 -0700 (PDT)
In-Reply-To: <20130618021929.18AA03600603@drugs.dv.isc.org>
References: <51BC6C18.3020802@bogus.com> <20130617061503.EC19035F6192@drugs.dv.isc.org> <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com> <20130618004905.4A72A35FF889@drugs.dv.isc.org> <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com> <20130618021929.18AA03600603@drugs.dv.isc.org>
Date: Mon, 17 Jun 2013 23:41:14 -0400
X-Google-Sender-Auth: zEYb52oX-NZLy0TNBEz-hfNvWUA
Message-ID: <CAL9jLaZA5WEgbGP51VczBpHrEkqPNB-H2jwuSAzSH=ZSCxELyQ@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: joel jaeggli <joelja@bogus.com>, Erik Kline <ek@google.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 03:41:16 -0000

On Mon, Jun 17, 2013 at 10:19 PM, Mark Andrews <marka@isc.org> wrote:
>
> In message <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com>, Christopher Morrow writes:
>> On Mon, Jun 17, 2013 at 8:49 PM, Mark Andrews <marka@isc.org> wrote:
>> >> Unfortunately the former are far too prevalent.  It's undoubtedly too
>> >> late, but unfortunately it might have been better to do the
>> >> fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
>> >> http://tools.ietf.org/html/rfc5405#section-3.2).
>> >
>> > It is *never* too late.  For IPv6 we are still in the very
>> > early days.
>>
>> but, what about the 'vast install base'  ?
>
> There isn't a "vast install base" of firewalls (border routers).
> If there was we would have 99% IPv6 traffic instead of 1.6% IPv6
> traffic.

I forgot my :) in my comment.
anyways...

-chris

From nweaver@icsi.berkeley.edu  Mon Jun 17 20:44:25 2013
Return-Path: <nweaver@icsi.berkeley.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8878D21F9BB3 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 20:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7YiU7sz+69t for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2013 20:44:19 -0700 (PDT)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) by ietfa.amsl.com (Postfix) with ESMTP id C487921F9C91 for <dnsop@ietf.org>; Mon, 17 Jun 2013 20:44:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 828852C4029; Mon, 17 Jun 2013 20:44:19 -0700 (PDT)
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 iN+0fmbPjHn3; Mon, 17 Jun 2013 20:44:19 -0700 (PDT)
Received: from [10.0.1.2] (c-76-103-162-14.hsd1.ca.comcast.net [76.103.162.14]) (Authenticated sender: nweaver) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id DEA322C4003; Mon, 17 Jun 2013 20:44:18 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Nicholas Weaver <nweaver@icsi.berkeley.edu>
In-Reply-To: <20130618021929.18AA03600603@drugs.dv.isc.org>
Date: Mon, 17 Jun 2013 20:44:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <87C17053-E549-4534-A324-1018AA331F53@icsi.berkeley.edu>
References: <51BC6C18.3020802@bogus.com> <20130617061503.EC19035F6192@drugs.dv.isc.org> <CAAedzxrr9Jnhuo5tM6wMogKhhOoudpD3+Wk0rRn6hXzH0S3Wjg@mail.gmail.com> <20130618004905.4A72A35FF889@drugs.dv.isc.org> <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com> <20130618021929.18AA03600603@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1508)
Cc: joel jaeggli <joelja@bogus.com>, Christopher Morrow <morrowc.lists@gmail.com>, "dnsop@ietf.org" <dnsop@ietf.org>, Nicholas Weaver <nweaver@icsi.berkeley.edu>, Erik Kline <ek@google.com>
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 03:44:25 -0000

Lets just say if you think the IPv4 fragmentation problem is bad, IPv6 =
makes it look positively benign by comparison on the IPv6 kit deployed =
today.

Basically, use a 1400B EDNS0 mtu, and failover to TCP.


From sthaug@nethelp.no  Tue Jun 18 01:48:00 2013
Return-Path: <sthaug@nethelp.no>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E611121F9D05 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 01:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8AJrujaqD8B for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 01:47:56 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 46A5A21F9CFD for <dnsop@ietf.org>; Tue, 18 Jun 2013 01:47:55 -0700 (PDT)
Received: (qmail 24073 invoked from network); 18 Jun 2013 08:47:54 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 18 Jun 2013 08:47:54 -0000
Date: Tue, 18 Jun 2013 10:47:53 +0200 (CEST)
Message-Id: <20130618.104753.74727677.sthaug@nethelp.no>
To: Mark Andrews <marka@isc.org>
From: sthaug@nethelp.no
In-Reply-To: <20130618021929.18AA03600603@drugs.dv.isc.org>
References: <20130618004905.4A72A35FF889@drugs.dv.isc.org> <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com> <20130618021929.18AA03600603@drugs.dv.isc.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: joelja@bogus.com, ek@google.com, dnsop@ietf.org, morrowc.lists@gmail.com
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 08:48:01 -0000

> > >> Unfortunately the former are far too prevalent.  It's undoubtedly too
> > >> late, but unfortunately it might have been better to do the
> > >> fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
> > >> http://tools.ietf.org/html/rfc5405#section-3.2).
> > >
> > > It is *never* too late.  For IPv6 we are still in the very
> > > early days.
> > 
> > but, what about the 'vast install base'  ?
> 
> There isn't a "vast install base" of firewalls (border routers).
> If there was we would have 99% IPv6 traffic instead of 1.6% IPv6
> traffic.

I'm afraid I have to disagree. There is a significant installed base
of border routers doing *stateless* firewall functions for various
reasons. Some of these border routers already have IPv6 turned on,
and many more of them *will* have IPv6 turned on in the near future.

Changes to IPv6 handling that require new software for these routers
is certainly possible - you "only" need to sell such a change to the
vendors. 

Changes that require hardware replacement (and therefore significant
capex) are obviously much harder.

Steinar Haug, AS 2116

From joelja@bogus.com  Tue Jun 18 02:00:21 2013
Return-Path: <joelja@bogus.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B4821F9D98 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 02:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2QXa0tz18G3 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 02:00:20 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7B03721F9D83 for <dnsop@ietf.org>; Tue, 18 Jun 2013 02:00:20 -0700 (PDT)
Received: from joels-MacBook-Air.local ([41.223.119.26]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r5I9074n042530 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 18 Jun 2013 09:00:14 GMT (envelope-from joelja@bogus.com)
Message-ID: <51C02195.4090003@bogus.com>
Date: Tue, 18 Jun 2013 11:00:05 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: sthaug@nethelp.no, Mark Andrews <marka@isc.org>
References: <20130618004905.4A72A35FF889@drugs.dv.isc.org>	<CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com>	<20130618021929.18AA03600603@drugs.dv.isc.org> <20130618.104753.74727677.sthaug@nethelp.no>
In-Reply-To: <20130618.104753.74727677.sthaug@nethelp.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 18 Jun 2013 09:00:17 +0000 (UTC)
Cc: ek@google.com, dnsop@ietf.org, morrowc.lists@gmail.com
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 09:00:21 -0000

On 6/18/13 10:47 AM, sthaug@nethelp.no wrote:
>>>>> Unfortunately the former are far too prevalent.  It's undoubtedly too
>>>>> late, but unfortunately it might have been better to do the
>>>>> fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
>>>>> http://tools.ietf.org/html/rfc5405#section-3.2).
>>>> It is *never* too late.  For IPv6 we are still in the very
>>>> early days.
>>> but, what about the 'vast install base'  ?
>> There isn't a "vast install base" of firewalls (border routers).
>> If there was we would have 99% IPv6 traffic instead of 1.6% IPv6
>> traffic.
So I like the assumption that I should limit edns0 responses to 
something  I don't have to fragment.

My goal as it were was to look at if fragmentation were expected to work 
that I don't really want to expose myself to reciving a 4k response (via 
UDP) because the risk of an amplification attack becomes very large 
indeed. Even if I filter fragments (because I have to or as a product of 
limitations such an attack my be targeted at the infrastructure rather 
than the endpoint that's the notional target.
> I'm afraid I have to disagree. There is a significant installed base
> of border routers doing *stateless* firewall functions for various
> reasons. Some of these border routers already have IPv6 turned on,
> and many more of them *will* have IPv6 turned on in the near future.
>
> Changes to IPv6 handling that require new software for these routers
> is certainly possible - you "only" need to sell such a change to the
> vendors.
>
> Changes that require hardware replacement (and therefore significant
> capex) are obviously much harder.
>
> Steinar Haug, AS 2116
>


From marka@isc.org  Tue Jun 18 08:23:32 2013
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E258A21F9BFA for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 08:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id abzvGCY1Qg78 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 08:23:03 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id B017521F9B86 for <dnsop@ietf.org>; Tue, 18 Jun 2013 08:23:03 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id BDB70C9432; Tue, 18 Jun 2013 15:22:51 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1371568981; bh=HH4bhoUCukDvD1uUH/aysDEzqchrUlSqIW9S4qPGNnI=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=jLx3OsCPgs6LLMWSIGIhE2F9+Dngur6kEJHUGyfRPxUOmX0vpEH2cgpFhE4ltbORh ZxBlqEoar2D1k1GMo7jD8bsv9MsKkm3SCIzJFe6v1B2h4WNvie6i6y+nztauqHTvfP EpUFM2Gf5vwjk7v7xUW1tRTtJECjNVT6wNjVy7iE=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue, 18 Jun 2013 15:22:51 +0000 (UTC) (envelope-from marka@isc.org)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 688D416006D; Tue, 18 Jun 2013 15:23:29 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id n_RQl0AhNSLs; Tue, 18 Jun 2013 15:23:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 7BF4F160069; Tue, 18 Jun 2013 15:23:28 +0000 (UTC)
X-Virus-Scanned: amavisd-new at zmx1.isc.org
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id WAcCgFFIQVK2; Tue, 18 Jun 2013 15:23:28 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) by zmx1.isc.org (Postfix) with ESMTPSA id 1D7AA16004F; Tue, 18 Jun 2013 15:23:28 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 8DA2D36079B0; Wed, 19 Jun 2013 01:22:47 +1000 (EST)
To: joel jaeggli <joelja@bogus.com>
From: Mark Andrews <marka@isc.org>
References: <20130618004905.4A72A35FF889@drugs.dv.isc.org> <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com> <20130618021929.18AA03600603@drugs.dv.isc.org> <20130618.104753.74727677.sthaug@nethelp.no> <51C02195.4090003@bogus.com>
In-reply-to: Your message of "Tue, 18 Jun 2013 11:00:05 +0200." <51C02195.4090003@bogus.com>
Date: Wed, 19 Jun 2013 01:22:47 +1000
Message-Id: <20130618152247.8DA2D36079B0@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ek@google.com, dnsop@ietf.org, morrowc.lists@gmail.com
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 15:23:32 -0000

In message <51C02195.4090003@bogus.com>, joel jaeggli writes:
> On 6/18/13 10:47 AM, sthaug@nethelp.no wrote:
> >>>>> Unfortunately the former are far too prevalent.  It's undoubtedly too
> >>>>> late, but unfortunately it might have been better to do the
> >>>>> fragmentation within the UDP payload (i.e. inside DNS) somehow (c.f.
> >>>>> http://tools.ietf.org/html/rfc5405#section-3.2).
> >>>> It is *never* too late.  For IPv6 we are still in the very
> >>>> early days.
> >>> but, what about the 'vast install base'  ?
> >> There isn't a "vast install base" of firewalls (border routers).
> >> If there was we would have 99% IPv6 traffic instead of 1.6% IPv6
> >> traffic.
> So I like the assumption that I should limit edns0 responses to 
> something  I don't have to fragment.
> 
> My goal as it were was to look at if fragmentation were expected to work 
> that I don't really want to expose myself to reciving a 4k response (via 
> UDP) because the risk of an amplification attack becomes very large 
> indeed. Even if I filter fragments (because I have to or as a product of 
> limitations such an attack my be targeted at the infrastructure rather 
> than the endpoint that's the notional target.

Yet fragmented packets work fine if you don't put a middle box in the
middle that has a conniption when it sees a fragmented packet.

As for being exposed you really can't prevent being exposed.

As for not replying with fragmented packets, that it self causes
operational problems as you move the traffic to TCP which unless
you have taken measures to reduce the sement sizes runs the risk
of PMTUD problems.  Some of the ORG servers limit the UDP size then
don't do PMTUD well which is a real pain if you are behind a tunnel.

> > I'm afraid I have to disagree. There is a significant installed base
> > of border routers doing *stateless* firewall functions for various
> > reasons. Some of these border routers already have IPv6 turned on,
> > and many more of them *will* have IPv6 turned on in the near future.
> >
> > Changes to IPv6 handling that require new software for these routers
> > is certainly possible - you "only" need to sell such a change to the
> > vendors.
> >
> > Changes that require hardware replacement (and therefore significant
> > capex) are obviously much harder.
> >
> > Steinar Haug, AS 2116
> >
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From nweaver@icsi.berkeley.edu  Tue Jun 18 08:28:06 2013
Return-Path: <nweaver@icsi.berkeley.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D6421F9DE8 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 08:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1FdWtOGxcji for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 08:28:00 -0700 (PDT)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) by ietfa.amsl.com (Postfix) with ESMTP id 46F2A21F9CCE for <dnsop@ietf.org>; Tue, 18 Jun 2013 08:28:00 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 351372C4059; Tue, 18 Jun 2013 08:27:54 -0700 (PDT)
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 QdxXLmTFUxuK; Tue, 18 Jun 2013 08:27:53 -0700 (PDT)
Received: from gala.icir.org (gala [192.150.187.49]) (Authenticated sender: nweaver) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id CFBBD2C4003; Tue, 18 Jun 2013 08:27:53 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Nicholas Weaver <nweaver@icsi.berkeley.edu>
In-Reply-To: <20130618152247.8DA2D36079B0@drugs.dv.isc.org>
Date: Tue, 18 Jun 2013 08:27:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2791D081-1D23-4B72-A4E3-211BDDB7C867@icsi.berkeley.edu>
References: <20130618004905.4A72A35FF889@drugs.dv.isc.org> <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com> <20130618021929.18AA03600603@drugs.dv.isc.org> <20130618.104753.74727677.sthaug@nethelp.no> <51C02195.4090003@bogus.com> <20130618152247.8DA2D36079B0@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1508)
Cc: joel jaeggli <joelja@bogus.com>, ek@google.com, dnsop@ietf.org, Nicholas Weaver <nweaver@icsi.berkeley.edu>, morrowc.lists@gmail.com
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 15:28:06 -0000

On Jun 18, 2013, at 8:22 AM, Mark Andrews <marka@isc.org> wrote:
>> My goal as it were was to look at if fragmentation were expected to =
work=20
>> that I don't really want to expose myself to reciving a 4k response =
(via=20
>> UDP) because the risk of an amplification attack becomes very large=20=

>> indeed. Even if I filter fragments (because I have to or as a product =
of=20
>> limitations such an attack my be targeted at the infrastructure =
rather=20
>> than the endpoint that's the notional target.
>=20
> Yet fragmented packets work fine if you don't put a middle box in the
> middle that has a conniption when it sees a fragmented packet.

This is practically every box on IPv6.  Fragments REALLY don't work on =
IPv6.

> As for being exposed you really can't prevent being exposed.
>=20
> As for not replying with fragmented packets, that it self causes
> operational problems as you move the traffic to TCP which unless
> you have taken measures to reduce the sement sizes runs the risk
> of PMTUD problems.  Some of the ORG servers limit the UDP size then
> don't do PMTUD well which is a real pain if you are behind a tunnel.

IPv6 is much better on PMTU discovery than IPv4, and with IPv6, you can =
always just set to use the minimum IPv6 (1200B) MTU and bypass all PMTU =
discovery anyway.


From paul@cypherpunks.ca  Tue Jun 18 11:14:54 2013
Return-Path: <paul@cypherpunks.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC9B511E80F7 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 11:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWki+W-rBmJ7 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 11:14:49 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id B5C3421F99BE for <dnsop@ietf.org>; Tue, 18 Jun 2013 11:14:48 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bZcrj4Gmnz7c1; Tue, 18 Jun 2013 14:14:45 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Z4vN_aW59HtG; Tue, 18 Jun 2013 14:14:44 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Tue, 18 Jun 2013 14:14:43 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id C90D882C56; Tue, 18 Jun 2013 14:14:44 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id B9ED482C54; Tue, 18 Jun 2013 14:14:44 -0400 (EDT)
Date: Tue, 18 Jun 2013 14:14:44 -0400 (EDT)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Wes Hardaker <wjhns1@hardakers.net>
In-Reply-To: <0lzjutsxiw.fsf@wjh.hardakers.net>
Message-ID: <alpine.LFD.2.10.1306181346230.30796@bofh.nohats.ca>
References: <0lzjutsxiw.fsf@wjh.hardakers.net>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] request draft-hardaker-dnsop-csync be adopted as a WG item
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 18:14:55 -0000

On Thu, 13 Jun 2013, Wes Hardaker wrote:

> Subject: [DNSOP] request draft-hardaker-dnsop-csync be adopted as a WG item

> A new version of I-D, draft-hardaker-dnsop-csync-00.txt
> has been successfully submitted by Wes Hardaker and posted to the
> IETF repository.

>   This document specifies how a child zone in the DNS can publish a
>   record that can indicate that a parental agent may copy and process
>   certain records from the child zone.  The existence and change of the
>   record may be monitored by a parental agent to either assist in
>   transferring or automatically transfer data from the child to the
>   parent.

Interesting draft. I'm not yet sure if I prefer this over the CDS draft
or not, or whether this draft should exclude DNSKEY/DS sync. I like that
this draft could potentially solve all parent-child record syncing.

Comments:

2.1.1.1 talks about the serial in the CSYNC record. Why did you prefer a
"soft" link between that and the SOA serial, instead of a "hard" link?
Or why is there is a need for a serial? Shouldn't it directly relate to
the SOA serial? You seem to think one would need a "minimal SOA serial"
to process the CSYNC record, but wouldn't the CSYNC record always be
correctin the _current_ zonefile? I don't see how prepublishing a CSYNC
with a current serial + 1 would be of any benefit.


    The following CSYNC RR shows an example entry for "example.com" that
    indicates the NS, A and AAAA records should be processed for the zone
    using a minimum SOA serial number of 66.

    example.com. 3600 IN CSYNC 73 1 A NS AAAA

Did you mean to write "66" in the RRDATA? Or did I misunderstand
something? Since you later write 0x42, I think you mean 66 here.

2.2.1 talks about fetching the SOA, CSYNC, data and again SOA record. I
think you need to state that you should also aboard if the CSYNC/SOA
serial obtained is lower then a previously processed CSYNC/SOA action.
This will prevent flipflopping when one NS server is out of sync and
presenting old data.

This section should also indicate processing MUST be aborted if there
was no full path of trust from the parent to the child (ie. we need
DNSSEC authenticated data)

2.2.2.1.  The NS type

It should note that parent policy might result in rejecting the proposed
change at the child, for example if only 1 NS record would be left.

2.2.2.4.  The DS type

I kinda lost track here. It's pretty confusing. Also because the "DS
type" would really need to query DNSKEY, as the child is not publishing
DS records. (eg "Queries should be sent to the child zone for all the DS
records" is wrong)

It talks quite a bit about whether to sync (C)DS or DNSKEY. In some
sense, perhaps to facilitate parents that insist on creating the DS from
DNSKEY, and parents that insist on getting a DS RRdata from child, to
split the DS type here into CDS and DNSKEY type, where the latter means
"create DS from DNSKEY". Although that would mean large parts of the CDS
draft would not really be used, if the CSYNC scheduling part is used.

2.3.3. support at parent.

If it is important that we know if the parent supoprts CSYNC and with
what parameters, should be define a RRtype for that which the parent
can publish? I'm hesitant to state in a protocol document that we need
something and suggest adding a human/manual procedure for that, when it
can be avoided.


Paul

From marka@isc.org  Tue Jun 18 15:43:34 2013
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1C0821F9B20 for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 15:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TrEVGM1+UVtY for <dnsop@ietfa.amsl.com>; Tue, 18 Jun 2013 15:43:30 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9FA21F9B19 for <dnsop@ietf.org>; Tue, 18 Jun 2013 15:43:29 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 0CC76C9465; Tue, 18 Jun 2013 22:43:21 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1371595409; bh=sY4ZNZGzFKW6akouMwpSOLITBvDuDurv3NY51tEQsEs=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=cRJaAyezUFKy8clNpd/wHVoHxWFyqjkffD+8XY04/6Mi0Vkkyzs9/gIj+8FbXCyKl VsOOrjsxWPxQ63CIu4OUrEG8X9o4IX+ZITCu1Yjx7GkeZwNmh61CX7Qv53IjArRvDk 2inidszF++G79rlaiSnzxI1D+n1hi920UnQzf+XQ=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue, 18 Jun 2013 22:43:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0896C16004F; Tue, 18 Jun 2013 22:44:00 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id vR-u-tc0J4tn; Tue, 18 Jun 2013 22:43:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 6282716006D; Tue, 18 Jun 2013 22:43:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at zmx1.isc.org
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id WG3T21Cl7Iq0; Tue, 18 Jun 2013 22:43:59 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) by zmx1.isc.org (Postfix) with ESMTPSA id AB94816004F; Tue, 18 Jun 2013 22:43:58 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id B94A13609A85; Wed, 19 Jun 2013 08:43:15 +1000 (EST)
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
From: Mark Andrews <marka@isc.org>
References: <20130618004905.4A72A35FF889@drugs.dv.isc.org> <CAL9jLabeK2Eh2jEJmm2RjRugJ6CTqtfZOJYhkrp7HZJTEFqnFw@mail.gmail.com> <20130618021929.18AA03600603@drugs.dv.isc.org> <20130618.104753.74727677.sthaug@nethelp.no> <51C02195.4090003@bogus.com> <20130618152247.8DA2D36079B0@drugs.dv.isc.org> <2791D081-1D23-4B72-A4E3-211BDDB7C867@icsi.berkeley.edu>
In-reply-to: Your message of "Tue, 18 Jun 2013 08:27:53 -0700." <2791D081-1D23-4B72-A4E3-211BDDB7C867@icsi.berkeley.edu>
Date: Wed, 19 Jun 2013 08:43:15 +1000
Message-Id: <20130618224315.B94A13609A85@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: joel jaeggli <joelja@bogus.com>, ek@google.com, dnsop@ietf.org, morrowc.lists@gmail.com
Subject: Re: [DNSOP] BIG RRSETS EDNS0 and ipv6 framentation.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 22:43:35 -0000

In message <2791D081-1D23-4B72-A4E3-211BDDB7C867@icsi.berkeley.edu>, Nicholas Weaver writes:
>
> On Jun 18, 2013, at 8:22 AM, Mark Andrews <marka@isc.org> wrote:
> >> My goal as it were was to look at if fragmentation were expected to
> work
> >> that I don't really want to expose myself to reciving a 4k response
> (via
> >> UDP) because the risk of an amplification attack becomes very large
> >> indeed. Even if I filter fragments (because I have to or as a product
> of
> >> limitations such an attack my be targeted at the infrastructure rather
> >> than the endpoint that's the notional target.
> >
> > Yet fragmented packets work fine if you don't put a middle box in the
> > middle that has a conniption when it sees a fragmented packet.
>
> This is practically every box on IPv6.  Fragments REALLY don't work on
> IPv6.

Which is not correct given the successful IPv6 reassembly counters
on my IPv6 boxes which are recursive servers.  Yes there is a IPv6
firewall in front of and on these boxes.

Hop-by-hop also cross the Internet fine.

Remember most of the firewalls are dropping fragmented UDP because
they can't identify if the fragment is part of a packet they are
allowing through.  Give the firewalls a way to identify that a UDP
fragments is part of a such a packet and they will be allowed through
/ reassembled and allowed through if dpi is being done and dpi is
often turned off on firewalls for DNS packets even when it defaults
to on.

6 to 8 extra octets per fragment would allow this.

Assuming this is the only hop-by-hop option and the fragment header
is next one would add the following and the next header option in
the IPv6 header would be zero.

	<44><0><tbd,4,src-port,dst-port>

and tbd would start with 000 <skip if unknown=00> and <unchanging=0>.

Mark

ip6:
	1883580 total packets received
	2604 fragments received
	0 fragments dropped (dup or out of space)
	68 fragments dropped after timeout
	0 fragments that exceeded limit
	1266 packets reassembled ok
	976983 packets for this host
	342821 packets not forwardable
	1643642 packets sent from this host
	32050 output packets discarded due to no route
	254 output datagrams fragmented
	508 fragments created
	12 packets that violated scope rules
	342753 multicast packets which we don't join
	Input histogram:
		hop by hop: 1055
		TCP: 934449
		UDP: 47301
		fragment: 2604
		ICMP6: 898170
	Mbuf statistics:
		319754 one mbuf
		two or more mbuf:
			lo0= 264312
		1299514 one ext mbuf

ip6:
	805638 total packets received
	831 fragments received
	0 fragments dropped (dup or out of space)
	11 fragments dropped after timeout
	0 fragments that exceeded limit
	410 packets reassembled ok
	380419 packets for this host
	409513 packets forwarded
	4502 packets not forwardable
	389337 packets sent from this host
	4485 multicast packets which we don't join
	Input histogram:
		hop by hop: 271
		TCP: 748570
		UDP: 12234
		fragment: 1060
		ICMP6: 43503
	Mbuf statistics:
		575 one mbuf
		805063 one ext mbuf
	source addresses on an outgoing I/F
		159 node-locals
		222 link-locals
		30757 globals
	source addresses on a non-outgoing I/F
		2 globals
	source addresses of same scope
		159 node-locals
		222 link-locals
		30759 globals
	568305 forward cache hit
	232283 forward cache miss

 
> > As for being exposed you really can't prevent being exposed.
> >
> > As for not replying with fragmented packets, that it self causes
> > operational problems as you move the traffic to TCP which unless
> > you have taken measures to reduce the sement sizes runs the risk
> > of PMTUD problems.  Some of the ORG servers limit the UDP size then
> > don't do PMTUD well which is a real pain if you are behind a tunnel.
>
> IPv6 is much better on PMTU discovery than IPv4, and with IPv6, you can
> always just set to use the minimum IPv6 (1200B) MTU and bypass all PMTU
> discovery anyway.
>

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

From wjhns1@hardakers.net  Wed Jun 19 16:00:52 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F208F21F9C53 for <dnsop@ietfa.amsl.com>; Wed, 19 Jun 2013 16:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jUibZh8FJ74f for <dnsop@ietfa.amsl.com>; Wed, 19 Jun 2013 16:00:46 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id CF2D021F9FAD for <dnsop@ietf.org>; Wed, 19 Jun 2013 16:00:46 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:c069:c3f8:2794:4bba]) by mail.hardakers.net (Postfix) with ESMTPSA id 2EC3622A61; Wed, 19 Jun 2013 16:00:43 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Wouters <paul@cypherpunks.ca>
References: <0lzjutsxiw.fsf@wjh.hardakers.net> <alpine.LFD.2.10.1306181346230.30796@bofh.nohats.ca>
Date: Wed, 19 Jun 2013 16:00:43 -0700
In-Reply-To: <alpine.LFD.2.10.1306181346230.30796@bofh.nohats.ca> (Paul Wouters's message of "Tue, 18 Jun 2013 14:14:44 -0400 (EDT)")
Message-ID: <0la9mlu2n8.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: dnsop <dnsop@ietf.org>, Wes Hardaker <wjhns1@hardakers.net>
Subject: Re: [DNSOP] request draft-hardaker-dnsop-csync be adopted as a WG item
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 23:00:52 -0000

Paul Wouters <paul@cypherpunks.ca> writes:

> Interesting draft. I'm not yet sure if I prefer this over the CDS draft
> or not, or whether this draft should exclude DNSKEY/DS sync. I like that
> this draft could potentially solve all parent-child record syncing.

Thanks; it's the latter problem that I was actually trying to solve.
The DS additions, as mentioned in the draft, were added late just as a
"food for thought" experiment.  Personally, I agree more with the CDS
draft that a CDS record would need to be signed by the SEP-bit key, or
else the security model of the SEP-bit is greatly changed.  But, I
understand that others have argued against this saying that there is
really very few zones where the keys are protected differently or
"owned" differently.  So, if that's the case then CSYNC should be a
suitable mechanism?  Hence, the thought experiment.
 
I'll get back to you about your other comments, but I appreciate
(already) you writing them up.  Thank you!
-- 
Wes Hardaker
Parsons

From warren@kumari.net  Fri Jun 21 08:25:33 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B6221E812B for <dnsop@ietfa.amsl.com>; Fri, 21 Jun 2013 08:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y-czuSvpxpK2 for <dnsop@ietfa.amsl.com>; Fri, 21 Jun 2013 08:25:28 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9E221F9DB5 for <dnsop@ietf.org>; Fri, 21 Jun 2013 08:25:28 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 4BD1B1B40A6A; Fri, 21 Jun 2013 11:25:27 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
Date: Fri, 21 Jun 2013 11:25:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3540A275-BDE9-4577-BD5E-7E0D0B9B894D@kumari.net>
References: <20130621000118.22228.76098.idtracker@ietfa.amsl.com>
To: IETF DNSOP WG <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-omniscient-as112-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 15:25:33 -0000

Hi there all,

We have incorporated consensus from the Orlando meeting (and ML =
discussions). We have also fleshed this out with e batter overview =
section, an explanation of why DNSSEC doesn't happen with AS112, etc.

We have requested that the DNSOP chairs adopt this version.

Things that requite more discussions:
1: Is DNAME a viable alternative?
There are pros and cons here -- a better understanding of DNAME support, =
it may be simpler to just delegate to AS112, etc.
2: Metazones - having a generic DNS sinkhole may be useful for all sorts =
of things.
3:  Delegating things other than PTR -- we have discussed this in person =
and it is mentioned in the draft, but perhaps we need more text on using =
Omniscient AS112 for blackholing things like .belkin / malware..

W


Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-wkumari-dnsop-omniscient-as112-03.txt
> Date: June 20, 2013 8:01:18 PM EDT
> To: William F. Maton Sotomayor <wfms@ryouko.imsb.nrc.ca>, Ray Bellis =
<ray.bellis@nominet.org.uk>, William F. M Sotomayor =
<wfms@ryouko.imsb.nrc.ca>, Joe Abley <joe.abley@icann.org>, Warren =
Kumari <warren@kumari.net>
>=20
>=20
> A new version of I-D, draft-wkumari-dnsop-omniscient-as112-03.txt
> has been successfully submitted by Warren Kumari and posted to the
> IETF repository.
>=20
> Filename:	 draft-wkumari-dnsop-omniscient-as112
> Revision:	 03
> Title:		 Omniscient AS112 Servers
> Creation date:	 2013-06-21
> Group:		 Individual Submission
> Number of pages: 14
> URL:             =
http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-omniscient-as112-0=
3.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-wkumari-dnsop-omniscient-as112
> Htmlized:        =
http://tools.ietf.org/html/draft-wkumari-dnsop-omniscient-as112-03
> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-wkumari-dnsop-omniscient-as112-03=

>=20
> Abstract:
>   The AS112 Project loosely coordinates Domain Name System (DNS)
>   servers to which DNS zones corresponding to private use addresses =
are
>   delegated.  Queries for names within those zones have no useful
>   responses in a global context.  The purpose of this project is to
>   reduce the load of such junk queries on the authoritative name
>   servers that would otherwise receive them, and instead direct the
>   load to name servers operated within the AS112 project.
>=20
>   Due to the loosely-coordinated nature of the project, adding and
>   dropping zones from the AS112 servers is difficult.  This document
>   proposes a mechanism by which AS112 name servers could answer
>   authoritatively for all possible zones.  This eliminates the =
add/drop
>   problem, changing it to a matter of delegation within the DNS and
>   requiring no operational changes on the servers themselves.
>=20
>   This document updates RFC 6304.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20

--
It's a mistake trying to cheer up camels. You might as well drop =
meringues into a black hole. -- Terry Prachett



From wjhns1@hardakers.net  Fri Jun 21 14:58:20 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD26A21F9E53 for <dnsop@ietfa.amsl.com>; Fri, 21 Jun 2013 14:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QzdmE+KiDDf for <dnsop@ietfa.amsl.com>; Fri, 21 Jun 2013 14:58:13 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4327F21F9E4D for <dnsop@ietf.org>; Fri, 21 Jun 2013 14:58:13 -0700 (PDT)
Received: from localhost (50-1-19-94.dsl.dynamic.sonic.net [50.1.19.94]) by mail.hardakers.net (Postfix) with ESMTPSA id E6658244D3; Fri, 21 Jun 2013 14:58:07 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Wouters <paul@cypherpunks.ca>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca>
Date: Fri, 21 Jun 2013 14:58:02 -0700
In-Reply-To: <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> (Paul Wouters's message of "Mon, 17 Jun 2013 14:28:12 -0400 (EDT)")
Message-ID: <0lsj0b2kk5.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 21:58:21 -0000

Paul Wouters <paul@cypherpunks.ca> writes:

> I am in favour of adopting this draft as a WG item.

Ditto.

> I don't think the CDS record should be able to cause a child domain to
> go from secure to insecure, or from insecure to secure. That
> (infrequent) change should have an additional authentication, eg via EPP
> or otherwise)

Ditto.  I think the goal of any of the automatic update techniques
should be to make the routine easy but it shouldn't be a goal to handle
the infrequent, and challenging cases.  (infrequent and easy is fine).

Unless we can show a clear, secured, path for some transition I don't
think it's worth solving.
-- 
Wes Hardaker
Parsons

From ondrej.sury@nic.cz  Mon Jun 24 00:39:42 2013
Return-Path: <ondrej.sury@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0DB621E80CA; Mon, 24 Jun 2013 00:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.702
X-Spam-Level: **
X-Spam-Status: No, score=2.702 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, J_CHICKENPOX_23=0.6, MIME_8BIT_HEADER=0.3, SUSPICIOUS_RECIPS=2.912]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MblZJgRPX5Hz; Mon, 24 Jun 2013 00:39:41 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) by ietfa.amsl.com (Postfix) with ESMTP id 72D8021E80C9; Mon, 24 Jun 2013 00:39:40 -0700 (PDT)
Received: from [192.168.1.36] (unknown [89.24.189.186]) by mail.nic.cz (Postfix) with ESMTPSA id 623E313F7AF; Mon, 24 Jun 2013 09:39:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1372059574; bh=BpUssv6g95iPHHznPclx/BqBMGWITtVN3u3gGJUcUYM=; h=From:Content-Type:Reply-To:Subject:Date:Message-Id:To: Mime-Version; b=Z6bUQsyTtO2Lt2WMPWCRVXyY6VYFuUYKEkL31w5JdbP7qstwAhnwLk24i1+z4XUCY n4CTTVtqQtQaXV/FDI+6pVslW627SUxpm/HL1OC+x9fRihh12HPKjbI+w7djEGT/Py 1FSIUu94+b/MP46LyYACNLpD0i5bocbI27ODHiFc=
From: =?utf-8?Q?Ond=C5=99ej_Sur=C3=BD?= <ondrej.sury@nic.cz>
Content-Type: multipart/signed; boundary="Apple-Mail=_15F61B90-7C4F-4CB2-ACFA-992D7C14F3B4"; protocol="application/pkcs7-signature"; micalg=sha1
Date: Mon, 24 Jun 2013 09:37:46 +0200
Message-Id: <2135CB7E-E2CC-41A1-B733-5225745F79FD@nic.cz>
To: dnssec-deployment@dnssec-deployment.org, dns-operations@lists.dns-oarc.net, knot-dns-users@lists.nic.cz, IETF DNSOP WG <dnsop@ietf.org>, dnsext@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1764\))
X-Mailer: Apple Mail (2.1764)
X-Virus-Scanned: clamav-milter 0.97.8 at mail
X-Virus-Status: Clean
Subject: [DNSOP] DNSSEC implementation survey
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: knot-dns-users@lists.nic.cz
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 Jun 2013 07:39:42 -0000

--Apple-Mail=_15F61B90-7C4F-4CB2-ACFA-992D7C14F3B4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

[sorry for cross-post, please don't cross-post when replying]

Hi,

we are currently implementing DNSSEC in Knot DNS and we would like to =
gather opinions on this topic.  I think we have all have more experience =
of DNSSEC deployment now and it would be very valuable for us to gather =
that experience and forge an implementation that would be liked by the =
users.

Could you please spare a few minutes and fill a little survey of ours on =
this topic?

=
https://docs.google.com/forms/d/1gS-Z1NAL78oFOU51HR6jmg-ZkAevU2CrvCHQgrNnX=
LU/viewform

If you don't want to give your answers to NSA :), you can reply to this =
email (the Reply-To is set to knot-dns-users@lists.nic.cz), or just send =
the feedback back to me.

Thank you very much,
Ondrej
--
Ond=C5=99ej Sur=C3=BD -- Chief Science Officer
-------------------------------------------
CZ.NIC, z.s.p.o.    --    Laborato=C5=99e CZ.NIC
Americka 23, 120 00 Praha 2, Czech Republic
mailto:ondrej.sury@nic.cz    http://nic.cz/
tel:+420.222745110       fax:+420.222745112
-------------------------------------------


--Apple-Mail=_15F61B90-7C4F-4CB2-ACFA-992D7C14F3B4
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMKTCCBgYw
ggTuoAMCAQICAQIwDQYJKoZIhvcNAQEFBQAwga8xCzAJBgNVBAYTAk5MMSAwHgYDVQQKExdUcnVz
dGVkIEludHJvZHVjZXIgKFRJKTEgMB4GA1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxMzAx
BgNVBAMTKlRydXN0ZWQgSW50cm9kdWNlciAoVEkpIFRvcGxldmVsIENBIC0gRzAwMTEnMCUGCSqG
SIb3DQEJARYYY2FAdHJ1c3RlZC1pbnRyb2R1Y2VyLm5sMB4XDTA0MTIwNzEwMzYxN1oXDTMwMTIw
NjAwMDAwMFowga0xCzAJBgNVBAYTAk5MMSAwHgYDVQQKExdUcnVzdGVkIEludHJvZHVjZXIgKFRJ
KTEgMB4GA1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxMTAvBgNVBAMTKFRydXN0ZWQgSW50
cm9kdWNlciAoVEkpIENsaWVudCBDQSAtIEcwMDExJzAlBgkqhkiG9w0BCQEWGGNhQHRydXN0ZWQt
aW50cm9kdWNlci5ubDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOKQxMR3KDUpfJBz
AhY2BPCByKo9SMp/V0RIboLBD6vO0miSYO9FmP3Q07OKPYR5WdlQyrpKqB1zl0SRz2cDjnYkzvDF
vK5kvMvlTYeQlHypQlvhkTsYWD4ZZxxEhAYBb1s7cYaIahLw6H/RZz+kyWTOc9TncPBvBWIQ1Ypo
S+uQqpopH8s5ebtB/17SbUty5yXiHoaPh/ScdMKqxbyJiL0YRM6SU4YX4HVZ5YGS9aWuiUSiA0YF
8dCR56nErx67wgq8O1GtsSKKOf/ueUxSmrqwgQNlfM9Or5O8kb61s1O2iACHtixoV3ENanylBafU
mRYpNo5tSZsElGfntMoGBy8CAwEAAaOCAiswggInMB0GA1UdDgQWBBSeX93lU8ExaSlN1ZaXxfOP
h2iHTjCB3AYDVR0jBIHUMIHRgBRdbehwJx/8iwlxnguJECc7MUXvoqGBtaSBsjCBrzELMAkGA1UE
BhMCTkwxIDAeBgNVBAoTF1RydXN0ZWQgSW50cm9kdWNlciAoVEkpMSAwHgYDVQQLExdDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eTEzMDEGA1UEAxMqVHJ1c3RlZCBJbnRyb2R1Y2VyIChUSSkgVG9wbGV2
ZWwgQ0EgLSBHMDAxMScwJQYJKoZIhvcNAQkBFhhjYUB0cnVzdGVkLWludHJvZHVjZXIubmyCAQAw
DwYDVR0TAQH/BAUwAwEB/zAjBgNVHRIEHDAagRhjYUB0cnVzdGVkLWludHJvZHVjZXIubmwwgasG
A1UdHwSBozCBoDBOoEygSoZIaHR0cDovL2NybDEudHJ1c3RlZC1pbnRyb2R1Y2VyLm5sL2NhL3g1
MDkvZzEvZGF0YS9jcmxzL2NybC1yb290LWNhLTEuY3JsME6gTKBKhkhodHRwOi8vY3JsMi50cnVz
dGVkLWludHJvZHVjZXIubmwvY2EveDUwOS9nMS9kYXRhL2NybHMvY3JsLXJvb3QtY2EtMS5jcmww
IwYDVR0RBBwwGoEYY2FAdHJ1c3RlZC1pbnRyb2R1Y2VyLm5sMAsGA1UdDwQEAwIBBjARBglghkgB
hvhCAQEEBAMCAAcwDQYJKoZIhvcNAQEFBQADggEBAI1sC2l8st3ElC74az6gH7tGXSiS7jicpHeI
10A3KY+7OEPT7BAJDpjMXxSvAwU1vBDFfwEAXGj42xAPB6cynOTDn0OiFpYGvi3EZV3khXYkGPLs
fxZttUyDKqhXcWYy4nnI3fBxqCgLboJFw6OO/SVj5qQdXMZ7VhyFBWJMQkVOnlt6i3xFkG3O5LMI
BDmdL5bZPEe8b6bJkMr+rUYEvorPJmV+CkiewYMaruCbdhwRkpkhXB3qLwB2ppnKxSinAU4f9Rcp
p73h8iDVQ9389iliUKomVQqj9NJv2G6SyJdDQdN2vrldLszNpw6t+zIzCjpgQ//kem5BJ1k4YG3L
CpAwggYbMIIFA6ADAgECAgIGSDANBgkqhkiG9w0BAQUFADCBrTELMAkGA1UEBhMCTkwxIDAeBgNV
BAoTF1RydXN0ZWQgSW50cm9kdWNlciAoVEkpMSAwHgYDVQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhv
cml0eTExMC8GA1UEAxMoVHJ1c3RlZCBJbnRyb2R1Y2VyIChUSSkgQ2xpZW50IENBIC0gRzAwMTEn
MCUGCSqGSIb3DQEJARYYY2FAdHJ1c3RlZC1pbnRyb2R1Y2VyLm5sMB4XDTEyMDgwMTA3NTEyNloX
DTE0MDgwMTA3NTEyNlowejELMAkGA1UEBhMCTkwxGzAZBgNVBAoTElRydXN0ZWQgSW50cm9kdWNl
cjEVMBMGA1UECxMMQ1ouTklDLUNTSVJUMRQwEgYDVQQDEwtPbmRyZWogU3VyeTEhMB8GCSqGSIb3
DQEJARYSb25kcmVqLnN1cnlAbmljLmN6MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
xlmN+hSg6RxWm1X6QOI3OXHSAqhRzWGb8ismR2+3LGDS640luS8x4VdWo490Ceqz+BZvMhQJwfny
9mb0IejFpx7kBOM7k2rMfOYUXa/pq07ysWEI8bXDcXRBf2ZcG0B/gajLPFA9MADlCWHSf7cNZF6S
XnIHwTn5DowxpbF403NqLWFnTM08wTJkFgGB7WZAtE6KoSigztI39NrtKRsnosZoBMNZS/JG1CLt
VdZPvkHVuiVQWEGYgswBEMGXoR7jtzVNhHr2F1atoBICJVGWFNA8fHvQRLAcXWJTXhKxb2uSq9Yp
kKaZPZ6rrp88qtemvwVnQKE9r3/iPFeTARY7AQIDAQABo4ICdTCCAnEwDAYDVR0TAQH/BAIwADAd
BgNVHQ4EFgQUgizwG0IeMZQlCSduLVeM1zDBdUEwgdwGA1UdIwSB1DCB0YAUnl/d5VPBMWkpTdWW
l8Xzj4doh06hgbWkgbIwga8xCzAJBgNVBAYTAk5MMSAwHgYDVQQKExdUcnVzdGVkIEludHJvZHVj
ZXIgKFRJKTEgMB4GA1UECxMXQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxMzAxBgNVBAMTKlRydXN0
ZWQgSW50cm9kdWNlciAoVEkpIFRvcGxldmVsIENBIC0gRzAwMTEnMCUGCSqGSIb3DQEJARYYY2FA
dHJ1c3RlZC1pbnRyb2R1Y2VyLm5sggECMCMGA1UdEgQcMBqBGGNhQHRydXN0ZWQtaW50cm9kdWNl
ci5ubDAdBgNVHREEFjAUgRJvbmRyZWouc3VyeUBuaWMuY3owCwYDVR0PBAQDAgSwMCcGA1UdJQQg
MB4GCCsGAQUFBwMCBggrBgEFBQcDAwYIKwYBBQUHAwQwEQYJYIZIAYb4QgEBBAQDAgSwMIHVBgNV
HR8Egc0wgcowY6BhoF+GXWh0dHA6Ly9jcmwxLnRydXN0ZWQtaW50cm9kdWNlci5ubC9jYS94NTA5
L2cxL2NhLXNzbC1jbGllbnQvZzEvZGF0YS9jcmxzL2NybC1jbGllbnQtY2EtMS0xLmNybDBjoGGg
X4ZdaHR0cDovL2NybDIudHJ1c3RlZC1pbnRyb2R1Y2VyLm5sL2NhL3g1MDkvZzEvY2Etc3NsLWNs
aWVudC9nMS9kYXRhL2NybHMvY3JsLWNsaWVudC1jYS0xLTEuY3JsMA0GCSqGSIb3DQEBBQUAA4IB
AQAZP/dznHW3BWajBVQ3fTaDsx/3csUE6+jX83r1dgzYjUOmapOzXQVZ2/VTwZTzJSsD7rDgzUN6
sk6YWmUJOwqoEcPasYG9zt9e+bpwc/PURjSowb+WjEE2e4L47x3mPgL0dtlGj4guhRaj247K9N1f
grvlyX0h/IL9JO4CN0I5lAuOaZ3Yfl0euHpHLlXZ9czxkc6dCbtGSZwr3RrltNmMjhp0O3D51fDd
D6mG1vvOEV9Kj1JfSE2cQI5j3GpMlNleZA6noZ93drs2G9/D7WP4uVLCtJfGmG6PJsy4+qN46qXu
ekJR/8WH1aNcH0Ya+JsYrwIFPwL4Cr+JXrbFqUOFMYIDzzCCA8sCAQEwgbQwga0xCzAJBgNVBAYT
Ak5MMSAwHgYDVQQKExdUcnVzdGVkIEludHJvZHVjZXIgKFRJKTEgMB4GA1UECxMXQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkxMTAvBgNVBAMTKFRydXN0ZWQgSW50cm9kdWNlciAoVEkpIENsaWVudCBD
QSAtIEcwMDExJzAlBgkqhkiG9w0BCQEWGGNhQHRydXN0ZWQtaW50cm9kdWNlci5ubAICBkgwCQYF
Kw4DAhoFAKCCAe8wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMw
NjI0MDczNzUzWjAjBgkqhkiG9w0BCQQxFgQUn/d0drgry4Sxa5XBwnjTBKfmc5IwgcUGCSsGAQQB
gjcQBDGBtzCBtDCBrTELMAkGA1UEBhMCTkwxIDAeBgNVBAoTF1RydXN0ZWQgSW50cm9kdWNlciAo
VEkpMSAwHgYDVQQLExdDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTExMC8GA1UEAxMoVHJ1c3RlZCBJ
bnRyb2R1Y2VyIChUSSkgQ2xpZW50IENBIC0gRzAwMTEnMCUGCSqGSIb3DQEJARYYY2FAdHJ1c3Rl
ZC1pbnRyb2R1Y2VyLm5sAgIGSDCBxwYLKoZIhvcNAQkQAgsxgbeggbQwga0xCzAJBgNVBAYTAk5M
MSAwHgYDVQQKExdUcnVzdGVkIEludHJvZHVjZXIgKFRJKTEgMB4GA1UECxMXQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkxMTAvBgNVBAMTKFRydXN0ZWQgSW50cm9kdWNlciAoVEkpIENsaWVudCBDQSAt
IEcwMDExJzAlBgkqhkiG9w0BCQEWGGNhQHRydXN0ZWQtaW50cm9kdWNlci5ubAICBkgwDQYJKoZI
hvcNAQEBBQAEggEAcrI2LaAYRRpdmvTfw4TsQ6E6TxBXopBmWw8edWqd/9Ux2Bcx32v3VE74MNYv
vzpNFKgqx0LKpDyHz7ivJG6IvuxR+XUSvoiBK3V3we24K79bMqdI26oe7wdnP1cAy7KVOD6Oea0o
wk1+jLMZIwB0SM8Omon3bMVsgh9nZ63Zj3CpIE6HNKvFmFjpgaSDWPknAq1dKz2r4421z4eQW5BI
iL/NzI+s8ETeF8lC7SXZdPOFx1L9k8GrpZLn+Jnabd/9t6cNmVWkbAG6JsdfKlvU431bJtT/i8Ly
aPRQtHeDv0x060UEHPmNZKUv78MDIO6kQz/L8z+NPtJRjtZ/tJ2tNQAAAAAAAA==

--Apple-Mail=_15F61B90-7C4F-4CB2-ACFA-992D7C14F3B4--

From jabley@hopcount.ca  Mon Jun 24 09:32:29 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4B5411E815C for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 09:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OI+Ucij8UG2 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 09:32:29 -0700 (PDT)
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 E284511E8150 for <dnsop@ietf.org>; Mon, 24 Jun 2013 09:32:28 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id 10so25289496ied.14 for <dnsop@ietf.org>; Mon, 24 Jun 2013 09:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Rmg9f8V1PvvH0KAqg6Eco/E3ZZiLHO+dcBuGZRKEpbw=; b=l6HkyZpYvITJs09mKEIkHPlpfcBeCRiuYCbtAjGP/GyvyerJweZ3Fx5gg2M2aIVYrH IIxnLn2OBygG0J5TYn+VY/vMDZ94HaQq0wrI7Jm4z3nCA1WsRk4PQZO+8VUTKSeNwRD9 GmIkLZPQ0MQ04K8J3xRnRs6p5L4P4H0BwvtDk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=Rmg9f8V1PvvH0KAqg6Eco/E3ZZiLHO+dcBuGZRKEpbw=; b=INuQw/zUbYOYp7+CtIzrr3BiJaPQCSspu60LvbYJiWa5m8HCue0eFZ9TtjXhMX8PyI nAmPZNIv4cgJNb1TNRO24aRss4vamJGTbLH8jcdGvOajXOSpi/LLyU6R3hwURQQmP9qE lgA9jQqwKnfgj8K+6gBubtADv15pK2gu5DfV/lcd8Qba8j4w2EjgoRIJfIroxFxgKKmx 8ROStj2E8MuIasYcNJk1CVzD5kh7gCLIvmnAg9GMTwRRg22crKVCZXWANjuk0iP6eQa4 qWNR/c9Icn/D0GoxqF0eeRWG49938TPRr1vTwxQL7pdnKOXlsIQ9gcQxmYxzuV3ZR5vR C1+w==
X-Received: by 10.42.29.2 with SMTP id p2mr8449122icc.70.1372091548433; Mon, 24 Jun 2013 09:32:28 -0700 (PDT)
Received: from [199.212.90.42] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id yt6sm779656igb.2.2013.06.24.09.32.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 09:32:27 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Joe Abley <jabley@hopcount.ca>
Date: Mon, 24 Jun 2013 12:32:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca>
References: <7DD9876B-B326-4553-AA4C-1E23E2D86F8C@icann.org>
To: IETF DNSOP WG <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQnNQWjGEP/rcqMZ06TNU+vTNmUXhF5NktGpVCbWVIf1KfV04LrEbaq8KrPVd6HxWZVGzxrE
Cc: Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-anycast-mapping-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:32:29 -0000

Hi all,

You may recall a little draft I threw together some time back to =
document facilities available to identify anycast nodes of the L-Root =
service.

There was sufficient enthusiasm expressed during earlier iterations that =
I proposed to the independent stream editor that this document be moved =
forward in that direction. Nevil graciously agreed, and this -02 is the =
result of a review solicited by Nevil from Paul Hoffman (thanks, Paul!)

Nevil needs additional reviewers. If you have a spare ten minutes to =
read through this revision and send feedback to Nevil (or to this list, =
and I'll forward) that'd be great.

Thanks,


Joe

Begin forwarded message:

> From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> Subject: New Version Notification for =
draft-jabley-dnsop-anycast-mapping-02.txt
> Date: 24 June 2013 12:22:42 EDT
> To: Joe Abley <joe.abley@icann.org>
>=20
>=20
> A new version of I-D, draft-jabley-dnsop-anycast-mapping-02.txt
> has been successfully submitted by Joe Abley and posted to the
> IETF repository.
>=20
> Filename:	 draft-jabley-dnsop-anycast-mapping
> Revision:	 02
> Title:		 A Summary of Various Mechanisms Deployed at =
L-Root for the Identification of Anycast Nodes
> Creation date:	 2013-06-24
> Group:		 Individual Submission
> Number of pages: 18
> URL:             =
http://www.ietf.org/internet-drafts/draft-jabley-dnsop-anycast-mapping-02.=
txt
> Status:          =
http://datatracker.ietf.org/doc/draft-jabley-dnsop-anycast-mapping
> Htmlized:        =
http://tools.ietf.org/html/draft-jabley-dnsop-anycast-mapping-02
> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-jabley-dnsop-anycast-mapping-02
>=20
> Abstract:
>  Anycast is a deployment technique commonly employed for
>  authoritative-only servers in the Domain Name System (DNS).  L-Root,
>  one of the thirteen root servers, is deployed in this fashion.
>=20
>  Various techniques have been used to map deployed anycast
>  infrastructure externally, i.e. without reference to inside knowledge
>  about where and how such infrastructure has been deployed.
>  Motivations for performing such measurement exercises include
>  operational troubleshooting and infrastructure risk assessment.  In
>  the specific case of L-Root, the ability to measure and map anycast
>  infrastructure using the techniques mentioned in this document is
>  provided for reasons of operational transparency.
>=20
>  This document describes all facilities deployed at L-Root to
>  facilitate mapping of its infrastructure and serves as documentation
>  for L-Root as a measurable service.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20



From paul.hoffman@vpnc.org  Mon Jun 24 09:56:30 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6FD11E816F for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 09:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.923
X-Spam-Level: 
X-Spam-Status: No, score=-101.923 tagged_above=-999 required=5 tests=[AWL=-0.524, BAYES_00=-2.599, J_CHICKENPOX_26=0.6, J_CHICKENPOX_84=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyGdwPWbYqqn for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 09:56:29 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0E41221E814A for <dnsop@ietf.org>; Mon, 24 Jun 2013 09:56:27 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5OGuNUu071156 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 24 Jun 2013 09:56:24 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca>
Date: Mon, 24 Jun 2013 09:56:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C7CD4F8-F747-4C0A-869A-87EBB2BF9D7F@vpnc.org>
References: <7DD9876B-B326-4553-AA4C-1E23E2D86F8C@icann.org> <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1508)
Cc: IETF DNSOP WG <dnsop@ietf.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: [DNSOP] New Version Notification for draft-jabley-dnsop-anycast-mapping-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:56:30 -0000

+1 to getting others to review this. Takes a few minutes, helps the RFC =
process

In looking at the diffs, I still have the question I had earlier about =
NSID. I give the following command three times quickly:
   dig -4 @L.ROOT-SERVERS.NET . SOA +nsid +norec +noall +comments
I get three different answers (lax16..., lax09..., lax13...).

This is similar to the variance I see when doing
   dig -4 @L.ROOT-SERVERS.NET HOSTNAME.BIND CH TXT +short
and
   dig -4 @L.ROOT-SERVERS.NET ID.SERVER CH TXT +short
However:
   dig IDENTITY.L.ROOT-SERVERS.ORG TXT +short
gives me the same answer each time I give it.

So, I'm still confused about the paragraph just before section 4.1.

--Paul Hoffman=

From jabley@hopcount.ca  Mon Jun 24 10:15:54 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0EF021E811E for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 10:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.399
X-Spam-Level: 
X-Spam-Status: No, score=-101.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_26=0.6, J_CHICKENPOX_84=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8txoU4fWHB5S for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 10:15:53 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 78F2421E811C for <dnsop@ietf.org>; Mon, 24 Jun 2013 10:15:53 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id aq17so25457106iec.36 for <dnsop@ietf.org>; Mon, 24 Jun 2013 10:15:53 -0700 (PDT)
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:x-mailer; bh=KG/7vnlzPCVxll8lEJQQMx/YgiE5k8JPievpVjeWkHI=; b=KuPDqsTbpNKa/2RTQ9f+/NfGBzw6LcBxotyej+8raZfwmD6mlgozBksnkVYgOOi0+X WY9+xXkjJkPTSSGy418j8Wj/04CpFKBmlu8XsgNk4vuVtz7iGE45Y8kjXxg+UGkTsK96 M/ZPRvGKp2dzlnAiZ/kX/nCzK3rOkrn0Aa+mY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=KG/7vnlzPCVxll8lEJQQMx/YgiE5k8JPievpVjeWkHI=; b=Yi6MFOOjbeBfn0fqQLDtrkdNfdf2puk6ZtJAwYwabmDXVEoPhq759yJ/Ykz89BrMfc yVNYDwkKMiMyMNpPuapG10j64tlyt3OZPl8eBIZ3ij0furLKi7a5ceSHKu+CzjZ7I2GR RPApMR4nPeqDpVDnOAxUiVc0SteahCOBR2xg+7vz935w2/RdGtleaMVvGTMs+0U/L9zn fKOHCiIbrXKERD5+b3WKzt9eNmNVqxYXAC/5GuzxShUn2eVogRYTuy/dlGTfmiHd3AQg wgV0a3lQdPOk32iRtK/4b2JYAtAF7emHq41qpyXg5+Q5z+s1v73Zl5pwLljAdVZ3bdGg /DWw==
X-Received: by 10.50.129.68 with SMTP id nu4mr6315109igb.9.1372094153068; Mon, 24 Jun 2013 10:15:53 -0700 (PDT)
Received: from [10.254.50.227] ([64.235.96.2]) by mx.google.com with ESMTPSA id ri10sm949708igc.1.2013.06.24.10.15.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 10:15:52 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6C7CD4F8-F747-4C0A-869A-87EBB2BF9D7F@vpnc.org>
Date: Mon, 24 Jun 2013 13:15:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BAEEE2E-081E-4F99-B030-4175EFE0A25E@hopcount.ca>
References: <7DD9876B-B326-4553-AA4C-1E23E2D86F8C@icann.org> <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca> <6C7CD4F8-F747-4C0A-869A-87EBB2BF9D7F@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmQoPqUT9qoNnUJjicbRXdjwqHX8rYyvs8vwx3kuMYOZCW0cp0ghqR8pJGmlJT66u8yeKPC
Cc: IETF DNSOP WG <dnsop@ietf.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: [DNSOP] New Version Notification for draft-jabley-dnsop-anycast-mapping-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:15:54 -0000

On 2013-06-24, at 12:56, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> In looking at the diffs, I still have the question I had earlier about =
NSID. I give the following command three times quickly:
>   dig -4 @L.ROOT-SERVERS.NET . SOA +nsid +norec +noall +comments
> I get three different answers (lax16..., lax09..., lax13...).
>=20
> This is similar to the variance I see when doing
>   dig -4 @L.ROOT-SERVERS.NET HOSTNAME.BIND CH TXT +short
> and
>   dig -4 @L.ROOT-SERVERS.NET ID.SERVER CH TXT +short
> However:
>   dig IDENTITY.L.ROOT-SERVERS.ORG TXT +short
> gives me the same answer each time I give it.
>=20
> So, I'm still confused about the paragraph just before section 4.1.

That paragraph addresses the case of:

 (a) send query, get problematic response
 (b) do HOSTNAME.BIND (or similar) query to identify what node I'm =
talking to

It's entirely possible that the responding node for (a) will be =
different from the responding name for (b), in which case the node =
identity wouldn't correspond with the node that seemed to be giving a =
problematic response.

If instead you do:

  (a) send query with NSID, get problematic response

then the identity of the node exposed by the use of NSID corresponds =
exactly to the node that supplied the problematic response, in all =
cases, guaranteed.


Joe=

From paul.hoffman@vpnc.org  Mon Jun 24 10:23:08 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E1A21E8112 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 10:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.917
X-Spam-Level: 
X-Spam-Status: No, score=-101.917 tagged_above=-999 required=5 tests=[AWL=-0.518, BAYES_00=-2.599, J_CHICKENPOX_26=0.6, J_CHICKENPOX_84=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxIZLzCo0wAl for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 10:23:06 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9F04421F9FF2 for <dnsop@ietf.org>; Mon, 24 Jun 2013 10:23:05 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5OHN3Vs072295 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 24 Jun 2013 10:23:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <7BAEEE2E-081E-4F99-B030-4175EFE0A25E@hopcount.ca>
Date: Mon, 24 Jun 2013 10:23:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2686F392-1E8C-407D-B068-3E68C37D7FAF@vpnc.org>
References: <7DD9876B-B326-4553-AA4C-1E23E2D86F8C@icann.org> <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca> <6C7CD4F8-F747-4C0A-869A-87EBB2BF9D7F@vpnc.org> <7BAEEE2E-081E-4F99-B030-4175EFE0A25E@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1508)
Cc: IETF DNSOP WG <dnsop@ietf.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: [DNSOP] New Version Notification for draft-jabley-dnsop-anycast-mapping-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:23:09 -0000

On Jun 24, 2013, at 10:15 AM, Joe Abley <jabley@hopcount.ca> wrote:

>=20
> On 2013-06-24, at 12:56, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>=20
>> In looking at the diffs, I still have the question I had earlier =
about NSID. I give the following command three times quickly:
>>  dig -4 @L.ROOT-SERVERS.NET . SOA +nsid +norec +noall +comments
>> I get three different answers (lax16..., lax09..., lax13...).
>>=20
>> This is similar to the variance I see when doing
>>  dig -4 @L.ROOT-SERVERS.NET HOSTNAME.BIND CH TXT +short
>> and
>>  dig -4 @L.ROOT-SERVERS.NET ID.SERVER CH TXT +short
>> However:
>>  dig IDENTITY.L.ROOT-SERVERS.ORG TXT +short
>> gives me the same answer each time I give it.
>>=20
>> So, I'm still confused about the paragraph just before section 4.1.
>=20
> That paragraph addresses the case of:
>=20
> (a) send query, get problematic response
> (b) do HOSTNAME.BIND (or similar) query to identify what node I'm =
talking to
>=20
> It's entirely possible that the responding node for (a) will be =
different from the responding name for (b), in which case the node =
identity wouldn't correspond with the node that seemed to be giving a =
problematic response.
>=20
> If instead you do:
>=20
>  (a) send query with NSID, get problematic response
>=20
> then the identity of the node exposed by the use of NSID corresponds =
exactly to the node that supplied the problematic response, in all =
cases, guaranteed.

Ah, got it. I missed the linkage of "add NSID to the troublesome query". =
Proposal:
Current:
Use of the NSID option can obviate this possibility
Proposed:
Adding the NSID option to the query that causes the problematic response =
can obviate this possibility=

From jabley@hopcount.ca  Mon Jun 24 10:25:01 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B74C311E8163 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 10:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gol60CPnBh+5 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 10:25:00 -0700 (PDT)
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 9F4B521E8123 for <dnsop@ietf.org>; Mon, 24 Jun 2013 10:24:58 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id qd12so25579380ieb.16 for <dnsop@ietf.org>; Mon, 24 Jun 2013 10:24:58 -0700 (PDT)
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:x-mailer; bh=kIJeKPIfHVpP+iTbzn3Tr4LL2IwKogA95aClTLqrSVI=; b=XccYdCltIrRd6oogDC2VjWJ2Dcv19tkqIp6cpxN4atmKj6fsIsHFspQSt/5IkzJPu+ uZsWq+AJJ3SthEmmni+IH3ZcPOcxWwkWbek6pKb5QuAAR/JYiB8tDbsqOkQUPZg/hYme OoWiZgsLtRdGbZEWqEeqJ6EbWLttUlEACH7Eo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=kIJeKPIfHVpP+iTbzn3Tr4LL2IwKogA95aClTLqrSVI=; b=d2O8fFThsIU8e+owa9JyddbBbOnpdn3kuHLCNOCtxp55NmqcFyjFMcyhQFvRaDthjb XLquimf+9efrA/x6uIOyIL7u3bfHd2s0jgyYyEpSAlBlYWp+xqkkr7JhX6mi/BJ0Nqam 1XSJSabDTYG/yLrSmQqEJT1P2Jms/NEJ1WMUWyTexknQ7ciCHtx/LS3bJERGH7O8OR2l /Mik2tWPT/R+JPGJG0+1TpGyl7OSWq4CVoox6iFaWA9K+xvQFHCkqEtWkl7CeTcpTKbm G9b5m4rkBS4tABW3pdvH07bWBS9+qKUIvjJ2Nb11OPb1RuQtq7ZUgE/34h+oRRqoCwYR ykjg==
X-Received: by 10.50.130.19 with SMTP id oa19mr5147426igb.18.1372094698230; Mon, 24 Jun 2013 10:24:58 -0700 (PDT)
Received: from [10.254.50.227] ([64.235.96.2]) by mx.google.com with ESMTPSA id fu2sm986968igb.3.2013.06.24.10.24.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 10:24:57 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <2686F392-1E8C-407D-B068-3E68C37D7FAF@vpnc.org>
Date: Mon, 24 Jun 2013 13:24:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2B8D6E5-E5B1-4A11-924A-4FBAF747E6B3@hopcount.ca>
References: <7DD9876B-B326-4553-AA4C-1E23E2D86F8C@icann.org> <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca> <6C7CD4F8-F747-4C0A-869A-87EBB2BF9D7F@vpnc.org> <7BAEEE2E-081E-4F99-B030-4175EFE0A25E@hopcount.ca> <2686F392-1E8C-407D-B068-3E68C37D7FAF@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQl2p53FBgnFLX56vT1odTJzn7Wc6gPmoNMUOnPFMJjZdoUYzyf44/EYCUYqyfxS9P9s0iii
Cc: IETF DNSOP WG <dnsop@ietf.org>, Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: [DNSOP] New Version Notification for draft-jabley-dnsop-anycast-mapping-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:25:01 -0000

On 2013-06-24, at 13:23, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> Ah, got it. I missed the linkage of "add NSID to the troublesome =
query". Proposal:
> Current:
> Use of the NSID option can obviate this possibility
> Proposed:
> Adding the NSID option to the query that causes the problematic =
response can obviate this possibility

Very happy to queue that for -03, thanks for the review (again :-)


Joe=

From jabley@hopcount.ca  Mon Jun 24 11:01:58 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7674621F99D4 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 11:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXTS7T7etc6I for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 11:01:57 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id C3EF821F99BC for <dnsop@ietf.org>; Mon, 24 Jun 2013 11:01:57 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id x12so24005471ief.26 for <dnsop@ietf.org>; Mon, 24 Jun 2013 11:01:50 -0700 (PDT)
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:x-mailer; bh=Lv+3PJkiQlhQd6jUH/TrSeftjUrSc5i8gxoIBUrID4M=; b=ne/Suh4gZ2G9U34//kCx+XcCkcAt2K/IVQ8Nuo6cYH8AODR1olJEy4yBaAwzjKpT9R R0+LO2Idnkl0GbfCMsdxm1SpuqEw0Oc8ry1sQTWbrWsORLaMrQNG0bG6WGRx/Kd9Whi9 q+J/EwnVkn+oHnmr9nnJy7lGp6ehmtfnQc1i8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=Lv+3PJkiQlhQd6jUH/TrSeftjUrSc5i8gxoIBUrID4M=; b=VcyUcubjUxJq+u/8mmunnnoCX7hN5p+tk/OIGmw76vZ7L/sKG77XHvZvf3FUWx04+p 68oYXQpTx0Y+iZh1jvZbc0DswMeOcsROpCTTOQoboy1iX+QB72Y11ooQbldxEh4qcbm8 M4Rzs0IhztzRSJU7qlsHbSlR6jzpSpkdHWIRCp7dQIJ6NrZvQkyXIXjASZCX4cajeDpg ZOYqbZN2AekNVa+RFMk07vMjW2JOneaMPkCd7txmJ4EJxvlCwTGzT1RX7qM1frVuV497 N3U7VQtt1TOhoCd9AnrbD1QRb1byn7Avxreu+xErY1c02/fgsvfV2bKFHoero9WjPJ5i lPog==
X-Received: by 10.42.121.211 with SMTP id k19mr12306941icr.26.1372096909160; Mon, 24 Jun 2013 11:01:49 -0700 (PDT)
Received: from [10.254.50.227] ([64.235.96.2]) by mx.google.com with ESMTPSA id n8sm1138367igk.7.2013.06.24.11.01.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 11:01:48 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <3540A275-BDE9-4577-BD5E-7E0D0B9B894D@kumari.net>
Date: Mon, 24 Jun 2013 14:01:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC424E77-7788-47CB-9685-777303C66F8E@hopcount.ca>
References: <20130621000118.22228.76098.idtracker@ietfa.amsl.com> <3540A275-BDE9-4577-BD5E-7E0D0B9B894D@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQl2vON4+xdAc2RBMM5DQaPFY/drh+KYbgQ76IjiGO8eAGaPeN9B5c96s77VdUpAMZOMnxSN
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-omniscient-as112-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 18:01:58 -0000

On 2013-06-21, at 11:25, Warren Kumari <warren@kumari.net> wrote:

> Things that requite more discussions:
> 1: Is DNAME a viable alternative?

I think it is. I found Brian Dickson's suggestion on this list quite =
compelling. Some experimentation is likely required to characterise the =
impact of that approach with and without DNAME-aware resolvers and =
authority-only servers, and I think that work is worth doing.

I'd be very happy to work with Brian (assuming he's interested; I =
haven't talked to him) and write this up as a second option.


Joe


From paul@nohats.ca  Mon Jun 24 11:24:51 2013
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0956D21E8159 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 11:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9gM7GPcHTvl for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 11:24:46 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id F181511E8151 for <dnsop@ietf.org>; Mon, 24 Jun 2013 11:24:43 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bfJnM13D9z5Jd; Mon, 24 Jun 2013 14:24:39 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id aShNh3Lv6d6G; Mon, 24 Jun 2013 14:24:37 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Mon, 24 Jun 2013 14:24:37 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id D5A2281365; Mon, 24 Jun 2013 14:24:37 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id CA65C805B0; Mon, 24 Jun 2013 14:24:37 -0400 (EDT)
Date: Mon, 24 Jun 2013 14:24:37 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca>
Message-ID: <alpine.LFD.2.10.1306241402260.22611@bofh.nohats.ca>
References: <7DD9876B-B326-4553-AA4C-1E23E2D86F8C@icann.org> <59DE3BC3-5B6A-4547-B5AE-50F723727EE9@hopcount.ca>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-anycast-mapping-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 18:24:51 -0000

On Mon, 24 Jun 2013, Joe Abley wrote:

> Nevil needs additional reviewers. If you have a spare ten minutes to read through this revision and send feedback to Nevil (or to this list, and I'll forward) that'd be great.





textual:

 	"L-Root, one of the thirteen root servers, is deployed in this fashion."

This could be misread to mean only L-root is deployed with anycast

    Using HOSTNAME.BIND/CH/TXT (Section 4.2), ID.SERVER/CH/TXT
    (Section 4.3) or IDENTITY.L.ROOT-SERVERS.ORG/IN/TXT or .../IN/A
    (Section 4.4) to identify a node for the purposes of reporting a
    problem is frequently reasonable, but it should be acknowledged that
    there is potential for re-routing between successive queries: an
    observed problem might relate to one node, whilst a subsequent query
    using one of those three techniques could be answered by a different
    node.  Use of the NSID option can obviate this possibility (see
    Section 4.1).

This section is confusing, especially since the previous paragraph sets
things up to be followed by a list of methods, not a sentence of a list
of methods and their usage. It should probably be moved towards the end
of section 4. Or moved up one paragraph. It would also be useful to
state that the listed methods below each have their pros and conns, and
that _that_ is the reason all of them are done (some of this can only be
indirectly concluded, and could be stated more explicitly, like:

- This method works through recursive DNS
- This method could fail because some DNS software does not allow the CHAOS class
- This method is currently not supported on most authoritative DS servers

Or perhaps state earlier in the document why more then one
method for identifying name servers is deployed.


Note while doing some testing I accidentally did:

 	dig +nsid org @l.root-servers.org

which just gave me a timeout error. It worked using the IP. Only then
did I notice my brain had caught IDENTITY.L.ROOT-SERVERS.ORG and used
"root-servers.org" instead of "root-servers.net" for the query. 
Perhaps bring up the text "(note the use of ORG, not NET)" to an earlier
point in the draft? :)

Paul

From jabley@hopcount.ca  Mon Jun 24 12:32:49 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9706821E815A for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 12:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPj2WAm+MhxT for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 12:32:48 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 74B7921F9B93 for <dnsop@ietf.org>; Mon, 24 Jun 2013 12:32:48 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so12383270oah.38 for <dnsop@ietf.org>; Mon, 24 Jun 2013 12:32:46 -0700 (PDT)
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:x-mailer; bh=kBvd/cZIAS7mZq2b2hIqivp8s/2YxtgbDN30Z60/iZc=; b=GgpVirEUGjzgVfw4rEdluncqpNPCbfnvv6jTT+tX7ve+S0e4Y79CE1e9/u/IBYr4Ly YFDF0iMEfYEOdtXRhS0L5dgIwCp1OC9dXIWIOk1h2v7vIwzX1Kao5INPmDd+07189/8+ H+ZX35mdijQYWo9CEK5lkM1NExRN2bssEUpx0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version:x-mailer:x-gm-message-state; bh=kBvd/cZIAS7mZq2b2hIqivp8s/2YxtgbDN30Z60/iZc=; b=JNPjrU9gPG0nLoFcGS+3iFZTx5le0hObeVbXnpQAG6etoWfitUaauuTPVvhiuaJgYe 9b5W/m1t7FhX7Jjk+0LEI5a76sCRo12naI1UbOCOQGCWEm2La2gR1l9+FAWgHFZ44xY+ +D9LUUjmHy7MRZNNFuTZfh1n/BSXZ8y1AHnQym/LodFekF1A8YURMj97Vz++8HkEwqSo roCLOwKCp7F4daVHDC6lSZmk2fOjjCXQCHE7UeVl2IRBDiln+zLLpzC3UKh+ajYN+9Iv UIhekUKUpP8Nz7jSf9WpbLgG1keNciBHSfHECtq9soNdvx5PwCph1CJwoz10i4MmG6Zf qqSA==
X-Received: by 10.182.74.131 with SMTP id t3mr8799340obv.87.1372102366871; Mon, 24 Jun 2013 12:32:46 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:5cb0:2f17:4b0d:2475? ([2001:4900:1042:100:5cb0:2f17:4b0d:2475]) by mx.google.com with ESMTPSA id el16sm3140673oeb.2.2013.06.24.12.32.46 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 12:32:46 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Jun 2013 15:32:45 -0400
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-Id: <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQlMRDSX3k4BAhtbiPFdl51dXIXAROkQky3pNwKwRjyS3KWq/TaRT2naYJaCHYR/dO8SlJP/
Subject: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 19:32:49 -0000

Greetings, draft-fans!

I just exhumed the below-mentioned draft and recruited a co-author, =
since it seems like a timely topic for discussion.

This draft proposes a mechanism whereby an authority-server operator can =
signal to one or more recursive servers that the recursive server should =
flush a section of its cache. It's an in-band mechanism using =
TSIG-secured NOTIFY.

No code-points were depleted during the preparation of this proposal.

The use-cases are things like "prominent zone suffered some kind of =
signing error, things are better now, bad data is cached, would be nice =
to flush it" and "registrar suffered some kind of database error, things =
are better now, bad data is cached, etc." hence timely, above.

Comments on the general idea or the specific proposal would be most =
welcome.


Joe

Begin forwarded message:

> From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> Subject: New Version Notification for =
draft-jabley-dnsop-dns-flush-00.txt
> Date: 24 June 2013 15:16:29 EDT
> To: Joe Abley <joe.abley@icann.org>
>=20
>=20
> A new version of I-D, draft-jabley-dnsop-dns-flush-00.txt
> has been successfully submitted by Joe Abley and posted to the
> IETF repository.
>=20
> Filename:	 draft-jabley-dnsop-dns-flush
> Revision:	 00
> Title:		 A Mechanism for Remote-Triggered DNS Cache =
Flushes (DNS FLUSH)
> Creation date:	 2013-06-24
> Group:		 Individual Submission
> Number of pages: 12
> URL:             =
http://www.ietf.org/internet-drafts/draft-jabley-dnsop-dns-flush-00.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-jabley-dnsop-dns-flush
> Htmlized:        =
http://tools.ietf.org/html/draft-jabley-dnsop-dns-flush-00
>=20
>=20
> Abstract:
>   DNS NOTIFY is a mechanism for prompt notification of zone changes
>   between DNS authority servers that is usually employed to trigger
>   immediate zone transfers.
>=20
>   This document specifies an additional use of DNS NOTIFY to allow DNS
>   authority servers to trigger cache flushes on recursive DNS servers.
>   Such signalling is authenticated and is intended for use between
>   cooperating DNS server operators.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20


From warren@kumari.net  Mon Jun 24 14:12:21 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9EF21F972E for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 14:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.365
X-Spam-Level: 
X-Spam-Status: No, score=-102.365 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01LCixRCZ7Y7 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 14:12:15 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 634C721F9926 for <dnsop@ietf.org>; Mon, 24 Jun 2013 14:12:11 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.90]) by vimes.kumari.net (Postfix) with ESMTPSA id CA3571B40341; Mon, 24 Jun 2013 17:12:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <EC424E77-7788-47CB-9685-777303C66F8E@hopcount.ca>
Date: Mon, 24 Jun 2013 17:12:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6B6B96E-0BEA-433A-9017-103F6F93D878@kumari.net>
References: <20130621000118.22228.76098.idtracker@ietfa.amsl.com> <3540A275-BDE9-4577-BD5E-7E0D0B9B894D@kumari.net> <EC424E77-7788-47CB-9685-777303C66F8E@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1508)
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-omniscient-as112-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 21:12:21 -0000

On Jun 24, 2013, at 2:01 PM, Joe Abley <jabley@hopcount.ca> wrote:

>=20
> On 2013-06-21, at 11:25, Warren Kumari <warren@kumari.net> wrote:
>=20
>> Things that requite more discussions:
>> 1: Is DNAME a viable alternative?
>=20
> I think it is. I found Brian Dickson's suggestion on this list quite =
compelling.

Yup. It is definitely worth investigating more...

> Some experimentation is likely required to characterise the impact of =
that approach with and without DNAME-aware resolvers and authority-only =
servers, and I think that work is worth doing.
>=20

Also yup.
This would require some experimentation to make sure that it works under =
most / all cases, and a better understanding of how widely deployed =
DNAME support is.=20
There were some studies into DNAME support a while back, things have =
gotten better since then (I'd assume!).

> I'd be very happy to work with Brian (assuming he's interested; I =
haven't talked to him) and write this up as a second option.

Great. We could:
A: replace the current method outlined in =
draft-wkumari-dnsop-omniscient-as112-03 with DNAME.
B: have two methods described in one draft or
C: have two drafts, each describing an option.

W=20

>=20
>=20
> Joe
>=20

--=20
"I think it would be a good idea."=20
- Mahatma Ghandi, when asked what he thought of Western civilization




From jabley@hopcount.ca  Mon Jun 24 15:56:07 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA0E621E810C for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 15:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzSz4iqzsEm9 for <dnsop@ietfa.amsl.com>; Mon, 24 Jun 2013 15:56:07 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEDE21E80EF for <dnsop@ietf.org>; Mon, 24 Jun 2013 15:56:06 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id aq17so26295109iec.36 for <dnsop@ietf.org>; Mon, 24 Jun 2013 15:56:00 -0700 (PDT)
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:x-mailer; bh=mRVdG99KJJkAMcGRKF3JpXHIkAN+tOs+/qIMiR0Gtyg=; b=NgLacJlQO7q0G1TFQxW+PKpBbA0RqnOS0BP73Pq8IsAtyBmPwNNTvTgPJAjbN8RWcY dXR/65e1Ji0iasjkUB3eiY6rpXHVxQyL3S4dC30Xg1auUJxH+ZT5g4Q8BJzW1eyIKmcd YOzDhKMJRFtlObSio7RmnMmeNj7URzUUCnZI8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=mRVdG99KJJkAMcGRKF3JpXHIkAN+tOs+/qIMiR0Gtyg=; b=HAaldjyblNjwvpAxMaqKxMgqeoKMwFUNLywV3SsY9s9/rOB3ioaLtlqbGVtikmOyvI zq2JMvNRyiXgKigYybJdPln7iud83jq/LS4TUcr2k8/Dh/QEHW/YHHPvweR1KOKHlmJb 2ejz6mCUu5eotSo79oF6kXKlNiPFQP9qG7snO38Wku0S13LdkdqP2KyeO0c1NiEEy6Q9 haKFSuMYot/68CBDrwTK/pIs+RGw7ycZe8ZvckwxA9Ojacuc45+gkbW7llb/QyE09Aba Om+TXEInKONBg6pOirAMR1So6wrtkYvoAqbxW4wAzJmM/nlU1ha17oL10ZITdtx/r6Ek qb4g==
X-Received: by 10.50.12.99 with SMTP id x3mr6872224igb.58.1372114560715; Mon, 24 Jun 2013 15:56:00 -0700 (PDT)
Received: from [199.212.90.42] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id p10sm475119igx.4.2013.06.24.15.55.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 15:56:00 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <E6B6B96E-0BEA-433A-9017-103F6F93D878@kumari.net>
Date: Mon, 24 Jun 2013 18:55:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <504B1E3C-44B5-426C-968D-738E160C6D02@hopcount.ca>
References: <20130621000118.22228.76098.idtracker@ietfa.amsl.com> <3540A275-BDE9-4577-BD5E-7E0D0B9B894D@kumari.net> <EC424E77-7788-47CB-9685-777303C66F8E@hopcount.ca> <E6B6B96E-0BEA-433A-9017-103F6F93D878@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQkdIQy1nQhCmwgr8ZtS7qU51sQ/eM0NpvH3GDIbXv6RtKEsT9lxqu6y5ousYVfYWGOfxmA6
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-omniscient-as112-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 22:56:07 -0000

On 2013-06-24, at 17:12, Warren Kumari <warren@kumari.net> wrote:

>> I'd be very happy to work with Brian (assuming he's interested; I =
haven't talked to him) and write this up as a second option.
>=20
> Great. We could:
> A: replace the current method outlined in =
draft-wkumari-dnsop-omniscient-as112-03 with DNAME.
> B: have two methods described in one draft or
> C: have two drafts, each describing an option.

I heard from Brian; we have a draft nearly ready to post, I would say. =
So I guess option C, to be followed by lively debate. :-)


Joe


From matthijs@nlnetlabs.nl  Tue Jun 25 03:05:30 2013
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3B521F9FDC for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 03:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6VKjcER-wZZ for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 03:05:29 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E90E21F9FF9 for <dnsop@ietf.org>; Tue, 25 Jun 2013 03:05:28 -0700 (PDT)
Received: from [213.154.224.18] (zoidberg.nlnetlabs.nl [213.154.224.18]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r5PA5NU6091613 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Tue, 25 Jun 2013 12:05:23 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r5PA5NU6091613
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1372154727; bh=K5fUcbEi8m6y9ZLZaEnt22iwzCskLFovK93BDCH+ARA=; h=Date:From:To:Subject:References:In-Reply-To; b=mbHBzhime88rbcWbcROpgAKjs2V29AMHoqKJcL50wo5ETMfnki9pcotE41eXTABXC yQjHTNNI16WFoH44JpLfwDjvkvTFlScDoyobRXZr0FPabdXn2T1IEy3HPcj8DIG2hC pJHONhYakjQofawKYkNojz/UvXr/6XhndfqhmBdQ=
Message-ID: <51C96B62.9030401@nlnetlabs.nl>
Date: Tue, 25 Jun 2013 12:05:22 +0200
From: Matthijs Mekking <matthijs@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net>
In-Reply-To: <0lsj0b2kk5.fsf@wjh.hardakers.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [213.154.224.1]); Tue, 25 Jun 2013 12:05:23 +0200 (CEST)
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 10:05:30 -0000

Hi,

On 06/21/2013 11:58 PM, Wes Hardaker wrote:
> Paul Wouters <paul@cypherpunks.ca> writes:
> 
>> I am in favour of adopting this draft as a WG item.
> 
> Ditto.

Another ditto. I am pleased to see that there is still activity on the
topic of automating the synchronization between DNSKEY at the child and
the DS at the parent.


>> I don't think the CDS record should be able to cause a child domain to
>> go from secure to insecure, or from insecure to secure. That
>> (infrequent) change should have an additional authentication, eg via EPP
>> or otherwise)
> 
> Ditto.  I think the goal of any of the automatic update techniques
> should be to make the routine easy but it shouldn't be a goal to handle
> the infrequent, and challenging cases.  (infrequent and easy is fine).
> 
> Unless we can show a clear, secured, path for some transition I don't
> think it's worth solving.

Another ditto. Agreeing with it's not worth solving to deal with the
irregular cases. Going unsigned is an irregular case.


Also backing a previous made comment by other people:

* I prefer to have the CDS wire format to be similar to the DS wire
format. With the current draft, it is already possible to automate all
possible key rollovers, no need for managerial hooks to say this record
is proposed, must be added, deleted, is valid for only this period etc.


Comments on the draft (apologies for its length):

* Nit: In section 1, it says there may be two interactions with the
parent. This could also be only one, this could be more in some freaky
rollovers, so I would prefer that it reads: "there may be one ore more
interactions with the parent".

* Section 3. I appreciate that most ZSK /KSK terminology is carefully
replaced with, but in section 3 is still something that itches: "The SEP
bit is an optional bit to indicate that the key is allowed to sign the
DNSKEY RRset". That is not true. Without the SEP bit, the key may also
sign the DNSKEY RRset.

* Section 3.1.1. As said above, I don't like the idea of using the CDS
record to go unsigned.

* Nit: Section 4.1. I think the last paragraph fits better in section
4.2. CDS Consumption.

* Section 4.2. About the polling strategy. I am wondering how well this
scales with respect to the number of delegations.

* Section 4.2. It is suggested that RFC 5011-like hold down timers are
being used, e.g. new keying information must be published for a month
before acceptance as a new trust anchor. This makes the duration of key
rollovers unnecessary long. The hold down timers in RFC 5011 are there
to mitigate against a compromise. The compromise allows the attacker to
sign data in the zone.

Similar we could look at a compromise that allows the attacker to upload
a DS/DNSKEY to the parent. However, there are no mechanisms to mitigate
against this attack. Why should we have mitigation for the CDS proposal,
if there is none for the current mechanism?

The difference between CDS and RFC 5011 is the location of the trust
anchor your are updating. With CDS, you are updating the DS in the
parent. With RFC 5011, you are updating lots of trust anchors in the
wild. The latter may indeed require a bit more conservative approach.

* Section 4.3. I wonder if the SHOULD in the first sentence should be a
MUST.

* Section 4.4. I dislike the idea of the side effect of parent
calculates DS, so I would like to see that only the "augment" mode is
supported (where I think it should read: "it will make sure there are
CDS records for the digest algorithm(s) it require(s)" (CDS instead of
DS)).

The publishing "Future DNSKEYs" does not go well with several rollover
scenarios (those based on Double-DS). I am wondering if the policy is
"We calculate the DS" or "We decide the digest algorithm". In case of
the latter, then augment mode can be used to support this. In case of
the first, the future DNSKEY is really required to be published, and
Double-DS based rollovers are not possible in combination with CDS.

* Section 6. Security Considerations. The last paragraph. Isn't this
solved by saying that the Parental Agent MUST ensure that old versions
of the CDS RRset do not override newer versions in section 4.3. Usage?
There is already a proposed method on how to achieve this there.

* When implementing a prototype for this in OpenDNSSEC, I questioned
myself what value I should use for the TTL. We could consider 0, as this
record is not really intended for the resolver. We could also use the
TTL to suggest a polling frequency for the parental agent. Just some
thoughts.


Best regards,
  Matthijs












*



From dengguangqing@cnnic.cn  Tue Jun 25 05:03:06 2013
Return-Path: <dengguangqing@cnnic.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE2BE21F9F08 for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 05:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.845
X-Spam-Level: 
X-Spam-Status: No, score=-0.845 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aailkWy73e6A for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 05:03:02 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id CD5CA21F9EE2 for <dnsop@ietf.org>; Tue, 25 Jun 2013 05:03:00 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: dengguangqing@cnnic.cn
Received: from unknown127.0.0.1 (HELO dgq-pc) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 25 Jun 2013 20:02:43 +0800
Date: Tue, 25 Jun 2013 20:02:46 +0800
From: "Guangqing Deng" <dengguangqing@cnnic.cn>
To: "Joe Abley" <jabley@hopcount.ca>
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com>,  <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.91[cn]
Mime-Version: 1.0
Message-ID: <201306252002459685411@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart540470347425_=----"
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dengguangqing <dengguangqing@cnnic.cn>
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 Jun 2013 12:03:06 -0000

This is a multi-part message in MIME format.

------=_001_NextPart540470347425_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGksIEpvZSwgSSBsaWtlIHRoaXMgZHJhZnQsIHRob3VnaCBJIGFtIHB1enpsZWQgYnkgc29tZSBx
dWVzdGlvbnMuIEZpcnN0LCB0aGUgY2hhbmdlIG9mIA0KdGhlIHpvbmUgY29udGVudCBvZiBhbiBh
dXRob3JpdHkgc2VydmVyIGRvZXMgbm90IG1lYW4gdGhhdCBhIGNvcnJlc3BvbmRpbmcgcmVjdXJz
aXZlIHNlcnZlciANCmhhcyB0byBmbHVzaCBpdHMgY2FjaGUsIHNpbmNlIGEgcmVjdXJzaXZlIHNl
cnZlciB1c3VhbGx5IGp1c3QgY2FjaGUgYSBzbWFsbCBwYXJ0IG9mIHpvbmUgY29udGVudA0Kb2Yg
YW4gYXV0aG9yaXR5IHNlcnZlciBidXQgbm90IGFsbC4gQWxzbywgYW4gYXV0aG9yaXR5IHNlcnZl
ciBkb2VzIG5vdCBrbm93IHdoaWNoIFJScyBvZiBpdHMgDQp6b25lIGNvbnRlbnQgYXJlIGNhY2hl
ZCBpbiByZWN1cnNpdmUgc2VydmVycy4gU28gc3VjaCBtZWNoYW5pc20gb2YgRE5TIEZMVVNIIG1h
eSBicmluZyBhYm91dCANCnNvbWUgYWRkaXRpb25hbCB0cmFmZmljIGJldHdlZW4gYXV0aG9yaXR5
IGFuZCByZWN1cnNpdmUgc2VydmVycyB3aXRoIG5vIGJlbmVmaXQuIFNlY29uZCwgaG93IA0KZG9l
cyB0aGUgYXV0aG9yaXR5IHNlcnZlciBvYnRhaW4gdGhlIElQcyBvZiByZWN1cnNpdmUgc2VydmVy
cz8gRnJvbSBxdWVyeSBsb2dzPyBUaGVuIHRoZSANCmF1dGhvcml0eSBzZXJ2ZXIgc2VuZHMgRE5T
IEZMVVNIIHRvIGFsbCBvciBwYXJ0IG9mIHJlY3Vyc2l2ZSBzZXJ2ZXJzPyBJdCBzZWVtcyB0aGF0
IHRoZXJlIA0KYXJlIGJpZyBkaWZmZXJlbmNlcyBiZXR3ZWVuIEROUyBOT1RJRlkgYW5kIHNvIGNh
bGxlZCBETlMgRkxVU0ggYW5kIHRodXMgbW9yZSB0aGluZ3MgbmVlZCB0byANCmJlIGNsYXJpZmll
ZC4NCg0KDQoNCg0KR3VhbmdxaW5nIERlbmcNCmNubmljIA0KDQpGcm9tOiBKb2UgQWJsZXkNCkRh
dGU6IDIwMTMtMDYtMjUgMDM6MzINClRvOiBJRVRGIEROU09QIFdHDQpTdWJqZWN0OiBbRE5TT1Bd
IEZ3ZDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1qYWJsZXktZG5zb3AtZG5z
LWZsdXNoLTAwLnR4dA0KR3JlZXRpbmdzLCBkcmFmdC1mYW5zIQ0KDQpJIGp1c3QgZXhodW1lZCB0
aGUgYmVsb3ctbWVudGlvbmVkIGRyYWZ0IGFuZCByZWNydWl0ZWQgYSBjby1hdXRob3IsIHNpbmNl
IGl0IHNlZW1zIGxpa2UgYSB0aW1lbHkgdG9waWMgZm9yIGRpc2N1c3Npb24uDQoNClRoaXMgZHJh
ZnQgcHJvcG9zZXMgYSBtZWNoYW5pc20gd2hlcmVieSBhbiBhdXRob3JpdHktc2VydmVyIG9wZXJh
dG9yIGNhbiBzaWduYWwgdG8gb25lIG9yIG1vcmUgcmVjdXJzaXZlIHNlcnZlcnMgdGhhdCB0aGUg
cmVjdXJzaXZlIHNlcnZlciBzaG91bGQgZmx1c2ggYSBzZWN0aW9uIG9mIGl0cyBjYWNoZS4gSXQn
cyBhbiBpbi1iYW5kIG1lY2hhbmlzbSB1c2luZyBUU0lHLXNlY3VyZWQgTk9USUZZLg0KDQpObyBj
b2RlLXBvaW50cyB3ZXJlIGRlcGxldGVkIGR1cmluZyB0aGUgcHJlcGFyYXRpb24gb2YgdGhpcyBw
cm9wb3NhbC4NCg0KVGhlIHVzZS1jYXNlcyBhcmUgdGhpbmdzIGxpa2UgInByb21pbmVudCB6b25l
IHN1ZmZlcmVkIHNvbWUga2luZCBvZiBzaWduaW5nIGVycm9yLCB0aGluZ3MgYXJlIGJldHRlciBu
b3csIGJhZCBkYXRhIGlzIGNhY2hlZCwgd291bGQgYmUgbmljZSB0byBmbHVzaCBpdCIgYW5kICJy
ZWdpc3RyYXIgc3VmZmVyZWQgc29tZSBraW5kIG9mIGRhdGFiYXNlIGVycm9yLCB0aGluZ3MgYXJl
IGJldHRlciBub3csIGJhZCBkYXRhIGlzIGNhY2hlZCwgZXRjLiIgaGVuY2UgdGltZWx5LCBhYm92
ZS4NCg0KQ29tbWVudHMgb24gdGhlIGdlbmVyYWwgaWRlYSBvciB0aGUgc3BlY2lmaWMgcHJvcG9z
YWwgd291bGQgYmUgbW9zdCB3ZWxjb21lLg0KDQoNCkpvZQ0KDQpCZWdpbiBmb3J3YXJkZWQgbWVz
c2FnZToNCg0KPiBGcm9tOiAiaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIiA8aW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnPg0KPiBTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRy
YWZ0LWphYmxleS1kbnNvcC1kbnMtZmx1c2gtMDAudHh0DQo+IERhdGU6IDI0IEp1bmUgMjAxMyAx
NToxNjoyOSBFRFQNCj4gVG86IEpvZSBBYmxleSA8am9lLmFibGV5QGljYW5uLm9yZz4NCj4gDQo+
IA0KPiBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtamFibGV5LWRuc29wLWRucy1mbHVzaC0w
MC50eHQNCj4gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBKb2UgQWJsZXkgYW5k
IHBvc3RlZCB0byB0aGUNCj4gSUVURiByZXBvc2l0b3J5Lg0KPiANCj4gRmlsZW5hbWU6ICBkcmFm
dC1qYWJsZXktZG5zb3AtZG5zLWZsdXNoDQo+IFJldmlzaW9uOiAgMDANCj4gVGl0bGU6ICBBIE1l
Y2hhbmlzbSBmb3IgUmVtb3RlLVRyaWdnZXJlZCBETlMgQ2FjaGUgRmx1c2hlcyAoRE5TIEZMVVNI
KQ0KPiBDcmVhdGlvbiBkYXRlOiAgMjAxMy0wNi0yNA0KPiBHcm91cDogIEluZGl2aWR1YWwgU3Vi
bWlzc2lvbg0KPiBOdW1iZXIgb2YgcGFnZXM6IDEyDQo+IFVSTDogICAgICAgICAgICAgaHR0cDov
L3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtamFibGV5LWRuc29wLWRucy1mbHVz
aC0wMC50eHQNCj4gU3RhdHVzOiAgICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWphYmxleS1kbnNvcC1kbnMtZmx1c2gNCj4gSHRtbGl6ZWQ6ICAgICAgICBodHRw
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1qYWJsZXktZG5zb3AtZG5zLWZsdXNoLTAwDQo+
IA0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgRE5TIE5PVElGWSBpcyBhIG1lY2hhbmlzbSBmb3IgcHJv
bXB0IG5vdGlmaWNhdGlvbiBvZiB6b25lIGNoYW5nZXMNCj4gICBiZXR3ZWVuIEROUyBhdXRob3Jp
dHkgc2VydmVycyB0aGF0IGlzIHVzdWFsbHkgZW1wbG95ZWQgdG8gdHJpZ2dlcg0KPiAgIGltbWVk
aWF0ZSB6b25lIHRyYW5zZmVycy4NCj4gDQo+ICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYW4g
YWRkaXRpb25hbCB1c2Ugb2YgRE5TIE5PVElGWSB0byBhbGxvdyBETlMNCj4gICBhdXRob3JpdHkg
c2VydmVycyB0byB0cmlnZ2VyIGNhY2hlIGZsdXNoZXMgb24gcmVjdXJzaXZlIEROUyBzZXJ2ZXJz
Lg0KPiAgIFN1Y2ggc2lnbmFsbGluZyBpcyBhdXRoZW50aWNhdGVkIGFuZCBpcyBpbnRlbmRlZCBm
b3IgdXNlIGJldHdlZW4NCj4gICBjb29wZXJhdGluZyBETlMgc2VydmVyIG9wZXJhdG9ycy4NCj4g
DQo+IA0KPiANCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+IA0KDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRE5TT1AgbWFpbGluZyBsaXN0DQpE
TlNPUEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbnNv
cA==

------=_001_NextPart540470347425_=----
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DGB2312" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =CE=A2=C8=ED=D1=C5=BA=DA; COLOR: #000080; =
FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18156"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>
<DIV>Hi,&nbsp;Joe,&nbsp;I&nbsp;like&nbsp;this&nbsp;draft,&nbsp;though&nbsp=
;I&nbsp;am=20
puzzled=20
by&nbsp;some&nbsp;questions.&nbsp;First,&nbsp;the&nbsp;change&nbsp;of&nbsp=
;</DIV>
<DIV>the&nbsp;zone&nbsp;content&nbsp;of&nbsp;an&nbsp;authority&nbsp;server=
&nbsp;does&nbsp;not&nbsp;mean&nbsp;that&nbsp;a&nbsp;corresponding&nbsp;rec=
ursive&nbsp;server&nbsp;</DIV>
<DIV>has&nbsp;to&nbsp;flush&nbsp;its&nbsp;cache,&nbsp;since&nbsp;a&nbsp;re=
cursive&nbsp;server&nbsp;usually&nbsp;just&nbsp;cache&nbsp;a&nbsp;small&nb=
sp;part&nbsp;of&nbsp;zone&nbsp;content</DIV>
<DIV>of&nbsp;an&nbsp;authority&nbsp;server&nbsp;but&nbsp;not&nbsp;all.&nbs=
p;Also,&nbsp;an&nbsp;authority&nbsp;server&nbsp;does&nbsp;not&nbsp;know&nb=
sp;which&nbsp;RRs&nbsp;of&nbsp;its&nbsp;</DIV>
<DIV>zone&nbsp;content&nbsp;are&nbsp;cached&nbsp;in&nbsp;recursive&nbsp;se=
rvers.&nbsp;So&nbsp;such&nbsp;mechanism&nbsp;of&nbsp;DNS&nbsp;FLUSH&nbsp;m=
ay&nbsp;bring&nbsp;about&nbsp;</DIV>
<DIV>some&nbsp;additional&nbsp;traffic&nbsp;between&nbsp;authority&nbsp;an=
d&nbsp;recursive&nbsp;servers&nbsp;with&nbsp;no&nbsp;benefit.&nbsp;Second,=
&nbsp;how&nbsp;</DIV>
<DIV>does&nbsp;the&nbsp;authority&nbsp;server&nbsp;obtain&nbsp;the&nbsp;IP=
s&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;From&nbsp;query&nbsp;logs?&nbs=
p;Then&nbsp;the&nbsp;</DIV>
<DIV>authority&nbsp;server&nbsp;sends&nbsp;DNS&nbsp;FLUSH&nbsp;to&nbsp;all=
&nbsp;or&nbsp;part&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;It&nbsp;seems=
&nbsp;that&nbsp;there&nbsp;</DIV>
<DIV>are&nbsp;big&nbsp;differences&nbsp;between&nbsp;DNS&nbsp;NOTIFY&nbsp;=
and&nbsp;so&nbsp;called&nbsp;DNS&nbsp;FLUSH&nbsp;and&nbsp;thus&nbsp;more&n=
bsp;things&nbsp;need&nbsp;to&nbsp;</DIV>
<DIV>be&nbsp;clarified.</DIV></DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV><SPAN><SPAN=20
style=3D"FONT-FAMILY: =CB=CE=CC=E5; COLOR: #000000; FONT-SIZE: 10.5pt">Gua=
ngqing=20
Deng<BR>cnnic&nbsp;</SPAN></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:jabley@hopcount.ca">Joe Abley</A>=
</DIV>
<DIV><B>Date:</B>&nbsp;2013-06-25&nbsp;03:32</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:dnsop@ietf.org">IETF DNSOP WG</A></=
DIV>
<DIV><B>Subject:</B>&nbsp;[DNSOP] Fwd: New Version Notification for=20
draft-jabley-dnsop-dns-flush-00.txt</DIV></DIV></DIV>
<DIV>
<DIV>Greetings,&nbsp;draft-fans!</DIV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;just&nbsp;exhumed&nbsp;the&nbsp;below-mentioned&nbsp;draft&nbs=
p;and&nbsp;recruited&nbsp;a&nbsp;co-author,&nbsp;since&nbsp;it&nbsp;seems&=
nbsp;like&nbsp;a&nbsp;timely&nbsp;topic&nbsp;for&nbsp;discussion.</DIV>
<DIV>&nbsp;</DIV>
<DIV>This&nbsp;draft&nbsp;proposes&nbsp;a&nbsp;mechanism&nbsp;whereby&nbsp=
;an&nbsp;authority-server&nbsp;operator&nbsp;can&nbsp;signal&nbsp;to&nbsp;=
one&nbsp;or&nbsp;more&nbsp;recursive&nbsp;servers&nbsp;that&nbsp;the&nbsp;=
recursive&nbsp;server&nbsp;should&nbsp;flush&nbsp;a&nbsp;section&nbsp;of&n=
bsp;its&nbsp;cache.&nbsp;It's&nbsp;an&nbsp;in-band&nbsp;mechanism&nbsp;usi=
ng&nbsp;TSIG-secured&nbsp;NOTIFY.</DIV>
<DIV>&nbsp;</DIV>
<DIV>No&nbsp;code-points&nbsp;were&nbsp;depleted&nbsp;during&nbsp;the&nbsp=
;preparation&nbsp;of&nbsp;this&nbsp;proposal.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;use-cases&nbsp;are&nbsp;things&nbsp;like&nbsp;"prominent&nbs=
p;zone&nbsp;suffered&nbsp;some&nbsp;kind&nbsp;of&nbsp;signing&nbsp;error,&=
nbsp;things&nbsp;are&nbsp;better&nbsp;now,&nbsp;bad&nbsp;data&nbsp;is&nbsp=
;cached,&nbsp;would&nbsp;be&nbsp;nice&nbsp;to&nbsp;flush&nbsp;it"&nbsp;and=
&nbsp;"registrar&nbsp;suffered&nbsp;some&nbsp;kind&nbsp;of&nbsp;database&n=
bsp;error,&nbsp;things&nbsp;are&nbsp;better&nbsp;now,&nbsp;bad&nbsp;data&n=
bsp;is&nbsp;cached,&nbsp;etc."&nbsp;hence&nbsp;timely,&nbsp;above.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Comments&nbsp;on&nbsp;the&nbsp;general&nbsp;idea&nbsp;or&nbsp;the&nbs=
p;specific&nbsp;proposal&nbsp;would&nbsp;be&nbsp;most&nbsp;welcome.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Joe</DIV>
<DIV>&nbsp;</DIV>
<DIV>Begin&nbsp;forwarded&nbsp;message:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&nbsp;From:&nbsp;"internet-drafts@ietf.org"&nbsp;&lt;internet-dra=
fts@ietf.org&gt;</DIV>
<DIV>&gt;&nbsp;Subject:&nbsp;New&nbsp;Version&nbsp;Notification&nbsp;for&n=
bsp;draft-jabley-dnsop-dns-flush-00.txt</DIV>
<DIV>&gt;&nbsp;Date:&nbsp;24&nbsp;June&nbsp;2013&nbsp;15:16:29&nbsp;EDT</D=
IV>
<DIV>&gt;&nbsp;To:&nbsp;Joe&nbsp;Abley&nbsp;&lt;joe.abley@icann.org&gt;</D=
IV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;A&nbsp;new&nbsp;version&nbsp;of&nbsp;I-D,&nbsp;draft-jabley=
-dnsop-dns-flush-00.txt</DIV>
<DIV>&gt;&nbsp;has&nbsp;been&nbsp;successfully&nbsp;submitted&nbsp;by&nbsp=
;Joe&nbsp;Abley&nbsp;and&nbsp;posted&nbsp;to&nbsp;the</DIV>
<DIV>&gt;&nbsp;IETF&nbsp;repository.</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;Filename: &nbsp;draft-jabley-dnsop-dns-flush</DIV>
<DIV>&gt;&nbsp;Revision: &nbsp;00</DIV>
<DIV>&gt;&nbsp;Title:=20
&nbsp;A&nbsp;Mechanism&nbsp;for&nbsp;Remote-Triggered&nbsp;DNS&nbsp;Cache&=
nbsp;Flushes&nbsp;(DNS&nbsp;FLUSH)</DIV>
<DIV>&gt;&nbsp;Creation&nbsp;date: &nbsp;2013-06-24</DIV>
<DIV>&gt;&nbsp;Group: &nbsp;Individual&nbsp;Submission</DIV>
<DIV>&gt;&nbsp;Number&nbsp;of&nbsp;pages:&nbsp;12</DIV>
<DIV>&gt;&nbsp;URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;http://www.ietf.org/internet-drafts/draft-jabley-dn=
sop-dns-flush-00.txt</DIV>
<DIV>&gt;&nbsp;Status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;http://datatracker.ietf.org/doc/draft-jabley-dnsop-dns-flush</DIV>
<DIV>&gt;&nbsp;Htmlized:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ht=
tp://tools.ietf.org/html/draft-jabley-dnsop-dns-flush-00</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;Abstract:</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;DNS&nbsp;NOTIFY&nbsp;is&nbsp;a&nbsp;mechanism&n=
bsp;for&nbsp;prompt&nbsp;notification&nbsp;of&nbsp;zone&nbsp;changes</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;between&nbsp;DNS&nbsp;authority&nbsp;servers&nb=
sp;that&nbsp;is&nbsp;usually&nbsp;employed&nbsp;to&nbsp;trigger</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;immediate&nbsp;zone&nbsp;transfers.</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;This&nbsp;document&nbsp;specifies&nbsp;an&nbsp;=
additional&nbsp;use&nbsp;of&nbsp;DNS&nbsp;NOTIFY&nbsp;to&nbsp;allow&nbsp;D=
NS</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;authority&nbsp;servers&nbsp;to&nbsp;trigger&nbs=
p;cache&nbsp;flushes&nbsp;on&nbsp;recursive&nbsp;DNS&nbsp;servers.</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;Such&nbsp;signalling&nbsp;is&nbsp;authenticated=
&nbsp;and&nbsp;is&nbsp;intended&nbsp;for&nbsp;use&nbsp;between</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;cooperating&nbsp;DNS&nbsp;server&nbsp;operators=
.</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&gt;&nbsp;The&nbsp;IETF&nbsp;Secretariat</DIV>
<DIV>&gt;&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>_______________________________________________</DIV>
<DIV>DNSOP&nbsp;mailing&nbsp;list</DIV>
<DIV>DNSOP@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/dnsop</DIV></DIV></BODY></HTML>

------=_001_NextPart540470347425_=------


From jabley@hopcount.ca  Tue Jun 25 06:10:05 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7E521F9E0E for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 06:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3lz+idu0gMY for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 06:10:04 -0700 (PDT)
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 8D5C721F9E0D for <dnsop@ietf.org>; Tue, 25 Jun 2013 06:10:04 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id e10so7297371qcy.27 for <dnsop@ietf.org>; Tue, 25 Jun 2013 06:10:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=Fz9XSfx1y+xEWj/Z53jIRB8d9jFWrAq5t4edpL1GXJ8=; b=YQTcKeSeFwEC3VDxDy2CCztpD3gqebX6JByV5b0mFOakSBFFsIcz+1NhGGjVmq6ZIM iv3krJY2DgpSSrACht5MgfdONdS/ZscN4IAhHQ+Jg2Z5x49oHHLuhWmmUIIyGXLjNOhi DdCW8t9xmrOHn93CMZbsQVlCCoaouY0r5ekX0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=Fz9XSfx1y+xEWj/Z53jIRB8d9jFWrAq5t4edpL1GXJ8=; b=P3i3aDrDs8QKgbKQhmuYzLTFOe15Ks2Rofb/fuFrTyiKBSW2c8hQSSYhbNDfZn0Qbk /g777wxOXJQmry5t9XhlvXZ7CMcC9eyQ4sKcPCnY4RmYIiY3pinAu6BB/LBf0IEZPSW1 Wc/+ugkHwEmnlsmSNPMvSPH8m04uob4+SCLvwK39BeDlgxBceNgSeIen5h3RRZupVucq vQztFcFO+zzgYb/EYHKya51qkUM3MQDe7kCPJCHWFvuMMYMRa4ynMF7gNXJ0GsAyV+Oz yvUjhS5RTLWARchVBNOcJ4TAbzHq9n3RpXCKp7JkMAJCBuYrMJJcQw4Mq1Nxsa4+a155 Rs9g==
X-Received: by 10.229.134.139 with SMTP id j11mr1769794qct.23.1372165804010; Tue, 25 Jun 2013 06:10:04 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:3908:f982:aba2:6402? ([2001:4900:1042:100:3908:f982:aba2:6402]) by mx.google.com with ESMTPSA id ng3sm25380156qeb.0.2013.06.25.06.10.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 06:10:03 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=GB2312
From: Joe Abley <jabley@hopcount.ca>
X-Priority: 3
In-Reply-To: <201306252002459685411@cnnic.cn>
Date: Tue, 25 Jun 2013 09:10:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD6B803D-D752-43BC-BDCF-AD01EFD8C816@hopcount.ca>
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com>, <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca> <201306252002459685411@cnnic.cn>
To: dengguangqing <dengguangqing@cnnic.cn>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQlJo98FKx30NrxVsjCFt8Jkddjj2XRKDkUiepZJQfcXzc9eIy3I7OmjcM4rohyOh5v9eaxV
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 13:10:05 -0000

Hi Guangqing,

On 2013-06-25, at 08:02, "Guangqing Deng" <dengguangqing@cnnic.cn> =
wrote:

> Hi, Joe, I like this draft, though I am puzzled by some questions. =
First, the change of=20
> the zone content of an authority server does not mean that a =
corresponding recursive server=20
> has to flush its cache, since a recursive server usually just cache a =
small part of zone content
> of an authority server but not all. Also, an authority server does not =
know which RRs of its=20
> zone content are cached in recursive servers. So such mechanism of DNS =
FLUSH may bring about=20
> some additional traffic between authority and recursive servers with =
no benefit.

I agree that in many cases this is a fairly coarse mechanism; however, =
arguably there are situations where incurring that overhead is better =
than enduring bad data that is widely-cached.

Following the recent incident affecting various .COM names there were =
widespread pleas to resolver operators to "flush your cache". It seems =
likely that some people interpreted that request on face-value, and =
flushed all records from their caches. Flushing just the COM domain (or =
specific sub-domains) would have been better. This mechanism would =
facilitate either of those.

I appreciate the previous paragraph is less than entirely convincing :-)

The BIZ event whereby (it appears from the outside) an apex DNSKEY RRSet =
was published that did not include a key corresponding to the BIZ DS =
RRSet in the root zone would have been another example where flushing =
the entire BIZ domain would have been overkill, but arguably better (for =
validators) than doing nothing.

I agree that it would make little sense for an authority server operator =
in the absence of a problem to flush remote caches every time a new zone =
was published. I would expect specific hooks to be in place to allow =
flush directions to be propagated under manual operator control, rather =
than automatically, triggered by a SOA serial bump.

There is a discontinuity here between the current use of DNS NOTIFY and =
the proposed new use; the former is based on zones, while the latter is =
based on domains. There is an argument here for a new opcode; the reuse =
of NOTIFY seemed expedient when I wrote the draft, but perhaps it's not =
the best way.

> Second, how=20
> does the authority server obtain the IPs of recursive servers? =46rom =
query logs? Then the=20
> authority server sends DNS FLUSH to all or part of recursive servers? =
It seems that there=20
> are big differences between DNS NOTIFY and so called DNS FLUSH and =
thus more things need to=20
> be clarified.

I can think of various models for this.

Bilateral agreements between authority server operators and recursive =
server operators would involve sharing of TSIG secrets as well as server =
addresses. A set of bilats will not scale to the whole Internet, =
obviously, but perhaps is good enough to deal with particular known =
resolvers that serve large communities of users (e.g. Google DNS, =
OpenDNS, Comcast DNS).

A mechanism such as this would enable a clearinghouse style business =
model where resolver operators and authority server operators could =
subscribe to a service that mediated the flush directions between =
authority servers and recursive servers, acting as a trusted =
intermediary.


Joe=

From dengguangqing@cnnic.cn  Tue Jun 25 19:26:28 2013
Return-Path: <dengguangqing@cnnic.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8137C21F9D50 for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 19:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.845
X-Spam-Level: 
X-Spam-Status: No, score=-0.845 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2E2zpz6pSk3m for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 19:26:23 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 215A021F99C7 for <dnsop@ietf.org>; Tue, 25 Jun 2013 19:26:21 -0700 (PDT)
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; Wed, 26 Jun 2013 10:26:09 +0800
Date: Wed, 26 Jun 2013 10:26:09 +0800
From: "Guangqing Deng" <dengguangqing@cnnic.cn>
To: "Joe Abley" <jabley@hopcount.ca>
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com>,  <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca> <201306252002459685411@cnnic.cn>,  <FD6B803D-D752-43BC-BDCF-AD01EFD8C816@hopcount.ca>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.91[cn]
Mime-Version: 1.0
Message-ID: <201306261026086071520@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart634625603845_=----"
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 02:26:28 -0000

This is a multi-part message in MIME format.

------=_001_NextPart634625603845_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGksIEpvZS4gSnVzdCBhcyB5b3Ugc2FpZCwgdGhlIG5lZWQgb2YgZmx1c2hpbmcgY2FjaGUgZXhp
c3RzIHRvIGEgY2VydGFpbiBleHRlbnQuIEJ1dCBtYXliZSBmaXJzdCB3ZSBzaG91bGQgY2hlY2sg
DQp3aHkgdGhlIGNhY2hlIG5lZWRzIHRvIGJlIGZsdXNoZWQuIElzIGl0IGR1ZSB0byBlcnJvcnMg
aW4gem9uZSBmaWxlLCBvdGhlciBjb25maWd1cmF0aW9uIGVycm9ycyBpbiBhdXRob3JpdHkgc2Vy
dmVycw0Kb3IgdGhlIGluZWZmaWNpZW5jeSBvZiBUVEwgbWVjaGFuaXNtPyBGb3IgdGhlIGZpcnN0
IHR3byByZWFzb25zLCBpdCBpcyBiZXR0ZXIgdG8gZG8gb3RoZXIgd29yayB0byBhdm9pZCBzdWNo
IGtpbmRzDQpvZiBlcnJvcnMgYW5kIHRoZW4gY2FjaGUgZmx1c2hpbmcgaXMgYnlwYXNzZWQuIEZv
ciB0aGUgdGhpcmQgcmVhc29uLCBzaG9ydGVuaW5nIHRoZSBUVEwgbWF5IGJlIGEgcG90ZW50aWFs
IGFwcHJvYWNoLCANCmFuZCBhbHNvIEROUyBGTFVTSCBjYW4gYmUgdGFrZW4gYXMgYW4gZWZmZWN0
aXZlIHN1cHBsZW1lbnQgb2YgVFRMIG1lY2hhbmlzbS4gRnVuZGFtZW50YWxseSwgVFRMIG1lY2hh
bmlzbSBpcyBiYXNlZCANCm9uICJwdWxsIiBmYXNoaW9uIHdoaWxlIEROUyBGTFVTSCBzb21laG93
IGlzIGJhc2VkIG9uICJwdXNoIiBmYXNoaW9uLiBBbmQgdGhlbiBob3cgdG8gZWZmZWN0aXZlbHkg
YnJpbmcgdGhlbSB0b2dldGhlcg0KaXMgbm90IGFuIGVhc3kgam9iLiBBbnl3YXksIHRoaXMgZHJh
ZnQgYnJpbmdzIGEgbmV3IGNob2ljZSBmb3IgYXV0aG9yaXR5IHNlcnZlciBvcGVyYXRvcnMgYW5k
IHJlc29sdmVyIHNlcnZlciBvcGVyYXRvcnMuDQoNCg0KDQoNCkd1YW5ncWluZyBEZW5nDQpDTk5J
QyANCg0KRnJvbTogSm9lIEFibGV5DQpEYXRlOiAyMDEzLTA2LTI1IDIxOjEwDQpUbzogZGVuZ2d1
YW5ncWluZw0KQ0M6IGRuc29wQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0ROU09QXSBGd2Q6IE5l
dyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtamFibGV5LWRuc29wLWRucy1mbHVzaC0w
MC50eHQNCkhpIEd1YW5ncWluZywNCg0KT24gMjAxMy0wNi0yNSwgYXQgMDg6MDIsICJHdWFuZ3Fp
bmcgRGVuZyIgPGRlbmdndWFuZ3FpbmdAY25uaWMuY24+IHdyb3RlOg0KDQo+IEhpLCBKb2UsIEkg
bGlrZSB0aGlzIGRyYWZ0LCB0aG91Z2ggSSBhbSBwdXp6bGVkIGJ5IHNvbWUgcXVlc3Rpb25zLiBG
aXJzdCwgdGhlIGNoYW5nZSBvZiANCj4gdGhlIHpvbmUgY29udGVudCBvZiBhbiBhdXRob3JpdHkg
c2VydmVyIGRvZXMgbm90IG1lYW4gdGhhdCBhIGNvcnJlc3BvbmRpbmcgcmVjdXJzaXZlIHNlcnZl
ciANCj4gaGFzIHRvIGZsdXNoIGl0cyBjYWNoZSwgc2luY2UgYSByZWN1cnNpdmUgc2VydmVyIHVz
dWFsbHkganVzdCBjYWNoZSBhIHNtYWxsIHBhcnQgb2Ygem9uZSBjb250ZW50DQo+IG9mIGFuIGF1
dGhvcml0eSBzZXJ2ZXIgYnV0IG5vdCBhbGwuIEFsc28sIGFuIGF1dGhvcml0eSBzZXJ2ZXIgZG9l
cyBub3Qga25vdyB3aGljaCBSUnMgb2YgaXRzIA0KPiB6b25lIGNvbnRlbnQgYXJlIGNhY2hlZCBp
biByZWN1cnNpdmUgc2VydmVycy4gU28gc3VjaCBtZWNoYW5pc20gb2YgRE5TIEZMVVNIIG1heSBi
cmluZyBhYm91dCANCj4gc29tZSBhZGRpdGlvbmFsIHRyYWZmaWMgYmV0d2VlbiBhdXRob3JpdHkg
YW5kIHJlY3Vyc2l2ZSBzZXJ2ZXJzIHdpdGggbm8gYmVuZWZpdC4NCg0KSSBhZ3JlZSB0aGF0IGlu
IG1hbnkgY2FzZXMgdGhpcyBpcyBhIGZhaXJseSBjb2Fyc2UgbWVjaGFuaXNtOyBob3dldmVyLCBh
cmd1YWJseSB0aGVyZSBhcmUgc2l0dWF0aW9ucyB3aGVyZSBpbmN1cnJpbmcgdGhhdCBvdmVyaGVh
ZCBpcyBiZXR0ZXIgdGhhbiBlbmR1cmluZyBiYWQgZGF0YSB0aGF0IGlzIHdpZGVseS1jYWNoZWQu
DQoNCkZvbGxvd2luZyB0aGUgcmVjZW50IGluY2lkZW50IGFmZmVjdGluZyB2YXJpb3VzIC5DT00g
bmFtZXMgdGhlcmUgd2VyZSB3aWRlc3ByZWFkIHBsZWFzIHRvIHJlc29sdmVyIG9wZXJhdG9ycyB0
byAiZmx1c2ggeW91ciBjYWNoZSIuIEl0IHNlZW1zIGxpa2VseSB0aGF0IHNvbWUgcGVvcGxlIGlu
dGVycHJldGVkIHRoYXQgcmVxdWVzdCBvbiBmYWNlLXZhbHVlLCBhbmQgZmx1c2hlZCBhbGwgcmVj
b3JkcyBmcm9tIHRoZWlyIGNhY2hlcy4gRmx1c2hpbmcganVzdCB0aGUgQ09NIGRvbWFpbiAob3Ig
c3BlY2lmaWMgc3ViLWRvbWFpbnMpIHdvdWxkIGhhdmUgYmVlbiBiZXR0ZXIuIFRoaXMgbWVjaGFu
aXNtIHdvdWxkIGZhY2lsaXRhdGUgZWl0aGVyIG9mIHRob3NlLg0KDQpJIGFwcHJlY2lhdGUgdGhl
IHByZXZpb3VzIHBhcmFncmFwaCBpcyBsZXNzIHRoYW4gZW50aXJlbHkgY29udmluY2luZyA6LSkN
Cg0KVGhlIEJJWiBldmVudCB3aGVyZWJ5IChpdCBhcHBlYXJzIGZyb20gdGhlIG91dHNpZGUpIGFu
IGFwZXggRE5TS0VZIFJSU2V0IHdhcyBwdWJsaXNoZWQgdGhhdCBkaWQgbm90IGluY2x1ZGUgYSBr
ZXkgY29ycmVzcG9uZGluZyB0byB0aGUgQklaIERTIFJSU2V0IGluIHRoZSByb290IHpvbmUgd291
bGQgaGF2ZSBiZWVuIGFub3RoZXIgZXhhbXBsZSB3aGVyZSBmbHVzaGluZyB0aGUgZW50aXJlIEJJ
WiBkb21haW4gd291bGQgaGF2ZSBiZWVuIG92ZXJraWxsLCBidXQgYXJndWFibHkgYmV0dGVyIChm
b3IgdmFsaWRhdG9ycykgdGhhbiBkb2luZyBub3RoaW5nLg0KDQpJIGFncmVlIHRoYXQgaXQgd291
bGQgbWFrZSBsaXR0bGUgc2Vuc2UgZm9yIGFuIGF1dGhvcml0eSBzZXJ2ZXIgb3BlcmF0b3IgaW4g
dGhlIGFic2VuY2Ugb2YgYSBwcm9ibGVtIHRvIGZsdXNoIHJlbW90ZSBjYWNoZXMgZXZlcnkgdGlt
ZSBhIG5ldyB6b25lIHdhcyBwdWJsaXNoZWQuIEkgd291bGQgZXhwZWN0IHNwZWNpZmljIGhvb2tz
IHRvIGJlIGluIHBsYWNlIHRvIGFsbG93IGZsdXNoIGRpcmVjdGlvbnMgdG8gYmUgcHJvcGFnYXRl
ZCB1bmRlciBtYW51YWwgb3BlcmF0b3IgY29udHJvbCwgcmF0aGVyIHRoYW4gYXV0b21hdGljYWxs
eSwgdHJpZ2dlcmVkIGJ5IGEgU09BIHNlcmlhbCBidW1wLg0KDQpUaGVyZSBpcyBhIGRpc2NvbnRp
bnVpdHkgaGVyZSBiZXR3ZWVuIHRoZSBjdXJyZW50IHVzZSBvZiBETlMgTk9USUZZIGFuZCB0aGUg
cHJvcG9zZWQgbmV3IHVzZTsgdGhlIGZvcm1lciBpcyBiYXNlZCBvbiB6b25lcywgd2hpbGUgdGhl
IGxhdHRlciBpcyBiYXNlZCBvbiBkb21haW5zLiBUaGVyZSBpcyBhbiBhcmd1bWVudCBoZXJlIGZv
ciBhIG5ldyBvcGNvZGU7IHRoZSByZXVzZSBvZiBOT1RJRlkgc2VlbWVkIGV4cGVkaWVudCB3aGVu
IEkgd3JvdGUgdGhlIGRyYWZ0LCBidXQgcGVyaGFwcyBpdCdzIG5vdCB0aGUgYmVzdCB3YXkuDQoN
Cj4gU2Vjb25kLCBob3cgDQo+IGRvZXMgdGhlIGF1dGhvcml0eSBzZXJ2ZXIgb2J0YWluIHRoZSBJ
UHMgb2YgcmVjdXJzaXZlIHNlcnZlcnM/IEZyb20gcXVlcnkgbG9ncz8gVGhlbiB0aGUgDQo+IGF1
dGhvcml0eSBzZXJ2ZXIgc2VuZHMgRE5TIEZMVVNIIHRvIGFsbCBvciBwYXJ0IG9mIHJlY3Vyc2l2
ZSBzZXJ2ZXJzPyBJdCBzZWVtcyB0aGF0IHRoZXJlIA0KPiBhcmUgYmlnIGRpZmZlcmVuY2VzIGJl
dHdlZW4gRE5TIE5PVElGWSBhbmQgc28gY2FsbGVkIEROUyBGTFVTSCBhbmQgdGh1cyBtb3JlIHRo
aW5ncyBuZWVkIHRvIA0KPiBiZSBjbGFyaWZpZWQuDQoNCkkgY2FuIHRoaW5rIG9mIHZhcmlvdXMg
bW9kZWxzIGZvciB0aGlzLg0KDQpCaWxhdGVyYWwgYWdyZWVtZW50cyBiZXR3ZWVuIGF1dGhvcml0
eSBzZXJ2ZXIgb3BlcmF0b3JzIGFuZCByZWN1cnNpdmUgc2VydmVyIG9wZXJhdG9ycyB3b3VsZCBp
bnZvbHZlIHNoYXJpbmcgb2YgVFNJRyBzZWNyZXRzIGFzIHdlbGwgYXMgc2VydmVyIGFkZHJlc3Nl
cy4gQSBzZXQgb2YgYmlsYXRzIHdpbGwgbm90IHNjYWxlIHRvIHRoZSB3aG9sZSBJbnRlcm5ldCwg
b2J2aW91c2x5LCBidXQgcGVyaGFwcyBpcyBnb29kIGVub3VnaCB0byBkZWFsIHdpdGggcGFydGlj
dWxhciBrbm93biByZXNvbHZlcnMgdGhhdCBzZXJ2ZSBsYXJnZSBjb21tdW5pdGllcyBvZiB1c2Vy
cyAoZS5nLiBHb29nbGUgRE5TLCBPcGVuRE5TLCBDb21jYXN0IEROUykuDQoNCkEgbWVjaGFuaXNt
IHN1Y2ggYXMgdGhpcyB3b3VsZCBlbmFibGUgYSBjbGVhcmluZ2hvdXNlIHN0eWxlIGJ1c2luZXNz
IG1vZGVsIHdoZXJlIHJlc29sdmVyIG9wZXJhdG9ycyBhbmQgYXV0aG9yaXR5IHNlcnZlciBvcGVy
YXRvcnMgY291bGQgc3Vic2NyaWJlIHRvIGEgc2VydmljZSB0aGF0IG1lZGlhdGVkIHRoZSBmbHVz
aCBkaXJlY3Rpb25zIGJldHdlZW4gYXV0aG9yaXR5IHNlcnZlcnMgYW5kIHJlY3Vyc2l2ZSBzZXJ2
ZXJzLCBhY3RpbmcgYXMgYSB0cnVzdGVkIGludGVybWVkaWFyeS4NCg0KDQpKb2U=

------=_001_NextPart634625603845_=----
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dgb2312" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: verdana; COLOR: #000000; FONT-SIZE: 10pt
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18156"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV style=3D"FONT-FAMILY: Verdana">
<DIV>Hi,&nbsp;Joe.&nbsp;Just&nbsp;as&nbsp;you&nbsp;said,&nbsp;the&nbsp;nee=
d&nbsp;of&nbsp;flushing&nbsp;cache&nbsp;exists&nbsp;to&nbsp;a&nbsp;certain=
&nbsp;extent.&nbsp;But&nbsp;maybe&nbsp;first&nbsp;we&nbsp;should&nbsp;chec=
k&nbsp;</DIV>
<DIV>why&nbsp;the&nbsp;cache&nbsp;needs&nbsp;to&nbsp;be&nbsp;flushed.&nbsp=
;Is&nbsp;it&nbsp;due&nbsp;to&nbsp;errors&nbsp;in&nbsp;zone&nbsp;file,&nbsp=
;other&nbsp;configuration&nbsp;errors&nbsp;in&nbsp;authority&nbsp;servers<=
/DIV>
<DIV>or&nbsp;the&nbsp;inefficiency&nbsp;of&nbsp;TTL&nbsp;mechanism?&nbsp;F=
or&nbsp;the&nbsp;first&nbsp;two&nbsp;reasons,&nbsp;it&nbsp;is&nbsp;better&=
nbsp;to&nbsp;do&nbsp;other&nbsp;work&nbsp;to&nbsp;avoid&nbsp;such&nbsp;kin=
ds</DIV>
<DIV>of&nbsp;errors&nbsp;and&nbsp;then&nbsp;cache&nbsp;flushing&nbsp;is&nb=
sp;bypassed.&nbsp;For&nbsp;the&nbsp;third&nbsp;reason,&nbsp;shortening&nbs=
p;the&nbsp;TTL&nbsp;may&nbsp;be&nbsp;a&nbsp;potential&nbsp;approach,&nbsp;=
</DIV>
<DIV>and&nbsp;also&nbsp;DNS&nbsp;FLUSH&nbsp;can&nbsp;be&nbsp;taken&nbsp;as=
&nbsp;an&nbsp;effective&nbsp;supplement&nbsp;of&nbsp;TTL&nbsp;mechanism.&n=
bsp;Fundamentally,&nbsp;TTL&nbsp;mechanism&nbsp;is&nbsp;based&nbsp;</DIV>
<DIV>on&nbsp;"pull"&nbsp;fashion&nbsp;while&nbsp;DNS&nbsp;FLUSH&nbsp;someh=
ow&nbsp;is&nbsp;based&nbsp;on&nbsp;"push"&nbsp;fashion.&nbsp;And&nbsp;then=
&nbsp;how&nbsp;to&nbsp;effectively&nbsp;bring&nbsp;them&nbsp;together</DIV=
>
<DIV>is&nbsp;not&nbsp;an&nbsp;easy&nbsp;job.&nbsp;Anyway,&nbsp;this&nbsp;d=
raft&nbsp;brings&nbsp;a&nbsp;new&nbsp;choice&nbsp;for&nbsp;authority&nbsp;=
server&nbsp;operators&nbsp;and&nbsp;resolver&nbsp;server&nbsp;operators.</=
DIV></DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV style=3D"FONT-FAMILY: Verdana"><SPAN>
<DIV><SPAN style=3D"FONT-FAMILY: =CB=CE=CC=E5; COLOR: #000000; FONT-SIZE: =
10.5pt">Guangqing=20
Deng</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: =CB=CE=CC=E5; COLOR: #000000; FONT-SIZE: 10.5pt">CNN=
IC&nbsp;</SPAN></DIV></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:jabley@hopcount.ca">Joe Abley</A>=
</DIV>
<DIV><B>Date:</B>&nbsp;2013-06-25&nbsp;21:10</DIV>
<DIV><B>To:</B>&nbsp;<A=20
href=3D"mailto:dengguangqing@cnnic.cn">dengguangqing</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:dnsop@ietf.org">dnsop@ietf.org</A><=
/DIV>
<DIV><B>Subject:</B>&nbsp;Re: [DNSOP] Fwd: New Version Notification for=20
draft-jabley-dnsop-dns-flush-00.txt</DIV></DIV></DIV>
<DIV>
<DIV>Hi&nbsp;Guangqing,</DIV>
<DIV>&nbsp;</DIV>
<DIV>On&nbsp;2013-06-25,&nbsp;at&nbsp;08:02,&nbsp;"Guangqing&nbsp;Deng"&nb=
sp;&lt;dengguangqing@cnnic.cn&gt;&nbsp;wrote:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&nbsp;Hi,&nbsp;Joe,&nbsp;I&nbsp;like&nbsp;this&nbsp;draft,&nbsp;t=
hough&nbsp;I&nbsp;am&nbsp;puzzled&nbsp;by&nbsp;some&nbsp;questions.&nbsp;F=
irst,&nbsp;the&nbsp;change&nbsp;of&nbsp;</DIV>
<DIV>&gt;&nbsp;the&nbsp;zone&nbsp;content&nbsp;of&nbsp;an&nbsp;authority&n=
bsp;server&nbsp;does&nbsp;not&nbsp;mean&nbsp;that&nbsp;a&nbsp;correspondin=
g&nbsp;recursive&nbsp;server&nbsp;</DIV>
<DIV>&gt;&nbsp;has&nbsp;to&nbsp;flush&nbsp;its&nbsp;cache,&nbsp;since&nbsp=
;a&nbsp;recursive&nbsp;server&nbsp;usually&nbsp;just&nbsp;cache&nbsp;a&nbs=
p;small&nbsp;part&nbsp;of&nbsp;zone&nbsp;content</DIV>
<DIV>&gt;&nbsp;of&nbsp;an&nbsp;authority&nbsp;server&nbsp;but&nbsp;not&nbs=
p;all.&nbsp;Also,&nbsp;an&nbsp;authority&nbsp;server&nbsp;does&nbsp;not&nb=
sp;know&nbsp;which&nbsp;RRs&nbsp;of&nbsp;its&nbsp;</DIV>
<DIV>&gt;&nbsp;zone&nbsp;content&nbsp;are&nbsp;cached&nbsp;in&nbsp;recursi=
ve&nbsp;servers.&nbsp;So&nbsp;such&nbsp;mechanism&nbsp;of&nbsp;DNS&nbsp;FL=
USH&nbsp;may&nbsp;bring&nbsp;about&nbsp;</DIV>
<DIV>&gt;&nbsp;some&nbsp;additional&nbsp;traffic&nbsp;between&nbsp;authori=
ty&nbsp;and&nbsp;recursive&nbsp;servers&nbsp;with&nbsp;no&nbsp;benefit.</D=
IV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;agree&nbsp;that&nbsp;in&nbsp;many&nbsp;cases&nbsp;this&nbsp;is=
&nbsp;a&nbsp;fairly&nbsp;coarse&nbsp;mechanism;&nbsp;however,&nbsp;arguabl=
y&nbsp;there&nbsp;are&nbsp;situations&nbsp;where&nbsp;incurring&nbsp;that&=
nbsp;overhead&nbsp;is&nbsp;better&nbsp;than&nbsp;enduring&nbsp;bad&nbsp;da=
ta&nbsp;that&nbsp;is&nbsp;widely-cached.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Following&nbsp;the&nbsp;recent&nbsp;incident&nbsp;affecting&nbsp;vari=
ous&nbsp;.COM&nbsp;names&nbsp;there&nbsp;were&nbsp;widespread&nbsp;pleas&n=
bsp;to&nbsp;resolver&nbsp;operators&nbsp;to&nbsp;"flush&nbsp;your&nbsp;cac=
he".&nbsp;It&nbsp;seems&nbsp;likely&nbsp;that&nbsp;some&nbsp;people&nbsp;i=
nterpreted&nbsp;that&nbsp;request&nbsp;on&nbsp;face-value,&nbsp;and&nbsp;f=
lushed&nbsp;all&nbsp;records&nbsp;from&nbsp;their&nbsp;caches.&nbsp;Flushi=
ng&nbsp;just&nbsp;the&nbsp;COM&nbsp;domain&nbsp;(or&nbsp;specific&nbsp;sub=
-domains)&nbsp;would&nbsp;have&nbsp;been&nbsp;better.&nbsp;This&nbsp;mecha=
nism&nbsp;would&nbsp;facilitate&nbsp;either&nbsp;of&nbsp;those.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;appreciate&nbsp;the&nbsp;previous&nbsp;paragraph&nbsp;is&nbsp;=
less&nbsp;than&nbsp;entirely&nbsp;convincing&nbsp;:-)</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;BIZ&nbsp;event&nbsp;whereby&nbsp;(it&nbsp;appears&nbsp;from&=
nbsp;the&nbsp;outside)&nbsp;an&nbsp;apex&nbsp;DNSKEY&nbsp;RRSet&nbsp;was&n=
bsp;published&nbsp;that&nbsp;did&nbsp;not&nbsp;include&nbsp;a&nbsp;key&nbs=
p;corresponding&nbsp;to&nbsp;the&nbsp;BIZ&nbsp;DS&nbsp;RRSet&nbsp;in&nbsp;=
the&nbsp;root&nbsp;zone&nbsp;would&nbsp;have&nbsp;been&nbsp;another&nbsp;e=
xample&nbsp;where&nbsp;flushing&nbsp;the&nbsp;entire&nbsp;BIZ&nbsp;domain&=
nbsp;would&nbsp;have&nbsp;been&nbsp;overkill,&nbsp;but&nbsp;arguably&nbsp;=
better&nbsp;(for&nbsp;validators)&nbsp;than&nbsp;doing&nbsp;nothing.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;agree&nbsp;that&nbsp;it&nbsp;would&nbsp;make&nbsp;little&nbsp;=
sense&nbsp;for&nbsp;an&nbsp;authority&nbsp;server&nbsp;operator&nbsp;in&nb=
sp;the&nbsp;absence&nbsp;of&nbsp;a&nbsp;problem&nbsp;to&nbsp;flush&nbsp;re=
mote&nbsp;caches&nbsp;every&nbsp;time&nbsp;a&nbsp;new&nbsp;zone&nbsp;was&n=
bsp;published.&nbsp;I&nbsp;would&nbsp;expect&nbsp;specific&nbsp;hooks&nbsp=
;to&nbsp;be&nbsp;in&nbsp;place&nbsp;to&nbsp;allow&nbsp;flush&nbsp;directio=
ns&nbsp;to&nbsp;be&nbsp;propagated&nbsp;under&nbsp;manual&nbsp;operator&nb=
sp;control,&nbsp;rather&nbsp;than&nbsp;automatically,&nbsp;triggered&nbsp;=
by&nbsp;a&nbsp;SOA&nbsp;serial&nbsp;bump.</DIV>
<DIV>&nbsp;</DIV>
<DIV>There&nbsp;is&nbsp;a&nbsp;discontinuity&nbsp;here&nbsp;between&nbsp;t=
he&nbsp;current&nbsp;use&nbsp;of&nbsp;DNS&nbsp;NOTIFY&nbsp;and&nbsp;the&nb=
sp;proposed&nbsp;new&nbsp;use;&nbsp;the&nbsp;former&nbsp;is&nbsp;based&nbs=
p;on&nbsp;zones,&nbsp;while&nbsp;the&nbsp;latter&nbsp;is&nbsp;based&nbsp;o=
n&nbsp;domains.&nbsp;There&nbsp;is&nbsp;an&nbsp;argument&nbsp;here&nbsp;fo=
r&nbsp;a&nbsp;new&nbsp;opcode;&nbsp;the&nbsp;reuse&nbsp;of&nbsp;NOTIFY&nbs=
p;seemed&nbsp;expedient&nbsp;when&nbsp;I&nbsp;wrote&nbsp;the&nbsp;draft,&n=
bsp;but&nbsp;perhaps&nbsp;it's&nbsp;not&nbsp;the&nbsp;best&nbsp;way.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&nbsp;Second,&nbsp;how&nbsp;</DIV>
<DIV>&gt;&nbsp;does&nbsp;the&nbsp;authority&nbsp;server&nbsp;obtain&nbsp;t=
he&nbsp;IPs&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;From&nbsp;query&nbsp=
;logs?&nbsp;Then&nbsp;the&nbsp;</DIV>
<DIV>&gt;&nbsp;authority&nbsp;server&nbsp;sends&nbsp;DNS&nbsp;FLUSH&nbsp;t=
o&nbsp;all&nbsp;or&nbsp;part&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;It&=
nbsp;seems&nbsp;that&nbsp;there&nbsp;</DIV>
<DIV>&gt;&nbsp;are&nbsp;big&nbsp;differences&nbsp;between&nbsp;DNS&nbsp;NO=
TIFY&nbsp;and&nbsp;so&nbsp;called&nbsp;DNS&nbsp;FLUSH&nbsp;and&nbsp;thus&n=
bsp;more&nbsp;things&nbsp;need&nbsp;to&nbsp;</DIV>
<DIV>&gt;&nbsp;be&nbsp;clarified.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;can&nbsp;think&nbsp;of&nbsp;various&nbsp;models&nbsp;for&nbsp;=
this.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Bilateral&nbsp;agreements&nbsp;between&nbsp;authority&nbsp;server&nbs=
p;operators&nbsp;and&nbsp;recursive&nbsp;server&nbsp;operators&nbsp;would&=
nbsp;involve&nbsp;sharing&nbsp;of&nbsp;TSIG&nbsp;secrets&nbsp;as&nbsp;well=
&nbsp;as&nbsp;server&nbsp;addresses.&nbsp;A&nbsp;set&nbsp;of&nbsp;bilats&n=
bsp;will&nbsp;not&nbsp;scale&nbsp;to&nbsp;the&nbsp;whole&nbsp;Internet,&nb=
sp;obviously,&nbsp;but&nbsp;perhaps&nbsp;is&nbsp;good&nbsp;enough&nbsp;to&=
nbsp;deal&nbsp;with&nbsp;particular&nbsp;known&nbsp;resolvers&nbsp;that&nb=
sp;serve&nbsp;large&nbsp;communities&nbsp;of&nbsp;users&nbsp;(e.g.&nbsp;Go=
ogle&nbsp;DNS,&nbsp;OpenDNS,&nbsp;Comcast&nbsp;DNS).</DIV>
<DIV>&nbsp;</DIV>
<DIV>A&nbsp;mechanism&nbsp;such&nbsp;as&nbsp;this&nbsp;would&nbsp;enable&n=
bsp;a&nbsp;clearinghouse&nbsp;style&nbsp;business&nbsp;model&nbsp;where&nb=
sp;resolver&nbsp;operators&nbsp;and&nbsp;authority&nbsp;server&nbsp;operat=
ors&nbsp;could&nbsp;subscribe&nbsp;to&nbsp;a&nbsp;service&nbsp;that&nbsp;m=
ediated&nbsp;the&nbsp;flush&nbsp;directions&nbsp;between&nbsp;authority&nb=
sp;servers&nbsp;and&nbsp;recursive&nbsp;servers,&nbsp;acting&nbsp;as&nbsp;=
a&nbsp;trusted&nbsp;intermediary.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Joe</DIV></DIV></BODY></HTML>

------=_001_NextPart634625603845_=------


From jewforice@gmail.com  Tue Jun 25 22:39:04 2013
Return-Path: <jewforice@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E18A221E809D for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 22:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DX0N6LaLOGN7 for <dnsop@ietfa.amsl.com>; Tue, 25 Jun 2013 22:39:03 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 17B1C21E8053 for <dnsop@ietf.org>; Tue, 25 Jun 2013 22:39:02 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id d10so1282356lbj.0 for <dnsop@ietf.org>; Tue, 25 Jun 2013 22:39:01 -0700 (PDT)
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=FlZ2by6hNRlb2x+mzDVRP+fBg0qu/f3ADWPMNF1/tTg=; b=NVuU74vPD2t67FIGk9JhGpqsSv/YBDQ+aT2H3Z9WoCdZNk7QVDhBPfnDQyIZ+41vny wt3PBuerPN57Vsgyo/TlaicWb+lPHgA0Ss2kdj2RP1kkhkiX8/K/YQWLYZDRfuJ1L4N/ ozdtWurDpfXni3AmFl8Vn/jU211hzWhhSWsphe7mhwPSnYMAN09NHa0Agktm7GgsYeck dotuQSqTZGJhr4DPHc4ZcCUoUKDt061sc3TLqHJmUCwWlEJ+0FYWShiSnAYx9v/iK7Pl BU5XWzgSUx/9fJ3WbShS58vOvKS+tat75bf6bTOF+Wnp9qr4JGds0lbqIgzz4ze/Auqn Xpgg==
MIME-Version: 1.0
X-Received: by 10.152.4.65 with SMTP id i1mr1098635lai.21.1372225141590; Tue, 25 Jun 2013 22:39:01 -0700 (PDT)
Received: by 10.114.174.200 with HTTP; Tue, 25 Jun 2013 22:39:01 -0700 (PDT)
In-Reply-To: <201306261026086071520@cnnic.cn>
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com> <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca> <201306252002459685411@cnnic.cn> <FD6B803D-D752-43BC-BDCF-AD01EFD8C816@hopcount.ca> <201306261026086071520@cnnic.cn>
Date: Wed, 26 Jun 2013 13:39:01 +0800
Message-ID: <CAB3ZD+=UuVEi48GFMuEp2OwqZVQzKfbZts3z03f9m6P8M_NjJw@mail.gmail.com>
From: ice jew <jewforice@gmail.com>
To: Guangqing Deng <dengguangqing@cnnic.cn>
Content-Type: multipart/alternative; boundary=089e014933801dd0a704e0081065
Cc: dnsop <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 05:39:05 -0000

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

This draft does provide some new possibility for decrease the negative
effects for the authority name server's mis-configuration in a certain way.
But I don't think it will work in the real world  even if all prerequisites
are meant.

First, there is standard way to solve this problem, as Guanqing says, it's
to shorten the TTL (both positive and negative cache). This may lead to
load increase for the authority name servers and  recursive resolver. But
this method take the least risk.

Second, I think it won't work under the condition that  the recursive
resolver and the cache name server are deprived. The authority cleans the
 cache of the recursive resolver from the log  but the cache name server
won't go to the recursive resolver for a newer  response until the TTL is
expired.  And the bad data in to cache name server still responses to the
incoming queries. The cleaning-cache-mechanism doesn't help to decrease the
negative effect.



On Wed, Jun 26, 2013 at 10:26 AM, Guangqing Deng <dengguangqing@cnnic.cn>wr=
ote:

> **
>
> Hi, Joe. Just as you said, the need of flushing cache exists to a certain=
 extent. But maybe first we should check
>
> why the cache needs to be flushed. Is it due to errors in zone file, othe=
r configuration errors in authority servers
>
> or the inefficiency of TTL mechanism? For the first two reasons, it is be=
tter to do other work to avoid such kinds
>
> of errors and then cache flushing is bypassed. For the third reason, shor=
tening the TTL may be a potential approach,
>
> and also DNS FLUSH can be taken as an effective supplement of TTL mechani=
sm. Fundamentally, TTL mechanism is based
>
> on "pull" fashion while DNS FLUSH somehow is based on "push" fashion. And=
 then how to effectively bring them together
>
> is not an easy job. Anyway, this draft brings a new choice for authority =
server operators and resolver server operators.
>
> ------------------------------
>  Guangqing Deng
> CNNIC
>
>  *From:* Joe Abley <jabley@hopcount.ca>
> *Date:* 2013-06-25 21:10
> *To:* dengguangqing <dengguangqing@cnnic.cn>
> *CC:* dnsop@ietf.org
> *Subject:* Re: [DNSOP] Fwd: New Version Notification for
> draft-jabley-dnsop-dns-flush-00.txt
>  Hi Guangqing,
>
> On 2013-06-25, at 08:02, "Guangqing Deng" <dengguangqing@cnnic.cn> wrote:
>
>
> > Hi, Joe, I like this draft, though I am puzzled by some questions. Firs=
t, the change of
>
> > the zone content of an authority server does not mean that a correspond=
ing recursive server
>
> > has to flush its cache, since a recursive server usually just cache a s=
mall part of zone content
>
> > of an authority server but not all. Also, an authority server does not =
know which RRs of its
>
> > zone content are cached in recursive servers. So such mechanism of DNS =
FLUSH may bring about
>
> > some additional traffic between authority and recursive servers with no=
 benefit.
>
>
> I agree that in many cases this is a fairly coarse mechanism; however, ar=
guably there are situations where incurring that overhead is better than en=
during bad data that is widely-cached.
>
>
> Following the recent incident affecting various .COM names there were wid=
espread pleas to resolver operators to "flush your cache". It seems likely =
that some people interpreted that request on face-value, and flushed all re=
cords from their caches. Flushing just the COM domain (or specific sub-doma=
ins) would have been better. This mechanism would facilitate either of thos=
e.
>
> I appreciate the previous paragraph is less than entirely convincing :-)
>
>
> The BIZ event whereby (it appears from the outside) an apex DNSKEY RRSet =
was published that did not include a key corresponding to the BIZ DS RRSet =
in the root zone would have been another example where flushing the entire =
BIZ domain would have been overkill, but arguably better (for validators) t=
han doing nothing.
>
>
> I agree that it would make little sense for an authority server operator =
in the absence of a problem to flush remote caches every time a new zone wa=
s published. I would expect specific hooks to be in place to allow flush di=
rections to be propagated under manual operator control, rather than automa=
tically, triggered by a SOA serial bump.
>
>
> There is a discontinuity here between the current use of DNS NOTIFY and t=
he proposed new use; the former is based on zones, while the latter is base=
d on domains. There is an argument here for a new opcode; the reuse of NOTI=
FY seemed expedient when I wrote the draft, but perhaps it's not the best w=
ay.
>
> > Second, how
>
> > does the authority server obtain the IPs of recursive servers? From que=
ry logs? Then the
>
> > authority server sends DNS FLUSH to all or part of recursive servers? I=
t seems that there
>
> > are big differences between DNS NOTIFY and so called DNS FLUSH and thus=
 more things need to
> > be clarified.
>
> I can think of various models for this.
>
>
> Bilateral agreements between authority server operators and recursive ser=
ver operators would involve sharing of TSIG secrets as well as server addre=
sses. A set of bilats will not scale to the whole Internet, obviously, but =
perhaps is good enough to deal with particular known resolvers that serve l=
arge communities of users (e.g. Google DNS, OpenDNS, Comcast DNS).
>
>
> A mechanism such as this would enable a clearinghouse style business mode=
l where resolver operators and authority server operators could subscribe t=
o a service that mediated the flush directions between authority servers an=
d recursive servers, acting as a trusted intermediary.
>
>
> Joe
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>

--089e014933801dd0a704e0081065
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This draft does provide some new possibility for decrease =
the negative effects for the authority name server&#39;s mis-configuration =
in a certain way. But I don&#39;t think it will work in the real world &nbs=
p;even if all prerequisites are meant.<div>
<br><div style>First, there is standard way to solve this problem, as Guanq=
ing says, it&#39;s to shorten the TTL (both positive and negative cache). T=
his may lead to load increase for the authority name servers and &nbsp;recu=
rsive resolver. But this method take the least risk.</div>
<div style><br></div><div style>Second, I think it won&#39;t work under the=
 condition that &nbsp;the recursive resolver and the cache name server are =
deprived. The authority cleans the &nbsp;cache of the recursive resolver fr=
om the log &nbsp;but the cache name server won&#39;t go to the recursive re=
solver for a newer &nbsp;response until the TTL is expired. &nbsp;And the b=
ad data in to cache name server still responses to the incoming queries. Th=
e cleaning-cache-mechanism doesn&#39;t help to decrease the negative effect=
.</div>
</div><div style><br></div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Wed, Jun 26, 2013 at 10:26 AM, Guangqing Deng <span =
dir=3D"ltr">&lt;<a href=3D"mailto:dengguangqing@cnnic.cn" target=3D"_blank"=
>dengguangqing@cnnic.cn</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"><u></u>





<div style=3D"MARGIN:10px">
<div style=3D"FONT-FAMILY:Verdana">
<div>Hi,&nbsp;Joe.&nbsp;Just&nbsp;as&nbsp;you&nbsp;said,&nbsp;the&nbsp;need=
&nbsp;of&nbsp;flushing&nbsp;cache&nbsp;exists&nbsp;to&nbsp;a&nbsp;certain&n=
bsp;extent.&nbsp;But&nbsp;maybe&nbsp;first&nbsp;we&nbsp;should&nbsp;check&n=
bsp;</div>
<div>why&nbsp;the&nbsp;cache&nbsp;needs&nbsp;to&nbsp;be&nbsp;flushed.&nbsp;=
Is&nbsp;it&nbsp;due&nbsp;to&nbsp;errors&nbsp;in&nbsp;zone&nbsp;file,&nbsp;o=
ther&nbsp;configuration&nbsp;errors&nbsp;in&nbsp;authority&nbsp;servers</di=
v>
<div>or&nbsp;the&nbsp;inefficiency&nbsp;of&nbsp;TTL&nbsp;mechanism?&nbsp;Fo=
r&nbsp;the&nbsp;first&nbsp;two&nbsp;reasons,&nbsp;it&nbsp;is&nbsp;better&nb=
sp;to&nbsp;do&nbsp;other&nbsp;work&nbsp;to&nbsp;avoid&nbsp;such&nbsp;kinds<=
/div>
<div>of&nbsp;errors&nbsp;and&nbsp;then&nbsp;cache&nbsp;flushing&nbsp;is&nbs=
p;bypassed.&nbsp;For&nbsp;the&nbsp;third&nbsp;reason,&nbsp;shortening&nbsp;=
the&nbsp;TTL&nbsp;may&nbsp;be&nbsp;a&nbsp;potential&nbsp;approach,&nbsp;</d=
iv>
<div>and&nbsp;also&nbsp;DNS&nbsp;FLUSH&nbsp;can&nbsp;be&nbsp;taken&nbsp;as&=
nbsp;an&nbsp;effective&nbsp;supplement&nbsp;of&nbsp;TTL&nbsp;mechanism.&nbs=
p;Fundamentally,&nbsp;TTL&nbsp;mechanism&nbsp;is&nbsp;based&nbsp;</div>
<div>on&nbsp;&quot;pull&quot;&nbsp;fashion&nbsp;while&nbsp;DNS&nbsp;FLUSH&n=
bsp;somehow&nbsp;is&nbsp;based&nbsp;on&nbsp;&quot;push&quot;&nbsp;fashion.&=
nbsp;And&nbsp;then&nbsp;how&nbsp;to&nbsp;effectively&nbsp;bring&nbsp;them&n=
bsp;together</div>
<div>is&nbsp;not&nbsp;an&nbsp;easy&nbsp;job.&nbsp;Anyway,&nbsp;this&nbsp;dr=
aft&nbsp;brings&nbsp;a&nbsp;new&nbsp;choice&nbsp;for&nbsp;authority&nbsp;se=
rver&nbsp;operators&nbsp;and&nbsp;resolver&nbsp;server&nbsp;operators.</div=
></div>
<div>&nbsp;</div>
<hr style=3D"WIDTH:210px;min-height:1px" align=3D"left" color=3D"#b5c4df" s=
ize=3D"1">

<div style=3D"FONT-FAMILY:Verdana"><span>
<div><span style=3D"font-size:10.5pt;font-family:=CB=CE=CC=E5">Guangqing=20
Deng</span></div>
<div><span style=3D"font-size:10.5pt;font-family:=CB=CE=CC=E5">CNNIC&nbsp;<=
/span></div></span></div>
<div>&nbsp;</div>
<div style=3D"BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOT=
TOM:0cm;PADDING-LEFT:0cm;PADDING-RIGHT:0cm;BORDER-TOP:#b5c4df 1pt solid;BOR=
DER-RIGHT:medium none;PADDING-TOP:3pt">
<div style=3D"padding-right:8px;padding-left:8px;padding-top:8px;font-size:=
12px;background:#efefef;padding-bottom:8px">
<div><b>From:</b>&nbsp;<a href=3D"mailto:jabley@hopcount.ca" target=3D"_bla=
nk">Joe Abley</a></div>
<div><b>Date:</b>&nbsp;2013-06-25&nbsp;21:10</div>
<div><b>To:</b>&nbsp;<a href=3D"mailto:dengguangqing@cnnic.cn" target=3D"_b=
lank">dengguangqing</a></div>
<div><b>CC:</b>&nbsp;<a href=3D"mailto:dnsop@ietf.org" target=3D"_blank">dn=
sop@ietf.org</a></div>
<div><b>Subject:</b>&nbsp;Re: [DNSOP] Fwd: New Version Notification for=20
draft-jabley-dnsop-dns-flush-00.txt</div></div></div><div><div class=3D"h5"=
>
<div>
<div>Hi&nbsp;Guangqing,</div>
<div>&nbsp;</div>
<div>On&nbsp;2013-06-25,&nbsp;at&nbsp;08:02,&nbsp;&quot;Guangqing&nbsp;Deng=
&quot;&nbsp;&lt;<a href=3D"mailto:dengguangqing@cnnic.cn" target=3D"_blank"=
>dengguangqing@cnnic.cn</a>&gt;&nbsp;wrote:</div>
<div>&nbsp;</div>
<div>&gt;&nbsp;Hi,&nbsp;Joe,&nbsp;I&nbsp;like&nbsp;this&nbsp;draft,&nbsp;th=
ough&nbsp;I&nbsp;am&nbsp;puzzled&nbsp;by&nbsp;some&nbsp;questions.&nbsp;Fir=
st,&nbsp;the&nbsp;change&nbsp;of&nbsp;</div>
<div>&gt;&nbsp;the&nbsp;zone&nbsp;content&nbsp;of&nbsp;an&nbsp;authority&nb=
sp;server&nbsp;does&nbsp;not&nbsp;mean&nbsp;that&nbsp;a&nbsp;corresponding&=
nbsp;recursive&nbsp;server&nbsp;</div>
<div>&gt;&nbsp;has&nbsp;to&nbsp;flush&nbsp;its&nbsp;cache,&nbsp;since&nbsp;=
a&nbsp;recursive&nbsp;server&nbsp;usually&nbsp;just&nbsp;cache&nbsp;a&nbsp;=
small&nbsp;part&nbsp;of&nbsp;zone&nbsp;content</div>
<div>&gt;&nbsp;of&nbsp;an&nbsp;authority&nbsp;server&nbsp;but&nbsp;not&nbsp=
;all.&nbsp;Also,&nbsp;an&nbsp;authority&nbsp;server&nbsp;does&nbsp;not&nbsp=
;know&nbsp;which&nbsp;RRs&nbsp;of&nbsp;its&nbsp;</div>
<div>&gt;&nbsp;zone&nbsp;content&nbsp;are&nbsp;cached&nbsp;in&nbsp;recursiv=
e&nbsp;servers.&nbsp;So&nbsp;such&nbsp;mechanism&nbsp;of&nbsp;DNS&nbsp;FLUS=
H&nbsp;may&nbsp;bring&nbsp;about&nbsp;</div>
<div>&gt;&nbsp;some&nbsp;additional&nbsp;traffic&nbsp;between&nbsp;authorit=
y&nbsp;and&nbsp;recursive&nbsp;servers&nbsp;with&nbsp;no&nbsp;benefit.</div=
>
<div>&nbsp;</div>
<div>I&nbsp;agree&nbsp;that&nbsp;in&nbsp;many&nbsp;cases&nbsp;this&nbsp;is&=
nbsp;a&nbsp;fairly&nbsp;coarse&nbsp;mechanism;&nbsp;however,&nbsp;arguably&=
nbsp;there&nbsp;are&nbsp;situations&nbsp;where&nbsp;incurring&nbsp;that&nbs=
p;overhead&nbsp;is&nbsp;better&nbsp;than&nbsp;enduring&nbsp;bad&nbsp;data&n=
bsp;that&nbsp;is&nbsp;widely-cached.</div>
<div>&nbsp;</div>
<div>Following&nbsp;the&nbsp;recent&nbsp;incident&nbsp;affecting&nbsp;vario=
us&nbsp;.COM&nbsp;names&nbsp;there&nbsp;were&nbsp;widespread&nbsp;pleas&nbs=
p;to&nbsp;resolver&nbsp;operators&nbsp;to&nbsp;&quot;flush&nbsp;your&nbsp;c=
ache&quot;.&nbsp;It&nbsp;seems&nbsp;likely&nbsp;that&nbsp;some&nbsp;people&=
nbsp;interpreted&nbsp;that&nbsp;request&nbsp;on&nbsp;face-value,&nbsp;and&n=
bsp;flushed&nbsp;all&nbsp;records&nbsp;from&nbsp;their&nbsp;caches.&nbsp;Fl=
ushing&nbsp;just&nbsp;the&nbsp;COM&nbsp;domain&nbsp;(or&nbsp;specific&nbsp;=
sub-domains)&nbsp;would&nbsp;have&nbsp;been&nbsp;better.&nbsp;This&nbsp;mec=
hanism&nbsp;would&nbsp;facilitate&nbsp;either&nbsp;of&nbsp;those.</div>

<div>&nbsp;</div>
<div>I&nbsp;appreciate&nbsp;the&nbsp;previous&nbsp;paragraph&nbsp;is&nbsp;l=
ess&nbsp;than&nbsp;entirely&nbsp;convincing&nbsp;:-)</div>
<div>&nbsp;</div>
<div>The&nbsp;BIZ&nbsp;event&nbsp;whereby&nbsp;(it&nbsp;appears&nbsp;from&n=
bsp;the&nbsp;outside)&nbsp;an&nbsp;apex&nbsp;DNSKEY&nbsp;RRSet&nbsp;was&nbs=
p;published&nbsp;that&nbsp;did&nbsp;not&nbsp;include&nbsp;a&nbsp;key&nbsp;c=
orresponding&nbsp;to&nbsp;the&nbsp;BIZ&nbsp;DS&nbsp;RRSet&nbsp;in&nbsp;the&=
nbsp;root&nbsp;zone&nbsp;would&nbsp;have&nbsp;been&nbsp;another&nbsp;exampl=
e&nbsp;where&nbsp;flushing&nbsp;the&nbsp;entire&nbsp;BIZ&nbsp;domain&nbsp;w=
ould&nbsp;have&nbsp;been&nbsp;overkill,&nbsp;but&nbsp;arguably&nbsp;better&=
nbsp;(for&nbsp;validators)&nbsp;than&nbsp;doing&nbsp;nothing.</div>

<div>&nbsp;</div>
<div>I&nbsp;agree&nbsp;that&nbsp;it&nbsp;would&nbsp;make&nbsp;little&nbsp;s=
ense&nbsp;for&nbsp;an&nbsp;authority&nbsp;server&nbsp;operator&nbsp;in&nbsp=
;the&nbsp;absence&nbsp;of&nbsp;a&nbsp;problem&nbsp;to&nbsp;flush&nbsp;remot=
e&nbsp;caches&nbsp;every&nbsp;time&nbsp;a&nbsp;new&nbsp;zone&nbsp;was&nbsp;=
published.&nbsp;I&nbsp;would&nbsp;expect&nbsp;specific&nbsp;hooks&nbsp;to&n=
bsp;be&nbsp;in&nbsp;place&nbsp;to&nbsp;allow&nbsp;flush&nbsp;directions&nbs=
p;to&nbsp;be&nbsp;propagated&nbsp;under&nbsp;manual&nbsp;operator&nbsp;cont=
rol,&nbsp;rather&nbsp;than&nbsp;automatically,&nbsp;triggered&nbsp;by&nbsp;=
a&nbsp;SOA&nbsp;serial&nbsp;bump.</div>

<div>&nbsp;</div>
<div>There&nbsp;is&nbsp;a&nbsp;discontinuity&nbsp;here&nbsp;between&nbsp;th=
e&nbsp;current&nbsp;use&nbsp;of&nbsp;DNS&nbsp;NOTIFY&nbsp;and&nbsp;the&nbsp=
;proposed&nbsp;new&nbsp;use;&nbsp;the&nbsp;former&nbsp;is&nbsp;based&nbsp;o=
n&nbsp;zones,&nbsp;while&nbsp;the&nbsp;latter&nbsp;is&nbsp;based&nbsp;on&nb=
sp;domains.&nbsp;There&nbsp;is&nbsp;an&nbsp;argument&nbsp;here&nbsp;for&nbs=
p;a&nbsp;new&nbsp;opcode;&nbsp;the&nbsp;reuse&nbsp;of&nbsp;NOTIFY&nbsp;seem=
ed&nbsp;expedient&nbsp;when&nbsp;I&nbsp;wrote&nbsp;the&nbsp;draft,&nbsp;but=
&nbsp;perhaps&nbsp;it&#39;s&nbsp;not&nbsp;the&nbsp;best&nbsp;way.</div>

<div>&nbsp;</div>
<div>&gt;&nbsp;Second,&nbsp;how&nbsp;</div>
<div>&gt;&nbsp;does&nbsp;the&nbsp;authority&nbsp;server&nbsp;obtain&nbsp;th=
e&nbsp;IPs&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;From&nbsp;query&nbsp;l=
ogs?&nbsp;Then&nbsp;the&nbsp;</div>
<div>&gt;&nbsp;authority&nbsp;server&nbsp;sends&nbsp;DNS&nbsp;FLUSH&nbsp;to=
&nbsp;all&nbsp;or&nbsp;part&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;It&nb=
sp;seems&nbsp;that&nbsp;there&nbsp;</div>
<div>&gt;&nbsp;are&nbsp;big&nbsp;differences&nbsp;between&nbsp;DNS&nbsp;NOT=
IFY&nbsp;and&nbsp;so&nbsp;called&nbsp;DNS&nbsp;FLUSH&nbsp;and&nbsp;thus&nbs=
p;more&nbsp;things&nbsp;need&nbsp;to&nbsp;</div>
<div>&gt;&nbsp;be&nbsp;clarified.</div>
<div>&nbsp;</div>
<div>I&nbsp;can&nbsp;think&nbsp;of&nbsp;various&nbsp;models&nbsp;for&nbsp;t=
his.</div>
<div>&nbsp;</div>
<div>Bilateral&nbsp;agreements&nbsp;between&nbsp;authority&nbsp;server&nbsp=
;operators&nbsp;and&nbsp;recursive&nbsp;server&nbsp;operators&nbsp;would&nb=
sp;involve&nbsp;sharing&nbsp;of&nbsp;TSIG&nbsp;secrets&nbsp;as&nbsp;well&nb=
sp;as&nbsp;server&nbsp;addresses.&nbsp;A&nbsp;set&nbsp;of&nbsp;bilats&nbsp;=
will&nbsp;not&nbsp;scale&nbsp;to&nbsp;the&nbsp;whole&nbsp;Internet,&nbsp;ob=
viously,&nbsp;but&nbsp;perhaps&nbsp;is&nbsp;good&nbsp;enough&nbsp;to&nbsp;d=
eal&nbsp;with&nbsp;particular&nbsp;known&nbsp;resolvers&nbsp;that&nbsp;serv=
e&nbsp;large&nbsp;communities&nbsp;of&nbsp;users&nbsp;(e.g.&nbsp;Google&nbs=
p;DNS,&nbsp;OpenDNS,&nbsp;Comcast&nbsp;DNS).</div>

<div>&nbsp;</div>
<div>A&nbsp;mechanism&nbsp;such&nbsp;as&nbsp;this&nbsp;would&nbsp;enable&nb=
sp;a&nbsp;clearinghouse&nbsp;style&nbsp;business&nbsp;model&nbsp;where&nbsp=
;resolver&nbsp;operators&nbsp;and&nbsp;authority&nbsp;server&nbsp;operators=
&nbsp;could&nbsp;subscribe&nbsp;to&nbsp;a&nbsp;service&nbsp;that&nbsp;media=
ted&nbsp;the&nbsp;flush&nbsp;directions&nbsp;between&nbsp;authority&nbsp;se=
rvers&nbsp;and&nbsp;recursive&nbsp;servers,&nbsp;acting&nbsp;as&nbsp;a&nbsp=
;trusted&nbsp;intermediary.</div>

<div>&nbsp;</div>
<div>&nbsp;</div>
<div>Joe</div></div></div></div></div>
<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>
<br></blockquote></div><br></div>

--089e014933801dd0a704e0081065--

From warren@kumari.net  Wed Jun 26 11:14:19 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C15411E81C7 for <dnsop@ietfa.amsl.com>; Wed, 26 Jun 2013 11:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nwxjgn0CCupm for <dnsop@ietfa.amsl.com>; Wed, 26 Jun 2013 11:14:14 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FCAB11E8117 for <dnsop@ietf.org>; Wed, 26 Jun 2013 11:14:14 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 98D411B40088; Wed, 26 Jun 2013 14:14:13 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51C96B62.9030401@nlnetlabs.nl>
Date: Wed, 26 Jun 2013 14:14:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BAB0DCE9-BBA1-4108-813C-F806D4E7F9B1@kumari.net>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@nlnetlabs.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 18:14:19 -0000

On Jun 25, 2013, at 6:05 AM, Matthijs Mekking <matthijs@nlnetlabs.nl> =
wrote:

> Hi,
>=20
> On 06/21/2013 11:58 PM, Wes Hardaker wrote:
>> Paul Wouters <paul@cypherpunks.ca> writes:
>>=20
>>> I am in favour of adopting this draft as a WG item.
>>=20
>> Ditto.
>=20
> Another ditto. I am pleased to see that there is still activity on the
> topic of automating the synchronization between DNSKEY at the child =
and
> the DS at the parent.

Thank you all.

We are still awaiting the official kickoff of the Call for Adoption. I'm =
*assuming* the chairs will be willing to accept these as demonstration =
of support.=20
If you respond to the official CfA as well, please also indicate if you =
are willing to review (I believe DNSOP wants 5 folk who support *and are =
willing to review*).

>=20
>=20
>>> I don't think the CDS record should be able to cause a child domain =
to
>>> go from secure to insecure, or from insecure to secure. That
>>> (infrequent) change should have an additional authentication, eg via =
EPP
>>> or otherwise)
>>=20
>> Ditto.  I think the goal of any of the automatic update techniques
>> should be to make the routine easy but it shouldn't be a goal to =
handle
>> the infrequent, and challenging cases.  (infrequent and easy is =
fine).
>>=20
>> Unless we can show a clear, secured, path for some transition I don't
>> think it's worth solving.
>=20
> Another ditto. Agreeing with it's not worth solving to deal with the
> irregular cases. Going unsigned is an irregular case.
>=20
>=20
> Also backing a previous made comment by other people:
>=20
> * I prefer to have the CDS wire format to be similar to the DS wire
> format. With the current draft, it is already possible to automate all
> possible key rollovers, no need for managerial hooks to say this =
record
> is proposed, must be added, deleted, is valid for only this period =
etc.

Thanks.

>=20
>=20
> Comments on the draft (apologies for its length):

*No* need to apologize for length -- we really appreciate detailed =
feedback.=20
We will be having a meeting later this afternoon and will discuss your =
comments -- at a quick glance they all seem sane and worthwhile to me=85

Thanks again,
W

>=20
> * Nit: In section 1, it says there may be two interactions with the
> parent. This could also be only one, this could be more in some freaky
> rollovers, so I would prefer that it reads: "there may be one ore more
> interactions with the parent".
>=20
> * Section 3. I appreciate that most ZSK /KSK terminology is carefully
> replaced with, but in section 3 is still something that itches: "The =
SEP
> bit is an optional bit to indicate that the key is allowed to sign the
> DNSKEY RRset". That is not true. Without the SEP bit, the key may also
> sign the DNSKEY RRset.
>=20
> * Section 3.1.1. As said above, I don't like the idea of using the CDS
> record to go unsigned.
>=20
> * Nit: Section 4.1. I think the last paragraph fits better in section
> 4.2. CDS Consumption.
>=20
> * Section 4.2. About the polling strategy. I am wondering how well =
this
> scales with respect to the number of delegations.
>=20
> * Section 4.2. It is suggested that RFC 5011-like hold down timers are
> being used, e.g. new keying information must be published for a month
> before acceptance as a new trust anchor. This makes the duration of =
key
> rollovers unnecessary long. The hold down timers in RFC 5011 are there
> to mitigate against a compromise. The compromise allows the attacker =
to
> sign data in the zone.
>=20
> Similar we could look at a compromise that allows the attacker to =
upload
> a DS/DNSKEY to the parent. However, there are no mechanisms to =
mitigate
> against this attack. Why should we have mitigation for the CDS =
proposal,
> if there is none for the current mechanism?
>=20
> The difference between CDS and RFC 5011 is the location of the trust
> anchor your are updating. With CDS, you are updating the DS in the
> parent. With RFC 5011, you are updating lots of trust anchors in the
> wild. The latter may indeed require a bit more conservative approach.
>=20
> * Section 4.3. I wonder if the SHOULD in the first sentence should be =
a
> MUST.
>=20
> * Section 4.4. I dislike the idea of the side effect of parent
> calculates DS, so I would like to see that only the "augment" mode is
> supported (where I think it should read: "it will make sure there are
> CDS records for the digest algorithm(s) it require(s)" (CDS instead of
> DS)).
>=20
> The publishing "Future DNSKEYs" does not go well with several rollover
> scenarios (those based on Double-DS). I am wondering if the policy is
> "We calculate the DS" or "We decide the digest algorithm". In case of
> the latter, then augment mode can be used to support this. In case of
> the first, the future DNSKEY is really required to be published, and
> Double-DS based rollovers are not possible in combination with CDS.
>=20
> * Section 6. Security Considerations. The last paragraph. Isn't this
> solved by saying that the Parental Agent MUST ensure that old versions
> of the CDS RRset do not override newer versions in section 4.3. Usage?
> There is already a proposed method on how to achieve this there.
>=20
> * When implementing a prototype for this in OpenDNSSEC, I questioned
> myself what value I should use for the TTL. We could consider 0, as =
this
> record is not really intended for the resolver. We could also use the
> TTL to suggest a polling frequency for the parental agent. Just some
> thoughts.
>=20
>=20
> Best regards,
>  Matthijs
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> *
>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20

--=20
No man is an island, But if you take a bunch of dead guys and tie them =
together, they make a pretty good raft.
                --Anon.



From ed.lewis@neustar.biz  Thu Jun 27 06:02:43 2013
Return-Path: <ed.lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F1D21F9B65 for <dnsop@ietfa.amsl.com>; Thu, 27 Jun 2013 06:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.868
X-Spam-Level: 
X-Spam-Status: No, score=-101.868 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQ1VX3xdoA28 for <dnsop@ietfa.amsl.com>; Thu, 27 Jun 2013 06:02:39 -0700 (PDT)
Received: from smtp135.dfw.emailsrvr.com (smtp135.dfw.emailsrvr.com [67.192.241.135]) by ietfa.amsl.com (Postfix) with ESMTP id CB39821F9D45 for <dnsop@ietf.org>; Thu, 27 Jun 2013 06:02:34 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp13.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 7751A3D02A7; Thu, 27 Jun 2013 09:02:32 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp13.relay.dfw1a.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id 0972B3D0107;  Thu, 27 Jun 2013 09:02:31 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FFE7CE84-A602-4884-8B52-BF2B7A659F0A"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net>
Date: Thu, 27 Jun 2013 09:02:35 -0400
Message-Id: <3DB464D5-8076-47DE-B56B-44398B0209DE@neustar.biz>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net>
To: IETF DNSOP WG <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 13:02:43 -0000

--Apple-Mail=_FFE7CE84-A602-4884-8B52-BF2B7A659F0A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

In the land of looking for support to take this on, the WG should.  =
Adoption by the WG or not, I'm taking this seriously and will help =
engineer this through to solution.

On Jun 17, 2013, at 13:32, Warren Kumari wrote:

> Hi there all,
>=20
> We have just posted a new version of draft-kumari-ogud-dnsop-cds=20
>=20
> This incorporates comments from both the list and in person =
discussions.=20
>=20
> The authors believe this version is ready for WG adoption and request =
the DNSOP chairs to kick off an adoption call.
>=20
> W
>=20
>=20
> Begin forwarded message:
>=20
>> From: internet-drafts@ietf.org
>> Subject: New Version Notification for =
draft-kumari-ogud-dnsop-cds-02.txt
>> Date: June 17, 2013 12:58:29 PM EDT
>> To: Olafur Gudmundsson <ogud@ogud.com>, Warren Kumari =
<warren@kumari.net>, George Barwood <george.barwood@blueyonder.co.uk>
>>=20
>>=20
>> A new version of I-D, draft-kumari-ogud-dnsop-cds-02.txt
>> has been successfully submitted by Warren Kumari and posted to the
>> IETF repository.
>>=20
>> Filename:	 draft-kumari-ogud-dnsop-cds
>> Revision:	 02
>> Title:		 Automating DNSSEC delegation trust maintenance
>> Creation date:	 2013-06-17
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             =
http://www.ietf.org/internet-drafts/draft-kumari-ogud-dnsop-cds-02.txt
>> Status:          =
http://datatracker.ietf.org/doc/draft-kumari-ogud-dnsop-cds
>> Htmlized:        =
http://tools.ietf.org/html/draft-kumari-ogud-dnsop-cds-02
>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kumari-ogud-dnsop-cds-02
>>=20
>> 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.
>>=20
>>=20
>>=20
>>=20
>> The IETF Secretariat
>>=20
>=20
> --
> "Let's just say that if complete and utter chaos was lightning, he'd =
be the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."
>=20
>    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)
>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_FFE7CE84-A602-4884-8B52-BF2B7A659F0A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>In the land of looking for support to take this on, the WG =
should. &nbsp;Adoption by the WG or not, I'm taking this seriously and =
will help engineer this through to solution.</div><br><div><div>On Jun =
17, 2013, at 13:32, Warren Kumari wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Hi =
there all,<br><br>We have just posted a new version of =
draft-kumari-ogud-dnsop-cds <br><br>This incorporates comments from both =
the list and in person discussions. <br><br>The authors believe this =
version is ready for WG adoption and request the DNSOP chairs to kick =
off an adoption call.<br><br>W<br><br><br>Begin forwarded =
message:<br><br><blockquote type=3D"cite">From: <a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/blockquote><blockquote type=3D"cite">Subject: New Version Notification =
for draft-kumari-ogud-dnsop-cds-02.txt<br></blockquote><blockquote =
type=3D"cite">Date: June 17, 2013 12:58:29 PM =
EDT<br></blockquote><blockquote type=3D"cite">To: Olafur Gudmundsson =
&lt;<a href=3D"mailto:ogud@ogud.com">ogud@ogud.com</a>&gt;, Warren =
Kumari &lt;<a href=3D"mailto:warren@kumari.net">warren@kumari.net</a>&gt;,=
 George Barwood &lt;<a =
href=3D"mailto:george.barwood@blueyonder.co.uk">george.barwood@blueyonder.=
co.uk</a>&gt;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">A new version =
of I-D, draft-kumari-ogud-dnsop-cds-02.txt<br></blockquote><blockquote =
type=3D"cite">has been successfully submitted by Warren Kumari and =
posted to the<br></blockquote><blockquote type=3D"cite">IETF =
repository.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Filename:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
draft-kumari-ogud-dnsop-cds<br></blockquote><blockquote =
type=3D"cite">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> 02<br></blockquote><blockquote =
type=3D"cite">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> Automating DNSSEC delegation =
trust maintenance<br></blockquote><blockquote type=3D"cite">Creation =
date:<span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
2013-06-17<br></blockquote><blockquote type=3D"cite">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></blockquote><blockquote type=3D"cite">Number =
of pages: 14<br></blockquote><blockquote type=3D"cite">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a=
 =
href=3D"http://www.ietf.org/internet-drafts/draft-kumari-ogud-dnsop-cds-02=
.txt">http://www.ietf.org/internet-drafts/draft-kumari-ogud-dnsop-cds-02.t=
xt</a><br></blockquote><blockquote type=3D"cite">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-kumari-ogud-dnsop-cds">http:=
//datatracker.ietf.org/doc/draft-kumari-ogud-dnsop-cds</a><br></blockquote=
><blockquote type=3D"cite">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-kumari-ogud-dnsop-cds-02">http://=
tools.ietf.org/html/draft-kumari-ogud-dnsop-cds-02</a><br></blockquote><bl=
ockquote type=3D"cite">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-kumari-ogud-dnsop-cds-02"=
>http://www.ietf.org/rfcdiff?url2=3Ddraft-kumari-ogud-dnsop-cds-02</a><br>=
</blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Abstract:<br></blockquote><blockquote type=3D"cite"> =
&nbsp;This document describes a method to allow DNS operators to =
more<br></blockquote><blockquote type=3D"cite"> &nbsp;easily update =
DNSSEC Key Signing Keys using DNS as =
communication<br></blockquote><blockquote type=3D"cite"> &nbsp;channel. =
&nbsp;This document does not address the initial configuration =
of<br></blockquote><blockquote type=3D"cite"> &nbsp;trust anchors for a =
domain.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The IETF =
Secretariat<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>--<br>"Let's just say that if =
complete and utter chaos was lightning, he'd be the sort to stand on a =
hilltop in a thunderstorm wearing wet copper armour and shouting 'All =
gods are bastards'."<br><br> &nbsp;&nbsp;&nbsp;-- Rincewind discussing =
Twoflower (Terry Pratchett, The Colour of =
Magic)<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></div></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></body></html>=

--Apple-Mail=_FFE7CE84-A602-4884-8B52-BF2B7A659F0A--

From warren@kumari.net  Thu Jun 27 07:55:48 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1564C21F9D57 for <dnsop@ietfa.amsl.com>; Thu, 27 Jun 2013 07:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQf05moQ-FlN for <dnsop@ietfa.amsl.com>; Thu, 27 Jun 2013 07:55:22 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2796F21F9D4F for <dnsop@ietf.org>; Thu, 27 Jun 2013 07:55:20 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 3424F1B40A6A; Thu, 27 Jun 2013 10:55:19 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <3DB464D5-8076-47DE-B56B-44398B0209DE@neustar.biz>
Date: Thu, 27 Jun 2013 10:55:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6A3A882-1854-4654-A29E-6B76ED65130F@kumari.net>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <3DB464D5-8076-47DE-B56B-44398B0209DE@neustar.biz>
To: Edward Lewis <ed.lewis@neustar.biz>
X-Mailer: Apple Mail (2.1508)
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 14:55:48 -0000

On Jun 27, 2013, at 9:02 AM, Edward Lewis <ed.lewis@neustar.biz> wrote:

> In the land of looking for support to take this on, the WG should.  =
Adoption by the WG or not, I'm taking this seriously and will help =
engineer this through to solution.

Thank you.=20

Now we just need the chairs to wave the terrible thurible, thereby =
incensing the censer[0] and officially kick off a CfA.

W

[0]: Horribly contrived, I know, but couldn't resist.

>=20
> On Jun 17, 2013, at 13:32, Warren Kumari wrote:
>=20
>> Hi there all,
>>=20
>> We have just posted a new version of draft-kumari-ogud-dnsop-cds=20
>>=20
>> This incorporates comments from both the list and in person =
discussions.=20
>>=20
>> The authors believe this version is ready for WG adoption and request =
the DNSOP chairs to kick off an adoption call.
>>=20
>> W
>>=20
>>=20
>> Begin forwarded message:
>>=20
>>> From: internet-drafts@ietf.org
>>> Subject: New Version Notification for =
draft-kumari-ogud-dnsop-cds-02.txt
>>> Date: June 17, 2013 12:58:29 PM EDT
>>> To: Olafur Gudmundsson <ogud@ogud.com>, Warren Kumari =
<warren@kumari.net>, George Barwood <george.barwood@blueyonder.co.uk>
>>>=20
>>>=20
>>> A new version of I-D, draft-kumari-ogud-dnsop-cds-02.txt
>>> has been successfully submitted by Warren Kumari and posted to the
>>> IETF repository.
>>>=20
>>> Filename:	 draft-kumari-ogud-dnsop-cds
>>> Revision:	 02
>>> Title:		 Automating DNSSEC delegation trust maintenance
>>> Creation date:	 2013-06-17
>>> Group:		 Individual Submission
>>> Number of pages: 14
>>> URL:             =
http://www.ietf.org/internet-drafts/draft-kumari-ogud-dnsop-cds-02.txt
>>> Status:          =
http://datatracker.ietf.org/doc/draft-kumari-ogud-dnsop-cds
>>> Htmlized:        =
http://tools.ietf.org/html/draft-kumari-ogud-dnsop-cds-02
>>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kumari-ogud-dnsop-cds-02
>>>=20
>>> 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.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat
>>>=20
>>=20
>> --
>> "Let's just say that if complete and utter chaos was lightning, he'd =
be the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."
>>=20
>>    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)
>>=20
>>=20
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>=20
> =
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
> Edward Lewis            =20
> NeuStar                    You can leave a voice message at =
+1-571-434-5468
>=20
> There are no answers - just tradeoffs, decisions, and responses.
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

--=20
No man is an island, But if you take a bunch of dead guys and tie them =
together, they make a pretty good raft.
                --Anon.



From tim.wicinski@teamaol.com  Fri Jun 28 01:57:14 2013
Return-Path: <tim.wicinski@teamaol.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5E5921F9E40 for <dnsop@ietfa.amsl.com>; Fri, 28 Jun 2013 01:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iNEE6WXB235t for <dnsop@ietfa.amsl.com>; Fri, 28 Jun 2013 01:57:05 -0700 (PDT)
Received: from omr-m01.mx.aol.com (omr-m01.mx.aol.com [64.12.143.75]) by ietfa.amsl.com (Postfix) with ESMTP id 0991321F9E22 for <dnsop@ietf.org>; Fri, 28 Jun 2013 01:56:59 -0700 (PDT)
Received: from aoldtcmei32.ad.aol.aoltw.net (aoldtcmei32.office.aol.com [10.180.121.111]) by omr-m01.mx.aol.com (Outbound Mail Relay) with ESMTP id 08932700000B2; Fri, 28 Jun 2013 04:56:57 -0400 (EDT)
Received: from still.local (172.17.8.193) by aoldtcmei32.ad.aol.aoltw.net (10.180.121.111) with Microsoft SMTP Server id 14.3.123.3; Fri, 28 Jun 2013 04:56:56 -0400
Message-ID: <51CD4FD7.80904@teamaol.com>
Date: Fri, 28 Jun 2013 04:56:55 -0400
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: ice jew <jewforice@gmail.com>, Guangqing Deng <dengguangqing@cnnic.cn>
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com>	<806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca>	<201306252002459685411@cnnic.cn>	<FD6B803D-D752-43BC-BDCF-AD01EFD8C816@hopcount.ca>	<201306261026086071520@cnnic.cn> <CAB3ZD+=UuVEi48GFMuEp2OwqZVQzKfbZts3z03f9m6P8M_NjJw@mail.gmail.com>
In-Reply-To: <CAB3ZD+=UuVEi48GFMuEp2OwqZVQzKfbZts3z03f9m6P8M_NjJw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060305070604090309010302"
X-Originating-IP: [172.17.8.193]
Cc: dnsop <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 08:57:14 -0000

--------------060305070604090309010302
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Actually flushing resolver caches in  larger environments (data 
center/enterprise/etc) where even short TTLs doesn't quite handle 
unexpected events, and there is a need to have consistent answers, even 
if the consistency is NXDOMAIN.

I don't know if the NOTIFY semantic mechanism (while a simple way of 
avoiding creating a new mechanism) is the correct method.

tim

On 6/26/13 1:39 AM, ice jew wrote:
> This draft does provide some new possibility for decrease the negative 
> effects for the authority name server's mis-configuration in a certain 
> way. But I don't think it will work in the real world  even if all 
> prerequisites are meant.
>
> First, there is standard way to solve this problem, as Guanqing says, 
> it's to shorten the TTL (both positive and negative cache). This may 
> lead to load increase for the authority name servers and  recursive 
> resolver. But this method take the least risk.
>
> Second, I think it won't work under the condition that  the recursive 
> resolver and the cache name server are deprived. The authority cleans 
> the  cache of the recursive resolver from the log  but the cache name 
> server won't go to the recursive resolver for a newer  response until 
> the TTL is expired.  And the bad data in to cache name server still 
> responses to the incoming queries. The cleaning-cache-mechanism 
> doesn't help to decrease the negative effect.
>
>
>
> On Wed, Jun 26, 2013 at 10:26 AM, Guangqing Deng 
> <dengguangqing@cnnic.cn <mailto:dengguangqing@cnnic.cn>> wrote:
>
>     Hi, Joe. Just as you said, the need of flushing cache exists to a certain extent. But maybe first we should check
>
>     why the cache needs to be flushed. Is it due to errors in zone file, other configuration errors in authority servers
>     or the inefficiency of TTL mechanism? For the first two reasons, it is better to do other work to avoid such kinds
>     of errors and then cache flushing is bypassed. For the third reason, shortening the TTL may be a potential approach,
>
>     and also DNS FLUSH can be taken as an effective supplement of TTL mechanism. Fundamentally, TTL mechanism is based
>
>     on "pull" fashion while DNS FLUSH somehow is based on "push" fashion. And then how to effectively bring them together
>     is not an easy job. Anyway, this draft brings a new choice for authority server operators and resolver server operators.
>     ------------------------------------------------------------------------
>     Guangqing Deng
>     CNNIC
>     *From:* Joe Abley <mailto:jabley@hopcount.ca>
>     *Date:* 2013-06-25 21:10
>     *To:* dengguangqing <mailto:dengguangqing@cnnic.cn>
>     *CC:* dnsop@ietf.org <mailto:dnsop@ietf.org>
>     *Subject:* Re: [DNSOP] Fwd: New Version Notification for
>     draft-jabley-dnsop-dns-flush-00.txt
>     Hi Guangqing,
>     On 2013-06-25, at 08:02, "Guangqing Deng" <dengguangqing@cnnic.cn
>     <mailto:dengguangqing@cnnic.cn>> wrote:
>     > Hi, Joe, I like this draft, though I am puzzled by some questions. First, the change of
>
>     > the zone content of an authority server does not mean that a corresponding recursive server
>
>     > has to flush its cache, since a recursive server usually just cache a small part of zone content
>     > of an authority server but not all. Also, an authority server does not know which RRs of its
>
>     > zone content are cached in recursive servers. So such mechanism of DNS FLUSH may bring about
>
>     > some additional traffic between authority and recursive servers with no benefit.
>     I agree that in many cases this is a fairly coarse mechanism; however, arguably there are situations where incurring that overhead is better than enduring bad data that is widely-cached.
>     Following the recent incident affecting various .COM names there were widespread pleas to resolver operators to "flush your cache". It seems likely that some people interpreted that request on face-value, and flushed all records from their caches. Flushing just the COM domain (or specific sub-domains) would have been better. This mechanism would facilitate either of those.
>     I appreciate the previous paragraph is less than entirely convincing :-)
>     The BIZ event whereby (it appears from the outside) an apex DNSKEY RRSet was published that did not include a key corresponding to the BIZ DS RRSet in the root zone would have been another example where flushing the entire BIZ domain would have been overkill, but arguably better (for validators) than doing nothing.
>     I agree that it would make little sense for an authority server operator in the absence of a problem to flush remote caches every time a new zone was published. I would expect specific hooks to be in place to allow flush directions to be propagated under manual operator control, rather than automatically, triggered by a SOA serial bump.
>     There is a discontinuity here between the current use of DNS NOTIFY and the proposed new use; the former is based on zones, while the latter is based on domains. There is an argument here for a new opcode; the reuse of NOTIFY seemed expedient when I wrote the draft, but perhaps it's not the best way.
>     > Second, how
>     > does the authority server obtain the IPs of recursive servers? From query logs? Then the
>
>     > authority server sends DNS FLUSH to all or part of recursive servers? It seems that there
>
>     > are big differences between DNS NOTIFY and so called DNS FLUSH and thus more things need to
>
>     > be clarified.
>     I can think of various models for this.
>     Bilateral agreements between authority server operators and recursive server operators would involve sharing of TSIG secrets as well as server addresses. A set of bilats will not scale to the whole Internet, obviously, but perhaps is good enough to deal with particular known resolvers that serve large communities of users (e.g. Google DNS, OpenDNS, Comcast DNS).
>     A mechanism such as this would enable a clearinghouse style business model where resolver operators and authority server operators could subscribe to a service that mediated the flush directions between authority servers and recursive servers, acting as a trusted intermediary.
>     Joe
>
>     _______________________________________________
>     DNSOP mailing list
>     DNSOP@ietf.org <mailto:DNSOP@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dnsop
>
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--------------060305070604090309010302
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 text="#000000" bgcolor="#FFFFFF">
    <tt>Actually flushing resolver caches in&nbsp; larger environments (data
      center/enterprise/etc) where even short TTLs doesn't quite handle
      unexpected events, and there is a need to have consistent answers,
      even if the consistency is NXDOMAIN. <br>
      <br>
      I don't know if the NOTIFY semantic mechanism (while a simple way
      of avoiding creating a new mechanism) is the correct method.<br>
      <br>
      tim<br>
      &nbsp;<br>
    </tt>
    <div class="moz-cite-prefix">On 6/26/13 1:39 AM, ice jew wrote:<br>
    </div>
    <blockquote
cite="mid:CAB3ZD+=UuVEi48GFMuEp2OwqZVQzKfbZts3z03f9m6P8M_NjJw@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr">This draft does provide some new possibility for
        decrease the negative effects for the authority name server's
        mis-configuration in a certain way. But I don't think it will
        work in the real world &nbsp;even if all prerequisites are meant.
        <div>
          <br>
          <div style="">First, there is standard way to solve this
            problem, as Guanqing says, it's to shorten the TTL (both
            positive and negative cache). This may lead to load increase
            for the authority name servers and &nbsp;recursive resolver. But
            this method take the least risk.</div>
          <div style=""><br>
          </div>
          <div style="">Second, I think it won't work under the
            condition that &nbsp;the recursive resolver and the cache name
            server are deprived. The authority cleans the &nbsp;cache of the
            recursive resolver from the log &nbsp;but the cache name server
            won't go to the recursive resolver for a newer &nbsp;response
            until the TTL is expired. &nbsp;And the bad data in to cache name
            server still responses to the incoming queries. The
            cleaning-cache-mechanism doesn't help to decrease the
            negative effect.</div>
        </div>
        <div style=""><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Wed, Jun 26, 2013 at 10:26 AM,
          Guangqing Deng <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:dengguangqing@cnnic.cn" target="_blank">dengguangqing@cnnic.cn</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div style="MARGIN:10px">
              <div style="FONT-FAMILY:Verdana">
                <div>Hi,&nbsp;Joe.&nbsp;Just&nbsp;as&nbsp;you&nbsp;said,&nbsp;the&nbsp;need&nbsp;of&nbsp;flushing&nbsp;cache&nbsp;exists&nbsp;to&nbsp;a&nbsp;certain&nbsp;extent.&nbsp;But&nbsp;maybe&nbsp;first&nbsp;we&nbsp;should&nbsp;check&nbsp;</div>
                <div>why&nbsp;the&nbsp;cache&nbsp;needs&nbsp;to&nbsp;be&nbsp;flushed.&nbsp;Is&nbsp;it&nbsp;due&nbsp;to&nbsp;errors&nbsp;in&nbsp;zone&nbsp;file,&nbsp;other&nbsp;configuration&nbsp;errors&nbsp;in&nbsp;authority&nbsp;servers</div>
                <div>or&nbsp;the&nbsp;inefficiency&nbsp;of&nbsp;TTL&nbsp;mechanism?&nbsp;For&nbsp;the&nbsp;first&nbsp;two&nbsp;reasons,&nbsp;it&nbsp;is&nbsp;better&nbsp;to&nbsp;do&nbsp;other&nbsp;work&nbsp;to&nbsp;avoid&nbsp;such&nbsp;kinds</div>
                <div>of&nbsp;errors&nbsp;and&nbsp;then&nbsp;cache&nbsp;flushing&nbsp;is&nbsp;bypassed.&nbsp;For&nbsp;the&nbsp;third&nbsp;reason,&nbsp;shortening&nbsp;the&nbsp;TTL&nbsp;may&nbsp;be&nbsp;a&nbsp;potential&nbsp;approach,&nbsp;</div>
                <div>and&nbsp;also&nbsp;DNS&nbsp;FLUSH&nbsp;can&nbsp;be&nbsp;taken&nbsp;as&nbsp;an&nbsp;effective&nbsp;supplement&nbsp;of&nbsp;TTL&nbsp;mechanism.&nbsp;Fundamentally,&nbsp;TTL&nbsp;mechanism&nbsp;is&nbsp;based&nbsp;</div>
                <div>on&nbsp;"pull"&nbsp;fashion&nbsp;while&nbsp;DNS&nbsp;FLUSH&nbsp;somehow&nbsp;is&nbsp;based&nbsp;on&nbsp;"push"&nbsp;fashion.&nbsp;And&nbsp;then&nbsp;how&nbsp;to&nbsp;effectively&nbsp;bring&nbsp;them&nbsp;together</div>
                <div>is&nbsp;not&nbsp;an&nbsp;easy&nbsp;job.&nbsp;Anyway,&nbsp;this&nbsp;draft&nbsp;brings&nbsp;a&nbsp;new&nbsp;choice&nbsp;for&nbsp;authority&nbsp;server&nbsp;operators&nbsp;and&nbsp;resolver&nbsp;server&nbsp;operators.</div>
              </div>
              <div>&nbsp;</div>
              <hr style="WIDTH:210px;min-height:1px" size="1"
                align="left" color="#b5c4df">
              <div style="FONT-FAMILY:Verdana"><span>
                  <div><span style="font-size:10.5pt;font-family:&#23435;&#20307;">Guangqing
                      Deng</span></div>
                  <div><span style="font-size:10.5pt;font-family:&#23435;&#20307;">CNNIC&nbsp;</span></div>
                </span></div>
              <div>&nbsp;</div>
              <div style="BORDER-BOTTOM:medium none;BORDER-LEFT:medium
                none;PADDING-BOTTOM:0cm;PADDING-LEFT:0cm;PADDING-RIGHT:0cm;BORDER-TOP:#b5c4df
                1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
                <div
style="padding-right:8px;padding-left:8px;padding-top:8px;font-size:12px;background:#efefef;padding-bottom:8px">
                  <div><b>From:</b>&nbsp;<a moz-do-not-send="true"
                      href="mailto:jabley@hopcount.ca" target="_blank">Joe
                      Abley</a></div>
                  <div><b>Date:</b>&nbsp;2013-06-25&nbsp;21:10</div>
                  <div><b>To:</b>&nbsp;<a moz-do-not-send="true"
                      href="mailto:dengguangqing@cnnic.cn"
                      target="_blank">dengguangqing</a></div>
                  <div><b>CC:</b>&nbsp;<a moz-do-not-send="true"
                      href="mailto:dnsop@ietf.org" target="_blank">dnsop@ietf.org</a></div>
                  <div><b>Subject:</b>&nbsp;Re: [DNSOP] Fwd: New Version
                    Notification for draft-jabley-dnsop-dns-flush-00.txt</div>
                </div>
              </div>
              <div>
                <div class="h5">
                  <div>
                    <div>Hi&nbsp;Guangqing,</div>
                    <div>&nbsp;</div>
                    <div>On&nbsp;2013-06-25,&nbsp;at&nbsp;08:02,&nbsp;"Guangqing&nbsp;Deng"&nbsp;&lt;<a
                        moz-do-not-send="true"
                        href="mailto:dengguangqing@cnnic.cn"
                        target="_blank">dengguangqing@cnnic.cn</a>&gt;&nbsp;wrote:</div>
                    <div>&nbsp;</div>
                    <div>&gt;&nbsp;Hi,&nbsp;Joe,&nbsp;I&nbsp;like&nbsp;this&nbsp;draft,&nbsp;though&nbsp;I&nbsp;am&nbsp;puzzled&nbsp;by&nbsp;some&nbsp;questions.&nbsp;First,&nbsp;the&nbsp;change&nbsp;of&nbsp;</div>
                    <div>&gt;&nbsp;the&nbsp;zone&nbsp;content&nbsp;of&nbsp;an&nbsp;authority&nbsp;server&nbsp;does&nbsp;not&nbsp;mean&nbsp;that&nbsp;a&nbsp;corresponding&nbsp;recursive&nbsp;server&nbsp;</div>
                    <div>&gt;&nbsp;has&nbsp;to&nbsp;flush&nbsp;its&nbsp;cache,&nbsp;since&nbsp;a&nbsp;recursive&nbsp;server&nbsp;usually&nbsp;just&nbsp;cache&nbsp;a&nbsp;small&nbsp;part&nbsp;of&nbsp;zone&nbsp;content</div>
                    <div>&gt;&nbsp;of&nbsp;an&nbsp;authority&nbsp;server&nbsp;but&nbsp;not&nbsp;all.&nbsp;Also,&nbsp;an&nbsp;authority&nbsp;server&nbsp;does&nbsp;not&nbsp;know&nbsp;which&nbsp;RRs&nbsp;of&nbsp;its&nbsp;</div>
                    <div>&gt;&nbsp;zone&nbsp;content&nbsp;are&nbsp;cached&nbsp;in&nbsp;recursive&nbsp;servers.&nbsp;So&nbsp;such&nbsp;mechanism&nbsp;of&nbsp;DNS&nbsp;FLUSH&nbsp;may&nbsp;bring&nbsp;about&nbsp;</div>
                    <div>&gt;&nbsp;some&nbsp;additional&nbsp;traffic&nbsp;between&nbsp;authority&nbsp;and&nbsp;recursive&nbsp;servers&nbsp;with&nbsp;no&nbsp;benefit.</div>
                    <div>&nbsp;</div>
                    <div>I&nbsp;agree&nbsp;that&nbsp;in&nbsp;many&nbsp;cases&nbsp;this&nbsp;is&nbsp;a&nbsp;fairly&nbsp;coarse&nbsp;mechanism;&nbsp;however,&nbsp;arguably&nbsp;there&nbsp;are&nbsp;situations&nbsp;where&nbsp;incurring&nbsp;that&nbsp;overhead&nbsp;is&nbsp;better&nbsp;than&nbsp;enduring&nbsp;bad&nbsp;data&nbsp;that&nbsp;is&nbsp;widely-cached.</div>
                    <div>&nbsp;</div>
                    <div>Following&nbsp;the&nbsp;recent&nbsp;incident&nbsp;affecting&nbsp;various&nbsp;.COM&nbsp;names&nbsp;there&nbsp;were&nbsp;widespread&nbsp;pleas&nbsp;to&nbsp;resolver&nbsp;operators&nbsp;to&nbsp;"flush&nbsp;your&nbsp;cache".&nbsp;It&nbsp;seems&nbsp;likely&nbsp;that&nbsp;some&nbsp;people&nbsp;interpreted&nbsp;that&nbsp;request&nbsp;on&nbsp;face-value,&nbsp;and&nbsp;flushed&nbsp;all&nbsp;records&nbsp;from&nbsp;their&nbsp;caches.&nbsp;Flushing&nbsp;just&nbsp;the&nbsp;COM&nbsp;domain&nbsp;(or&nbsp;specific&nbsp;sub-domains)&nbsp;would&nbsp;have&nbsp;been&nbsp;better.&nbsp;This&nbsp;mechanism&nbsp;would&nbsp;facilitate&nbsp;either&nbsp;of&nbsp;those.</div>
                    <div>&nbsp;</div>
                    <div>I&nbsp;appreciate&nbsp;the&nbsp;previous&nbsp;paragraph&nbsp;is&nbsp;less&nbsp;than&nbsp;entirely&nbsp;convincing&nbsp;:-)</div>
                    <div>&nbsp;</div>
                    <div>The&nbsp;BIZ&nbsp;event&nbsp;whereby&nbsp;(it&nbsp;appears&nbsp;from&nbsp;the&nbsp;outside)&nbsp;an&nbsp;apex&nbsp;DNSKEY&nbsp;RRSet&nbsp;was&nbsp;published&nbsp;that&nbsp;did&nbsp;not&nbsp;include&nbsp;a&nbsp;key&nbsp;corresponding&nbsp;to&nbsp;the&nbsp;BIZ&nbsp;DS&nbsp;RRSet&nbsp;in&nbsp;the&nbsp;root&nbsp;zone&nbsp;would&nbsp;have&nbsp;been&nbsp;another&nbsp;example&nbsp;where&nbsp;flushing&nbsp;the&nbsp;entire&nbsp;BIZ&nbsp;domain&nbsp;would&nbsp;have&nbsp;been&nbsp;overkill,&nbsp;but&nbsp;arguably&nbsp;better&nbsp;(for&nbsp;validators)&nbsp;than&nbsp;doing&nbsp;nothing.</div>
                    <div>&nbsp;</div>
                    <div>I&nbsp;agree&nbsp;that&nbsp;it&nbsp;would&nbsp;make&nbsp;little&nbsp;sense&nbsp;for&nbsp;an&nbsp;authority&nbsp;server&nbsp;operator&nbsp;in&nbsp;the&nbsp;absence&nbsp;of&nbsp;a&nbsp;problem&nbsp;to&nbsp;flush&nbsp;remote&nbsp;caches&nbsp;every&nbsp;time&nbsp;a&nbsp;new&nbsp;zone&nbsp;was&nbsp;published.&nbsp;I&nbsp;would&nbsp;expect&nbsp;specific&nbsp;hooks&nbsp;to&nbsp;be&nbsp;in&nbsp;place&nbsp;to&nbsp;allow&nbsp;flush&nbsp;directions&nbsp;to&nbsp;be&nbsp;propagated&nbsp;under&nbsp;manual&nbsp;operator&nbsp;control,&nbsp;rather&nbsp;than&nbsp;automatically,&nbsp;triggered&nbsp;by&nbsp;a&nbsp;SOA&nbsp;serial&nbsp;bump.</div>
                    <div>&nbsp;</div>
                    <div>There&nbsp;is&nbsp;a&nbsp;discontinuity&nbsp;here&nbsp;between&nbsp;the&nbsp;current&nbsp;use&nbsp;of&nbsp;DNS&nbsp;NOTIFY&nbsp;and&nbsp;the&nbsp;proposed&nbsp;new&nbsp;use;&nbsp;the&nbsp;former&nbsp;is&nbsp;based&nbsp;on&nbsp;zones,&nbsp;while&nbsp;the&nbsp;latter&nbsp;is&nbsp;based&nbsp;on&nbsp;domains.&nbsp;There&nbsp;is&nbsp;an&nbsp;argument&nbsp;here&nbsp;for&nbsp;a&nbsp;new&nbsp;opcode;&nbsp;the&nbsp;reuse&nbsp;of&nbsp;NOTIFY&nbsp;seemed&nbsp;expedient&nbsp;when&nbsp;I&nbsp;wrote&nbsp;the&nbsp;draft,&nbsp;but&nbsp;perhaps&nbsp;it's&nbsp;not&nbsp;the&nbsp;best&nbsp;way.</div>
                    <div>&nbsp;</div>
                    <div>&gt;&nbsp;Second,&nbsp;how&nbsp;</div>
                    <div>&gt;&nbsp;does&nbsp;the&nbsp;authority&nbsp;server&nbsp;obtain&nbsp;the&nbsp;IPs&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;From&nbsp;query&nbsp;logs?&nbsp;Then&nbsp;the&nbsp;</div>
                    <div>&gt;&nbsp;authority&nbsp;server&nbsp;sends&nbsp;DNS&nbsp;FLUSH&nbsp;to&nbsp;all&nbsp;or&nbsp;part&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;It&nbsp;seems&nbsp;that&nbsp;there&nbsp;</div>
                    <div>&gt;&nbsp;are&nbsp;big&nbsp;differences&nbsp;between&nbsp;DNS&nbsp;NOTIFY&nbsp;and&nbsp;so&nbsp;called&nbsp;DNS&nbsp;FLUSH&nbsp;and&nbsp;thus&nbsp;more&nbsp;things&nbsp;need&nbsp;to&nbsp;</div>
                    <div>&gt;&nbsp;be&nbsp;clarified.</div>
                    <div>&nbsp;</div>
                    <div>I&nbsp;can&nbsp;think&nbsp;of&nbsp;various&nbsp;models&nbsp;for&nbsp;this.</div>
                    <div>&nbsp;</div>
                    <div>Bilateral&nbsp;agreements&nbsp;between&nbsp;authority&nbsp;server&nbsp;operators&nbsp;and&nbsp;recursive&nbsp;server&nbsp;operators&nbsp;would&nbsp;involve&nbsp;sharing&nbsp;of&nbsp;TSIG&nbsp;secrets&nbsp;as&nbsp;well&nbsp;as&nbsp;server&nbsp;addresses.&nbsp;A&nbsp;set&nbsp;of&nbsp;bilats&nbsp;will&nbsp;not&nbsp;scale&nbsp;to&nbsp;the&nbsp;whole&nbsp;Internet,&nbsp;obviously,&nbsp;but&nbsp;perhaps&nbsp;is&nbsp;good&nbsp;enough&nbsp;to&nbsp;deal&nbsp;with&nbsp;particular&nbsp;known&nbsp;resolvers&nbsp;that&nbsp;serve&nbsp;large&nbsp;communities&nbsp;of&nbsp;users&nbsp;(e.g.&nbsp;Google&nbsp;DNS,&nbsp;OpenDNS,&nbsp;Comcast&nbsp;DNS).</div>
                    <div>&nbsp;</div>
                    <div>A&nbsp;mechanism&nbsp;such&nbsp;as&nbsp;this&nbsp;would&nbsp;enable&nbsp;a&nbsp;clearinghouse&nbsp;style&nbsp;business&nbsp;model&nbsp;where&nbsp;resolver&nbsp;operators&nbsp;and&nbsp;authority&nbsp;server&nbsp;operators&nbsp;could&nbsp;subscribe&nbsp;to&nbsp;a&nbsp;service&nbsp;that&nbsp;mediated&nbsp;the&nbsp;flush&nbsp;directions&nbsp;between&nbsp;authority&nbsp;servers&nbsp;and&nbsp;recursive&nbsp;servers,&nbsp;acting&nbsp;as&nbsp;a&nbsp;trusted&nbsp;intermediary.</div>
                    <div>&nbsp;</div>
                    <div>&nbsp;</div>
                    <div>Joe</div>
                  </div>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            DNSOP mailing list<br>
            <a moz-do-not-send="true" href="mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
            <a moz-do-not-send="true"
              href="https://www.ietf.org/mailman/listinfo/dnsop"
              target="_blank">https://www.ietf.org/mailman/listinfo/dnsop</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
DNSOP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:DNSOP@ietf.org">DNSOP@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dnsop">https://www.ietf.org/mailman/listinfo/dnsop</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060305070604090309010302--

From ogud@ogud.com  Fri Jun 28 11:18:02 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B3B21F9C31 for <dnsop@ietfa.amsl.com>; Fri, 28 Jun 2013 11:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r7UgJSso0PKJ for <dnsop@ietfa.amsl.com>; Fri, 28 Jun 2013 11:17:57 -0700 (PDT)
Received: from smtp149.ord.emailsrvr.com (smtp149.ord.emailsrvr.com [173.203.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 208BA21F9C33 for <dnsop@ietf.org>; Fri, 28 Jun 2013 11:17:57 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp23.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id D24E41C8127; Fri, 28 Jun 2013 14:17:55 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp23.relay.ord1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 57B511C811D;  Fri, 28 Jun 2013 14:17:55 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <51C96B62.9030401@nlnetlabs.nl>
Date: Fri, 28 Jun 2013 14:18:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 18:18:02 -0000

On Jun 25, 2013, at 6:05 AM, Matthijs Mekking <matthijs@NLnetLabs.nl> =
wrote:

> Hi,
>=20
> On 06/21/2013 11:58 PM, Wes Hardaker wrote:
>> Paul Wouters <paul@cypherpunks.ca> writes:
>>=20
>>> I am in favour of adopting this draft as a WG item.
>>=20
>> Ditto.
>=20
> Another ditto. I am pleased to see that there is still activity on the
> topic of automating the synchronization between DNSKEY at the child =
and
> the DS at the parent.
>=20
>=20
Thanks

>>> I don't think the CDS record should be able to cause a child domain =
to
>>> go from secure to insecure, or from insecure to secure. That
>>> (infrequent) change should have an additional authentication, eg via =
EPP
>>> or otherwise)
>>=20
>> Ditto.  I think the goal of any of the automatic update techniques
>> should be to make the routine easy but it shouldn't be a goal to =
handle
>> the infrequent, and challenging cases.  (infrequent and easy is =
fine).
>>=20
>> Unless we can show a clear, secured, path for some transition I don't
>> think it's worth solving.
>=20
> Another ditto. Agreeing with it's not worth solving to deal with the
> irregular cases. Going unsigned is an irregular case.
>=20
>=20
> Also backing a previous made comment by other people:
>=20
> * I prefer to have the CDS wire format to be similar to the DS wire
> format. With the current draft, it is already possible to automate all
> possible key rollovers, no need for managerial hooks to say this =
record
> is proposed, must be added, deleted, is valid for only this period =
etc.
>=20
>=20

> Comments on the draft (apologies for its length):

Thanks for the comments.=20

>=20
> * Nit: In section 1, it says there may be two interactions with the
> parent. This could also be only one, this could be more in some freaky
> rollovers, so I would prefer that it reads: "there may be one ore more
> interactions with the parent".

Applied=20

>=20
> * Section 3. I appreciate that most ZSK /KSK terminology is carefully
> replaced with, but in section 3 is still something that itches: "The =
SEP
> bit is an optional bit to indicate that the key is allowed to sign the
> DNSKEY RRset". That is not true. Without the SEP bit, the key may also
> sign the DNSKEY RRset.
>=20

I agree but still want to bring up the SEP bit,=20
would some thing like this be better:=20
"The SEP bit is an optional bit that indicates that the child expects to =
sign the
DNSKEY RRset with that key, while the key is in use."=20


> * Section 3.1.1. As said above, I don't like the idea of using the CDS
> record to go unsigned.
>=20

Ack,=20
this is going to be a design point allow or not allow this function.=20
We can remove this part and later propose it as part of an extension, =
just like=20
any protocol to automate the tickling of the parent.=20
=20
> * Nit: Section 4.1. I think the last paragraph fits better in section
> 4.2. CDS Consumption.

Reworked both sections to address this=20
>=20
> * Section 4.2. About the polling strategy. I am wondering how well =
this
> scales with respect to the number of delegations.

The next version will indicate that polling has scaling issues, but punt =
the problem of=20
defining a mechanishm to another document.=20
The thinking is the "parental notification" is the HARDEST part of the =
proposal,=20
and we might need multiple solutions depending number of delegations and =
other factors.=20
Having said that in many cases in particular the enterprise and =
university cases polling is perfectly fine=20
and will scale, thus our thinking is we will document that and start a =
parallel document on "MAGIC" system=20
that does the notification, along the lines you documented few years =
back.=20

>=20
> * Section 4.2. It is suggested that RFC 5011-like hold down timers are
> being used, e.g. new keying information must be published for a month
> before acceptance as a new trust anchor. This makes the duration of =
key
> rollovers unnecessary long. The hold down timers in RFC 5011 are there
> to mitigate against a compromise. The compromise allows the attacker =
to
> sign data in the zone.

I hear you and want other people to chime in, both in the context of=20
compromise and time to perform rollover. If rollover is done by=20
automated systems that perform checks before progressing who cares how =
long the=20
rollover takes?=20

>=20
> Similar we could look at a compromise that allows the attacker to =
upload
> a DS/DNSKEY to the parent. However, there are no mechanisms to =
mitigate
> against this attack. Why should we have mitigation for the CDS =
proposal,
> if there is none for the current mechanism?
>=20
> The difference between CDS and RFC 5011 is the location of the trust
> anchor your are updating. With CDS, you are updating the DS in the
> parent. With RFC 5011, you are updating lots of trust anchors in the
> wild. The latter may indeed require a bit more conservative approach.
>=20
> * Section 4.3. I wonder if the SHOULD in the first sentence should be =
a
> MUST.
>=20
I think a better way is to encourage the child to ONLY publish CDS when =
there is a need to change the DS record and
remove after parents performs change.=20

> * Section 4.4. I dislike the idea of the side effect of parent
> calculates DS, so I would like to see that only the "augment" mode is
> supported (where I think it should read: "it will make sure there are
> CDS records for the digest algorithm(s) it require(s)" (CDS instead of
> DS)).
>=20

You are not alone, but there are some people in your neighborhood that=20=

feel strongly the other way and argued strongly against version 01 =
because=20
this was outlawed.=20

> The publishing "Future DNSKEYs" does not go well with several rollover
> scenarios (those based on Double-DS). I am wondering if the policy is
> "We calculate the DS" or "We decide the digest algorithm". In case of
> the latter, then augment mode can be used to support this. In case of
> the first, the future DNSKEY is really required to be published, and
> Double-DS based rollovers are not possible in combination with CDS.
>=20

exactly=20

> * Section 6. Security Considerations. The last paragraph. Isn't this
> solved by saying that the Parental Agent MUST ensure that old versions
> of the CDS RRset do not override newer versions in section 4.3. Usage?
> There is already a proposed method on how to achieve this there.
>=20

Strictly speaking using RFC5011 will address this as all the signatures =
in=20
"disjoint" authorative servers wil have expired.=20

> * When implementing a prototype for this in OpenDNSSEC, I questioned
> myself what value I should use for the TTL. We could consider 0, as =
this
> record is not really intended for the resolver. We could also use the
> TTL to suggest a polling frequency for the parental agent. Just some
> thoughts.
>=20
>=20
I had not thought about guidance on the CDS TTL, nor on the signature =
lifetime on the record.=20
You have any ideas?=20


> Best regards,
>  Matthijs
>=20
Thanks for great review.=20

	Olafur


From jabley@hopcount.ca  Fri Jun 28 15:32:15 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FA421F9D4E for <dnsop@ietfa.amsl.com>; Fri, 28 Jun 2013 15:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kqto7GNiSoG8 for <dnsop@ietfa.amsl.com>; Fri, 28 Jun 2013 15:32:15 -0700 (PDT)
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 08BB521F9D17 for <dnsop@ietf.org>; Fri, 28 Jun 2013 15:32:14 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id c11so1731885qcv.9 for <dnsop@ietf.org>; Fri, 28 Jun 2013 15:32:14 -0700 (PDT)
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:x-mailer; bh=4pEKuuxC9MODZIOQjlfav9bYulQEHLZ6ac9uwurMc3s=; b=SXmXj3BNTSaeGrrSgbDegnSNSyLmmuZhCBWIEZ1uHEdUxwTetGTps7qdaYcMgflgg0 ohii7mfbxMckNqYNfQ2Sum5aFJoFpn5QWiWSV6xpjBt2jqqWO4BM9Kf32MQ1rcSw5FGg ROgUBDHkKzDjqnl4zhQ5LAl5dH/40KciVKaag=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version:x-mailer:x-gm-message-state; bh=4pEKuuxC9MODZIOQjlfav9bYulQEHLZ6ac9uwurMc3s=; b=Gsl0+682XPF9cvlJjKF3eg2VQrPScsjhpn5RIW09Z9mdvSBr0286Ydkxj018xp7/Ld R6CziKSqaXuQ/f21ktL+H7wMJt5z+TpvtdYR6AsuWjXFME5pcbvW4Rk3pS70lDWvO1yZ Ievli4SdH+7qsiRSaMraIm1UF8cfiq3y+qvOtC42dzYtLdU4qq9votNZ8pEOBPv9d1gS 2GBM4tSQUNrjH46qhkngcXGEaBoQgtw6Ul0YVOl6QWgCACj1niQ4DNgiw+i1kPU5r5rA srzbyD2m+f2UNHDnFixnjQLw16TwqNyRFqQU7iwKHom+qZmbhpkv9MOEpaxrkkHx8bmh kqjA==
X-Received: by 10.49.48.83 with SMTP id j19mr19549705qen.56.1372458734230; Fri, 28 Jun 2013 15:32:14 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:6d51:7949:c592:fc8c? ([2001:4900:1042:100:6d51:7949:c592:fc8c]) by mx.google.com with ESMTPSA id 11sm13153058qek.1.2013.06.28.15.32.13 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 28 Jun 2013 15:32:13 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 28 Jun 2013 18:32:13 -0400
References: <20130628222333.29265.44695.idtracker@ietfa.amsl.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-Id: <BEE324D5-260E-4441-BCEF-26016F3DA0B8@hopcount.ca>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmZoCz0wxCvkPakgfDGXM0oD1UPXBsvKc1avQbF4SYI9k2M8AwPQ+IADSSOhwiX1CGJ3sRr
Subject: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-as112-dname-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 22:32:15 -0000

Hi all,

As promised, here's a draft which describes the alternate approach =
(alternate to the omniscient, custom-code route that our other document =
proposes) of using DNAME to extend AS112 service.

<sales pitch>
  This one has the side-effect of supporting DNSSEC-validatable =
redirection to AS112 nodes!
</sales pitch>

:-)


Joe

Begin forwarded message:

> From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> Subject: New Version Notification for =
draft-jabley-dnsop-as112-dname-00.txt
> Date: 28 June 2013 18:23:33 EDT
> To: Joe Abley <joe.abley@icann.org>, Brian Dickson =
<brian.peter.dickson@gmail.com>
>=20
>=20
> A new version of I-D, draft-jabley-dnsop-as112-dname-00.txt
> has been successfully submitted by Joe Abley and posted to the
> IETF repository.
>=20
> Filename:	 draft-jabley-dnsop-as112-dname
> Revision:	 00
> Title:		 AS112 Redirection using DNAME
> Creation date:	 2013-06-28
> Group:		 Individual Submission
> Number of pages: 20
> URL:             =
http://www.ietf.org/internet-drafts/draft-jabley-dnsop-as112-dname-00.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-jabley-dnsop-as112-dname
> Htmlized:        =
http://tools.ietf.org/html/draft-jabley-dnsop-as112-dname-00
>=20
>=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
>=20
>=20
> The IETF Secretariat
>=20


From dengguangqing@cnnic.cn  Sat Jun 29 09:42:09 2013
Return-Path: <dengguangqing@cnnic.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5C711E8199 for <dnsop@ietfa.amsl.com>; Sat, 29 Jun 2013 09:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7WHpWMETEKX9 for <dnsop@ietfa.amsl.com>; Sat, 29 Jun 2013 09:42:04 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id C728411E8197 for <dnsop@ietf.org>; Sat, 29 Jun 2013 09:42:03 -0700 (PDT)
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; Sun, 30 Jun 2013 00:41:49 +0800
Date: Sun, 30 Jun 2013 00:41:48 +0800
From: "Guangqing Deng" <dengguangqing@cnnic.cn>
To: "Tim Wicinski" <tim.wicinski@teamaol.com>
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com>	<806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca>	<201306252002459685411@cnnic.cn>	<FD6B803D-D752-43BC-BDCF-AD01EFD8C816@hopcount.ca>	<201306261026086071520@cnnic.cn> <CAB3ZD+=UuVEi48GFMuEp2OwqZVQzKfbZts3z03f9m6P8M_NjJw@mail.gmail.com>, <51CD4FD7.80904@teamaol.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.91[cn]
Mime-Version: 1.0
Message-ID: <201306300041470714506@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart881847005851_=----"
Cc: ice jew <jewforice@gmail.com>, dnsop <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Jun 2013 16:42:09 -0000

This is a multi-part message in MIME format.

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

SG93IHRvIHByb3BhZ2F0ZSB0aGUgbmV3bHkgZ2VuZXJhdGVkIChvciBuZXdseSBjaGFuZ2VkKSBE
TlMgcmVzb3VyY2UgcmVjb3JkcyAoUlJzKSBmcm9tIGF1dGhvcml0eSB0byByZWN1cnNpdmUgc2Vy
dmVycyBpcyBvYnZpb3VzbHkgdmVyeSBpbXBvcnRhbnQgZm9yIHRoZSBETlMgc3lzdGVtLiANCkZv
ciBSUiBwcm9wYWdhdGlvbiwgdGhlcmUgYXJlIGZ1bmRhbWVudGFsbHkgdHdvIGFwcHJvYWNoZXM6
IHB1bGwtYmFzZWQgYW5kIHB1c2gtYmFzZWQgYXBwcm9hY2guIEluIHRoZSBmb3JtZXIgb25lLCBy
ZWN1cnNpdmUgc2VydmVycyBwdWxsIFJScyBmcm9tIGF1dGhvcml0eSANCnNlcnZlcnMgd2hlbiB0
aGUgVFRMIGV4cGlyZXMuIFVzdWFsbHksIHRoaXMga2luZCBvZiBhcHByb2FjaCBoYXMgYWR2YW50
YWdlcyBvZiBsb3cgdHJhZmZpYyBvdmVyaGVhZCBhbmQgaGlnaCByZXNpbGllbmNlIGJ1dCBhIGRp
c2FkdmFudGFnZSBvZiBiYWQgcmVhbCB0aW1lLiANCkluIHRoZSBsYXR0ZXIgb25lLCBhdXRob3Jp
dHkgc2VydmVycyBwdXNoIHRoZSBSUnMgdG8gcmVjdXJzaXZlIHNlcnZlcnMgd2hlbiB6b25lIGZp
bGUgaXMgY2hhbmdlZC4gVGhpcyBhcHByb2FjaCBoYXMgZ29vZCByZWFsIHRpbWUgYnV0IGJyaW5n
cyB2ZXJ5IGhpZ2ggdHJhZmZpYyANCm92ZXJoZWFkIHNpbmNlIGF1dGhvcml0eSBzZXJ2ZXJzIGRv
IG5vdCBrbm93IHdoaWNoIFJScyBpcyBuZWVkZWQgYnkgcmVjdXJzaXZlIHNlcnZlcnMuIE9idmlv
dXNseSwgdGhlIHB1bGwtYmFzZWQgYXBwcm9hY2ggbm93IGlzIHdpZGVseSB1c2VkIGluIEROUyBk
dWUgdG8gaXRzIHNpbXBsaWNpdHkuIA0KSWYgdGhlcmUgaXMgYSB0aGlyZCBhcHByb2FjaCwgaXQg
bXVzdCBiZSBhIG1peHR1cmUgb2YgcHVsbC1iYXNlZCBhbmQgcHVzaC1iYXNlZCBhcHByb2FjaGVz
IGFuZCBhIG5ldyBzaWduYWxpbmcgcHJvdG9jb2wgYmV0d2VlbiBhdXRob3JpdHkgYW5kIHJlY3Vy
c2l2ZSBzZXJ2ZXJzIG1heSANCmJlIG5lZWRlZCB0byBzY2hlZHVsZSB0aGUgdHJhbnNtaXNzaW9u
IG9mIFJScyAoRE5TIE5PVElGWSBjYW4gYmUgdGFrZW4gYXMgYW4gZXhhbXBsZSkuIEhvd2V2ZXIs
IHRoZSBkcmF3YmFjayBvZiB0aGUgc2Vjb25kIGFwcHJvYWNoIGlzIGFsc28gYnJvdWdodCBpbnRv
IHRoZSB0aGlyZCANCm9uZS4gTGFzdGx5LCB0aG91Z2ggSSBhbSBub3QgdG90YWxseSBzYXRpc2Zp
ZWQgd2l0aCB0aGUgY3VycmVudGx5IHVzZWQgYXBwcm9hY2gsIEkgaGF2ZSBub3QgZ290IGEgYmV0
dGVyIGlkZWEgeWV0LiBBbnl3YXksIEROUyBOT1RJRlkgaXMgYSBnb29kIHN0YXJ0IGluIG15IG9w
aW5pb24uIA0KIA0KDQoNCg0KR3VhbmdxaW5nIERlbmcNCkNOTklDIA0KDQpGcm9tOiBUaW0gV2lj
aW5za2kNCkRhdGU6IDIwMTMtMDYtMjggMTY6NTYNClRvOiBpY2UgamV3OyBHdWFuZ3FpbmcgRGVu
Zw0KQ0M6IGRuc29wOyBKb2UgQWJsZXkNClN1YmplY3Q6IFJlOiBbRE5TT1BdIEZ3ZDogTmV3IFZl
cnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1qYWJsZXktZG5zb3AtZG5zLWZsdXNoLTAwLnR4
dA0KQWN0dWFsbHkgZmx1c2hpbmcgcmVzb2x2ZXIgY2FjaGVzIGluICBsYXJnZXIgZW52aXJvbm1l
bnRzIChkYXRhIGNlbnRlci9lbnRlcnByaXNlL2V0Yykgd2hlcmUgZXZlbiBzaG9ydCBUVExzIGRv
ZXNuJ3QgcXVpdGUgaGFuZGxlIHVuZXhwZWN0ZWQgZXZlbnRzLCBhbmQgdGhlcmUgaXMgYSBuZWVk
IHRvIGhhdmUgY29uc2lzdGVudCBhbnN3ZXJzLCBldmVuIGlmIHRoZSBjb25zaXN0ZW5jeSBpcyBO
WERPTUFJTi4gDQoNCkkgZG9uJ3Qga25vdyBpZiB0aGUgTk9USUZZIHNlbWFudGljIG1lY2hhbmlz
bSAod2hpbGUgYSBzaW1wbGUgd2F5IG9mIGF2b2lkaW5nIGNyZWF0aW5nIGEgbmV3IG1lY2hhbmlz
bSkgaXMgdGhlIGNvcnJlY3QgbWV0aG9kLg0KDQp0aW0NCiANCg0KT24gNi8yNi8xMyAxOjM5IEFN
LCBpY2UgamV3IHdyb3RlOg0KDQpUaGlzIGRyYWZ0IGRvZXMgcHJvdmlkZSBzb21lIG5ldyBwb3Nz
aWJpbGl0eSBmb3IgZGVjcmVhc2UgdGhlIG5lZ2F0aXZlIGVmZmVjdHMgZm9yIHRoZSBhdXRob3Jp
dHkgbmFtZSBzZXJ2ZXIncyBtaXMtY29uZmlndXJhdGlvbiBpbiBhIGNlcnRhaW4gd2F5LiBCdXQg
SSBkb24ndCB0aGluayBpdCB3aWxsIHdvcmsgaW4gdGhlIHJlYWwgd29ybGQgIGV2ZW4gaWYgYWxs
IHByZXJlcXVpc2l0ZXMgYXJlIG1lYW50LiANCg0KDQpGaXJzdCwgdGhlcmUgaXMgc3RhbmRhcmQg
d2F5IHRvIHNvbHZlIHRoaXMgcHJvYmxlbSwgYXMgR3VhbnFpbmcgc2F5cywgaXQncyB0byBzaG9y
dGVuIHRoZSBUVEwgKGJvdGggcG9zaXRpdmUgYW5kIG5lZ2F0aXZlIGNhY2hlKS4gVGhpcyBtYXkg
bGVhZCB0byBsb2FkIGluY3JlYXNlIGZvciB0aGUgYXV0aG9yaXR5IG5hbWUgc2VydmVycyBhbmQg
IHJlY3Vyc2l2ZSByZXNvbHZlci4gQnV0IHRoaXMgbWV0aG9kIHRha2UgdGhlIGxlYXN0IHJpc2su
DQoNCg0KU2Vjb25kLCBJIHRoaW5rIGl0IHdvbid0IHdvcmsgdW5kZXIgdGhlIGNvbmRpdGlvbiB0
aGF0ICB0aGUgcmVjdXJzaXZlIHJlc29sdmVyIGFuZCB0aGUgY2FjaGUgbmFtZSBzZXJ2ZXIgYXJl
IGRlcHJpdmVkLiBUaGUgYXV0aG9yaXR5IGNsZWFucyB0aGUgIGNhY2hlIG9mIHRoZSByZWN1cnNp
dmUgcmVzb2x2ZXIgZnJvbSB0aGUgbG9nICBidXQgdGhlIGNhY2hlIG5hbWUgc2VydmVyIHdvbid0
IGdvIHRvIHRoZSByZWN1cnNpdmUgcmVzb2x2ZXIgZm9yIGEgbmV3ZXIgIHJlc3BvbnNlIHVudGls
IHRoZSBUVEwgaXMgZXhwaXJlZC4gIEFuZCB0aGUgYmFkIGRhdGEgaW4gdG8gY2FjaGUgbmFtZSBz
ZXJ2ZXIgc3RpbGwgcmVzcG9uc2VzIHRvIHRoZSBpbmNvbWluZyBxdWVyaWVzLiBUaGUgY2xlYW5p
bmctY2FjaGUtbWVjaGFuaXNtIGRvZXNuJ3QgaGVscCB0byBkZWNyZWFzZSB0aGUgbmVnYXRpdmUg
ZWZmZWN0Lg0KDQoNCg0KDQoNCk9uIFdlZCwgSnVuIDI2LCAyMDEzIGF0IDEwOjI2IEFNLCBHdWFu
Z3FpbmcgRGVuZyA8ZGVuZ2d1YW5ncWluZ0Bjbm5pYy5jbj4gd3JvdGU6DQoNCkhpLCBKb2UuIEp1
c3QgYXMgeW91IHNhaWQsIHRoZSBuZWVkIG9mIGZsdXNoaW5nIGNhY2hlIGV4aXN0cyB0byBhIGNl
cnRhaW4gZXh0ZW50LiBCdXQgbWF5YmUgZmlyc3Qgd2Ugc2hvdWxkIGNoZWNrIA0Kd2h5IHRoZSBj
YWNoZSBuZWVkcyB0byBiZSBmbHVzaGVkLiBJcyBpdCBkdWUgdG8gZXJyb3JzIGluIHpvbmUgZmls
ZSwgb3RoZXIgY29uZmlndXJhdGlvbiBlcnJvcnMgaW4gYXV0aG9yaXR5IHNlcnZlcnMNCm9yIHRo
ZSBpbmVmZmljaWVuY3kgb2YgVFRMIG1lY2hhbmlzbT8gRm9yIHRoZSBmaXJzdCB0d28gcmVhc29u
cywgaXQgaXMgYmV0dGVyIHRvIGRvIG90aGVyIHdvcmsgdG8gYXZvaWQgc3VjaCBraW5kcw0Kb2Yg
ZXJyb3JzIGFuZCB0aGVuIGNhY2hlIGZsdXNoaW5nIGlzIGJ5cGFzc2VkLiBGb3IgdGhlIHRoaXJk
IHJlYXNvbiwgc2hvcnRlbmluZyB0aGUgVFRMIG1heSBiZSBhIHBvdGVudGlhbCBhcHByb2FjaCwg
DQphbmQgYWxzbyBETlMgRkxVU0ggY2FuIGJlIHRha2VuIGFzIGFuIGVmZmVjdGl2ZSBzdXBwbGVt
ZW50IG9mIFRUTCBtZWNoYW5pc20uIEZ1bmRhbWVudGFsbHksIFRUTCBtZWNoYW5pc20gaXMgYmFz
ZWQgDQpvbiAicHVsbCIgZmFzaGlvbiB3aGlsZSBETlMgRkxVU0ggc29tZWhvdyBpcyBiYXNlZCBv
biAicHVzaCIgZmFzaGlvbi4gQW5kIHRoZW4gaG93IHRvIGVmZmVjdGl2ZWx5IGJyaW5nIHRoZW0g
dG9nZXRoZXINCmlzIG5vdCBhbiBlYXN5IGpvYi4gQW55d2F5LCB0aGlzIGRyYWZ0IGJyaW5ncyBh
IG5ldyBjaG9pY2UgZm9yIGF1dGhvcml0eSBzZXJ2ZXIgb3BlcmF0b3JzIGFuZCByZXNvbHZlciBz
ZXJ2ZXIgb3BlcmF0b3JzLg0KDQoNCg0KDQpHdWFuZ3FpbmcgRGVuZw0KQ05OSUMgDQoNCkZyb206
IEpvZSBBYmxleQ0KRGF0ZTogMjAxMy0wNi0yNSAyMToxMA0KVG86IGRlbmdndWFuZ3FpbmcNCkND
OiBkbnNvcEBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtETlNPUF0gRndkOiBOZXcgVmVyc2lvbiBO
b3RpZmljYXRpb24gZm9yIGRyYWZ0LWphYmxleS1kbnNvcC1kbnMtZmx1c2gtMDAudHh0DQpIaSBH
dWFuZ3FpbmcsDQoNCk9uIDIwMTMtMDYtMjUsIGF0IDA4OjAyLCAiR3VhbmdxaW5nIERlbmciIDxk
ZW5nZ3VhbmdxaW5nQGNubmljLmNuPiB3cm90ZToNCg0KPiBIaSwgSm9lLCBJIGxpa2UgdGhpcyBk
cmFmdCwgdGhvdWdoIEkgYW0gcHV6emxlZCBieSBzb21lIHF1ZXN0aW9ucy4gRmlyc3QsIHRoZSBj
aGFuZ2Ugb2YgDQo+IHRoZSB6b25lIGNvbnRlbnQgb2YgYW4gYXV0aG9yaXR5IHNlcnZlciBkb2Vz
IG5vdCBtZWFuIHRoYXQgYSBjb3JyZXNwb25kaW5nIHJlY3Vyc2l2ZSBzZXJ2ZXIgDQo+IGhhcyB0
byBmbHVzaCBpdHMgY2FjaGUsIHNpbmNlIGEgcmVjdXJzaXZlIHNlcnZlciB1c3VhbGx5IGp1c3Qg
Y2FjaGUgYSBzbWFsbCBwYXJ0IG9mIHpvbmUgY29udGVudA0KPiBvZiBhbiBhdXRob3JpdHkgc2Vy
dmVyIGJ1dCBub3QgYWxsLiBBbHNvLCBhbiBhdXRob3JpdHkgc2VydmVyIGRvZXMgbm90IGtub3cg
d2hpY2ggUlJzIG9mIGl0cyANCj4gem9uZSBjb250ZW50IGFyZSBjYWNoZWQgaW4gcmVjdXJzaXZl
IHNlcnZlcnMuIFNvIHN1Y2ggbWVjaGFuaXNtIG9mIEROUyBGTFVTSCBtYXkgYnJpbmcgYWJvdXQg
DQo+IHNvbWUgYWRkaXRpb25hbCB0cmFmZmljIGJldHdlZW4gYXV0aG9yaXR5IGFuZCByZWN1cnNp
dmUgc2VydmVycyB3aXRoIG5vIGJlbmVmaXQuDQoNCkkgYWdyZWUgdGhhdCBpbiBtYW55IGNhc2Vz
IHRoaXMgaXMgYSBmYWlybHkgY29hcnNlIG1lY2hhbmlzbTsgaG93ZXZlciwgYXJndWFibHkgdGhl
cmUgYXJlIHNpdHVhdGlvbnMgd2hlcmUgaW5jdXJyaW5nIHRoYXQgb3ZlcmhlYWQgaXMgYmV0dGVy
IHRoYW4gZW5kdXJpbmcgYmFkIGRhdGEgdGhhdCBpcyB3aWRlbHktY2FjaGVkLg0KDQpGb2xsb3dp
bmcgdGhlIHJlY2VudCBpbmNpZGVudCBhZmZlY3RpbmcgdmFyaW91cyAuQ09NIG5hbWVzIHRoZXJl
IHdlcmUgd2lkZXNwcmVhZCBwbGVhcyB0byByZXNvbHZlciBvcGVyYXRvcnMgdG8gImZsdXNoIHlv
dXIgY2FjaGUiLiBJdCBzZWVtcyBsaWtlbHkgdGhhdCBzb21lIHBlb3BsZSBpbnRlcnByZXRlZCB0
aGF0IHJlcXVlc3Qgb24gZmFjZS12YWx1ZSwgYW5kIGZsdXNoZWQgYWxsIHJlY29yZHMgZnJvbSB0
aGVpciBjYWNoZXMuIEZsdXNoaW5nIGp1c3QgdGhlIENPTSBkb21haW4gKG9yIHNwZWNpZmljIHN1
Yi1kb21haW5zKSB3b3VsZCBoYXZlIGJlZW4gYmV0dGVyLiBUaGlzIG1lY2hhbmlzbSB3b3VsZCBm
YWNpbGl0YXRlIGVpdGhlciBvZiB0aG9zZS4NCg0KSSBhcHByZWNpYXRlIHRoZSBwcmV2aW91cyBw
YXJhZ3JhcGggaXMgbGVzcyB0aGFuIGVudGlyZWx5IGNvbnZpbmNpbmcgOi0pDQoNClRoZSBCSVog
ZXZlbnQgd2hlcmVieSAoaXQgYXBwZWFycyBmcm9tIHRoZSBvdXRzaWRlKSBhbiBhcGV4IEROU0tF
WSBSUlNldCB3YXMgcHVibGlzaGVkIHRoYXQgZGlkIG5vdCBpbmNsdWRlIGEga2V5IGNvcnJlc3Bv
bmRpbmcgdG8gdGhlIEJJWiBEUyBSUlNldCBpbiB0aGUgcm9vdCB6b25lIHdvdWxkIGhhdmUgYmVl
biBhbm90aGVyIGV4YW1wbGUgd2hlcmUgZmx1c2hpbmcgdGhlIGVudGlyZSBCSVogZG9tYWluIHdv
dWxkIGhhdmUgYmVlbiBvdmVya2lsbCwgYnV0IGFyZ3VhYmx5IGJldHRlciAoZm9yIHZhbGlkYXRv
cnMpIHRoYW4gZG9pbmcgbm90aGluZy4NCg0KSSBhZ3JlZSB0aGF0IGl0IHdvdWxkIG1ha2UgbGl0
dGxlIHNlbnNlIGZvciBhbiBhdXRob3JpdHkgc2VydmVyIG9wZXJhdG9yIGluIHRoZSBhYnNlbmNl
IG9mIGEgcHJvYmxlbSB0byBmbHVzaCByZW1vdGUgY2FjaGVzIGV2ZXJ5IHRpbWUgYSBuZXcgem9u
ZSB3YXMgcHVibGlzaGVkLiBJIHdvdWxkIGV4cGVjdCBzcGVjaWZpYyBob29rcyB0byBiZSBpbiBw
bGFjZSB0byBhbGxvdyBmbHVzaCBkaXJlY3Rpb25zIHRvIGJlIHByb3BhZ2F0ZWQgdW5kZXIgbWFu
dWFsIG9wZXJhdG9yIGNvbnRyb2wsIHJhdGhlciB0aGFuIGF1dG9tYXRpY2FsbHksIHRyaWdnZXJl
ZCBieSBhIFNPQSBzZXJpYWwgYnVtcC4NCg0KVGhlcmUgaXMgYSBkaXNjb250aW51aXR5IGhlcmUg
YmV0d2VlbiB0aGUgY3VycmVudCB1c2Ugb2YgRE5TIE5PVElGWSBhbmQgdGhlIHByb3Bvc2VkIG5l
dyB1c2U7IHRoZSBmb3JtZXIgaXMgYmFzZWQgb24gem9uZXMsIHdoaWxlIHRoZSBsYXR0ZXIgaXMg
YmFzZWQgb24gZG9tYWlucy4gVGhlcmUgaXMgYW4gYXJndW1lbnQgaGVyZSBmb3IgYSBuZXcgb3Bj
b2RlOyB0aGUgcmV1c2Ugb2YgTk9USUZZIHNlZW1lZCBleHBlZGllbnQgd2hlbiBJIHdyb3RlIHRo
ZSBkcmFmdCwgYnV0IHBlcmhhcHMgaXQncyBub3QgdGhlIGJlc3Qgd2F5Lg0KDQo+IFNlY29uZCwg
aG93IA0KPiBkb2VzIHRoZSBhdXRob3JpdHkgc2VydmVyIG9idGFpbiB0aGUgSVBzIG9mIHJlY3Vy
c2l2ZSBzZXJ2ZXJzPyBGcm9tIHF1ZXJ5IGxvZ3M/IFRoZW4gdGhlIA0KPiBhdXRob3JpdHkgc2Vy
dmVyIHNlbmRzIEROUyBGTFVTSCB0byBhbGwgb3IgcGFydCBvZiByZWN1cnNpdmUgc2VydmVycz8g
SXQgc2VlbXMgdGhhdCB0aGVyZSANCj4gYXJlIGJpZyBkaWZmZXJlbmNlcyBiZXR3ZWVuIEROUyBO
T1RJRlkgYW5kIHNvIGNhbGxlZCBETlMgRkxVU0ggYW5kIHRodXMgbW9yZSB0aGluZ3MgbmVlZCB0
byANCj4gYmUgY2xhcmlmaWVkLg0KDQpJIGNhbiB0aGluayBvZiB2YXJpb3VzIG1vZGVscyBmb3Ig
dGhpcy4NCg0KQmlsYXRlcmFsIGFncmVlbWVudHMgYmV0d2VlbiBhdXRob3JpdHkgc2VydmVyIG9w
ZXJhdG9ycyBhbmQgcmVjdXJzaXZlIHNlcnZlciBvcGVyYXRvcnMgd291bGQgaW52b2x2ZSBzaGFy
aW5nIG9mIFRTSUcgc2VjcmV0cyBhcyB3ZWxsIGFzIHNlcnZlciBhZGRyZXNzZXMuIEEgc2V0IG9m
IGJpbGF0cyB3aWxsIG5vdCBzY2FsZSB0byB0aGUgd2hvbGUgSW50ZXJuZXQsIG9idmlvdXNseSwg
YnV0IHBlcmhhcHMgaXMgZ29vZCBlbm91Z2ggdG8gZGVhbCB3aXRoIHBhcnRpY3VsYXIga25vd24g
cmVzb2x2ZXJzIHRoYXQgc2VydmUgbGFyZ2UgY29tbXVuaXRpZXMgb2YgdXNlcnMgKGUuZy4gR29v
Z2xlIEROUywgT3BlbkROUywgQ29tY2FzdCBETlMpLg0KDQpBIG1lY2hhbmlzbSBzdWNoIGFzIHRo
aXMgd291bGQgZW5hYmxlIGEgY2xlYXJpbmdob3VzZSBzdHlsZSBidXNpbmVzcyBtb2RlbCB3aGVy
ZSByZXNvbHZlciBvcGVyYXRvcnMgYW5kIGF1dGhvcml0eSBzZXJ2ZXIgb3BlcmF0b3JzIGNvdWxk
IHN1YnNjcmliZSB0byBhIHNlcnZpY2UgdGhhdCBtZWRpYXRlZCB0aGUgZmx1c2ggZGlyZWN0aW9u
cyBiZXR3ZWVuIGF1dGhvcml0eSBzZXJ2ZXJzIGFuZCByZWN1cnNpdmUgc2VydmVycywgYWN0aW5n
IGFzIGEgdHJ1c3RlZCBpbnRlcm1lZGlhcnkuDQoNCg0KSm9lDQoNCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpETlNPUCBtYWlsaW5nIGxpc3QNCkROU09Q
QGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Ruc29wDQoN
Cg0KDQoNCg0KIA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KRE5TT1AgbWFpbGluZyBsaXN0DQpETlNPUEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbnNvcA==

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

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
DIV.FoxDiv20130630002813276320 {
	LINE-HEIGHT: 1.5; FONT-FAMILY: verdana; COLOR: #000000; FONT-SIZE: 10pt
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: verdana; COLOR: #000000; FONT-SIZE: 10pt
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18156"></HEAD>
<BODY style=3D"MARGIN: 10px" text=3D#000000>
<DIV style=3D"FONT-FAMILY: Verdana">
<DIV>How&nbsp;to&nbsp;propagate&nbsp;the&nbsp;newly&nbsp;generated&nbsp;(o=
r=20
newly changed)=20
DNS&nbsp;resource&nbsp;records&nbsp;(RRs)&nbsp;from&nbsp;authority&nbsp;to=
&nbsp;recursive&nbsp;servers&nbsp;is&nbsp;obviously&nbsp;very&nbsp;importa=
nt&nbsp;for&nbsp;the&nbsp;DNS&nbsp;system.&nbsp;</DIV>
<DIV>For&nbsp;RR&nbsp;propagation,&nbsp;there&nbsp;are&nbsp;fundamentally&=
nbsp;two&nbsp;approaches:&nbsp;pull-based&nbsp;and&nbsp;push-based&nbsp;ap=
proach.&nbsp;In&nbsp;the&nbsp;former&nbsp;one,&nbsp;recursive&nbsp;servers=
&nbsp;pull&nbsp;RRs&nbsp;from&nbsp;authority&nbsp;</DIV>
<DIV>servers&nbsp;when&nbsp;the&nbsp;TTL&nbsp;expires.&nbsp;Usually,&nbsp;=
this&nbsp;kind&nbsp;of&nbsp;approach&nbsp;has&nbsp;advantages&nbsp;of&nbsp=
;low&nbsp;traffic&nbsp;overhead&nbsp;and&nbsp;high&nbsp;resilience&nbsp;bu=
t&nbsp;a&nbsp;disadvantage&nbsp;of&nbsp;bad&nbsp;real&nbsp;time.&nbsp;</DI=
V>
<DIV>In&nbsp;the&nbsp;latter&nbsp;one,&nbsp;authority&nbsp;servers&nbsp;pu=
sh&nbsp;the&nbsp;RRs&nbsp;to&nbsp;recursive&nbsp;servers&nbsp;when&nbsp;zo=
ne&nbsp;file&nbsp;is&nbsp;changed.&nbsp;This&nbsp;approach&nbsp;has&nbsp;g=
ood&nbsp;real&nbsp;time&nbsp;but&nbsp;brings&nbsp;very&nbsp;high&nbsp;traf=
fic&nbsp;</DIV>
<DIV>overhead&nbsp;since&nbsp;authority&nbsp;servers&nbsp;do&nbsp;not&nbsp=
;know&nbsp;which&nbsp;RRs&nbsp;is&nbsp;needed&nbsp;by&nbsp;recursive&nbsp;=
servers.&nbsp;Obviously,&nbsp;the&nbsp;pull-based&nbsp;approach&nbsp;now=20
is&nbsp;widely&nbsp;used&nbsp;in&nbsp;DNS&nbsp;due&nbsp;to&nbsp;its&nbsp;s=
implicity.&nbsp;</DIV>
<DIV>If&nbsp;there&nbsp;is&nbsp;a&nbsp;third&nbsp;approach,&nbsp;it&nbsp;m=
ust&nbsp;be&nbsp;a&nbsp;mixture&nbsp;of&nbsp;pull-based&nbsp;and&nbsp;push=
-based&nbsp;approaches&nbsp;and&nbsp;a&nbsp;new&nbsp;signaling=20
protocol&nbsp;between&nbsp;authority&nbsp;and&nbsp;recursive&nbsp;servers&=
nbsp;may&nbsp;</DIV>
<DIV>be&nbsp;needed&nbsp;to&nbsp;schedule&nbsp;the&nbsp;transmission&nbsp;=
of&nbsp;RRs&nbsp;(DNS&nbsp;NOTIFY&nbsp;can&nbsp;be&nbsp;taken&nbsp;as&nbsp=
;an&nbsp;example).&nbsp;However,&nbsp;the&nbsp;drawback&nbsp;of&nbsp;the&n=
bsp;second&nbsp;approach&nbsp;is&nbsp;also&nbsp;brought&nbsp;into&nbsp;the=
&nbsp;third&nbsp;</DIV>
<DIV>one.&nbsp;Lastly,&nbsp;though&nbsp;I&nbsp;am&nbsp;not&nbsp;totally=20
satisfied&nbsp;with&nbsp;the&nbsp;currently&nbsp;used&nbsp;approach,&nbsp;=
I&nbsp;have&nbsp;not&nbsp;got=20
a&nbsp;better&nbsp;idea&nbsp;yet.=20
Anyway,&nbsp;DNS&nbsp;NOTIFY&nbsp;is&nbsp;a&nbsp;good&nbsp;start&nbsp;in&n=
bsp;my&nbsp;opinion.=20
</DIV>
<DIV>&nbsp;</DIV></DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV style=3D"FONT-FAMILY: Verdana"><SPAN>
<DIV><SPAN style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; FONT-=
SIZE: 10.5pt">Guangqing=20
Deng</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; FONT-SIZE: 10.5p=
t">CNNIC&nbsp;</SPAN></DIV></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:tim.wicinski@teamaol.com">Tim=20
Wicinski</A></DIV>
<DIV><B>Date:</B>&nbsp;2013-06-28&nbsp;16:56</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:jewforice@gmail.com">ice jew</A>; <=
A=20
href=3D"mailto:dengguangqing@cnnic.cn">Guangqing Deng</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:dnsop@ietf.org">dnsop</A>; <A=20
href=3D"mailto:jabley@hopcount.ca">Joe Abley</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: [DNSOP] Fwd: New Version Notification for=20
draft-jabley-dnsop-dns-flush-00.txt</DIV></DIV></DIV>
<DIV>
<DIV class=3DFoxDiv20130630002813276320><TT>Actually flushing resolver cac=
hes=20
in&nbsp; larger environments (data center/enterprise/etc) where even short=
 TTLs=20
doesn't quite handle unexpected events, and there is a need to have consis=
tent=20
answers, even if the consistency is NXDOMAIN. <BR><BR>I don't know if the =
NOTIFY=20
semantic mechanism (while a simple way of avoiding creating a new mechanis=
m) is=20
the correct method.<BR><BR>tim<BR>&nbsp;<BR></TT>
<DIV class=3Dmoz-cite-prefix>On 6/26/13 1:39 AM, ice jew wrote:<BR></DIV>
<BLOCKQUOTE=20
cite=3Dmid:CAB3ZD+=3DUuVEi48GFMuEp2OwqZVQzKfbZts3z03f9m6P8M_NjJw@mail.gmai=
l.com=20
type=3D"cite">
  <DIV dir=3Dltr>This draft does provide some new possibility for decrease=
 the=20
  negative effects for the authority name server's mis-configuration in a=20
  certain way. But I don't think it will work in the real world &nbsp;even=
 if=20
  all prerequisites are meant.=20
  <DIV><BR>
  <DIV>First, there is standard way to solve this problem, as Guanqing say=
s,=20
  it's to shorten the TTL (both positive and negative cache). This may lea=
d to=20
  load increase for the authority name servers and &nbsp;recursive resolve=
r. But=20
  this method take the least risk.</DIV>
  <DIV><BR></DIV>
  <DIV>Second, I think it won't work under the condition that &nbsp;the=20
  recursive resolver and the cache name server are deprived. The authority=
=20
  cleans the &nbsp;cache of the recursive resolver from the log &nbsp;but =
the=20
  cache name server won't go to the recursive resolver for a newer=20
  &nbsp;response until the TTL is expired. &nbsp;And the bad data in to ca=
che=20
  name server still responses to the incoming queries. The=20
  cleaning-cache-mechanism doesn't help to decrease the negative=20
  effect.</DIV></DIV>
  <DIV><BR></DIV></DIV>
  <DIV class=3Dgmail_extra><BR><BR>
  <DIV class=3Dgmail_quote>On Wed, Jun 26, 2013 at 10:26 AM, Guangqing Den=
g <SPAN=20
  dir=3Dltr>&lt;<A href=3D"mailto:dengguangqing@cnnic.cn" target=3D_blank=20
  moz-do-not-send=3D"true">dengguangqing@cnnic.cn</A>&gt;</SPAN> wrote:<BR=
>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING=
-LEFT: 1ex"=20
  class=3Dgmail_quote>
    <DIV style=3D"MARGIN: 10px">
    <DIV style=3D"FONT-FAMILY: Verdana">
    <DIV>Hi,&nbsp;Joe.&nbsp;Just&nbsp;as&nbsp;you&nbsp;said,&nbsp;the&nbsp=
;need&nbsp;of&nbsp;flushing&nbsp;cache&nbsp;exists&nbsp;to&nbsp;a&nbsp;cer=
tain&nbsp;extent.&nbsp;But&nbsp;maybe&nbsp;first&nbsp;we&nbsp;should&nbsp;=
check&nbsp;</DIV>
    <DIV>why&nbsp;the&nbsp;cache&nbsp;needs&nbsp;to&nbsp;be&nbsp;flushed.&=
nbsp;Is&nbsp;it&nbsp;due&nbsp;to&nbsp;errors&nbsp;in&nbsp;zone&nbsp;file,&=
nbsp;other&nbsp;configuration&nbsp;errors&nbsp;in&nbsp;authority&nbsp;serv=
ers</DIV>
    <DIV>or&nbsp;the&nbsp;inefficiency&nbsp;of&nbsp;TTL&nbsp;mechanism?&nb=
sp;For&nbsp;the&nbsp;first&nbsp;two&nbsp;reasons,&nbsp;it&nbsp;is&nbsp;bet=
ter&nbsp;to&nbsp;do&nbsp;other&nbsp;work&nbsp;to&nbsp;avoid&nbsp;such&nbsp=
;kinds</DIV>
    <DIV>of&nbsp;errors&nbsp;and&nbsp;then&nbsp;cache&nbsp;flushing&nbsp;i=
s&nbsp;bypassed.&nbsp;For&nbsp;the&nbsp;third&nbsp;reason,&nbsp;shortening=
&nbsp;the&nbsp;TTL&nbsp;may&nbsp;be&nbsp;a&nbsp;potential&nbsp;approach,&n=
bsp;</DIV>
    <DIV>and&nbsp;also&nbsp;DNS&nbsp;FLUSH&nbsp;can&nbsp;be&nbsp;taken&nbs=
p;as&nbsp;an&nbsp;effective&nbsp;supplement&nbsp;of&nbsp;TTL&nbsp;mechanis=
m.&nbsp;Fundamentally,&nbsp;TTL&nbsp;mechanism&nbsp;is&nbsp;based&nbsp;</D=
IV>
    <DIV>on&nbsp;"pull"&nbsp;fashion&nbsp;while&nbsp;DNS&nbsp;FLUSH&nbsp;s=
omehow&nbsp;is&nbsp;based&nbsp;on&nbsp;"push"&nbsp;fashion.&nbsp;And&nbsp;=
then&nbsp;how&nbsp;to&nbsp;effectively&nbsp;bring&nbsp;them&nbsp;together<=
/DIV>
    <DIV>is&nbsp;not&nbsp;an&nbsp;easy&nbsp;job.&nbsp;Anyway,&nbsp;this&nb=
sp;draft&nbsp;brings&nbsp;a&nbsp;new&nbsp;choice&nbsp;for&nbsp;authority&n=
bsp;server&nbsp;operators&nbsp;and&nbsp;resolver&nbsp;server&nbsp;operator=
s.</DIV></DIV>
    <DIV>&nbsp;</DIV>
    <HR style=3D"MIN-HEIGHT: 1px; WIDTH: 210px" align=3Dleft color=3D#b5c4=
df SIZE=3D1>

    <DIV style=3D"FONT-FAMILY: Verdana"><SPAN>
    <DIV><SPAN style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; FONT-SIZE: 10.5pt=
">Guangqing=20
    Deng</SPAN></DIV>
    <DIV><SPAN=20
    style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; FONT-SIZE: 10.5pt">CNNIC&nbs=
p;</SPAN></DIV></SPAN></DIV>
    <DIV>&nbsp;</DIV>
    <DIV=20
    style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING=
-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1=
pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
    <DIV=20
    style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; B=
ACKGROUND: #efefef; FONT-SIZE: 12px; PADDING-TOP: 8px">
    <DIV><B>From:</B>&nbsp;<A href=3D"mailto:jabley@hopcount.ca" target=3D=
_blank=20
    moz-do-not-send=3D"true">Joe Abley</A></DIV>
    <DIV><B>Date:</B>&nbsp;2013-06-25&nbsp;21:10</DIV>
    <DIV><B>To:</B>&nbsp;<A href=3D"mailto:dengguangqing@cnnic.cn" target=
=3D_blank=20
    moz-do-not-send=3D"true">dengguangqing</A></DIV>
    <DIV><B>CC:</B>&nbsp;<A href=3D"mailto:dnsop@ietf.org" target=3D_blank=
=20
    moz-do-not-send=3D"true">dnsop@ietf.org</A></DIV>
    <DIV><B>Subject:</B>&nbsp;Re: [DNSOP] Fwd: New Version Notification fo=
r=20
    draft-jabley-dnsop-dns-flush-00.txt</DIV></DIV></DIV>
    <DIV>
    <DIV class=3Dh5>
    <DIV>
    <DIV>Hi&nbsp;Guangqing,</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>On&nbsp;2013-06-25,&nbsp;at&nbsp;08:02,&nbsp;"Guangqing&nbsp;Deng=
"&nbsp;&lt;<A=20
    href=3D"mailto:dengguangqing@cnnic.cn" target=3D_blank=20
    moz-do-not-send=3D"true">dengguangqing@cnnic.cn</A>&gt;&nbsp;wrote:</D=
IV>
    <DIV>&nbsp;</DIV>
    <DIV>&gt;&nbsp;Hi,&nbsp;Joe,&nbsp;I&nbsp;like&nbsp;this&nbsp;draft,&nb=
sp;though&nbsp;I&nbsp;am&nbsp;puzzled&nbsp;by&nbsp;some&nbsp;questions.&nb=
sp;First,&nbsp;the&nbsp;change&nbsp;of&nbsp;</DIV>
    <DIV>&gt;&nbsp;the&nbsp;zone&nbsp;content&nbsp;of&nbsp;an&nbsp;authori=
ty&nbsp;server&nbsp;does&nbsp;not&nbsp;mean&nbsp;that&nbsp;a&nbsp;correspo=
nding&nbsp;recursive&nbsp;server&nbsp;</DIV>
    <DIV>&gt;&nbsp;has&nbsp;to&nbsp;flush&nbsp;its&nbsp;cache,&nbsp;since&=
nbsp;a&nbsp;recursive&nbsp;server&nbsp;usually&nbsp;just&nbsp;cache&nbsp;a=
&nbsp;small&nbsp;part&nbsp;of&nbsp;zone&nbsp;content</DIV>
    <DIV>&gt;&nbsp;of&nbsp;an&nbsp;authority&nbsp;server&nbsp;but&nbsp;not=
&nbsp;all.&nbsp;Also,&nbsp;an&nbsp;authority&nbsp;server&nbsp;does&nbsp;no=
t&nbsp;know&nbsp;which&nbsp;RRs&nbsp;of&nbsp;its&nbsp;</DIV>
    <DIV>&gt;&nbsp;zone&nbsp;content&nbsp;are&nbsp;cached&nbsp;in&nbsp;rec=
ursive&nbsp;servers.&nbsp;So&nbsp;such&nbsp;mechanism&nbsp;of&nbsp;DNS&nbs=
p;FLUSH&nbsp;may&nbsp;bring&nbsp;about&nbsp;</DIV>
    <DIV>&gt;&nbsp;some&nbsp;additional&nbsp;traffic&nbsp;between&nbsp;aut=
hority&nbsp;and&nbsp;recursive&nbsp;servers&nbsp;with&nbsp;no&nbsp;benefit=
.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>I&nbsp;agree&nbsp;that&nbsp;in&nbsp;many&nbsp;cases&nbsp;this&nbs=
p;is&nbsp;a&nbsp;fairly&nbsp;coarse&nbsp;mechanism;&nbsp;however,&nbsp;arg=
uably&nbsp;there&nbsp;are&nbsp;situations&nbsp;where&nbsp;incurring&nbsp;t=
hat&nbsp;overhead&nbsp;is&nbsp;better&nbsp;than&nbsp;enduring&nbsp;bad&nbs=
p;data&nbsp;that&nbsp;is&nbsp;widely-cached.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>Following&nbsp;the&nbsp;recent&nbsp;incident&nbsp;affecting&nbsp;=
various&nbsp;.COM&nbsp;names&nbsp;there&nbsp;were&nbsp;widespread&nbsp;ple=
as&nbsp;to&nbsp;resolver&nbsp;operators&nbsp;to&nbsp;"flush&nbsp;your&nbsp=
;cache".&nbsp;It&nbsp;seems&nbsp;likely&nbsp;that&nbsp;some&nbsp;people&nb=
sp;interpreted&nbsp;that&nbsp;request&nbsp;on&nbsp;face-value,&nbsp;and&nb=
sp;flushed&nbsp;all&nbsp;records&nbsp;from&nbsp;their&nbsp;caches.&nbsp;Fl=
ushing&nbsp;just&nbsp;the&nbsp;COM&nbsp;domain&nbsp;(or&nbsp;specific&nbsp=
;sub-domains)&nbsp;would&nbsp;have&nbsp;been&nbsp;better.&nbsp;This&nbsp;m=
echanism&nbsp;would&nbsp;facilitate&nbsp;either&nbsp;of&nbsp;those.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>I&nbsp;appreciate&nbsp;the&nbsp;previous&nbsp;paragraph&nbsp;is&n=
bsp;less&nbsp;than&nbsp;entirely&nbsp;convincing&nbsp;:-)</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>The&nbsp;BIZ&nbsp;event&nbsp;whereby&nbsp;(it&nbsp;appears&nbsp;f=
rom&nbsp;the&nbsp;outside)&nbsp;an&nbsp;apex&nbsp;DNSKEY&nbsp;RRSet&nbsp;w=
as&nbsp;published&nbsp;that&nbsp;did&nbsp;not&nbsp;include&nbsp;a&nbsp;key=
&nbsp;corresponding&nbsp;to&nbsp;the&nbsp;BIZ&nbsp;DS&nbsp;RRSet&nbsp;in&n=
bsp;the&nbsp;root&nbsp;zone&nbsp;would&nbsp;have&nbsp;been&nbsp;another&nb=
sp;example&nbsp;where&nbsp;flushing&nbsp;the&nbsp;entire&nbsp;BIZ&nbsp;dom=
ain&nbsp;would&nbsp;have&nbsp;been&nbsp;overkill,&nbsp;but&nbsp;arguably&n=
bsp;better&nbsp;(for&nbsp;validators)&nbsp;than&nbsp;doing&nbsp;nothing.</=
DIV>
    <DIV>&nbsp;</DIV>
    <DIV>I&nbsp;agree&nbsp;that&nbsp;it&nbsp;would&nbsp;make&nbsp;little&n=
bsp;sense&nbsp;for&nbsp;an&nbsp;authority&nbsp;server&nbsp;operator&nbsp;i=
n&nbsp;the&nbsp;absence&nbsp;of&nbsp;a&nbsp;problem&nbsp;to&nbsp;flush&nbs=
p;remote&nbsp;caches&nbsp;every&nbsp;time&nbsp;a&nbsp;new&nbsp;zone&nbsp;w=
as&nbsp;published.&nbsp;I&nbsp;would&nbsp;expect&nbsp;specific&nbsp;hooks&=
nbsp;to&nbsp;be&nbsp;in&nbsp;place&nbsp;to&nbsp;allow&nbsp;flush&nbsp;dire=
ctions&nbsp;to&nbsp;be&nbsp;propagated&nbsp;under&nbsp;manual&nbsp;operato=
r&nbsp;control,&nbsp;rather&nbsp;than&nbsp;automatically,&nbsp;triggered&n=
bsp;by&nbsp;a&nbsp;SOA&nbsp;serial&nbsp;bump.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>There&nbsp;is&nbsp;a&nbsp;discontinuity&nbsp;here&nbsp;between&nb=
sp;the&nbsp;current&nbsp;use&nbsp;of&nbsp;DNS&nbsp;NOTIFY&nbsp;and&nbsp;th=
e&nbsp;proposed&nbsp;new&nbsp;use;&nbsp;the&nbsp;former&nbsp;is&nbsp;based=
&nbsp;on&nbsp;zones,&nbsp;while&nbsp;the&nbsp;latter&nbsp;is&nbsp;based&nb=
sp;on&nbsp;domains.&nbsp;There&nbsp;is&nbsp;an&nbsp;argument&nbsp;here&nbs=
p;for&nbsp;a&nbsp;new&nbsp;opcode;&nbsp;the&nbsp;reuse&nbsp;of&nbsp;NOTIFY=
&nbsp;seemed&nbsp;expedient&nbsp;when&nbsp;I&nbsp;wrote&nbsp;the&nbsp;draf=
t,&nbsp;but&nbsp;perhaps&nbsp;it's&nbsp;not&nbsp;the&nbsp;best&nbsp;way.</=
DIV>
    <DIV>&nbsp;</DIV>
    <DIV>&gt;&nbsp;Second,&nbsp;how&nbsp;</DIV>
    <DIV>&gt;&nbsp;does&nbsp;the&nbsp;authority&nbsp;server&nbsp;obtain&nb=
sp;the&nbsp;IPs&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp;From&nbsp;query&=
nbsp;logs?&nbsp;Then&nbsp;the&nbsp;</DIV>
    <DIV>&gt;&nbsp;authority&nbsp;server&nbsp;sends&nbsp;DNS&nbsp;FLUSH&nb=
sp;to&nbsp;all&nbsp;or&nbsp;part&nbsp;of&nbsp;recursive&nbsp;servers?&nbsp=
;It&nbsp;seems&nbsp;that&nbsp;there&nbsp;</DIV>
    <DIV>&gt;&nbsp;are&nbsp;big&nbsp;differences&nbsp;between&nbsp;DNS&nbs=
p;NOTIFY&nbsp;and&nbsp;so&nbsp;called&nbsp;DNS&nbsp;FLUSH&nbsp;and&nbsp;th=
us&nbsp;more&nbsp;things&nbsp;need&nbsp;to&nbsp;</DIV>
    <DIV>&gt;&nbsp;be&nbsp;clarified.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>I&nbsp;can&nbsp;think&nbsp;of&nbsp;various&nbsp;models&nbsp;for&n=
bsp;this.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>Bilateral&nbsp;agreements&nbsp;between&nbsp;authority&nbsp;server=
&nbsp;operators&nbsp;and&nbsp;recursive&nbsp;server&nbsp;operators&nbsp;wo=
uld&nbsp;involve&nbsp;sharing&nbsp;of&nbsp;TSIG&nbsp;secrets&nbsp;as&nbsp;=
well&nbsp;as&nbsp;server&nbsp;addresses.&nbsp;A&nbsp;set&nbsp;of&nbsp;bila=
ts&nbsp;will&nbsp;not&nbsp;scale&nbsp;to&nbsp;the&nbsp;whole&nbsp;Internet=
,&nbsp;obviously,&nbsp;but&nbsp;perhaps&nbsp;is&nbsp;good&nbsp;enough&nbsp=
;to&nbsp;deal&nbsp;with&nbsp;particular&nbsp;known&nbsp;resolvers&nbsp;tha=
t&nbsp;serve&nbsp;large&nbsp;communities&nbsp;of&nbsp;users&nbsp;(e.g.&nbs=
p;Google&nbsp;DNS,&nbsp;OpenDNS,&nbsp;Comcast&nbsp;DNS).</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>A&nbsp;mechanism&nbsp;such&nbsp;as&nbsp;this&nbsp;would&nbsp;enab=
le&nbsp;a&nbsp;clearinghouse&nbsp;style&nbsp;business&nbsp;model&nbsp;wher=
e&nbsp;resolver&nbsp;operators&nbsp;and&nbsp;authority&nbsp;server&nbsp;op=
erators&nbsp;could&nbsp;subscribe&nbsp;to&nbsp;a&nbsp;service&nbsp;that&nb=
sp;mediated&nbsp;the&nbsp;flush&nbsp;directions&nbsp;between&nbsp;authorit=
y&nbsp;servers&nbsp;and&nbsp;recursive&nbsp;servers,&nbsp;acting&nbsp;as&n=
bsp;a&nbsp;trusted&nbsp;intermediary.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>Joe</DIV></DIV></DIV></DIV></DIV><BR>____________________________=
___________________<BR>DNSOP=20
    mailing list<BR><A href=3D"mailto:DNSOP@ietf.org"=20
    moz-do-not-send=3D"true">DNSOP@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D_blank=20
    moz-do-not-send=3D"true">https://www.ietf.org/mailman/listinfo/dnsop</=
A><BR><BR></BLOCKQUOTE></DIV><BR></DIV><BR>
  <FIELDSET class=3DmimeAttachmentHeader></FIELDSET> <BR><PRE wrap=3D"">__=
_____________________________________________
DNSOP mailing list
<A class=3Dmoz-txt-link-abbreviated href=3D"mailto:DNSOP@ietf.org">DNSOP@i=
etf.org</A>
<A class=3Dmoz-txt-link-freetext href=3D"https://www.ietf.org/mailman/list=
info/dnsop">https://www.ietf.org/mailman/listinfo/dnsop</A>
</PRE></BLOCKQUOTE><BR></DIV></DIV></BODY></HTML>

------=_001_NextPart881847005851_=------


From cet1@hermes.cam.ac.uk  Sat Jun 29 13:50:29 2013
Return-Path: <cet1@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBCA921F8C66 for <dnsop@ietfa.amsl.com>; Sat, 29 Jun 2013 13:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a4NE9P17hCJK for <dnsop@ietfa.amsl.com>; Sat, 29 Jun 2013 13:50:28 -0700 (PDT)
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 4EDE021F9F6C for <dnsop@ietf.org>; Sat, 29 Jun 2013 13:50:24 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:55452) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:cet1) id 1Ut266-0000e0-0A (Exim 4.80_167-5a66dd3) (return-path <cet1@hermes.cam.ac.uk>); Sat, 29 Jun 2013 21:50:18 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:cet1) id 1Ut266-0001eI-0M (Exim 4.72) (return-path <cet1@hermes.cam.ac.uk>); Sat, 29 Jun 2013 21:50:18 +0100
Received: from [131.111.11.47] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 29 Jun 2013 21:50:17 +0100
Date: 29 Jun 2013 21:50:17 +0100
From: Chris Thompson <cet1@cam.ac.uk>
To: Joe Abley <jabley@hopcount.ca>
Message-ID: <Prayer.1.3.5.1306292150170.27002@hermes-2.csi.cam.ac.uk>
In-Reply-To: <BEE324D5-260E-4441-BCEF-26016F3DA0B8@hopcount.ca>
References: <20130628222333.29265.44695.idtracker@ietfa.amsl.com> <BEE324D5-260E-4441-BCEF-26016F3DA0B8@hopcount.ca>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Chris Thompson <cet1@hermes.cam.ac.uk>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-as112-dname-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Jun 2013 20:50:29 -0000

On Jun 28 2013, Joe Abley wrote:

>Hi all,
>
>As promised, here's a draft which describes the alternate approach
>(alternate to the omniscient, custom-code route that our other document
>proposes) of using DNAME to extend AS112 service.

This approach does seem quite attractive.

A point that maybe needs mention in section 6, in the context of caching.
For a DNAME-unaware resolver, this depends on the TTL of the synthesised
CNAME. RFC 2672 (Aug 1999) specified that this should be zero, and this
wasn't officially changed until RFC 6672 (June 2012) re-specified it as
a copy of the TTL of the DNAME. It perhaps ought to be emphasised that
the authoritative nameservers for zones containing DNAMEs referencing
EMPTY.AS112.ARPA should be using the later specification.

Does one have to worry about DNAME-broken resolvers? That is, ones that
choke on the presence of the DNAME in the answer and never get as far as
looking at the synthesised CNAME, effectively treating it as a SERVFAIL.
We certainly had some problems of that sort back in early 2011 when
we started using DNAMEs for reverse lookups of IPv4 addresses in
128.232.128.0/17. It's the reason why for 128.232.233.0/24 we use
256 CNAMEs rather than one DNAME.

><sales pitch>
>  This one has the side-effect of supporting DNSSEC-validatable redirection to AS112 nodes!
></sales pitch>

If the DNAME is signed, what effect is that going to have on overriding
local definitions of the redirected names (as in BIND's "automatic empty
zones")?

Of course if the scheme goes ahead, EMPTY.AS112.ARPA itself becomes an
obvious candidate for such a local definition as well.

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.
