[homenet] RFC 7787 on Distributed Node Consensus Protocol

rfc-editor@rfc-editor.org Tue, 19 April 2016 00:24 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 435A512E4F1; Mon, 18 Apr 2016 17:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, 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 w6s4PcLbH0KN; Mon, 18 Apr 2016 17:24:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4B4212DD53; Mon, 18 Apr 2016 17:24:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C74FB180005; Mon, 18 Apr 2016 17:23:42 -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: <20160419002342.C74FB180005@rfc-editor.org>
Date: Mon, 18 Apr 2016 17:23:42 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nPFZQ4e4tRJwH23AmCz3CS8KjM8>
Cc: drafts-update-ref@iana.org, homenet@ietf.org, rfc-editor@rfc-editor.org
Subject: [homenet] RFC 7787 on Distributed Node Consensus Protocol
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 19 Apr 2016 00:24:13 -0000

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

        
        RFC 7787

        Title:      Distributed Node Consensus Protocol 
        Author:     M. Stenberg, S. Barth
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2016
        Mailbox:    markus.stenberg@iki.fi, 
                    cyrus@openwrt.org
        Pages:      41
        Characters: 96466
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-homenet-dncp-12.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7787

This document describes the Distributed Node Consensus Protocol
(DNCP), a generic state synchronization protocol that uses the
Trickle algorithm and hash trees.  DNCP is an abstract protocol and
must be combined with a specific profile to make a complete
implementable protocol.

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