[dns-privacy] How do we want to use draft-ietf-dprive-phase2-requirements?

Brian Haberman <brian@innovationslab.net> Mon, 19 April 2021 21:13 UTC

Return-Path: <brian@innovationslab.net>
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 0C7BF3A2755 for <dns-privacy@ietfa.amsl.com>; Mon, 19 Apr 2021 14:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=innovationslab-net.20150623.gappssmtp.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 M5xRJOw_ItIc for <dns-privacy@ietfa.amsl.com>; Mon, 19 Apr 2021 14:13:07 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 2EC283A2753 for <dns-privacy@ietf.org>; Mon, 19 Apr 2021 14:13:06 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id s5so28568370qkj.5 for <dns-privacy@ietf.org>; Mon, 19 Apr 2021 14:13:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovationslab-net.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version; bh=i3R8zakN+9qVACaaNyUro0OAD9+NU2KaX7dY8qyN9G0=; b=OTCUisvz38pUXfG6BEd1xvTM6Qomp7cGLfKmo3Eo+KgoHfXpKL0roVrcSjASJ2L69V QXMhsSG5e76RAGgUnO1sLIPTWxyI8DyY1xKweAXDrofZxeQYgucE12M8yTm+KSauEJJI v126Zx0R57/FqPVC7o4ble8ms8DcBcZ3wuh+8Klig/85hKVFC/bVi7zpbhK0E4MqS1Xa lwBG/s4obh3yKVVKrsvMP6GmvBkrYfyeBpwU63ZskxPex6NnAiXojCc07u5bmD2lJSSS FEjGp9K2KorIJ8yAEiydhcJGBrq7XGDggJMFkakiI7+NpBLxIF1hEX3D0BBrBlKT/FFD wcyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=i3R8zakN+9qVACaaNyUro0OAD9+NU2KaX7dY8qyN9G0=; b=dqYML9AXbT8pRt3kzuXy7NhKiCySnew8W/krDlBjGQ71ldjtt/jwA8t2Jt99JNTiRv +oSLfPgWip+tDYiylNXdQ5dzY/338qZoeWzlmrCXrEAb2dn6VJiRYstPOsaxGWJFdZzS N79K0B+/e5SbYz+GzB3/+bnXXi6VIJApfyPIoWUEnx65ohSd9j1SX8iaS0KJddL2xdoY f3yhINNjy3ToZLKhUD/KIXa73WJvzmMWLUVdg71xYxIXpYDAIMTN5YguW3aIiBH/suJG oE3PnInCQWeHv/DjZzhF4ky5SbQGU4PgXSwtYPbmbye2YiNs2Zo4H1SvzzRS2UbchPOj ycWA==
X-Gm-Message-State: AOAM533MXxOObzEZr2PE7iCyln7Ouz6FeGu7OvuJXaYMo8cM8FDrtA1I Y4wnj2rNBC/DcIatJwIIyk4aYR1N6gXvZc84
X-Google-Smtp-Source: ABdhPJza6Kucx6z/1JBqi5s2MbbhyteUGfmMCFZkZMQI6a59yxopMKgptJ+mOI1k1Ccr70piViEf2A==
X-Received: by 2002:a37:5fc2:: with SMTP id t185mr13711230qkb.254.1618866784327; Mon, 19 Apr 2021 14:13:04 -0700 (PDT)
Received: from clemson.local ([2601:5ce:300:84e:604e:2038:bb01:633a]) by smtp.gmail.com with ESMTPSA id l124sm10633341qkf.31.2021.04.19.14.13.03 for <dns-privacy@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 19 Apr 2021 14:13:03 -0700 (PDT)
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <121ae494-d7f0-37da-cf53-44f75df2fa75@innovationslab.net>
Date: Mon, 19 Apr 2021 17:13:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.1
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="em0bFbLXyL3KbWqiNOjQzPoj4CA4ZYfSj"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/eRC6UqQFxWOe4fu1RT0IUinp-Yg>
Subject: [dns-privacy] How do we want to use draft-ietf-dprive-phase2-requirements?
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: Mon, 19 Apr 2021 21:13:12 -0000

All,
     As was raised on the thread discussing suggestions for the
requirements draft, there is some question on how the WG wants to use
draft-ietf-dprive-phase2-requirements in progressing our
recursive-to-authoritative privacy work item. The draft currently has
one sub-section that describes requirements (5.1) and another section
that describes optional features (5.2), albeit with 2119 SHOULDs.

     My question to the WG is how do we want to use this draft? I see
four possible approaches, but I am sure someone will point out others.

1. Strictly requirements - these would be MUST-level functions that the
WG determines have to be supported by any solutions draft.

2. Strictly design considerations - these would be functional areas that
the WG determines need to be considered, but not necessarily included,
by any solutions draft.

3. Requirements & design considerations - This is generally where the
current draft sits IMO.

4. Drop the draft and let the solutions flow.

Let's discuss the focus of the draft and then we can determine what
updates are needed/necessary.

Regards,
Brian