RFC 7873 on Domain Name System (DNS) Cookies

rfc-editor@rfc-editor.org Sat, 28 May 2016 01:08 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F56D12D504; Fri, 27 May 2016 18:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.348
X-Spam-Level:
X-Spam-Status: No, score=-108.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 CiUF5HiGN8RX; Fri, 27 May 2016 18:08:01 -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 484CC12D1D9; Fri, 27 May 2016 18:08:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2562C180006; Fri, 27 May 2016 18:07:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7873 on Domain Name System (DNS) Cookies
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160528010719.2562C180006@rfc-editor.org>
Date: Fri, 27 May 2016 18:07:19 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/kynR2CmX9HPpunwyrBsplNxeFik>
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.17
Precedence: list
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: Sat, 28 May 2016 01:08:02 -0000

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

        
        RFC 7873

        Title:      Domain Name System (DNS) Cookies 
        Author:     D. Eastlake 3rd, 
                    M. Andrews
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    d3e3e3@gmail.com, 
                    marka@isc.org
        Pages:      25
        Characters: 55356
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-cookies-10.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7873

DNS Cookies are a lightweight DNS transaction security mechanism that
provides limited protection to DNS servers and clients against a
variety of increasingly common denial-of-service and amplification/
forgery or cache poisoning attacks by off-path attackers.  DNS
Cookies are tolerant of NAT, NAT-PT (Network Address Translation -
Protocol Translation), and anycast and can be incrementally deployed.
(Since DNS Cookies are only returned to the IP address from which
they were originally received, they cannot be used to generally track
Internet users.)


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