RFC 8244 on Special-Use Domain Names Problem Statement
rfc-editor@rfc-editor.org Thu, 19 October 2017 19:46 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 8247913306B; Thu, 19 Oct 2017 12:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 yb1SaioDylDH; Thu, 19 Oct 2017 12:46:13 -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 05C0E132D89; Thu, 19 Oct 2017 12:46:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A4209B810C1; Thu, 19 Oct 2017 12:45:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8244 on Special-Use Domain Names Problem Statement
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnsop@ietf.org
Message-Id: <20171019194549.A4209B810C1@rfc-editor.org>
Date: Thu, 19 Oct 2017 12:45:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/EZ1rvxuYxgQSSysf8jAV_oty_uo>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 19 Oct 2017 19:46:14 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8244
Title: Special-Use Domain Names Problem Statement
Author: T. Lemon,
R. Droms,
W. Kumari
Status: Informational
Stream: IETF
Date: October 2017
Mailbox: ted.lemon@nominum.com,
rdroms.ietf@gmail.com,
warren@kumari.net
Pages: 25
Characters: 59995
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dnsop-sutld-ps-08.txt
URL: https://www.rfc-editor.org/info/rfc8244
DOI: 10.17487/RFC8244
The policy defined in RFC 6761 for IANA registrations in the
"Special-Use Domain Names" registry has been shown, through
experience, to present challenges that were not anticipated when RFC
6761 was written. This memo presents a list, intended to be
comprehensive, of the problems that have since been identified. In
addition, it reviews the history of domain names and summarizes
current IETF publications and some publications from other
organizations relating to Special-Use Domain Names.
This document should be considered required reading for IETF
participants who wish to express an informed opinion on the topic of
Special-Use Domain Names.
This document is a product of the Domain Name System Operations Working Group of the IETF.
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