MIME-Version: 1.0
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 17 Dec 2016 15:32:14 -0500
Message-ID: <CAPt1N1mykGTaGoUgMdXaQRR6tcMq676yML2UCK+fHui7dbmEVA@mail.gmail.com>
To: william manning <chinese.apricot@gmail.com>
Content-Type: multipart/alternative; boundary=001a114102d8fc93860543e094ad
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rb1fIEtZceXJb6_oasO9nSUZFRs>
Cc: dnsop WG <dnsop@ietf.org>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] Aggressive NSEC statistics
Precedence: list

--001a114102d8fc93860543e094ad
Content-Type: text/plain; charset=UTF-8

We are deep down a rathole here. If this is worthy of discussion, which I
don't dispute, it is probably better discussed under a different heading.

On Dec 17, 2016 3:17 PM, "william manning" <chinese.apricot@gmail.com>
wrote:

David, it would seem that fact-driven processes might serve the operational
ecosystem better than SWAG, don't you agree?
Warren, do you have, even antecdotal data on the impact of aggressive NSEC
and traffic to the roots, that would inform this discussion (maybe).  At
least it would give the root operators a heads up that they were, once
again, being asked to backstop issues that should be handled elsewhere.

/Wm

On Sat, Dec 17, 2016 at 11:42 AM, David Conrad <drc@virtualized.org> wrote:

> Bill,
>
> On Dec 17, 2016, at 11:36 AM, william manning <chinese.apricot@gmail.com>
> wrote:
> > Is there any public data to support the presumptions of excess capacity
> at the roots and the impact of NSEC aggressive use on the DNS?
>
> Warren provided some interesting anecdotes at the last IEPG, but I'm
> unaware of any formal modeling.
>
> > I know that in the previous century, punting on operational impact by
> guessing about outcomes was common.   I thought the IETF had moved away
> from SWAG and was working toward a more disciplined and fact based process
> for making changes.
>
> I make no comment on what the IETF has moved towards or away from.
>
> Regards,
> -drc
> (speaking only for myself)
>
>
>
>

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

--001a114102d8fc93860543e094ad
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">We are deep down a rathole here. If this is worthy of dis=
cussion, which I don&#39;t dispute, it is probably better discussed under a=
 different heading.=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Dec 17, 2016 3:17 PM, &quot;william manning&quot; &lt;<a h=
ref=3D"mailto:chinese.apricot@gmail.com">chinese.apricot@gmail.com</a>&gt; =
wrote:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Da=
vid, it would seem that fact-driven processes might serve the operational e=
cosystem better than SWAG, don&#39;t you agree?<div>Warren, do you have, ev=
en antecdotal data on the impact of aggressive NSEC and traffic to the root=
s, that would inform this discussion (maybe).=C2=A0 At least it would give =
the root operators a heads up that they were, once again, being asked to ba=
ckstop issues that should be handled elsewhere.</div><font color=3D"#888888=
"><div><br></div><div>/Wm=C2=A0</div></font></div><div class=3D"elided-text=
"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Dec 17,=
 2016 at 11:42 AM, David Conrad <span dir=3D"ltr">&lt;<a href=3D"mailto:drc=
@virtualized.org" target=3D"_blank">drc@virtualized.org</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Bill,<br>
<span><br>
On Dec 17, 2016, at 11:36 AM, william manning &lt;<a href=3D"mailto:chinese=
.apricot@gmail.com" target=3D"_blank">chinese.apricot@gmail.com</a>&gt; wro=
te:<br>
&gt; Is there any public data to support the presumptions of excess capacit=
y at the roots and the impact of NSEC aggressive use on the DNS?<br>
<br>
</span>Warren provided some interesting anecdotes at the last IEPG, but I&#=
39;m unaware of any formal modeling.<br>
<span><br>
&gt; I know that in the previous century, punting on operational impact by =
guessing about outcomes was common.=C2=A0 =C2=A0I thought the IETF had move=
d away from SWAG and was working toward a more disciplined and fact based p=
rocess for making changes.<br>
<br>
</span>I make no comment on what the IETF has moved towards or away from.<b=
r>
<div class=3D"m_8176217313132481634HOEnZb"><div class=3D"m_8176217313132481=
634h5"><br>
Regards,<br>
-drc<br>
(speaking only for myself)<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>
</div><br>______________________________<wbr>_________________<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" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
<br></blockquote></div><br></div>

--001a114102d8fc93860543e094ad--