Re: [DNSOP] Fwd: [Add] new draft: draft-grover-add-policy-detection-00

Rob Sayre <sayrer@gmail.com> Mon, 15 July 2019 01:41 UTC

Return-Path: <sayrer@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 A8AB0120118 for <dnsop@ietfa.amsl.com>; Sun, 14 Jul 2019 18:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYdks6ux9lLT for <dnsop@ietfa.amsl.com>; Sun, 14 Jul 2019 18:41:22 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCCF012001B for <dnsop@ietf.org>; Sun, 14 Jul 2019 18:41:22 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id s7so31537243iob.11 for <dnsop@ietf.org>; Sun, 14 Jul 2019 18:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rtXyOH38X7i9UVRjWFR5l6Lo94r5v7eC0ocr9yhzFqs=; b=MkmaUh0YzhS5/6XR/xf8xZR2c3GAKhOUCYgwIQ730K/YurD8VjhZGj7Rx3+iWJhouL KG7pQh5dttTTaKLSLTlq2mOVn/zMMYbon5uZ7YWbroM5+C7Px2Sd7OQrzQeYQaUG5YE4 055r+OZ0z5nTZHef1Ttr5ex2V+Lrea470U/Cv6Ndvhz7679cDUE586lLPGmOWenYoM7m K1qohz+mocoSzBqjrIpDpd/zq+1fEct9Tljtpl7g9SHp0dnY7JQeIPqkbJ2Y99cZpS+p 3ye9WfqN5o3CKsmlWwbowoHTgK5I1vCkZ3KFT0AzeicZUZHF8YiTRPpFRryftqTIRGf4 OeOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rtXyOH38X7i9UVRjWFR5l6Lo94r5v7eC0ocr9yhzFqs=; b=bSCEYxxduacypOfaumYDpEL36yZrmie659PhBGdjiK0vRpByUoBRYt49WZwmAJ/8e6 Jkf0mNGonu1jFyXE3UFFs+4lTC/soP6iXfSBjdCF1YHZhQc8l5q3XM9J1zv5rg4JrvZo 2q1ByatkuYCf8Tpy3WK8UobahG4gsqNPLSM+1HXiC6RC//QjfEK9BNAQfghCPuaTRs23 00aWWsbSp19t932oUSJ43L9LGBmyUN2YZdTP32SJF3toG7D40xx6wm8rsg9SN4YL5z3T xzgs56p5AUYUmhPiGIwzdBC8tC6c+1yzi+O46TQ2f57Le5XkTb7iCv3G2Wcb4EsYjwYj GaNg==
X-Gm-Message-State: APjAAAXM8vXepY8k9XJGlu1SBqDr/Um671Sx1GPNC0RFqIN8zlqnq4vM lwFGK/zifxuxl9bGj+p6arZfdNLade7i/oUUNKQ=
X-Google-Smtp-Source: APXvYqzKfDOtJlxho8PomZ2yJotorUwDhwBUsI8CQHmTgGYcpyx18j3XJvAQvb2Q1IDQdShME/06X1Qk1RDW3UfBSbQ=
X-Received: by 2002:a6b:bc42:: with SMTP id m63mr9904692iof.189.1563154881986; Sun, 14 Jul 2019 18:41:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SyVmgMpD6Cd=m2Z03nts-Bv9ZVgJkG8oaj_jzwYMUZuCg@mail.gmail.com> <4966582.gC1Lsr5W4Z@linux-9daj>
In-Reply-To: <4966582.gC1Lsr5W4Z@linux-9daj>
From: Rob Sayre <sayrer@gmail.com>
Date: Sun, 14 Jul 2019 18:41:10 -0700
Message-ID: <CAChr6SyapDz8ZKNU8nOuncPMWajBuE+eF3WMFP9GWAs+B-uP9g@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org
Content-Type: multipart/alternative; boundary="00000000000078483a058dae5be5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/O8VUhbgLziSRKt9sSYOB4q_LAkE>
Subject: Re: [DNSOP] Fwd: [Add] new draft: draft-grover-add-policy-detection-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@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, 15 Jul 2019 01:41:25 -0000

Thank you for the elegant response. BCP 61 describes this issue well, too.

https://tools.ietf.org/html/bcp61

DNS seems like it still operates in the clear, and that doesn't seem good.

thanks,
Rob



On Sun, Jul 14, 2019 at 6:34 PM Paul Vixie <paul@redbarn.org> wrote:

> On Sunday, 14 July 2019 23:09:00 UTC Rob Sayre wrote:
> > Paul Vixie wrote:
> > > ...
> >
> > Was DNS intentionally designed to be insecure?
>
> no. nor ip itself, or ncp which preceded it, or tcp, or udp, or icmp, or
> smtp,
> ot http. it was insecure because it evolved in a safe, germ free academic
> bubble. absolutely none of it was designed with billions of people in
> mind, or
> the full cross section of humanity which would include criminals and
> national
> intelligence services. the world of the internet in 2019 would have been
> seen
> as a total freak show by the community who deployed dns  in the 1980's.
>
> nothing that can be abused won't be. you may or may not believe this; it's
> considered controversial, and there are arguments being had about it today.
>
> but noone considered that now-controversial near-truism at all when the
> core
> internet protocols were first designed and implemented. the idea of abuse
> was
> considered novel in the 1990's when commercialization and privatization
> brought abuse into the internet world and burst the academic bubble. a lot
> of
> old timers blamed AOL and MSN and even Usenet for the problems, but in
> actuality, it's what humans _always_ do at scale. putting the full
> spectrum of
> human culture atop a technology platform designed for academic and
> professional culture should have been understood to be a recipe for
> disaster.
>
> --
> Paul
>
>
>