[dns-privacy] Alvaro Retana's No Objection on draft-ietf-dprive-dnsoquic-10: (with COMMENT)
Alvaro Retana via Datatracker <noreply@ietf.org> Wed, 09 March 2022 14:49 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 479DC3A07D7; Wed, 9 Mar 2022 06:49:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alvaro Retana via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dprive-dnsoquic@ietf.org, dprive-chairs@ietf.org, brian@innovationslab.net, dns-privacy@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alvaro Retana <aretana.ietf@gmail.com>
Message-ID: <164683736825.27301.4543628994183045646@ietfa.amsl.com>
Date: Wed, 09 Mar 2022 06:49:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/zvTfKG0NpeamDzNn_mhGdmGbTIo>
Subject: [dns-privacy] Alvaro Retana's No Objection on draft-ietf-dprive-dnsoquic-10: (with COMMENT)
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 09 Mar 2022 14:49:29 -0000
Alvaro Retana has entered the following ballot position for draft-ietf-dprive-dnsoquic-10: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dprive-dnsoquic/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- §5.3.3 lists some protocol error scenarios that are considered fatal. If a peer encounters such an error condition it is considered a fatal error. It SHOULD forcibly abort the connection using QUIC's CONNECTION_CLOSE mechanism, and SHOULD use the DoQ error code DOQ_PROTOCOL_ERROR. When is it ok not to abort the connection? Why is aborting the connection recommended and not required if the errors are considered fatal?
- [dns-privacy] Alvaro Retana's No Objection on dra… Alvaro Retana via Datatracker
- Re: [dns-privacy] Alvaro Retana's No Objection on… Sara Dickinson