RFC 8023 on Report from the Workshop and Prize on Root Causes and Mitigation of Name Collisions
rfc-editor@rfc-editor.org Thu, 10 November 2016 23:04 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 51DA012987C for <ietf-announce@ietfa.amsl.com>; Thu, 10 Nov 2016 15:04:57 -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 5BXWM1Y69J7G for <ietf-announce@ietfa.amsl.com>; Thu, 10 Nov 2016 15:04:55 -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 3C488129872 for <ietf-announce@ietf.org>; Thu, 10 Nov 2016 15:04:55 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3157AB800A0; Thu, 10 Nov 2016 15:04:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8023 on Report from the Workshop and Prize on Root Causes and Mitigation of Name Collisions
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161110230455.3157AB800A0@rfc-editor.org>
Date: Thu, 10 Nov 2016 15:04:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/oEaZ1EusXacu61Q_izFc4Po7G0Q>
Cc: drafts-update-ref@iana.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: Thu, 10 Nov 2016 23:04:57 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8023 Title: Report from the Workshop and Prize on Root Causes and Mitigation of Name Collisions Author: M. Thomas, A. Mankin, L. Zhang Status: Informational Stream: Independent Date: November 2016 Mailbox: mthomas@verisign.com, allison.mankin@gmail.com, lixia@cs.ucla.edu Pages: 17 Characters: 41899 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-thomas-namecollisions-workshop-report-05.txt URL: https://www.rfc-editor.org/info/rfc8023 DOI: http://dx.doi.org/10.17487/RFC8023 This document provides context and a report on the workshop on "Root Causes and Mitigation of Name Collisions", which took place in London, United Kingdom, from March 8 to 10, 2014. The main goal of the workshop was to foster a discussion on the causes and potential mitigations of domain name collisions. This report provides a small amount of background and context; then, it provides a summary of the workshop's discussions. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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