[homenet] RFC 8375 on Special-Use Domain 'home.arpa.'

rfc-editor@rfc-editor.org Thu, 17 May 2018 15:41 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7299412EB1C; Thu, 17 May 2018 08:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 KfyKTzGedIwY; Thu, 17 May 2018 08:41:54 -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 BA75F1270AE; Thu, 17 May 2018 08:41:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 18621B8126B; Thu, 17 May 2018 08:41:50 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, homenet@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180517154150.18621B8126B@rfc-editor.org>
Date: Thu, 17 May 2018 08:41:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/tUoXyz56joX27y2eBKW4L5Vujoo>
Subject: [homenet] RFC 8375 on Special-Use Domain 'home.arpa.'
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 15:41:57 -0000

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

        
        RFC 8375

        Title:      Special-Use Domain 'home.arpa.' 
        Author:     P. Pfister, 
                    T. Lemon
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2018
        Mailbox:    pierre.pfister@darou.fr, 
                    mellon@fugue.com
        Pages:      12
        Characters: 27377
        Updates:    RFC 7788

        I-D Tag:    draft-ietf-homenet-dot-14.txt

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

        DOI:        10.17487/RFC8375

This document specifies the behavior that is expected from the Domain
Name System with regard to DNS queries for names ending with
'.home.arpa.' and designates this domain as a special-use domain
name. 'home.arpa.' is designated for non-unique use in residential
home networks.  The Home Networking Control Protocol (HNCP) is
updated to use the 'home.arpa.' domain instead of '.home'.

This document is a product of the Home Networking 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