[dns-privacy] Fwd: New Version Notification for draft-schwartz-dprive-name-signal-00.txt

Ben Schwartz <bemasc@google.com> Tue, 08 June 2021 15:09 UTC

Return-Path: <bemasc@google.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 078F33A3394 for <dns-privacy@ietfa.amsl.com>; Tue, 8 Jun 2021 08:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level:
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 1is9M4_BVS5L for <dns-privacy@ietfa.amsl.com>; Tue, 8 Jun 2021 08:09:19 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 0746F3A3390 for <dns-privacy@ietf.org>; Tue, 8 Jun 2021 08:09:18 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id m18so21990966wrv.2 for <dns-privacy@ietf.org>; Tue, 08 Jun 2021 08:09:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=YjRmRSdXN62L+89N0S8RV5TqRs1KHXHSw2ZB3xN08SY=; b=Xx/lGXJ0+zkheokDLmqm+Q9TLWRPATjXzVXoAFprRYPw9/wTeigyh6NAnIz8pEqk5s WiwsnAibUyxt/wm+yJaZTjy/1EC2+WUbq+voEJWQNCcJN3fVGgBLfolvFmFlLZvxemSN xjVy3vdt0dE9Iir9E7brbesUciSz0bJ8p4YFu/pNft4jlfFz32rrRErto8Cn37jcf/1e vu7VfWFt9l/MIuOwjWvsB0wXP0CTaIivU5NvRFpyMsUo387pZmUkRwBKz1A0KutJ1OPS WJa/ujXz5tMVjT9TyuszmHFdpwy5Qw/j63s0tW8TctC5U3VrZVxRLiC5ovNUi4NHQC4s a99w==
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; bh=YjRmRSdXN62L+89N0S8RV5TqRs1KHXHSw2ZB3xN08SY=; b=bWS1rHIPG3/pmchjpk7cGZ61zonR9Cxrr1EYzssTKuMwUbh4SsSu0fiws9skjcqYcC 025U8QBaOidnM07As1gK/6rH68Cn5kO36Cc0QuPs2kELJtJDefyPwcHEp/Jt9vVZfgra nQ8ReCABH2lbRJpfZbwIypqgq8r3iAZPL7xBfMbShE9XbMA6ZMnVAOaVjpYj8zfAMH6W opc4ZltIDsWSQnvCYINbNZ7dHFcAD32HxIyFaDZqhSzvGA3WKhZy7SMZTG710Uxn9OBL t/anK6Ad3FTtUEotryrhb1gIFC4r2OFapOhUhRUL8H4FpvdJHORdwfoHV/zuh0zQFM83 qWvQ==
X-Gm-Message-State: AOAM530F6GAfpC9X/xfpNKszUrz1oSn6N6Udc+uJ96tqIVxvG0UNS0Ko ytW7A/tYNMz35l2/TFppryEcSCFtjg+wbgTCIXLYnkPByAY=
X-Google-Smtp-Source: ABdhPJwjKzyHKQ09/h9tG+fUXV84GFkreSdWWQjIR5mgbTo/We2eT1XsbGKiAtL+1TI2C5dVvLg97XUECfw3AlHQ0xQ=
X-Received: by 2002:adf:cd82:: with SMTP id q2mr16669913wrj.258.1623164955926; Tue, 08 Jun 2021 08:09:15 -0700 (PDT)
MIME-Version: 1.0
References: <162316371122.23079.9063492508515802379@ietfa.amsl.com>
In-Reply-To: <162316371122.23079.9063492508515802379@ietfa.amsl.com>
From: Ben Schwartz <bemasc@google.com>
Date: Tue, 8 Jun 2021 11:09:04 -0400
Message-ID: <CAHbrMsA1n5KRN3=wu-w_gx-EDhQyCMx9rFHCpK-d1SvrpgdrbQ@mail.gmail.com>
To: DNS Privacy Working Group <dns-privacy@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="000000000000a4cbd805c4428ad6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/pxyLOFIQZtSO1mSzQlv0fpPV1R0>
Subject: [dns-privacy] Fwd: New Version Notification for draft-schwartz-dprive-name-signal-00.txt
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: Tue, 08 Jun 2021 15:09:24 -0000

Hi DPRIVE,

A few years ago(!), Warren Kumari proposed a hacky way to signal ADoT
support by choosing a special nameserver name [1].  Since then, folks have
proposed a ton of different ways to indicate ADoT support, making use of
the nameserver name, DS record fields, or new RR types.

Warren and I recently revisited that old idea, and felt that it might fill
a gap in some of the active proposals, so we reworked it into a new
proposal (intended status: experimental) that better matches the WG's
adopted drafts.

Enjoy responsibly,
Ben Schwartz

[1]
https://mailarchive.ietf.org/arch/msg/dns-privacy/RbaImWVdtEZN_VqWBYGqVWP3eqk/

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Tue, Jun 8, 2021 at 10:48 AM
Subject: New Version Notification for
draft-schwartz-dprive-name-signal-00.txt
To: Benjamin M. Schwartz <bemasc@google.com>om>, Warren Kumari <
warren@kumari.net>



A new version of I-D, draft-schwartz-dprive-name-signal-00.txt
has been successfully submitted by Benjamin M. Schwartz and posted to the
IETF repository.

Name:           draft-schwartz-dprive-name-signal
Revision:       00
Title:          Nameserver Access Modes with Encryption Held in
Alphanumeric Configuration Keys
Document date:  2021-06-08
Group:          Individual Submission
Pages:          9
URL:
https://www.ietf.org/archive/id/draft-schwartz-dprive-name-signal-00.txt
Status:
https://datatracker.ietf.org/doc/draft-schwartz-dprive-name-signal/
Html:
https://www.ietf.org/archive/id/draft-schwartz-dprive-name-signal-00.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-schwartz-dprive-name-signal


Abstract:
   Some recent proposals to the DPRIVE working group rely on the use of
   SVCB records to provide instructions about how to reach an
   authoritative nameserver over an encrypted transport.  These
   proposals will be difficult to deploy until the parent domain's
   delegation software has been modified to support these records.  As
   an interim solution for these domains, this draft proposes encoding
   relevant signals in the child's NS-name.




The IETF Secretariat