[rfc-dist] RFC 9250 on DNS over Dedicated QUIC Connections

rfc-editor@rfc-editor.org Wed, 11 May 2022 23:36 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9117CC3A4B76; Wed, 11 May 2022 16:36:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1652312167; bh=mvZU4V3tj5TZWXHul7UNcS7eg1Gg0tbRH1KaDiC8j4s=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=J3CZoPtlUEpAySV/7QVXfPJCc1yfv81wsNFCghepaxVpLMfo++80DvrWFfCH1Nmp0 /qkgG01OstwuKONG5DyEUoaU4RnjX72KZSX+P5dYMafEO1VWycuSnkG4jyj7v8d/B5 dVcDya7ewc0t1G0aoJstHUjjrGKKI2E7eQ4YYI5g=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Wed May 11 16:36:07 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 793A2C2CE8DF; Wed, 11 May 2022 16:36:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1652312166; bh=mvZU4V3tj5TZWXHul7UNcS7eg1Gg0tbRH1KaDiC8j4s=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=Ch+3ff29NLLlHWbMNz9M8Csf37p1WMHgrNsGSj71cSTSg2WwAsFdvfHfAqfcjUW6b KuAxNMNq44nVN4ze4jnbej0eaQY5HmwLGYQrsXkF/wAAh4T1nDcOrM04oqztdFoUFg IQJojtGOh8wMiVvtYO+d1i5a7wuZogAI+3ibeIEM=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD1AC15949A; Wed, 11 May 2022 16:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.645
X-Spam-Level:
X-Spam-Status: No, score=-1.645 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 OrWbvLZ-D5lM; Wed, 11 May 2022 16:35:56 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (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 BBE5FC1595FB; Wed, 11 May 2022 16:35:56 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 91E8F119F0; Wed, 11 May 2022 16:35:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dns-privacy@ietf.org
Message-Id: <20220511233556.91E8F119F0@rfcpa.amsl.com>
Date: Wed, 11 May 2022 16:35:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/KkwwtMVb-WHwRd6fQVW8Ul23rCQ>
Subject: [rfc-dist] RFC 9250 on DNS over Dedicated QUIC Connections
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9250

        Title:      DNS over Dedicated QUIC Connections 
        Author:     C. Huitema,
                    S. Dickinson,
                    A. Mankin
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2022
        Mailbox:    huitema@huitema.net,
                    sara@sinodun.com,
                    allison.mankin@gmail.com
        Pages:      27
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dprive-dnsoquic-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9250

        DOI:        10.17487/RFC9250

This document describes the use of QUIC to provide transport
confidentiality for DNS. The encryption provided by QUIC has similar
properties to those provided by TLS, while QUIC transport eliminates
the head-of-line blocking issues inherent with TCP and provides more
efficient packet-loss recovery than UDP. DNS over QUIC (DoQ) has
privacy properties similar to DNS over TLS (DoT) specified in RFC
7858, and latency characteristics similar to classic DNS over UDP.
This specification describes the use of DoQ as a general-purpose
transport for DNS and includes the use of DoQ for stub to recursive,
recursive to authoritative, and zone transfer scenarios.

This document is a product of the DNS PRIVate Exchange Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org