[DNSOP] RFC 7828 on The edns-tcp-keepalive EDNS0 Option
rfc-editor@rfc-editor.org Thu, 07 April 2016 02:28 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB3812D138; Wed, 6 Apr 2016 19:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.932
X-Spam-Level:
X-Spam-Status: No, score=-106.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 BtciDYnT1WB1; Wed, 6 Apr 2016 19:28:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 624A512D0A3; Wed, 6 Apr 2016 19:28:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E247C18000B; Wed, 6 Apr 2016 19:27:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160407022742.E247C18000B@rfc-editor.org>
Date: Wed, 06 Apr 2016 19:27:42 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/XKkHO6yvh-ai8vTxxvqpuJoTii0>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
Subject: [DNSOP] RFC 7828 on The edns-tcp-keepalive EDNS0 Option
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 02:28:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7828
Title: The edns-tcp-keepalive EDNS0 Option
Author: P. Wouters,
J. Abley,
S. Dickinson,
R. Bellis
Status: Standards Track
Stream: IETF
Date: April 2016
Mailbox: pwouters@redhat.com,
jabley@dyn.com,
sara@sinodun.com,
ray@isc.org
Pages: 11
Characters: 24282
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dnsop-edns-tcp-keepalive-06.txt
URL: https://www.rfc-editor.org/info/rfc7828
DOI: http://dx.doi.org/10.17487/RFC7828
DNS messages between clients and servers may be received over
either UDP or TCP. UDP transport involves keeping less state
on a busy server, but can cause truncation and retries over
TCP. Additionally, UDP can be exploited for reflection attacks.
Using TCP would reduce retransmits and amplification. However,
clients commonly use TCP only for retries and servers typically
use idle timeouts on the order of seconds.
This document defines an EDNS0 option ("edns-tcp-keepalive")
that allows DNS servers to signal a variable idle timeout.
This signalling encourages the use of long-lived TCP connections
by allowing the state associated with TCP transport to be managed
effectively with minimal impact on the DNS transaction time.
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