BCP 207, RFC 8027 on DNSSEC Roadblock Avoidance

rfc-editor@rfc-editor.org Tue, 29 November 2016 02:47 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 E052512A268; Mon, 28 Nov 2016 18:47:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level:
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, 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 FZfE9y7Xv4Zd; Mon, 28 Nov 2016 18:47:26 -0800 (PST)
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 58BCB129FCF; Mon, 28 Nov 2016 18:47:26 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4A29CB80175; Mon, 28 Nov 2016 18:47:26 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 207, RFC 8027 on DNSSEC Roadblock Avoidance
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161129024726.4A29CB80175@rfc-editor.org>
Date: Mon, 28 Nov 2016 18:47:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/xYUG9tbmxT8DPB75mT3xrZ-dO4w>
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
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: Tue, 29 Nov 2016 02:47:28 -0000

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

        BCP 207        
        RFC 8027

        Title:      DNSSEC Roadblock Avoidance 
        Author:     W. Hardaker, 
                    O. Gudmundsson,
                    S. Krishnaswamy
        Status:     Best Current Practice
        Stream:     IETF
        Date:       November 2016
        Mailbox:    ietf@hardakers.net, 
                    olafur+ietf@cloudflare.com, 
                    suresh@tislabs.com
        Pages:      19
        Characters: 40173
        See Also:   BCP 207

        I-D Tag:    draft-ietf-dnsop-dnssec-roadblock-avoidance-05.txt

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

        DOI:        10.17487/RFC8027

This document describes problems that a Validating DNS resolver,
stub-resolver, or application might run into within a non-compliant
infrastructure.  It outlines potential detection and mitigation
techniques.  The scope of the document is to create a shared approach
to detect and overcome network issues that a DNSSEC software/system
may face.

This document is a product of the Domain Name System Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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