[rfc-dist] RFC 8880 on Special Use Domain Name 'ipv4only.arpa'
rfc-editor@rfc-editor.org Mon, 31 August 2020 22:32 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29013A0943 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 31 Aug 2020 15:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 8Yf9yXcWiceL for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 31 Aug 2020 15:32:00 -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 756733A0954 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 31 Aug 2020 15:32:00 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2E0FCF40775; Mon, 31 Aug 2020 15:31:49 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id ABAC9F40773; Mon, 31 Aug 2020 15:31:48 -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: <20200831223148.ABAC9F40773@rfc-editor.org>
Date: Mon, 31 Aug 2020 15:31:48 -0700
Subject: [rfc-dist] RFC 8880 on Special Use Domain Name 'ipv4only.arpa'
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8880
Title: Special Use Domain Name 'ipv4only.arpa'
Author: S. Cheshire,
D. Schinazi
Status: Standards Track
Stream: IETF
Date: August 2020
Mailbox: cheshire@apple.com,
dschinazi.ietf@gmail.com
Pages: 17
Updates: RFC 7050
I-D Tag: draft-cheshire-sudn-ipv4only-dot-arpa-17.txt
URL: https://www.rfc-editor.org/info/rfc8880
DOI: 10.17487/RFC8880
NAT64 (Network Address and Protocol Translation from IPv6 Clients to
IPv4 Servers) allows client devices using IPv6 to communicate with
servers that have only IPv4 connectivity.
The specification for how a client discovers its local network's
NAT64 prefix (RFC 7050) defines the special name 'ipv4only.arpa' for
this purpose. However, in its Domain Name Reservation Considerations
section (Section 8.1), that specification (RFC 7050) indicates that
the name actually has no particularly special properties that would
require special handling.
Consequently, despite the well-articulated special purpose of the
name, 'ipv4only.arpa' was not recorded in the Special-Use Domain
Names registry as a name with special properties.
This document updates RFC 7050. It describes the special treatment
required and formally declares the special properties of the name. It
also adds similar declarations for the corresponding reverse mapping
names.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org