Re: [dns-privacy] [Ext] A Few More Suggestions for the Requirements Draft

Paul Hoffman <paul.hoffman@icann.org> Mon, 19 April 2021 17:52 UTC

Return-Path: <paul.hoffman@icann.org>
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 EEF873A3C8F; Mon, 19 Apr 2021 10:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 21oxDpPCOmlS; Mon, 19 Apr 2021 10:52:33 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D78DA3A3C8B; Mon, 19 Apr 2021 10:52:33 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa2.lax.icann.org (8.16.0.43/8.16.0.43) with ESMTPS id 13JHqW8Q005905 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Apr 2021 17:52:32 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.858.5; Mon, 19 Apr 2021 10:52:31 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.0858.010; Mon, 19 Apr 2021 10:52:31 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>
CC: "dprive@ietf.org" <dprive@ietf.org>
Thread-Topic: [dns-privacy] [Ext] A Few More Suggestions for the Requirements Draft
Thread-Index: AQHXNUEIPk7oZNeZikKdbXN4SesgGKq8lGCA
Date: Mon, 19 Apr 2021 17:52:31 +0000
Message-ID: <1BE0F181-68A1-464A-9D7D-824181F4A69B@icann.org>
References: <fc3621bb82f24753ba3a17d60df59879@verisign.com> <E2D1CEE3-64F1-4A48-8EF3-19B37ABB0F83@icann.org> <064c169412764689a3129b8e162806ac@verisign.com>
In-Reply-To: <064c169412764689a3129b8e162806ac@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_CA9D7F5E-AE78-4D83-9729-C72FAFDA61EC"; protocol="application/pkcs7-signature"; micalg=sha-256
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-04-19_11:2021-04-19, 2021-04-19 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/QlelQKZyGU3PYhcdYkbAfwO7v5M>
Subject: Re: [dns-privacy] [Ext] A Few More Suggestions for the Requirements Draft
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 17:52:38 -0000

On Apr 19, 2021, at 10:25 AM, Hollenbeck, Scott <shollenbeck=40verisign.com@dmarc.ietf.org> wrote:
> The WG charter currently says this:
> 
> "Develop requirements for adding confidentiality to DNS exchanges between recursive resolvers and authoritative servers (unpublished document)."
> 
> Does that need to change?

I don't think so, because the WG has been actively developing those requirements without the draft moving forward, just by having good WG discussions. Maybe the current document can just expire gracefully?

--Paul Hoffman