Re: [dns-privacy] New Version Notification - draft-ietf-dprive-dnsoquic-12.txt

Christian Huitema <huitema@huitema.net> Thu, 28 April 2022 14:30 UTC

Return-Path: <huitema@huitema.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 B3FE3C14F75F for <dns-privacy@ietfa.amsl.com>; Thu, 28 Apr 2022 07:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.741
X-Spam-Level:
X-Spam-Status: No, score=-3.741 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 BuXg3kQuSJig for <dns-privacy@ietfa.amsl.com>; Thu, 28 Apr 2022 07:30:05 -0700 (PDT)
Received: from mx36-out20.antispamcloud.com (mx36-out20.antispamcloud.com [209.126.121.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 11986C14F726 for <dns-privacy@ietf.org>; Thu, 28 Apr 2022 07:30:04 -0700 (PDT)
Received: from xse219.mail2web.com ([66.113.196.219] helo=xse.mail2web.com) by mx256.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nk59b-000MRQ-UJ for dns-privacy@ietf.org; Thu, 28 Apr 2022 16:30:03 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4Kpydk5HvCz9vf for <dns-privacy@ietf.org>; Thu, 28 Apr 2022 07:28:10 -0700 (PDT)
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nk57q-0005jj-JS for dns-privacy@ietf.org; Thu, 28 Apr 2022 07:28:10 -0700
Received: (qmail 19004 invoked from network); 28 Apr 2022 14:28:10 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.43.172]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dns-privacy@ietf.org>; 28 Apr 2022 14:28:09 -0000
Message-ID: <b914c6b6-3d93-3097-e950-3c6b15af070d@huitema.net>
Date: Thu, 28 Apr 2022 07:28:09 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Content-Language: en-US
To: dns-privacy@ietf.org
References: <165044503269.10126.3247340236340798049@ietfa.amsl.com> <CA+nkc8B0UepO3QJvKmsc7VpR4OUSeHaNq+XHVmoieeYUhHGj0g@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <CA+nkc8B0UepO3QJvKmsc7VpR4OUSeHaNq+XHVmoieeYUhHGj0g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: 66.113.196.219
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.07)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT/m8dTeRvW6lgOUxxwR9ImTPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zh2yKlFwkOJL4c32G0KduLVjVx0XVkNnHJMw/amoreOYjo wcDIV8QHomOK4Z/tX6aCn3oZFShGuGVczvnnMQuySxIRXVMlFuiz/acFNeeXtxN2fFxZWB9eYgpR BRu3UlDHMLIJYRi1cXH9Dbm+IxLV8AR8cCjrStxUsN7UropoWXGFd932lfz+R/06O3Iy4anr3obc i1BDUx+cEdj2Yf5+kVWClPVvbW5lVyQanRxw5hTHswbbB/ha+ZWrSAi8SkwqWAikMcSxTAWn8RCv ieGEqjG/gXZAaRh1X6LVetRf2ZYIiHqfCgG4wrA3w4/kQTYKxDHA9JN9J4k4XZq11JQkMemT4rxn nByU11Ftkqf3f/PF3GUV+KdBBqrnCX8j0Gi8Ksk+aedMfNWSnJswrtlNtZo3HPHi5Q+jjsF5dcBx ehWYzrkgsp4/Fysgb2cPV4IH0+lPwKr4i5mAANUcVraZYOaeuiH/yEdZH8S1+TgcJBOjh0vPxcQO jKKOrYIQYpwamUdylUIKhf3z2GAHxH7IBAaAB9SiL80iwHtGBZiikjTur3/Ubw75F414tOprxl2t V+6x5M5QG2ettrdBoHA9KK8qgoX3qtqBY7olcAAV8pXloqisSitb6n6JVjosdW/TulJRptMnEIdG JW7dfhGq92PNDpgLsd6Ddd/s7VM53v39XUgdp9prJZvZjjxLIBAOtp+q3yU+z72+fnpodgpDkvYN 23xC0NKWN5vnLl0dzQKi6GNm7LuJ2sOWj9PmA5FmMRr+w2X69ygMahiTQMBd+F8KFo7CgLAyCt1D L5XbFfoPFZIShBSdpVJW5HbjQTCUIzbw71BPKv8cPtVshTSLr6YHJu91A3avrF49rf9JcoEpejCA XczArXyV+OFXiMtbLPp9n350Mbemie5JWWm/MpxAyl4q1x5O0+PBD/gPmWjXVA9S7TnWXDlmMpVd cwCFwrnT0GQK/7labXRdXAB+MS+4ayUpOtEhdxekWDmK9g==
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/lHd6dw69Wsm_Dgl0qI7FsHNq-Hw>
Subject: Re: [dns-privacy] New Version Notification - draft-ietf-dprive-dnsoquic-12.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.34
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: Thu, 28 Apr 2022 14:30:05 -0000

Thanks for the review, Bob.

On 4/28/2022 6:02 AM, Bob Harold wrote:
> On Wed, Apr 20, 2022 at 4:57 AM <internet-drafts@ietf.org> wrote:
>
>> A new version (-12) has been submitted for draft-ietf-dprive-dnsoquic:
>> https://www.ietf.org/archive/id/draft-ietf-dprive-dnsoquic-12.txt
>>
>>
>> The IETF datatracker page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-dprive-dnsoquic/
>>
>> Diff from previous version:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-dprive-dnsoquic-12
>>
>> IETF Secretariat.
>>
>>
> Minor nits:
>
> In 5.1.1. Draft Version Identification
> In the example "doq-i00"
> Where does the "i" come from?  I was expecting "doq-00".
That was introduced a long time ago, to differentiate between this draft 
and the incompatible encodings used in the individual draft 
draft-huitema-dprive-dnsoquic. The whole section 5.1.1 where this is 
defined is provisional, and will be removed before RFC publication.
>
> 5.5.  Session Resumption and 0-RTT
>
> Next to last paragraph, "errros" -> "errors"
>
>
> 6.3.  Address Validation
>
> The end of the first paragraph "to a factor 3."  -> "to a factor of 3."

The draft is now in the hands of the RFC editors. I trust them, but I 
will verify that these issues are fixed.

-- Christian Huitema