RFC 7766 on DNS Transport over TCP - Implementation Requirements
rfc-editor@rfc-editor.org Thu, 03 March 2016 19:44 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FCF31B4213; Thu, 3 Mar 2016 11:44:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level:
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 sOvAK4Jwjyui; Thu, 3 Mar 2016 11:44:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F00C1B4212; Thu, 3 Mar 2016 11:44:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 733BB18019D; Thu, 3 Mar 2016 11:43:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7766 on DNS Transport over TCP - Implementation Requirements
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160303194304.733BB18019D@rfc-editor.org>
Date: Thu, 03 Mar 2016 11:43:04 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/FbJEqrK7k6aRqyo2mPrhxIpXelM>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2016 19:44:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7766
Title: DNS Transport over TCP -
Implementation Requirements
Author: J. Dickinson, S. Dickinson,
R. Bellis, A. Mankin,
D. Wessels
Status: Standards Track
Stream: IETF
Date: March 2016
Mailbox: jad@sinodun.com,
sara@sinodun.com,
ray@isc.org,
allison.mankin@gmail.com,
dwessels@verisign.com
Pages: 19
Characters: 40616
Obsoletes: RFC 5966
Updates: RFC 1035, RFC 1123
I-D Tag: draft-ietf-dnsop-5966bis-06.txt
URL: https://www.rfc-editor.org/info/rfc7766
DOI: http://dx.doi.org/10.17487/RFC7766
This document specifies the requirement for support of TCP as a
transport protocol for DNS implementations and provides guidelines
towards DNS-over-TCP performance on par with that of DNS-over-UDP.
This document obsoletes RFC 5966 and therefore updates RFC 1035 and
RFC 1123.
This document is a product of the Domain Name System Operations 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