[DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 on Home Networking Control Protocol]
Stephane Bortzmeyer <bortzmeyer@nic.fr> Sat, 23 April 2016 20:08 UTC
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E327512D0F9 for <dnsop@ietfa.amsl.com>; Sat, 23 Apr 2016 13:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 z13xhFWu9xZQ for <dnsop@ietfa.amsl.com>; Sat, 23 Apr 2016 13:08:11 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E842812D0E9 for <dnsop@ietf.org>; Sat, 23 Apr 2016 13:08:10 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 3AB1531CF6; Sat, 23 Apr 2016 22:08:07 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id F06EC1906D3; Sat, 23 Apr 2016 22:07:42 +0200 (CEST)
Date: Sat, 23 Apr 2016 22:07:42 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dnsop@ietf.org
Message-ID: <20160423200742.GA12313@sources.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="d6Gm4EdcadzBjdND"
Content-Disposition: inline
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 8.4
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/phsSra3BylfK65enPn-3wLSbCl4>
Subject: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 on Home Networking Control Protocol]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Apr 2016 20:08:13 -0000
Interesting RFC, which introduces officially the TLD .home, without using the RFC 6761 framework. So, apparently, you can reserve TLDs without going through the Special-Use Domain registry. I also note that some people complained that registering .onion was squatting on ICANN's property. But .home was accepted while, unlike .onion, there are actually people who are candidates to manage it.
--- Begin Message ---A new Request for Comments is now available in online RFC libraries. RFC 7788 Title: Home Networking Control Protocol Author: M. Stenberg, S. Barth, P. Pfister Status: Standards Track Stream: IETF Date: April 2016 Mailbox: markus.stenberg@iki.fi, cyrus@openwrt.org, pierre.pfister@darou.fr Pages: 40 Characters: 94146 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-homenet-hncp-10.txt URL: https://www.rfc-editor.org/info/rfc7788 DOI: http://dx.doi.org/10.17487/RFC7788 This document describes the Home Networking Control Protocol (HNCP), an extensible configuration protocol, and a set of requirements for home network devices. HNCP is described as a profile of and extension to the Distributed Node Consensus Protocol (DNCP). HNCP enables discovery of network borders, automated configuration of addresses, name resolution, service discovery, and the use of any routing protocol that supports routing based on both the source and destination address. 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--- End Message ---
- [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 on H… Stephane Bortzmeyer
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … John Levine
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Adrien de Croy
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … David Conrad
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … John Levine
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Ted Lemon
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Patrik Fältström
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Patrik Fältström
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Ted Lemon
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Patrik Fältström
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Paul Hoffman
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Ted Lemon
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Ted Lemon
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Suzanne Woolf
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Ted Lemon
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … joel jaeggli
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Stephane Bortzmeyer
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Stephane Bortzmeyer
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Stephane Bortzmeyer
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Stephane Bortzmeyer
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Stephane Bortzmeyer
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Ray Bellis
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … David Conrad
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Alain Durand
- Re: [DNSOP] [rfc-editor@rfc-editor.org: RFC 7788 … Tim Wicinski