Re: [dns-privacy] Possible use case: Opportunistic encryption for recursive to authoritative

Tim Wicinski <tjw.ietf@gmail.com> Thu, 06 August 2020 19:49 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CEB43A0E45 for <dns-privacy@ietfa.amsl.com>; Thu, 6 Aug 2020 12:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 6DS5pJoOCGiV for <dns-privacy@ietfa.amsl.com>; Thu, 6 Aug 2020 12:49:39 -0700 (PDT)
Received: from mail-oo1-xc32.google.com (mail-oo1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (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 D7FB43A0E44 for <dprive@ietf.org>; Thu, 6 Aug 2020 12:49:39 -0700 (PDT)
Received: by mail-oo1-xc32.google.com with SMTP id s190so9805435ooa.13 for <dprive@ietf.org>; Thu, 06 Aug 2020 12:49:39 -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=/2nADvptIiJz64vWK509+2qOUyKSB+1njd7YcnoVoHg=; b=CV1TNTPbvDtpr0uXuyvZUVeVV3W2mtD8VLyL1+QZtpWILoDHR0QPxyTnrHYoHaZG8F +cgFHn9s57bQXOWaQhLFrVcKboRY0UlCAL58bfSAFNm04XuicPkOSL0OsrKnN8s14Kis ueWUyHfZ0xhfzvVCbkeLOcvpL30c8svyRO9XMVVa2dloMF4IodCMJNe1uavgt7oaFMSy N4f/yKaE9tgMZOrU7uX2fd/TmsuX0wyrIHaRltJQEi39PtZ+GlDm8KUzF/dLlDzUD4v1 GPbkh1CdqOce93wRheOCxaXKTd1h718YtLN072xfFQGymxlMaxvGGZEAMka7vs6jyr4c xZ7Q==
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=/2nADvptIiJz64vWK509+2qOUyKSB+1njd7YcnoVoHg=; b=VWuVljbng/YCBWTuvRNOdIZcHv/HkBHHfIt8mwRYauIvwS6Vp9x7GDXROIiylKOLck 09Isuc8AB1FPv3nEnVOvtrgiDs61nqIYh8Z/VFJczatmTj1SE8OjHRxVAGH21xKo2sxn CQmzPxHa8xHu8Pw5mALXL6KH4P4ngzm7noj2yS7d3eSvvrNf3h0djvJcCYLU2U6XP+Tr ih8JdjNGOYX75k+SZuT/dBDzX9Q4pFj2O8q2HSx4nBqY7vqOw9CEgIazWgoXna+IYni9 6+tBCSiEnBOe9fC9upDHVgeQ/6JVqGqY8tB4nD9OfL8yvxSAEgtYtjqvwG26p4eVydpq VtTw==
X-Gm-Message-State: AOAM530lLB6qD5HpswFjHv/GrDioU3Bi0LMjjVSGAgacZWY5SYpHpY1k /e5gM96haGlOFEIi41EkaGYYRQ4Xc6CyWl0i6+Y=
X-Google-Smtp-Source: ABdhPJxz0UpUi87EFLDXrVRAxKmWXkw8SYk352UIXMxm2CWq7k9gvCnOkkXcd3a3/0mZicqkjOVFM/jXwDw075srU8s=
X-Received: by 2002:a4a:1542:: with SMTP id 63mr457796oon.73.1596743379108; Thu, 06 Aug 2020 12:49:39 -0700 (PDT)
MIME-Version: 1.0
References: <3BA75997-3DE4-4DF5-B1F5-C57DBC423288@icann.org> <8d295fe-f183-e13d-d619-2b847e4e2293@iecc.com>
In-Reply-To: <8d295fe-f183-e13d-d619-2b847e4e2293@iecc.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Thu, 06 Aug 2020 15:49:26 -0400
Message-ID: <CADyWQ+Hjmi3gZvVLj7qc-4VaMF1vRB-W8Z5_ykjoU=eNSvfCzw@mail.gmail.com>
To: "John R. Levine" <johnl@iecc.com>
Cc: Paul Hoffman <paul.hoffman@icann.org>, "dprive@ietf.org" <dprive@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e8c87405ac3ac97b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/JIBI8Xypir4SlIP8i6FgdqaWzSY>
Subject: Re: [dns-privacy] Possible use case: Opportunistic encryption for recursive to authoritative
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2020 19:49:42 -0000

(speaking not as a chair)

I think this is worth doing.

tim



On Thu, Aug 6, 2020 at 3:45 PM John R. Levine <johnl@iecc.com> wrote:

> Yes, this is worth doing.  Agree with comments that it has to be
> compatible with non-opportunistic encryption.
>
> R's,
> John
>
> PS: RFC 7435.
>
> > Greetings again. The following is a short text-based version of my
> slides from last week's WG meeting. I'd like to find out if this is one of
> the use cases that the WG would be interested in dealing with.
> >
> > Use case: Opportunistic encryption for recursive to authoritative
> >
> > In this use case, a resolver operator says “I’m happy to use encryption
> with the authoritative servers if it doesn’t slow down getting answers by
> much”, and an authoritative server says “I’m happy to use encryption with
> the recursive resolvers if it doesn’t cost me much”.
> >
> > Opportunistic encryption is defined in RFC 7535. From the abstract:
> "Protocol designs based on Opportunistic Security use encryption even when
> authentication is not available, and use authentication when possible,
> thereby removing barriers to the widespread use of encryption on the
> Internet."
> >
> > The assumptions behind the use case are:
> > • More encryption is good for the Internet
> > • Resolver vendors are smart and motivated
> > • Most resolvers don’t validate with DNSSEC and may never want to
> > • Authoritative operators don’t care much about encryption, but some
> would turn it on because more encryption is good for the Internet
> > • Other use cases for authentication stronger than opportunistic may
> appear and would co-exist with this one
> >
> > The other slides had thoughts about possible solutions that implement
> this use case, but before we go there, I wanted to find out if more than a
> handful of people here are interested in this use case. If so, I could turn
> the above into a draft with some possible solutions for us to bang on.
> >
> > --Paul Hoffman
> >
> >
>
> Regards,
> John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for
> Dummies",
> Please consider the environment before reading this e-mail. https://jl.ly
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy
>