Re: [homenet] RFC 7787 on Distributed Node Consensus Protocol

Hermin Anggawijaya <hermin.anggawijaya@gmail.com> Wed, 20 April 2016 10:26 UTC

Return-Path: <hermin.anggawijaya@gmail.com>
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 EA6A212EE1C for <homenet@ietfa.amsl.com>; Wed, 20 Apr 2016 03:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Kar5DsuRC2ft for <homenet@ietfa.amsl.com>; Wed, 20 Apr 2016 03:26:20 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A86FF12EE17 for <homenet@ietf.org>; Wed, 20 Apr 2016 03:26:19 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id j11so38002172lfb.1 for <homenet@ietf.org>; Wed, 20 Apr 2016 03:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=HiPkPuXG9+aaXr/XuG2AWcSn4DFRAfvnYpAyWdHP1Kc=; b=Ji+WfTfn3qrqW/SESvnzFly8i8VrO2nJ08V6o0FwjFAbd85QpxYlV53HckN6bTP4WI hEPUgO1os6yDzLJdU6y6xfIkCViXXDrBmHhvdAFYf236lHPQD7MbpMsQKs5eE3CfTLws gxbUBgG2ZJab84yYNtLLg0+ilur8QhNVG7rQd28D0raU0oYul4yhS9MPkfg0sY5O3t4E kFELium0mlkefXJnrdttQXDWrlqNBJ4U3+0w3ZYLO8YTNPl64VssR1yf3fzUBcVToZGN Uk35HYvfSwswx/UQ1NvGztdYAaqp2niXNQjhGbaTCC2aMfXxrj3CsqyEUM5t3woMoq6o 7OSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=HiPkPuXG9+aaXr/XuG2AWcSn4DFRAfvnYpAyWdHP1Kc=; b=ZSH3sgnexiAo6b2BkgnoRL4g9lE1sIw8SMKOoAGDsuD8LGP7Q9WyX/gy/gbnth2NhU 1NHDO/7gNHDV0kU+YaTEAaxnLfGAC4cb8y30phy358KDKq8AcGkxmydrx48fXFbyrSPw HVWTg91ECHK8QZl2fj7cJLjx+DwoatyfyRcYTkF4oZlXJvNTI5M0nrmMN9xZ81JlSpKd +E4vM4i79usHe752PW1wIHEA3rh2s2wyKZJurxxaZdyl2Bu3/sAvtzTLWyCbEV2JFDgk Ul9jyQRjCGpWlCrg25dmByC51b4ozuTEFlt7KLq/PJyb0CinY3i/wSoTI3n3oscmjlrG C1PQ==
X-Gm-Message-State: AOPr4FUWdgxzT6lW3cdDdgZb5+5+DfpgQtD99MtLEu+ZyYxdmdIFE/uLPigrtgZPHyRoA+A8Q2GYU6fqpM5g7A==
MIME-Version: 1.0
X-Received: by 10.25.23.86 with SMTP id n83mr3399509lfi.159.1461147977834; Wed, 20 Apr 2016 03:26:17 -0700 (PDT)
Received: by 10.25.83.17 with HTTP; Wed, 20 Apr 2016 03:26:17 -0700 (PDT)
Date: Wed, 20 Apr 2016 22:26:17 +1200
Message-ID: <CAJgsEzUKLOF1dK68MQ3b_a1EkhLBcNDWbbG1aznfOpZF9NG3hw@mail.gmail.com>
From: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/h4PB7mCFtJ8VD8hHzNazS1airNk>
Subject: Re: [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: Wed, 20 Apr 2016 10:26:22 -0000

Hi

RFC 7787, Section 1.1, says

...
Furthermore, it can be used as a basis to run distributed algorithms
like [RFC7596] or use cases as described in Appendix C.
...

I think it should say

Furthermore, it can be used as a basis to run distributed algorithms
like [RFC7695] or use cases as described in Appendix C.


And page 37


   [RFC7596]  Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I.
              Farrer, "Lightweight 4over6: An Extension to the Dual-
              Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596,
              July 2015, <http://www.rfc-editor.org/info/rfc7596>;.


Should say



   [RFC7695]  P. Pfister, B. Paterson, J. Arkko, "Distributed Prefix Assignment
                         Algorithm", RFC 7695, November 2015,
                         <http://www.rfc-editor.org/info/rfc7695>;.


Is that correct ?


Regards

Angga



> From: rfc-editor@rfc-editor.org
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: drafts-update-ref@iana.org, homenet@ietf.org, rfc-editor@rfc-editor.org
> Date: Mon, 18 Apr 2016 17:23:42 -0700 (PDT)
> Subject: [homenet] RFC 7787 on Distributed Node Consensus Protocol
> 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
>