[dns-privacy] Next steps : draft-ietf-dprive-unilateral-probing

Brian Haberman <brian@innovationslab.net> Mon, 26 June 2023 15:21 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 C8CAAC151092 for <dns-privacy@ietfa.amsl.com>; Mon, 26 Jun 2023 08:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0HgXpBM6sC1 for <dns-privacy@ietfa.amsl.com>; Mon, 26 Jun 2023 08:21:03 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E4C5C151070 for <dns-privacy@ietf.org>; Mon, 26 Jun 2023 08:20:41 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3a1ebb79579so346543b6e.3 for <dns-privacy@ietf.org>; Mon, 26 Jun 2023 08:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovationslab-net.20221208.gappssmtp.com; s=20221208; t=1687792840; x=1690384840; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=Sn2efshq1mTSEv6I7rrbNUtTUIXlo10x2eCgvqlYMIs=; b=Tks5swbBnFFkTqsQbq/ZLHBra2vK2d4aWFTdVsjhfLvALRCh4t9Jz35Ty4qKRQtHlk mXYYhmRG5R4vEjnNm/UPQl3DuRKJsauZy7GUGr6KTcB1ILo9n2mIufBtFy/tlm/xi8Ue yf1gjUrq0PSNCVCqIlTzkCopHJOVzt6ZAPGRVRpiLMXi06o8xBplge+tY6MTOKIQx+bn Gi9YVU+fNC/ZCbNZ4NyLKJ9O18oIGjzUNNrOGCH+YcZDNd43yt6wpRnbU+l8WzbolbWz /cmuMzC3a8GSTshl1TxX9zAie0MQAPpNEXXuFI4K2i76b4TfqoBnpaSjkxNctQXmp3XU MjsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687792840; x=1690384840; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Sn2efshq1mTSEv6I7rrbNUtTUIXlo10x2eCgvqlYMIs=; b=Jt3jatTpDo2JL0dJONMmisjKnB12QPHGYrUgNrccWgRF6A6JHo/33ySh+C5ozMy66F OEIS9PfUjstwAGmrQ+AZ9sDU54peWDWrhjKWOCUhqdGKLhVlqm/Sl44/5sPvzkXNIohx 3Jm6sqs+EWFqaXQJBnQ24VnGkTBnawamm8HIs2FT6IMlxavJ4OnTWWFWX2O2/O1iF7YN IzIStpMDmJcda+vJddLILOf2PXVPA1tu4M1VIixXnUjs/I1/WdSOatCqgJ3BHogZZ9KM cPxNEdQofG/VCTBL2zZ4vnVJx4uCSrEYA3MtvM6xCPgzz/Y7s2RIVXTvtPJRcHUnH1oV ZVxQ==
X-Gm-Message-State: AC+VfDyzwpqTaX408hcA0ETI90pXWF6MCjrj0aGbmxzLSP8WkEwsQy08 JElBjhFIF5RnI+5V4Q+WuZIoQJ1Ewex8N74TXIk=
X-Google-Smtp-Source: ACHHUZ6fDQFN0APdkz5j0sCxj32t7ntILqmtI40t4v7Zk/XhAajnHxBf0bhM9lsVuMTVE2YbUvQe/Q==
X-Received: by 2002:a05:6808:2096:b0:3a0:5bfe:e8a1 with SMTP id s22-20020a056808209600b003a05bfee8a1mr16659535oiw.25.1687792840409; Mon, 26 Jun 2023 08:20:40 -0700 (PDT)
Received: from [192.168.1.11] ([172.59.113.222]) by smtp.gmail.com with ESMTPSA id o2-20020a05620a110200b0075b13a89c30sm2825731qkk.3.2023.06.26.08.20.39 for <dns-privacy@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 26 Jun 2023 08:20:39 -0700 (PDT)
Message-ID: <abc2826b-9e2b-6cea-85f9-b2060408105b@innovationslab.net>
Date: Mon, 26 Jun 2023 11:20:38 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
From: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------ZADhvPNDVRteKSVSmM6ivHNH"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/XpGFQHbn9QKSQdufkBA6G-AFhfI>
Subject: [dns-privacy] Next steps : draft-ietf-dprive-unilateral-probing
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Addition of privacy to the DNS protocol <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, 26 Jun 2023 15:21:07 -0000

Hi all,
      Tim, Éric, and I have chatted about the next steps for the 
unilateral probing draft. Here is the proposed plan for moving the draft 
forward as Experimental:

1. The authors verify that the implementations listed in Appendix A is 
up-to-date. The chairs will request that this list be retained in the 
published RFC.

2. The authors capture the key metrics submitted to the mailing list for 
assessing the experiment in a new appendix. The chairs believe that the 
below metrics proposed by Scott Hollenbeck are a good starting point but 
other WG participants may have other proposed metrics:

      A. Measurement of CPU and memory use between Do53 and DoT or DoQ.
      B. Measurement of query response rates between Do53 and DoT or DoQ.
      C. Measurement of server authentication successes and failures.
      D. Measurement and descriptions of observed attack traffic, if any.

3. The chairs will solicit a volunteer (or volunteers) to collect 
information on any interoperability testing that has been carried out 
between implementations that support this specification.

Once the WG is comfortable with the experimentation section and the 
metrics, the chairs will submit the draft to the IESG for publication. 
We will propose to revisit the status of the document twelve (12) months 
after publication as an RFC.

Any concerns or suggestions on the above plan?

Regards,
Brian