
From nobody Mon Jun  1 02:01:49 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCAA11A9094; Mon,  1 Jun 2015 02:01:46 -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
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 c4xGzLJkd6KV; Mon,  1 Jun 2015 02:01:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B2161A9086; Mon,  1 Jun 2015 02:01:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150601090145.5550.10455.idtracker@ietfa.amsl.com>
Date: Mon, 01 Jun 2015 02:01:45 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/dXyQJUZP-AcwkwgAl3h739Pk1ck>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-dncp-04.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 01 Jun 2015 09:01:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Distributed Node Consensus Protocol
        Authors         : Markus Stenberg
                          Steven Barth
	Filename        : draft-ietf-homenet-dncp-04.txt
	Pages           : 27
	Date            : 2015-06-01

Abstract:
   This document describes the Distributed Node Consensus Protocol
   (DNCP), a generic state synchronization protocol which uses Trickle
   and Merkle trees.  DNCP is transport agnostic and leaves some of the
   details to be specified in profiles, which define actual
   implementable DNCP based protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-dncp/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-dncp-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-dncp-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jun  1 02:09:33 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8690A1A90B3 for <homenet@ietfa.amsl.com>; Mon,  1 Jun 2015 02:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=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 VCrMt7-HuII9 for <homenet@ietfa.amsl.com>; Mon,  1 Jun 2015 02:09:30 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 9C7261A90BD for <homenet@ietf.org>; Mon,  1 Jun 2015 02:09:30 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YzLin-0007iS-AQ with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for homenet@ietf.org; Mon, 01 Jun 2015 11:09:25 +0200
Message-ID: <556C213B.2080709@openwrt.org>
Date: Mon, 01 Jun 2015 11:09:15 +0200
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <20150601090145.5550.10455.idtracker@ietfa.amsl.com>
In-Reply-To: <20150601090145.5550.10455.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/NmPv7HBoHZzbzAxg_ke0H9lGaoA>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-dncp-04.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 01 Jun 2015 09:09:32 -0000

Thanks for all the comments we got on-list and in private during the
WGLC. We tried to address them in -04. Besides clarifications there is
one minor change:

Added mandatory rate limiting for network state requests, and
      optional slightly faster convergence mechanism by including
      current local network state in the remote network state requests.


We will prepare the next version of the HNCP-draft in the coming days so
it can be last called as well.


Thanks,

Steven and Markus


On 01.06.2015 11:01, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Home Networking Working Group of the IETF.
> 
>         Title           : Distributed Node Consensus Protocol
>         Authors         : Markus Stenberg
>                           Steven Barth
> 	Filename        : draft-ietf-homenet-dncp-04.txt
> 	Pages           : 27
> 	Date            : 2015-06-01
> 
> Abstract:
>    This document describes the Distributed Node Consensus Protocol
>    (DNCP), a generic state synchronization protocol which uses Trickle
>    and Merkle trees.  DNCP is transport agnostic and leaves some of the
>    details to be specified in profiles, which define actual
>    implementable DNCP based protocols.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-homenet-dncp/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-homenet-dncp-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-dncp-04
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 


From nobody Tue Jun  2 02:47:21 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 005831A90D9; Tue,  2 Jun 2015 02:47:18 -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
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 PzRxkWKtTC_N; Tue,  2 Jun 2015 02:47:16 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2815D1A90DD; Tue,  2 Jun 2015 02:47:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150602094716.27185.66990.idtracker@ietfa.amsl.com>
Date: Tue, 02 Jun 2015 02:47:16 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/YdvgGeOZVtt3A-CM2AIal7Lxtek>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-hncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2015 09:47:18 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Home Networking Control Protocol
        Authors         : Markus Stenberg
                          Steven Barth
                          Pierre Pfister
	Filename        : draft-ietf-homenet-hncp-05.txt
	Pages           : 30
	Date            : 2015-06-02

Abstract:
   This document describes the Home Networking Control Protocol (HNCP),
   an extensible configuration protocol and a set of requirements for
   home network devices on top of the Distributed Node Consensus
   Protocol (DNCP).  It enables automated configuration of addresses,
   naming, network borders and the seamless use of a routing protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-hncp/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-hncp-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-hncp-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Jun  2 02:52:56 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7FF41B2A0E for <homenet@ietfa.amsl.com>; Tue,  2 Jun 2015 02:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=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 eRbXvhZ_WxnW for <homenet@ietfa.amsl.com>; Tue,  2 Jun 2015 02:52:53 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 F18F61B2A0D for <homenet@ietf.org>; Tue,  2 Jun 2015 02:52:52 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YzisL-0006uk-8w with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for ; Tue, 02 Jun 2015 11:52:49 +0200
Message-ID: <556D7CE5.6080500@openwrt.org>
Date: Tue, 02 Jun 2015 11:52:37 +0200
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <20150602094716.27185.66990.idtracker@ietfa.amsl.com>
In-Reply-To: <20150602094716.27185.66990.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Errcr_d09jEyNhozAyHd2SyCgZc>
Cc: homenet-chairs@tools.ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2015 09:52:55 -0000

Hello everyone,

as announced here is the latest version of HNCP. We would kindly like to
request a WGLC for this as well.
This one also already includes feedback for HNCP we got during the
DNCP-LC, so thanks again for this.

Draft URL: https://tools.ietf.org/html/draft-ietf-homenet-hncp-05

Notable changes since HNCP-04:

* Renamed "Adjacent Link" to "Common Link".
* Changed single IPv4 uplink election from MUST to MAY.
* Added explicit indication to distinguish (IPv4-)DPs for local
connectivity and ones with uplink connectivity allowing e.g. better
local-only IPv4-connectivity.


Cheers,

Steven, Markus & Pierre

On 02.06.2015 11:47, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Home Networking Working Group of the IETF.
> 
>         Title           : Home Networking Control Protocol
>         Authors         : Markus Stenberg
>                           Steven Barth
>                           Pierre Pfister
> 	Filename        : draft-ietf-homenet-hncp-05.txt
> 	Pages           : 30
> 	Date            : 2015-06-02
> 
> Abstract:
>    This document describes the Home Networking Control Protocol (HNCP),
>    an extensible configuration protocol and a set of requirements for
>    home network devices on top of the Distributed Node Consensus
>    Protocol (DNCP).  It enables automated configuration of addresses,
>    naming, network borders and the seamless use of a routing protocol.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-homenet-hncp/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-homenet-hncp-05
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-hncp-05
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 


From nobody Tue Jun  2 03:05:00 2015
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECCBC1B2A63 for <homenet@ietfa.amsl.com>; Tue,  2 Jun 2015 03:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.078
X-Spam-Level: 
X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 vd94iovQm5QK for <homenet@ietfa.amsl.com>; Tue,  2 Jun 2015 03:04:57 -0700 (PDT)
Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com [209.85.213.169]) (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 3FC631B2A62 for <homenet@ietf.org>; Tue,  2 Jun 2015 03:04:57 -0700 (PDT)
Received: by igbsb11 with SMTP id sb11so83409653igb.0 for <homenet@ietf.org>; Tue, 02 Jun 2015 03:04:56 -0700 (PDT)
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:cc :content-type; bh=XzJ3AoFM4fEJXr+z/y04B9NP9yDpyShom1oNBmDZ1AU=; b=Svud/EFbv560dADrWkKNYFlw/aa0wl4sm2gIAf9LfFhwRZbV3D7sPomYp3j8fO2xq+ 0N0/ndUdiT3mKoHGNcCUDm61DCpfqYD0jlEwPcxqOMWJVXiX5SON8H6DTYxGAB9Bzu5G 3AUIcpuLvk2lFxWavaXyLuw9dkLJPW5vf2FoixCttZZLSW25tE82kJ7zaOTAEhjWmKyO G2w142VZUwWOdmXMCoJayxRIXNBrqINUsltf7MUTuegZtKLwvIvEgsbM+YxVgenSD1zh GTGNcTSYVs83imz1paFQMG7/nmpBGsLATOmLPO75j6cAuSFCcmQ2sfdHO0FcwVODbkWR C6tQ==
X-Gm-Message-State: ALoCoQkRnM1xPISWLGfJUe0fT8vdWGg5mfHN3objzpWV3H3lKCtft5Eopfs5skLvgYFp25omYcR/
MIME-Version: 1.0
X-Received: by 10.50.43.137 with SMTP id w9mr19117125igl.30.1433239496596; Tue, 02 Jun 2015 03:04:56 -0700 (PDT)
Received: by 10.36.2.84 with HTTP; Tue, 2 Jun 2015 03:04:56 -0700 (PDT)
Date: Tue, 2 Jun 2015 12:04:56 +0200
Message-ID: <CAESTAVsW=gwLJocMDveLeXG_G+4nxxXhBhEMnDGJ5EhmTEmWwA@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: draft-ietf-homenet-dncp@tools.ietf.org
Content-Type: multipart/alternative; boundary=e89a8f8388f512e55705178613a7
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/f0XiH7fJmZmRts25PCQvqEG-q9I>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: [homenet] A few more DNCP nits
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 02 Jun 2015 10:04:59 -0000

--e89a8f8388f512e55705178613a7
Content-Type: text/plain; charset=UTF-8

Authors,

We have reviewed your changes (just the diffs). Thank you for your efforts
and the quick response to WGLC comments. We found a few nits of our own,
would you mind including these in a quick -05 update? We will then hand
this off to the ADs their review, IETF last call, and IESG review.

Thanks,

- Mark and Ray

Terminology section - please delineate the terms from the definition. e.g.,

DNCP Profile: is a definition...

We found the use of ()'s confusing. e.g., Effective (trust) verdict.. are
the ()'s necessary?

"Something with data about most recent request(s) for network state -
simplest one being a timestamp for the most recent request for network
state (see Section 5.2)."

What is this something? This seems ambiguously worded.

Section 4, and perhaps elsewhere in the doc now, suffers from a lack of
delineation between the term being defined and the definition. What you had
before was better in our view (with the articles, "A", "An", "The"...), but
we are fine with you removing them if you make the terms stand out
separately.

Rather than "Zeroed", can we say something like "Padding (of value zero)
... "

Also, rather than "These padding bytes MUST NOT be included in the length
field." .. Of course you mean that the padding bytes must not contributed
to the length field, or included in the calculation of the length field.
But, that's not what the sentence actually says.

Just above section 7.2, the pipe symbol used in the ascii art is in the
wrong spot (16.5 rather than 16).

Also, spurious "with" just before 7.2:

"for the node with matching node"

--e89a8f8388f512e55705178613a7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div>Authors,</div><div><br></div><div>We h=
ave reviewed your changes (just the diffs). Thank you for your efforts and =
the quick response to WGLC comments. We found a few nits of our own, would =
you mind including these in a quick -05 update? We will then hand this off =
to the ADs their review, IETF last call, and IESG review.</div><div><br></d=
iv><div>Thanks,</div><div><br></div><div>- Mark and Ray</div><br><div>Termi=
nology section - please delineate the terms from the definition. e.g.,=C2=
=A0</div><div><br></div><div><span style=3D"color:rgb(0,0,0);font-family:mo=
nospace;font-size:11.1800003051758px;white-space:pre;background-color:rgb(2=
55,255,136)">DNCP Profile: is a definition...</span></div><div><span style=
=3D"color:rgb(0,0,0);font-family:monospace;font-size:11.1800003051758px;whi=
te-space:pre;background-color:rgb(255,255,136)"><br></span></div><div>We fo=
und the use of ()&#39;s confusing. e.g., Effective (trust) verdict.. are th=
e ()&#39;s necessary?<br></div><div><br></div><div>&quot;Something with dat=
a about most recent request(s) for network state<span style=3D"white-space:=
pre">=C2=A0</span>- simplest one being a timestamp for the most recent requ=
est for<span style=3D"white-space:pre">=C2=A0</span>network state (see Sect=
ion 5.2).&quot;</div><div><br></div><div>What is this something? This seems=
 ambiguously worded.</div><div><br></div><div>Section 4, and perhaps elsewh=
ere in the doc now, suffers from a lack of delineation between the term bei=
ng defined and the definition. What you had before was better in our view (=
with the articles, &quot;A&quot;, &quot;An&quot;, &quot;The&quot;...), but =
we are fine with you removing them if you make the terms stand out separate=
ly.=C2=A0</div><div><br></div><div>Rather than &quot;Zeroed&quot;, can we s=
ay something like &quot;Padding (of value zero) ... &quot;</div><div><br></=
div><div>Also, rather than &quot;These padding bytes MUST NOT be<span class=
=3D"" style=3D"white-space:pre">	</span>included in the length field.&quot;=
 .. Of course you mean that the padding bytes must not contributed to the l=
ength field, or included in the calculation of the length field. But, that&=
#39;s not what the sentence actually says.=C2=A0</div><div><br></div><div>J=
ust above section 7.2, the pipe symbol used in the ascii art is in the wron=
g spot (16.5 rather than 16).</div><div><br></div><div>Also, spurious &quot=
;with&quot; just before 7.2:=C2=A0</div><div><br></div><div>&quot;<span sty=
le=3D"color:rgb(0,0,0);font-family:monospace;font-size:11.1800003051758px;w=
hite-space:pre;background-color:rgb(255,255,136)">for the node with matchin=
g node&quot;</span></div><div><br></div><div><br></div><div><br></div><div>=
<br></div><div><br></div><div><br></div><div><span style=3D"color:rgb(0,0,0=
);font-family:monospace;font-size:11.1800003051758px;white-space:pre;backgr=
ound-color:rgb(255,255,136)"><br></span></div><div><span style=3D"color:rgb=
(0,0,0);font-family:monospace;font-size:11.1800003051758px;white-space:pre;=
background-color:rgb(255,255,136)"><br></span></div><div><span style=3D"col=
or:rgb(0,0,0);font-family:monospace;font-size:11.1800003051758px;white-spac=
e:pre;background-color:rgb(255,255,136)"><br></span></div></div>

--e89a8f8388f512e55705178613a7--


From nobody Wed Jun  3 04:49:14 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02FF91A6F2E; Wed,  3 Jun 2015 04:49: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
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 twWEXQR83Ux7; Wed,  3 Jun 2015 04:49:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5557D1A6EFC; Wed,  3 Jun 2015 04:49:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150603114907.15590.96491.idtracker@ietfa.amsl.com>
Date: Wed, 03 Jun 2015 04:49:07 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bT2H0LZX2CIaNfhAs4VbBGwdOCo>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-dncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 03 Jun 2015 11:49:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Distributed Node Consensus Protocol
        Authors         : Markus Stenberg
                          Steven Barth
	Filename        : draft-ietf-homenet-dncp-05.txt
	Pages           : 28
	Date            : 2015-06-03

Abstract:
   This document describes the Distributed Node Consensus Protocol
   (DNCP), a generic state synchronization protocol which uses Trickle
   and Merkle trees.  DNCP is transport agnostic and leaves some of the
   details to be specified in profiles, which define actual
   implementable DNCP based protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-dncp/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-dncp-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-dncp-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Jun  3 04:55:23 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21631A6F22 for <homenet@ietfa.amsl.com>; Wed,  3 Jun 2015 04:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=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 FMX-saJfPdxi for <homenet@ietfa.amsl.com>; Wed,  3 Jun 2015 04:55:19 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 8DD101A6F13 for <homenet@ietf.org>; Wed,  3 Jun 2015 04:55:19 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1Z07GN-00012N-O7 with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for ; Wed, 03 Jun 2015 13:55:15 +0200
Message-ID: <556EEB14.9090801@openwrt.org>
Date: Wed, 03 Jun 2015 13:55:00 +0200
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: Mark Townsley <mark@townsley.net>, draft-ietf-homenet-dncp@tools.ietf.org
References: <CAESTAVsW=gwLJocMDveLeXG_G+4nxxXhBhEMnDGJ5EhmTEmWwA@mail.gmail.com>
In-Reply-To: <CAESTAVsW=gwLJocMDveLeXG_G+4nxxXhBhEMnDGJ5EhmTEmWwA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/M0EBgmG9KG_JUZQmgxGPGDdh4-w>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] A few more DNCP nits
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 03 Jun 2015 11:55:21 -0000

Thanks for the review.

We just submitted https://tools.ietf.org/html/draft-ietf-homenet-dncp-05
and hope this versions addresses the remaining issues.


Cheers,

Steven

On 02.06.2015 12:04, Mark Townsley wrote:
> 
> Authors,
> 
> We have reviewed your changes (just the diffs). Thank you for your
> efforts and the quick response to WGLC comments. We found a few nits of
> our own, would you mind including these in a quick -05 update? We will
> then hand this off to the ADs their review, IETF last call, and IESG review.
> 
> Thanks,
> 
> - Mark and Ray
> 
> Terminology section - please delineate the terms from the definition. e.g., 
> 
> DNCP Profile: is a definition...
> 
> We found the use of ()'s confusing. e.g., Effective (trust) verdict..
> are the ()'s necessary?
> 
> "Something with data about most recent request(s) for network state -
> simplest one being a timestamp for the most recent request for network
> state (see Section 5.2)."
> 
> What is this something? This seems ambiguously worded.
> 
> Section 4, and perhaps elsewhere in the doc now, suffers from a lack of
> delineation between the term being defined and the definition. What you
> had before was better in our view (with the articles, "A", "An",
> "The"...), but we are fine with you removing them if you make the terms
> stand out separately. 
> 
> Rather than "Zeroed", can we say something like "Padding (of value zero)
> ... "
> 
> Also, rather than "These padding bytes MUST NOT beincluded in the length
> field." .. Of course you mean that the padding bytes must not
> contributed to the length field, or included in the calculation of the
> length field. But, that's not what the sentence actually says. 
> 
> Just above section 7.2, the pipe symbol used in the ascii art is in the
> wrong spot (16.5 rather than 16).
> 
> Also, spurious "with" just before 7.2: 
> 
> "for the node with matching node"
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 


From nobody Mon Jun  8 05:53:46 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17CFB1A702F for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 05:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 g_pBfIF5JLso for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 05:53:43 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47C181A1A40 for <homenet@ietf.org>; Mon,  8 Jun 2015 05:53:42 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t58Cre16022146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 8 Jun 2015 14:53:40 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t58Crc1h010190; Mon, 8 Jun 2015 14:53:39 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id D535461FA5; Mon,  8 Jun 2015 14:53:38 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Mmo8c7lm6DPG; Mon,  8 Jun 2015 14:53:26 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 779AB61F9A; Mon,  8 Jun 2015 14:53:22 +0200 (CEST)
Date: Mon, 08 Jun 2015 14:53:28 +0200
Message-ID: <87y4juwed3.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <556D7CE5.6080500@openwrt.org>
References: <20150602094716.27185.66990.idtracker@ietfa.amsl.com> <556D7CE5.6080500@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 08 Jun 2015 14:53:40 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 08 Jun 2015 14:53:40 +0200 (CEST)
X-Miltered: at korolev with ID 55759054.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 55759052.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 55759054.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 55759052.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 55759054.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 55759052.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/l_76HfW1uFdpwkj_hFuFKtxnvIs>
Cc: homenet@ietf.org, homenet-chairs@tools.ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 08 Jun 2015 12:53:45 -0000

> as announced here is the latest version of HNCP.

Thanks a lot.

As mentioned previously, we did set up a wired HNCP network here in Paris 
last month, and it works beautifully (at least on wired links).  I strongly 
support this work.

I rather like HNCP, which feels much less rigid than DNCP.  In particular, 
I'm glad to see that mDNS-proxying remains optional.

Questions and minor nits below, probably more to follow.


# Ad-hoc interfaces

You don't define ad-hoc interfaces.  From Section 4, it would seem that 
these are for non-transitive links with no prefix assignment (a la AHCP), 
but in that case some changes may be needed to DNCP, which I don't think 
will work on non-transitive links in its current shape.  In any case, the 
purpose of this feature needs to be made explained to the naive reader.


# Border discovery

What happens if there is a non-Homenet DHCP server on a link, but for some 
reason an address cannot be obtained from it (e.g. the server NAKs all 
DISCOVER/REQUEST messages)?  My reading is that the interface will be 
considered internal, and therefore not firewalled.  Is that the expected 
outcome?


# Policy needs review

There is a certain amount of policy in Section 6.4 and in Section 7 that 
needs careful review by a competent third party.  In particular, I'm not 
entirely comfortable with the IPv4 requirements in Section 6.4 (the IPv6 
requirements look fine to my amateurish eyes).

Section 7.1: I'm not familiar with DHCPv6, but is a preferred lifetime of 
1s a good idea?

Sections 7.2 and 7.4: why announce a route for each subnet?  We've got 
redirects for that.


# Reassembly

An HNCP node MUST be able to reassemble datagrams of 4000 octets.  IPv6 
allows a node to silently drop datagrams above 1500 octets.  Are there any 
widely-deployed stacks that limit reassembly to 1500 octets?  If so, 
I expect this to be the source of difficult to diagnose bugs.


From nobody Mon Jun  8 06:43:31 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2E4C1A8761 for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 06:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35] autolearn=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 OnHWvrlODrEA for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 06:43:28 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 7607A1A87AE for <homenet@ietf.org>; Mon,  8 Jun 2015 06:43:27 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1Z1xKm-0000e0-7E with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for ; Mon, 08 Jun 2015 15:43:24 +0200
Message-ID: <55759BEA.7080508@openwrt.org>
Date: Mon, 08 Jun 2015 15:43:06 +0200
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <20150602094716.27185.66990.idtracker@ietfa.amsl.com> <556D7CE5.6080500@openwrt.org> <87y4juwed3.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87y4juwed3.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/wfMayhOmLvxqN2fe9Q4-5ShWFjI>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 08 Jun 2015 13:43:30 -0000

Hi Juliusz,

> As mentioned previously, we did set up a wired HNCP network here in
> Paris last month, and it works beautifully (at least on wired links). 
> I strongly support this work.
thanks a lot for your (repeated) feedback and support.

>
> # Ad-hoc interfaces
>
> You don't define ad-hoc interfaces.  From Section 4, it would seem
> that these are for non-transitive links with no prefix assignment (a
> la AHCP), but in that case some changes may be needed to DNCP, which I
> don't think will work on non-transitive links in its current shape. 
> In any case, the purpose of this feature needs to be made explained to
> the naive reader.
In it's current form the adhoc-interface category in-fact results in an
assignment of a /64 per EACH adhoc-interface since the common-link is
defined to only consist of the single ad-hoc interface (including
potentially connected client-devices). An implementation can of course
provide configuration mechanisms to turn off address assignment on a
per-interface basis - independent of the interface being adhoc or not.

>
>
> # Border discovery
>
> What happens if there is a non-Homenet DHCP server on a link, but for
> some reason an address cannot be obtained from it (e.g. the server
> NAKs all DISCOVER/REQUEST messages)?  My reading is that the interface
> will be considered internal, and therefore not firewalled.  Is that
> the expected outcome?
Your reading is correct. However since homenet routers also reject (or
ignore) DHCP requests coming from other homenet routers, the situation
would be ambiguous if the outcome was different. Also please note that
the automatic border discovery is a best-effort heuristic to provide a
good (zeroconf) user experience as also explicitly noted in the security
considerations section. A router must in anyway provide means to set an
interface to a fixed category of internal or external.

>
> # Policy needs review
>
> There is a certain amount of policy in Section 6.4 and in Section 7
> that needs careful review by a competent third party.  In particular,
> I'm not entirely comfortable with the IPv4 requirements in Section 6.4
> (the IPv6 requirements look fine to my amateurish eyes).
The IPv4-policy is a bit complex, yes. The reasoning behind this is that
DHCP (and most client OS in general) do not really deal well with
multiple IPv4-addresses thats why we make sure that there is at most one
IPv4-prefix. There are other factors here, e.g. router's with global
IPv4 connectivity having preference other router's that can only provide
local IPv4 connectivity, etc.

>
> Section 7.1: I'm not familiar with DHCPv6, but is a preferred lifetime
> of 1s a good idea?
Noted, I will change this in the next revision, the intention here is to
keep fast renumbering working even with stateful DHCPv6. The given
procedure is probably debatable and inferior to others, i.e. one might
only hand out a lease for a ULA-based address and let global addresses
be numbered using RAs only.

>
> Sections 7.2 and 7.4: why announce a route for each subnet?  We've got
> redirects for that.
I think you misread that. The text says to announce one route per
"delegated prefix" not per "assigned prefix". This is e.g. to allow
differentiation of local and global connectivity. It is inherited from
RFC 7084 which more or less mandates that (for IPv6).



Cheers,

Steven


From nobody Mon Jun  8 07:28:46 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8BE21A88D7 for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 07:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 lYgq_gR5HGoK for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 07:28:44 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35E291A8920 for <homenet@ietf.org>; Mon,  8 Jun 2015 07:28:43 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t58ESfW1019281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 8 Jun 2015 16:28:41 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t58ESfFg025284; Mon, 8 Jun 2015 16:28:41 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 57FDF61FA3; Mon,  8 Jun 2015 16:28:41 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id V-0gc5WwHsEv; Mon,  8 Jun 2015 16:28:40 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0427461F9A; Mon,  8 Jun 2015 16:28:39 +0200 (CEST)
Date: Mon, 08 Jun 2015 16:28:44 +0200
Message-ID: <87sia2w9yb.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <55759BEA.7080508@openwrt.org>
References: <20150602094716.27185.66990.idtracker@ietfa.amsl.com> <556D7CE5.6080500@openwrt.org> <87y4juwed3.wl-jch@pps.univ-paris-diderot.fr> <55759BEA.7080508@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 08 Jun 2015 16:28:41 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 08 Jun 2015 16:28:41 +0200 (CEST)
X-Miltered: at korolev with ID 5575A699.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5575A699.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5575A699.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5575A699.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5575A699.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5575A699.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/uwa9qBffSBUyqxTQ1Ns9BfVBu8c>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 08 Jun 2015 14:28:44 -0000

>> You don't define ad-hoc interfaces.  From Section 4, it would seem 
>> that these are for non-transitive links with no prefix assignment (a 
>> la AHCP), but in that case some changes may be needed to DNCP,

> In it's current form the adhoc-interface category in-fact results in an 
> assignment of a /64 per EACH adhoc-interface

I see.

So is that meant to support non-transitive links, or something else?  If 
the former, I'll need to go through the DNCP draft and stare at the places 
that seem to assume transitivity until grokking comes.

In any case, you need to provide some rationale and implementation 
guidance for the ad-hoc interface type.

>> Sections 7.2 and 7.4: why announce a route for each subnet?  We've got 
>> redirects for that.

> I think you misread that. The text says to announce one route per 
> "delegated prefix"

Right.  Am I the only person who got confused by that?

-- Juliusz


From nobody Mon Jun  8 07:39:48 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEEAF1A89B1 for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 07:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 lf-LXf1DNfAm for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 07:39:41 -0700 (PDT)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id E040A1A898F for <homenet@ietf.org>; Mon,  8 Jun 2015 07:39:27 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 552B87C904BEDBF1 for homenet@ietf.org; Mon, 8 Jun 2015 17:39:26 +0300
Message-ID: <5575A91E.6020105@iki.fi>
Date: Mon, 08 Jun 2015 17:39:26 +0300
From: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <20150602094716.27185.66990.idtracker@ietfa.amsl.com> <556D7CE5.6080500@openwrt.org> <87y4juwed3.wl-jch@pps.univ-paris-diderot.fr> <55759BEA.7080508@openwrt.org> <87sia2w9yb.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87sia2w9yb.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DN3EvTNeh_ypvNm5vDU7GIDqni0>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 08 Jun 2015 14:39:47 -0000

Thanks for the review from me as well.

On 8.6.2015 17.28, Juliusz Chroboczek wrote:
>>> You don't define ad-hoc interfaces.  From Section 4, it would seem
>>> that these are for non-transitive links with no prefix assignment (a
>>> la AHCP), but in that case some changes may be needed to DNCP,
>> In it's current form the adhoc-interface category in-fact results in
>> an assignment of a /64 per EACH adhoc-interface
> I see.
>
> So is that meant to support non-transitive links, or something else?  If
> the former, I'll need to go through the DNCP draft and stare at the
> places that seem to assume transitivity until grokking comes.

DNCP supports transitive links _and_ non-transitive links, but some 
corner cases (e.g. consistently unreliable non-transitive links) result 
in the well-known (and typically bad) naive non-mesh link-state routing 
protocol-like behavior (flapping neighbor status, and in this case, 
Trickle never settling down so bit more churn overall).

> In any case, you need to provide some rationale and implementation
> guidance for the ad-hoc interface type.

I wonder how well the implementation and the spec are in sync these days 
- at least the implementation is very hairy in the various specialized 
HNCP modes.

>>> Sections 7.2 and 7.4: why announce a route for each subnet?  We've
>>> got redirects for that.
>
>> I think you misread that. The text says to announce one route per
>> "delegated prefix"
>
> Right.  Am I the only person who got confused by that?

I would like to get 'proof of life' of other people actually reading the 
spec - anyone? ;)

Cheers,

-Markus


From nobody Mon Jun  8 15:06:22 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 757051A9101 for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 15:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 JniUWtQVVTzL for <homenet@ietfa.amsl.com>; Mon,  8 Jun 2015 15:06:19 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6AC11A90E6 for <homenet@ietf.org>; Mon,  8 Jun 2015 15:06:18 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t58M6Gso019571; Tue, 9 Jun 2015 00:06:16 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 2F12361FA2; Tue,  9 Jun 2015 00:06:16 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id X6rryXaqHRbB; Tue,  9 Jun 2015 00:06:11 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E0FCD61F9A; Tue,  9 Jun 2015 00:06:10 +0200 (CEST)
Date: Tue, 09 Jun 2015 00:06:15 +0200
Message-ID: <87pp55x3c8.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <5575A91E.6020105@iki.fi>
References: <20150602094716.27185.66990.idtracker@ietfa.amsl.com> <556D7CE5.6080500@openwrt.org> <87y4juwed3.wl-jch@pps.univ-paris-diderot.fr> <55759BEA.7080508@openwrt.org> <87sia2w9yb.wl-jch@pps.univ-paris-diderot.fr> <5575A91E.6020105@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 09 Jun 2015 00:06:17 +0200 (CEST)
X-Miltered: at korolev with ID 557611D8.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 557611D8.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 557611D8.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Jv329hFmb8uh2qXwXvQY5xBj1xI>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 08 Jun 2015 22:06:20 -0000

> DNCP supports [...] non-transitive links

The optional algorithm in Section 6.2 most certainly won't work on 
non-transitive links.  (It's optional, so no big deal, but if DNCP is 
documented to work on non-transitive links, then this should be mentioned 
somewhere.)

I'm not sure if there are any other issues with non-transitive links, and 
I'm too tired right now for further nit-picking.  I'll do my best tomorrow.

-- Juliusz


From nobody Mon Jun 15 04:01:23 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5957C1A1B03; Mon, 15 Jun 2015 04:01:22 -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
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 xZGWB9wH075y; Mon, 15 Jun 2015 04:01:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BCCF91A1B05; Mon, 15 Jun 2015 04:01:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150615110116.19793.74572.idtracker@ietfa.amsl.com>
Date: Mon, 15 Jun 2015 04:01:16 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/aDe9XJqByHtCozK4EkpMIBB1www>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-prefix-assignment-07.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 15 Jun 2015 11:01:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Distributed Prefix Assignment Algorithm
        Authors         : Pierre Pfister
                          Benjamin Paterson
                          Jari Arkko
	Filename        : draft-ietf-homenet-prefix-assignment-07.txt
	Pages           : 19
	Date            : 2015-06-15

Abstract:
   This document specifies a distributed algorithm for automatic prefix
   assignment.  Thus it provides an alternative to manual or centralized
   prefix and address assignment techniques.  Given a set of delegated
   prefixes, it ensures that at most one prefix is assigned from each
   delegated prefix to each link.  Nodes may assign available prefixes
   to the links they are directly connected to, or for other private
   purposes.  The algorithm eventually converges and ensures that all
   assigned prefixes do not overlap.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-prefix-assignment/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-prefix-assignment-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-prefix-assignment-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Jun 16 02:59:15 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED391ACE44 for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 02:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 f1G_Pw8_PFtU for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 02:58:56 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 992511AD0B3 for <homenet@ietf.org>; Tue, 16 Jun 2015 02:58:56 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 3513DA3; Tue, 16 Jun 2015 11:58:53 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1434448733; bh=YDmsyBEbMy5DOWWNV/o6r+d2A2TDOKeqXsbZG48YJxc=; h=Date:From:To:Subject:From; b=rYvq3Uh/tRnQ0xXC2RRWdu/zeYwPoGrSG9GWqmwXQEgMEmv0sq5bwI+20XY18DmTK x693UMwli0LUeVXuRHauNuM0UdAZGQuYiiKAyxw+4b+f8wtYWZck585UJcldtxtS3l LScigUmcKmJdYZKm3Dlc5dmEbYmfdAZ6YMZWyOKA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 296F7A2 for <homenet@ietf.org>; Tue, 16 Jun 2015 11:58:53 +0200 (CEST)
Date: Tue, 16 Jun 2015 11:58:53 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: homenet@ietf.org
Message-ID: <alpine.DEB.2.02.1506161154390.9487@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-915990141-1434448733=:9487"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/7kSuxggEjoD54AAScP3MgT4CNAw>
Subject: [homenet] ISIS upcoming development and demo
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2015 09:59:07 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-915990141-1434448733=:9487
Content-Type: TEXT/PLAIN; format=flowed; charset=UTF-8
Content-Transfer-Encoding: 8BIT


Hi, everbody.

We’d like to announce that at the IETF in Prague there will be a demo at 
the Bits’n’Bytes of IS-IS running over IPv6 link local addressing, 
including using mostly unicast packets for node to node communication to 
work better with wifi. The needed modifications will be taken to the ISIS 
working group as well, in order to make these changes standards track, 
with -00 drafts released before the draft submission deadlines for Prague 
IETF. There will be two code bases presented that’ll interoperate using 
these changes, both the Erlang one (which will be fully managed using 
zebrad in Quagga), and the existing C based one in Quagga will see 
implementations of all the mentioned changes.

During Q3, all the changes to both code bases will be rigorously tested 
using ISIS testing suites and bugs fixed to assure that both code bases 
adhere to the IS-IS standards and that both code bases will be “production 
grade” code.

We hope this will address the major concerns about IS-IS being not 
suitable for homenet use because of its use of multicast and that it 
doesn’t run over IPv6, and also that the Erlang codebase is too big.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-915990141-1434448733=:9487--


From nobody Tue Jun 16 03:09:18 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B3F1B29BF for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 03:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 GAsiI8c4972q for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 03:09:15 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 792F11AD09A for <homenet@ietf.org>; Tue, 16 Jun 2015 03:09:15 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5GA9DwJ020803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Jun 2015 12:09:13 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t5GA9DSZ015408; Tue, 16 Jun 2015 12:09:13 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 71D1A61FBB; Tue, 16 Jun 2015 12:09:13 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id AdnEgeVZH_r7; Tue, 16 Jun 2015 12:09:12 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 5D28961FAB; Tue, 16 Jun 2015 12:09:12 +0200 (CEST)
Date: Tue, 16 Jun 2015 12:09:14 +0200
Message-ID: <87twu82cdx.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1506161154390.9487@uplift.swm.pp.se>
References: <alpine.DEB.2.02.1506161154390.9487@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 16 Jun 2015 12:09:13 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 16 Jun 2015 12:09:13 +0200 (CEST)
X-Miltered: at korolev with ID 557FF5C9.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 557FF5C9.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 557FF5C9.003 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 557FF5C9.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 557FF5C9.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 557FF5C9.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xGGpOTGzsZAABM8ugOnqAgakNyg>
Cc: homenet@ietf.org
Subject: Re: [homenet] ISIS upcoming development and demo
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2015 10:09:17 -0000

> We’d like to announce that at the IETF in Prague there will be a demo at 
> the Bits’n’Bytes of IS-IS running over IPv6 link local addressing,

Excellent.

> using mostly unicast packets for node to node communication to work 
> better with wifi

Interesting workaround.  Can you share your experimental data?

-- Juliusz


From nobody Tue Jun 16 08:34:17 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 732FA1B2DE3 for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 08:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Ny2QqfQ59DPi for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 08:34:14 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 EDCD81B2DDE for <homenet@ietf.org>; Tue, 16 Jun 2015 08:34:13 -0700 (PDT)
Received: by oiha141 with SMTP id a141so14086462oih.0 for <homenet@ietf.org>; Tue, 16 Jun 2015 08:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=u6xGBALDmMLgmM5ED8yz4saUr6HZuDjajIFZkiOlfZo=; b=Qu+CKUWXiPGZeR8ot/XV0o3oVac5nA6KgMnhhDtoNFz7cRE/pdZcm0QMRHBpb//LnS +eL2PFO5/ILg4virrQis8MowGWlhVvuRv0tg6aFYimNHvMjWfKcHn1IW2CpWx/37aeHv NU9aY63xE5ePBn0i/pvGg0j2ceEjmkdRKiNMyEp/a5GD/7ShxaaBvmOGUHqd20WBVsAh 6agKQQgIPbY9ZfBYsQwM8LZcU0ePGp/rUjW/4bIHpi04Hk+C3YRIoG/mDTXtczbJaEgV CZ0d/zuUMTOqrGUL3t4mIJVElyzdBDvmnJQG+f3WOsMYD4fBztux3agkUZAQUOs5dQBI yUfw==
MIME-Version: 1.0
X-Received: by 10.182.246.9 with SMTP id xs9mr726942obc.45.1434468853502; Tue, 16 Jun 2015 08:34:13 -0700 (PDT)
Received: by 10.202.105.129 with HTTP; Tue, 16 Jun 2015 08:34:13 -0700 (PDT)
In-Reply-To: <87twu82cdx.wl-jch@pps.univ-paris-diderot.fr>
References: <alpine.DEB.2.02.1506161154390.9487@uplift.swm.pp.se> <87twu82cdx.wl-jch@pps.univ-paris-diderot.fr>
Date: Tue, 16 Jun 2015 08:34:13 -0700
Message-ID: <CAA93jw4WgDi_RskUD31eVZ2DrkUQRmdbp_7DU-4X3Zj-rUbbjA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/5HutMwPeOOTNrSQcJ_KPO4BL69Q>
Cc: HOMENET <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] ISIS upcoming development and demo
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2015 15:34:15 -0000

What I have never figured out was how to get something in bits & bytes.
I am hauling a boatload of gear from various manufacturers, might as
well set it up.

Is there going to be dogfooding?

On Tue, Jun 16, 2015 at 3:09 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> We=E2=80=99d like to announce that at the IETF in Prague there will be a=
 demo at
>> the Bits=E2=80=99n=E2=80=99Bytes of IS-IS running over IPv6 link local a=
ddressing,
>
>
> Excellent.
>
>> using mostly unicast packets for node to node communication to work bett=
er
>> with wifi
>
>
> Interesting workaround.  Can you share your experimental data?
>
> -- Juliusz
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast


From nobody Tue Jun 16 08:45:45 2015
Return-Path: <ietf@thomasclausen.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18F521B3B0B; Tue, 16 Jun 2015 08:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_INVITATION=-2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 yEj80FL4UeMj; Tue, 16 Jun 2015 08:45:38 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3CEF1B3B07; Tue, 16 Jun 2015 08:45:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 72A6524038D; Tue, 16 Jun 2015 08:45:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.78] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id CF8202403A3; Tue, 16 Jun 2015 08:45:36 -0700 (PDT)
From: Thomas Clausen <ietf@thomasclausen.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Jun 2015 17:45:34 +0200
Message-Id: <BA8A243F-70C3-43C8-8B5E-B813942BA590@thomasclausen.org>
To: "<rtg-ads@tools.ietf.org>" <rtg-ads@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8eCWzftyXl8O-qWW29WzB-kLq4c>
Cc: "<rtg-dir@ietf.org>" <rtg-dir@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, draft-ietf-homenet-dncp.all@tools.ietf.org
Subject: [homenet] RtgDir review: draft-ietf-homenet-dncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2015 15:45:44 -0000

Hello,

I have been selected as the Routing Directorate reviewer for this draft. =
The Routing Directorate seeks to review all routing or routing-related =
drafts as they pass through IETF last call and IESG review, and =
sometimes on special request. The purpose of the review is to provide =
assistance to the Routing ADs. For more information about the Routing =
Directorate, please see =
http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it =
would be helpful if you could consider them along with any other IETF =
Last Call comments that you receive, and strive to resolve them through =
discussion or by updating the draft.

Document: draft-ietf-homenet-dncp-05.txt
Reviewer: Thomas Heide Clausen
Review Date: June 16, 2015
IETF LC End Date: <Reviewed during (just after - apologies) WGLC>

Intended Status: Standards Track

Summary:=20

	o	I have significant concerns about this document and =
recommend that the
		Routing ADs discuss these issues further with the =
authors.

Comments:

	o	Is there any good reason why the authors have no listed =
affiliation?
=09
	o	It is somewhat contradictory that the abstract talks =
about=20
		"...describes a protocol" and then later "...leaves some =
details
		 to be specified in profiles, which define actual =
implementable DNCP
		 based protocols"
		=20
		 Does that not mean, then, that this document specifies =
an algorithm,
		 a framework, and not a protocol?

	o	On that, I see "DNCP protocol" several places. Expanded, =
that becomes
		"Dynamic Network Configuration Protocol Protocol" ...
	=09
	o	In general, and despite actually knowing some of the =
core algorithms
		somewhat before this review, I found the document really =
tough to
		read, with convoluted sentences, inconsistent =
requirements-language,
		and a lack of introductory "here's the 1000ft view of =
the protocol,
		what it does, how it works, and under which conditions =
it works".
	=09
	o	On that, I do not find the chosen structure of the =
document to be
		optimal for conveying an unambiguous protocol =
specification. For one,
		the same concepts are occasionally described slightly =
differently.
		For another, it is often hard to find the information =
needed to
		parse a specific mandated processing (for example). I =
provide an
		example of what I would suggest a better structure in =
the below.=20
		=09
		The goal is to provide first concepts and an overview, =
followed by a
		single, easy to identify place for "precise and =
unambiguous definitions
		of concepts", and then use those in the detailed =
expression of the
		protocol. Note that this is just an example, of course:
			=09
			Section "Terminology:"
				The Network State Hash is a hash value =
which represents the
				current state of the network, as known =
by a node.
			=09
			Section "Protocol Overview and Functioning"
		=09
				When receiving a FOO TLV, the DNCP node =
compares the received
				Network State Hash with its own Network =
State Hash. This
				represents the consistency check rom =
RFC6206. If same,
				then...if not, then ....
			=09
			Section "Protocol Information Bases"
				For the purpose of this specification, =
the Protocol
				Information Bases are orgnaized as sets =
of tuples ... any
					implementation can chose =
whatever representation it wants.
			=09
					The Network State Information =
Base in a DNCP node is a set
					of tuples:
						(x, y, z, w)
				=09
					where x is ..., y is ..., z is =
..., and w is ...
				=09
			Section "How to calculate the Network State =
Hash":
				=20
				 The network State Hash is calculated =
using the information
				 from the Network State Information =
Base, as follows:
				=20
					 	1. First, the tuples in =
that information base are sorted
				 		   in ascending order =
based on ....
				 	  =20
					 	2. Second, .... =
(concatenation)
				 =09
					 	3. Third, the hash =
function from <profile> is used
				 =09
					 	4. Fourth, the first n =
bits of the resulting hash value,=20
					 	   are retained, witn n =
being from <profile>.

			And then, in remaining sections simply reference =
the Network
			State Hash, which is now ubiquitously defined in =
a single place.
		=09
			I am taking this example, since when reading =
section 5.3 I found=20
			myself chasing through the document, finding =
multiple slightly
			different definitions of "Network State Hash" -- =
 but beyond this
			example, it generally does apply to the document =
as a whole, and
			certainly to all of the processing and =
generation considerations in
			section 5.
=09
	o	As a general comment, the document would do well with a =
good editorial
		overhaul to bring consistency in language usage, =
consistency in 2119
		terminology, coherence in defined terms and their =
definition, document
		structure, etc.
	=09
Major Issues:
=09
	o	The introduction does not read well; it contains parts =
of something that
	 	could be considered as part of an applicability =
statement (without it
	 	being called out as such, and without forming a complete =
applicability
		statement), and does not actually introduce the =
protocol. Reading just=20
		the introduction and the abstract, it is very obscure if
		this is a framework, a protocol, a building block, an =
architecture, an
		algorithm -- and, if either of those, what it is =
actually accomplishing,
		and why one would chose to use DNCP. It does, however, =
transpire that
		"whatever it is", it has two "modes" and that it =
requires something
		(presumably a routing protocol) to provide each "node" =
with a topology
		map.
	=09
		Suggest that a proper introduction consisting of three =
parts would be
		beneficial: (i) what this document is, (ii) what doing =
DNCP actually
		gets you, and (iii) the operating conditions under which =
the
		DNCP is applicable.
	=09
		On the latter point, given that you state that DNCP =
requires profiles
		to provide "actual implementable DNCP based protocols", =
it appears
		important to understand what the limits for "what a =
profile can give=20
		you" are.
	=09
		I am calling this out as a major issue, since I believe =
that it is
		not just editorial, but is a matter of scoping this =
document correctly,
		and in particular not falling into the trap of "claiming =
applicability
		where it's not".

	o	The document, in my understanding, defines an exchange =
format with
		limited ability to evolve, as simply "a steam of TLVs".

		As long as there's never a need to evolve the TLV format =
itself, and
		as long as you do not run out of TLV types, that's not =
going to be
		a problem. The doc sets aside a 16bit TLV type space, =
that's reasonable
		enough, but I worry if eventually a DNCPv2 will need to =
evolve the=20
		format. One purely hypothetical example could be if a =
"sequence number"
		would be needed in each DNCP message to detect "link =
success rates", or
		something of that sort. =20
	=09
		I do not have an actual example in mind -- and that's =
exactly the point:
		to be evolutive for the unknown future and (at the very =
least) be able
		to discriminate between "old" and "new".
	=09
		A discussion could be had if a "version number" in each =
TLV would do,
		or if a concept of "protocol message with a version =
number" is
		preferential. I do not believe, however, that "no =
version number" is
		viable.

	o	Noting that the "overhearing n reduncant transmissions" =
is a key=20
		retransmission suppression mechanism in Trickle, and =
that this
		seems to assume broad/multicast, using unicast seems to =
contradict
		the statement of "consists of Trickle", at least in the =
way the
		algorithm is defined in RFC6206. Note: it's fine to use =
an algorithm
		outside of its initial scope, but it should be with the =
caveat of
		"which of the characteristics still hold, and which do =
not"

	o	DNCP claims to be trickle based, yet supports unicast. =
It also
		(apparently) is a request/reply protocol.  It doesn't =
have messages.
		This document needs a good, and pedagogical, "protocol =
overview and
		functioning" section somewhere: one needs to get through =
the end of
		Section 5 before having even a vague idea of how DNCP =
works.
	=09
	o	The use of normative language is not as tight as could =
be desired.
		For example, a number of SHOULDs seem to really ought to =
be "MAYs" since=20
		not following the SHOULD won't break the algorithm. It =
would be good=20
		to walk through the document and take a careful look at =
these to
		either MUST/MAY the SHOULDs, or to qualify the SHOULDs =
remaining.
	=09
	o	I am going to go out on a limb here, and say that "the =
protocol is
		underspecified". That's a deliberately provocative =
statement, but it
		was honestly how I felt upon having completed the =
review.=20
	=09
		The document does not help the reader get an intuitive =
understanding
		of the protocol functioning, but jumps right into minute =
details --
		requiring the reader to "build up her or his own model =
of how DNCP
		works". On having read the document a few times, I think =
that I=20
		understand it -- but there's nothing permitting me to =
verify my
		understanding, and thereby I'd not feel confident to be =
able to
		provide an interoperable and independent implementation. =
I've given
		some comments in the "Comments" section as to what I =
think would be
		viable ways to improve this point.

	 o	Section 5.3, penultimate paragraph:
	=20
	 		"If keep-alives specified in Section 6.1 are NOT =
sent by the peer
		     (either the DNCP profile does not specify the use =
of keep-alives or
		     the particular peer chooses not to send =
keep-alives), some other
		     means MUST be employed to ensure its presence.  =
When the peer is no
		     longer present, the Neighbor TLV and the local DNCP =
peer state MUST
		     be removed."
		    =20
		"...some other means MUST be employed to ensure its =
presence." --
		followed by more MUST verage when a peer disappears...I =
am not sure that
		that's conductive to interoperable implementations.
	=09
		Two implementatons may chose different "means" and then =
turn off keep-
		alives - and be non-interoperable.
	=09
		For interoperability, we need:
	=09
				o	A mandatory to implement =
mechanism, that always is
					present, but can be complemented =
by another "means", or
				=09
				o	A mandatory to implement =
mechanism, which by way of a
					specified negotiation mechanism =
can be turned off between
					two peers, to allow them to use =
another "means".
				=09
		If you argument is "...this will be specified in the =
profile", then
		you still should provide the two above in this document, =
with the note
		that "...and a profile may specify which from among =
these MUST be
		used in a given deployment"

	o	Section 8:
		Interesting; I am not a security expert, but I am very =
curious to
		see the SEC-DIR review of this document. That said, =
section 8.3.1=20
		contains normative verbage:
	=09
			"A node MUST be trusted for participating in the =
DNCP network if and
			only if..."
		=09
		Which I think needs a qualifier of the "If the =
certificate based
		trust model is used, then a node must be trusted for =
...."
=09
		Same goes for the subsequent SHOULD - it really reads =
as-if this
		certificate based mechanism initially was intended as =
MTI, but then
		was backed away from subsequently without a complete =
cleanup of the
		text?
	=09
		I do actually question the value of having a =
laundry-list of trust=20
		management methods, and for one of those (certs) a =
laundry-list
		of all sorts of trust relationship establishment =
methods, in this
		document; this in no small part as the lists are =
explicitly indicated
		as "non-exhaustive" and that none are listed as =
"mandatory to
		implement". Was any thought given to factoring this into =
a seperate
		document, and focusing in this document on one, =
mandatory-to-implement,
		security mechanism?
	=09
Minor Issues:

	Introduction:
		o	1st paragraph: "reachable nodes"; two things:
	=09
				-	I always have a problem with the =
term "node"; it is often
					used as a shorthand for "routers =
and hosts, both". I was
					given to understand that homenet =
specifically did not want
					to consider host changes?
				=09
				-	"Reachable" - does that mean =
something as in "radio range",
					does it mean "on the same link", =
does it mean within a
					specific (DNCP?) domain, or does =
it mean simply "on the
					Internet somewhere"?
				=09
		o	2nd paragraph: "nodes that are currently =
accounted for":
				-	What does that mean?
			=09
				-	Also, the conclusion "Therefore =
unlike Time-To-Live (TTL) =09
					based solutions, it does not =
require periodic re-publishing
					of the data by the nodes" does =
actually not follow from
					the previous sentence in that =
paragraph.

				-	I actually do not think that the =
introduction describes
					what DNCP does, and so the =
comparison to TTL-based=20
					solutions is rather hard to get =
here.
				=09
				-	Continuing:
			=09
						"On the other hand, it =
does require the topology
						to be visible to every =
node that wants to be able to
						identify unreachable =
nodes and therefore remove old,
						stale data."
					=09
					This reads a lot more like an =
applicability statement than
					an introduction; the take-away =
when reading this is:
				=09
						"Each node must have =
something that maintains
						 a topology map of the =
entire network, such as=20
						 a (LS) routing =
protocol, for DNCP to function"
						=20
					Is that actually the intent =
here?
				=09
				-	"DNCP is most suitable for data =
that changes only gradually"
					How is the reader to interpret =
"gradually"? Do you mean
					"infrequently", or do you really =
mean "gradualy"?
				=09
		o Last paragraph:
				"DNCP has relatively few requirements =
for the underlying
				 transport; it requires some way of =
transmitting either unicast
				 datagram or stream data to a peer"
		=09
			This is a bit of a forward comment, but we now =
have "nodes
			that are accounted for" and "peers". I see =
neither defined in
			the terminology section.
			=09
				"and, if used in multicast mode, a way =
of
				 sending multicast datagrams."
		=09
			This is the first mention of two "modes" of this =
protocol. This
			loops back to an earlier comment, that the =
introduction actually
			does not introduce the protocol, but rather is =
an incomplete
			applicability statement.
			=09
				"If security is desired and one of the
 	 			 built-in security methods is to be =
used, support for some
				TLS-derived transport scheme - such as =
TLS [RFC5246] on top of
				TCP or DTLS [RFC6347] on top of UDP - is =
also required."
  =20
   			I am not pretending to be a security expert, but =
"some
   			TLS-derived...such as ... on top of TCP or =
DTLS..." (i) does not
   			sound like it could lead to interoperable =
implementations, and (ii)
   			does not sound sufficiently tight as a MTI =
security mechanism to
   			pass security reviews. Again, I am no security =
expert, but perhaps
   			getting one looped in early would be advicable?
		=09
	Terminology:
		o	Suggest adding "In this document ..." somewhere =
to this text:

				"For readability, any DNCP profile =
specific
				 parameters with a profile-specific =
fixed value are
				 prefixed with DNCP_."
				=20
		o	DNCP network: I read this twice, and came away =
with two different
			understandings, perhaps you can clarify which it =
is:

				o	A set of nodes running DNCP, =
within the same domain, and
					for which a path betwen any two =
DNCP nodes includes only
					other DNCP nodes; i.e., a DNCP =
network forms a connected
					component with only other DNCP =
nodes.
				=09
				o	A set of nodes running DNCP. =
They may be anywhere on the
					Internet, they are part of the =
same DNCP network as long
					as they (through other means) =
have learned of each others
					addresses.
				=09
			In the former, that'd be (for example) a =
deployment within my
			home -- in the latter, it could be a node in my =
home and a node in
			your home forming a DNCP network.=20
		=09
			The text is not quite clear on this point.
=09
		o	Link: a point of clarification here. In "DNCP =
network", there was
			talk about "unidirectional links" and =
"bidirectional links"; in
			"Link" the definition is somewhat vague =
"directly connected" and=20
			"can communicate". Could something like "without =
decrementing TTL/
			hop-count" be added, and could a statement on =
bidirectionality=20
			(IOW, that this is just an IP link) be added?
		=09
		=09
		o	"Interface" is overloading the term "port" (IP =
port) which can be
			confusing
		=09
		o	"Endpoint" - The definition "locally configured =
use of DNCP" is not
			clear -- are you really not talking about a DNCP =
process?=20
		=09
			I am not sure that it is clear how a DNCP =
process can be "attached
			to  ... a specific remote unicast address, or to =
a range of unicast
			addresses that are allowed to contact"

			I can see how a DNCP process can be configured =
to allow connections=20
			from a specific range of addresses, or can be =
configured to connect
			to a specific remote unicast address. Is that =
what you mean instead?
		=09
		=09
		o	"Peer" - states that two peers "communicate =
directly". For link,
			the definition is "directly connected nodes can =
communicate".
			Would it then not be easier to say "a DNCP node =
on the same link=20
			as ..." ?
	=09
		o	"Node state"
				"The hash function and the number of =
bits used are defined=20
				 in the DNCP profile."
				=20
			Suggest:
				"The hash function and the length of the =
hash value are defined=20
				 in the DNCP profile."
		=09
		=09
		o	"Network state hash" - same comment as for node =
state (above)
	=09
	Data model:
		o	"Latest update sequence number"
			This may just be my personal taste, but does it =
hurt to mandate
			a specific way of doing the looping comparison? =
The reason I=20
			suggest this is, that it's one of those things =
where creativity
			in an implementation seems to simply be an =
invitation for bugs,
			and for little gain
		=09
		o	"Relative time delta"
			Document talks about "a 32 bit number on the =
wire" -- does that
			mean that wireless links are excluded?
		=09
		o	Related to terminology, there seems to be some =
fuzzyness around
			node and endpoint. For example, in data model =
one of the things that
			a DNCP node may have is:

				"Unicast address: the DNCP node it =
should connect with"
		=09
			Does that mean *any* DNCP process (i.e., *any* =
endpoint) at that
			address, or a *specific* DNCP process at that =
address?
		=09
			The same, but inverse, for "Range of addresses: =
the DNCP nodes that
			are allowed to connect" - is this "any DHCP =
process (i.e., *any*
			endpoint) on any of these addresses?
		=09
			Following, the same section reads:

				"For each remote (peer, endpoint) pair =
detected on a local
				endpoint, a DNCP node has..."
	=09
			the following text indicating that there's some =
sort of distinction
			between which endpoint.
		=09
			This whole thing needs some clarification.		=
=09
	=09
	Operation
	=09
		o	First a generic comment that Trickle itself has =
some operating
			conditions which scopes its applicability, and =
it would behove
			this document to, in its own applicability =
statement, call out
			those.
		=09
		o	On the same token, while the use of Trickle in =
an unicast fashion
			is possible, I wonder if (in general) unicast =
use is advicable. I
			appreciate that some links are point-to-point =
and so a broadcast=20
			across it becomes an unicast -- but, does that =
necessitate being
			called out?
		=09
			IF the reason for this "because we can use TCP", =
then be explicit
			about this - but, also, that you're then not =
exactly using Trickle
			where and how it was intended. I wonder if you =
could be explicit=20
			as to what consequences this "alternate use of =
Trickle" have? It
			seems that the use of unicast is directly =
contradicting the main
			operating consideration of Trickle?
		=09
		o	2nd paragraph states:=20
	=09
				"the multicast transport does not have =
to be particularly
				 secure"
	=09
			What is the definition of "not have to be =
particularly secure"?
			Is cleartext OK? Authentication? Encryption?
			Should I do something more?
		=09
	5.1 Trickle-driven status updates
		o 	First paragraph:
	=09
				"Multicast MUST be employed on a =
multicast-capable interface;
				 otherwise, unicast can be used as well"
			=20
			If the interface is not multicast-capable, then =
unicast can be
			used as well as what? Certainly not multicast, =
since the interface
			is not multicast capable...?
		=09
		o	Continuing:
	=09
				"If possible, most recent,"
		=09
			What would make it "not possible"?
			=09
   				"recently changed, or best of all, all =
known Node State TLVs"
   		=09
   			OK, so assuming that for some reason (MTU =
limitation) it is not
   			possible, does the above represent an order that =
I MUST respect,
   			or is it "take a pick from among these, =
according to your whim of
   			the day"?
=20
 				"(Section 7.2.3) SHOULD be also =
included,"
 			=09
 			SHOULD is a strong statement, especially when =
prefixed by=20
 			"if possible". That, essentially, renders it a =
MAY.
 		=09
 				"unless it is defined as undesirable for =
some reason=20
 				 by the DNCP profile
		=09
			Now it DEFINITELY is a MAY since apparently a =
profile can state
			that these TLVs MUST NOT be included -- and, I =
assume, since the
			document permits it to do so, it is possible =
without breaking the
			algorithm.
		=09
		o	And, continuing again:
	=09
				"If the
   				 DNCP profile supports dense broadcast =
link optimization
				 (Section 6.2), and if a node does not =
have the highest node
				 identifier on a link, the endpoint may =
be in a unicast mode in
				 which multicast traffic is only =
listened to.  In that mode,
				 multicast updates MUST NOT be sent."

			Really hard to parse. Is that not equivalent to =
saying:
		=09
				"If a DNCP endpoint is not configured to =
be in multicast
				  mode, then it MUST NOT send multicast =
updates"
				 =20
			?
		=09
			If it is, then say that -- if it is not, then a =
rewrite is needed,
			as that's what I manage to extract from the =
text.

=09
	5.2.  Processing of Received TLVs
		o	First paragraph reads:
	=09
				"The DNCP profile may specify criteria =
based on which particular=20
				 TLVs are ignored."
		=09
			Criteria for what? Do you perhaps mean:
		=09
				"The DNCP profile may specify which TLVs =
to process, and=20
				 which to ignore"?
		=09
			Auxiliary question, then, and related to my =
penultimate comment=20
			to 5.1, are there any constraints on that, any =
risks from ignoring
			(or not) specific TLVs to the operation of the =
network?
		=09
		o	I am also confused by the 3rd sentence in the =
first paragraph:
	=09
				"Any =E2=80=99reply=E2=80=99 mentioned =
in the steps below denotes sending of
			 	 the specified TLV(s) via unicast to the =
originator of the TLV
			 	 being processed."
			 	=20
			 This confusion is likely due to the lack of a =
"protocol overview=20
			 and functioning" description [either as its own =
section, or as part
			 of the introduction].
			=20
			 I know how trickle works. Trickle is a =
distributed consistency
			 algorithm. When an inconsistency is detected, =
then an action is
			 triggered that rectifies that inconsistency.  =
DNCP claims to be trickle based, but apparently also a sort of =
request/reply=20
			 mechanism. Combined with =
trickle-over-unicast-links, I am not sure
			 what the protocol logic actually is. Reading =
through to the end of
			 Section 5, I think that I understand the idea, =
but I am not sure.
			=20
			 And the old "when in doubt, look at the state =
machines" didn't help
			 either, there aren't any.=20
			=20
			 The point to this comment is, that the document =
immediately jumps
			 into the details -- but forgets to give the =
"10000ft view" of the
			 protocol functioning.
			=20
		o	First paragraph states two SHOULD. Would those =
not be MUST? What
			breaks if not respecting those criteria?
		=09
		o	2nd paragraph, a "valid address", that =
definition is rather unclear.
			I understand that that's something specified in =
"the profile", but
			what is the relationship to the different =
addresses discussed in
			the data model section?
		=09
			It is not clear what the parenthesis to this =
paragraph means,=20
			but that is probably again a case of the "use =
case" and "protocol
			overview" not being documented - the document so =
far has nowhere=20
			described interaction with outside processes.
	=09
		o	First bullet, but generally through these, and =
other, bullets:
	=09
			I had a really hard time deciphering this. =
First:
		=09
				"The receiver MUST reply
		         with a Network State TLV (Section 7.2.2) and a =
Node State TLV
		         (Section 7.2.3) for each node data used to =
calculate the
		         network state hash"
		   =20
		    Alright, off to find "network state hash".
		   =20
		    The terminology tells me that it is:
		   =20
		    	"a hash value which represents the current state =
of
  				 the network.  The hash function and the =
number of
                 bits used are defined in the DNCP profile.
                 Whenever a node is added, removed or updates its
                 published node data this hash value changes as
                 well. It is calculated over each reachable nodes'
                 update number concatenated with the hash value of
                 its node data. For calculation these tuples are
                 sorted in ascending order of the respective node's
                 node identifier.

		    Searching further, I find Section 5.1, but that =
simply states:
		   =20
		    	"The Trickle state for all endpoints is
			     considered inconsistent and reset if and =
only if the locally
			     calculated network state hash changes."

			Next occurence is in these bullets, and then =
just before Section 6,
		=09
				"During
			     the grace period, the nodes that were not =
marked reachable=20
			     in the most recent graph traversal MUST NOT =
be used for
			     calculation of the network state hash, be =
provided to any
			     applications that need to use the whole TLV =
graph, or be
			     provided to remote nodes."
			    =20
			Alright, now I know what I can't use for =
calculating it.
		=09
			A few occurences later, in section 7.2.2, in =
what looks like a
			section laying out the packet -- sorry, TLV -- =
format, I see for=20
			"Network State TLV":
		=09
				"This TLV contains the current locally =
calculated network state
				hash. It is calculated over each =
reachable nodes' update number
   				concatenated with the hash value of its =
node data in ascending
   				order of the respective node =
identifiers"
   			=09
			Phew. Now, it does seem a little at odds with =
the terminology. The
			terminology states something about tuples that =
are ordered. While
			those tuples are not defined (they should be), =
at least what is
			described is clear and possibly can be =
implemented. What is in 7.2.2
			is not ant cannot.
		=09
			This is an instance of a general issue that I =
have with this
			document: that it doesn't take a step back, and =
properly define
			things in a proper order, but dives into (and =
repeats) details.
		=09
		=09
		o	Also to section 5.2, for each of the cases that =
are described, could
			a conceptual description of "what this =
corresponds to" be added? For
			example:
	=09
				Upon reciept of a Node State TLV:
					If the node identifier matches =
the local node identifier and
					the TLV has a higher update =
sequence number than its current
    	     		local value, or the same update sequence number =
and a=20
    	     		different hash, the node SHOULD re-publish its =
own node data
    	     		with an update sequence number 1000 higher than =
the received
    	     		one.
		=09
		 	It's not clear why it is a "SHOULD re-publish" =
(not MUST, nor what
		 	happens if SHOULD is not followed). And it is =
not clear why 1000 ...
		=09
			[I just pick this example, but it applies to all =
processing bullets]
		=09
	o	In the same cases, it is a lot more readable (IMO) to do =
nested bullets:
=09
		o	If FOO; and either of:	=09
	 			- BAR
	 			- GNYF
	 			- BLAB
	 		Then do all of the following:
	 			- ...
	 			- ...
	 			- ...
	 	o 	Otherwise, if not-FOO, ...
	 =09
	 	That's a personal preference, though, so feel free to =
disregard this
	 	comment.
	 	=09
	 o	Section 5.3 and elsewhere, suggest replacing:
	=20
	 		"If it comes via..."
	 =09
	 	by:
	 =09
	 		"If received over ..."
	 =09
	=09
	o	Last paragraph in 5.3:
			Same comment as 3rd comment to 5.1 made above.
	=09
	o 	Section 5.4, first sentence:
			"DNCP validates the set of data within it ..."
		=09
		Should that not be:
			"A DNCP instance validates the data within its =
data sets ..."
	=09
		?

		Also, "nodes that are currently accounted for; what's =
the definition
		of "accounted for"?
	=09
	o	Section 5.4, first paragraph
		The statement:
	=09
			"therefore,
   			 unlike Time-To-Live (TTL) based solutions, it =
does not require
		     periodic re-publishing of the data by the nodes.  =
On the other
		     hand, it does require the topology to be visible to =
every node that
		     wants to be able to identify unreachable nodes and =
therefore remove
		     old, stale data."
		    =20
		which also appeared in the introduction, is copied =
verbatimly. Once
		more, the statement is a claim which is not supported, =
and that which
		follows "therefore" is not a consequence of that which =
comes before
		"therefore".
=09
	o	Section 5.4, first paragraph
=09
			"When a Neighbor TLV or a whole node is added or =
removed, the
			neighbor graph SHOULD be traversed, starting =
from the local node.
			The edges to be traversed are identified by =
looking for Neighbor
			TLVs on both nodes, that have the other node=E2=80=
=99s identifier in the
			neighbor node identifier, and local and neighbor =
endpoint
			identifiers swapped. Each node reached should be =
marked currently
			reachable."
		=09
		First comment, why SHOULD and not MUST?
	=09
		Second comment, and now you made me go =
look...."neighbor" sounds like
		"someone on the same link as me" so  the "neighbor =
graph" is really just
		a set relating "this node" and "another node which is on =
the same link
		as this node".
=09
		Yet, looking in the terminology, I see "Neighbor graph" =
defined as:
				"the undirected graph of DNCP nodes =
produced by
                 retaining only bidirectional peer relationships
                 between nodes.
	=09
		Which doesn't sound as much like a "neighbor graph" as =
it does a
		"topology graph" for the whole network.
	=09
		So, is the terminology wrong, or is the definition =
wrong?
	=09
	o	Section 5.4, 3rd paragraph
	=09
		Is it actually important that the content of that graph =
be "purged"?
		That sounds like an implementation detail -- rather, it =
sounds like
		the elements of the graph should "not be used for =
calculations and
		MAY be removed". Or, is there a specific requirement =
that I am
		missing?
	=09
	o	Section 6.1, I do not understand the parenthesis in this =
sentence:
=09
			Trickle-driven status updates (Section 5.1) =
provide a mechanism for
			handling of new peer detection (if applicable) =
on an endpoint
	=09
		Under what conditions is that applicable, and under =
which is it not?
=09
	o	Section 6.2:
=09
			"An upper bound for the number of neighbors that =
are allowed for a
   			 (particular type of) link that an endpoint runs =
on SHOULD be
   			 provided by a DNCP profile, user configuration, =
or some hardcoded
   			 default in the implementation."
   			=20
   		A couple of things to that:
   			1)	Can you explain the parenthesis? What =
type of link?
   			2)	How does "an endpoint runs on" a link?
   			3)	Why SHOULD?
   			4)	Is this specification seriously =
suggesting "some hardcoded
   				default in the implementation" as a =
SHOULD?

		[I am tempted to upgrade this to a "Major issue" simply =
because of 4) ]   	=09
	=09
	=09
		Also to 6.2, this particular optimization, do you have =
any
		quantification of its actual benefit? What should I look =
for to
		determine if this "optimization" yields a benefit or =
not? What are
		you trying to optimize? Over what link types does this =
function?
		I am dubious that it "optimizes" much, if anything, =
across an Ethernet, for example ...
	=09
	o	Section 7
		As indicated previously, having to search through the =
frame format
		diagrams for "how to calculate the value" isn't ideal.
	=09
	o	Section 7.2.3, I worry when I see something like this:
=09
			"The whole network should have roughly the same =
idea about the time
			 since origination of any particular published =
state."
		=09
		What is the definition of "roughly"?
		Is the "should" intentionally in non-caps?
		What're the consequences if not?
		[Note that trickle almost mechanically makes information =
propagate=20
		with non-trivial jitter across a network, so how do you =
ensure this?]
	=09
	o	Section 7.2.4, CUSTOM-DATA TLV.
=09
		Given the description:
			"This TLV can be used to contain anything; the =
URI used should be
			 under control of the author of that =
specification."
	=09
		It seems that (i) the description is self-contradictory: =
it cannot=20
		contain *anything* but can contain an URI?
	=09
		Secondly, how is this supposed to work, what does it =
mean [for DNCP]
		that "the URI is under control of the author"?
	=09
		Thirdly, what does "that specification" refer to?
	=09
		Fourthly, why lower-case should? Indeed, why is the =
"control" of the
		URI of any importance to DNCP?

	o	Section 9, the bullet:
=09
			"When receiving messages, what sort of messages =
are dropped, as
			specified in Section 5.2"
	=09
		Seems at odds with Section 5.2, which discusses TLV =
processing.
	=09

Nits:
   	=09
	Requirement Language:
		o	Please reflect Errata 499 for RFC2119 in the =
boilerplate
	=09
		o	The RFC2119 boilerplate could conveniently be in =
the terminology
			section, given that it is terminology.
		=09=


From nobody Tue Jun 16 14:33:29 2015
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA6F1A9173 for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 14:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 bejxq8OsVvJq for <homenet@ietfa.amsl.com>; Tue, 16 Jun 2015 14:33:26 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::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 080151A9171 for <homenet@ietf.org>; Tue, 16 Jun 2015 14:33:26 -0700 (PDT)
Received: by wgzl5 with SMTP id l5so21611111wgz.3 for <homenet@ietf.org>; Tue, 16 Jun 2015 14:33:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=q8jQZ452IMXy4/7I5iDtDi0TNwRwRfULWbNnpjKxBJE=; b=FU2luPxpv0XZ2j6ThsIR0aK/ee0NG6Ji3DNgwQ9ETqsdRXRBKNmJzXwSBf2DCaWffb BSy26bXtvlKiK1rY/XBU3NzleUmP/7GICRdWSt5czPDsjI+E2Luz4pzw5//FdtcRsFUH qe1MhOVJK26yvSkjb+dTOHMlMO3oCOQyGmdJ7zn0JHBReAJFdxSqrK1+qNRupx/DI7lM MB3kkx41U2In5Dr6pv6KPWcIseIpjTZW52JNf4DEadPsqhhMeJbqWmfmdTLp/Fltw1KL aX6t6TKtCD2I4qes2yfI+7giF7iLIAy0cx14yHpPhdWmb7lG5bwQCG5d4LidOhjxxPYo MqQg==
MIME-Version: 1.0
X-Received: by 10.180.73.10 with SMTP id h10mr11138784wiv.3.1434490404806; Tue, 16 Jun 2015 14:33:24 -0700 (PDT)
Sender: mglt.ietf@gmail.com
Received: by 10.194.11.6 with HTTP; Tue, 16 Jun 2015 14:33:24 -0700 (PDT)
In-Reply-To: <555C7193.9090307@globis.net>
References: <20150519155840.15630.1455.idtracker@ietfa.amsl.com> <2DD56D786E600F45AC6BDE7DA4E8A8C161FA2F@eusaamb107.ericsson.se> <555C7193.9090307@globis.net>
Date: Tue, 16 Jun 2015 17:33:24 -0400
X-Google-Sender-Auth: AF2BeTqeLqhLqflxkS74CiOsF6g
Message-ID: <CADZyTknpLq3skPrGmA2k4k4kbCVCf=ZOdJE7xN3grCh1TVvOfg@mail.gmail.com>
From: Daniel Migault <daniel.migault@ericsson.com>
To: Ray Hunter <v6ops@globis.net>
Content-Type: multipart/alternative; boundary=f46d043c7f1e0324870518a95362
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/AiSL3Yo50qpyZa9GqoY9fLmHW2M>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] FW: I-D Action: draft-ietf-homenet-naming-architecture-dhc-options-02.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Jun 2015 21:33:28 -0000

--f46d043c7f1e0324870518a95362
Content-Type: text/plain; charset=UTF-8

Hi Ray,

Thank you for the comments. Please see inline my response.

BR,
Daniel

I have just read through
> https://tools.ietf.org/html/draft-ietf-homenet-naming-architecture-dhc-options-02
> again
>
> Generally, it is looking pretty good.
>
> A couple of comments:
>
> 1. The use of the name "Security Field" in section 6.1 this draft is
> rather unfortunate IMHO.
>
> Humbly suggest "Supported Authentication Methods"? [to match terminology
> in
> https://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-02
> ]
>
> Plus s/Security/Supported Authentication Methods/g in other sections.
>
> I agree we may have had a better terminology. I changed Security to
Supported Authentication.



> 2. I miss more detailed discussion in Section 7.1 about when/if a server
> should accept an update of the public key record from a CPE.
>

I do not see any issue as long as the link between the DHCP Server an dthe
CPE is trusted. I have added the following text:

" A CPE may update its Public Key by sending a new value in the DHCP Public
Key Option (OPTION_PUBLIC_KEY) as this document assumes the link between
the CPE and the DHCP Server is considered authenticated and trusted."

>
> Section 9.2 notes this problem but doesn't address the problem further.
>
> Section 9.2 should also probably note:
> "The initial update of the public key between the CPE to the ISP
> infrastructure is fundamental to the security of the entire name delegation
> process. If an attacker can subvert the initial public key update, then all
> further security and encryption mechanisms may also be subverted."
>

Shouldn't section 9.2 of the draft " It is therefore RECOMMENDED to use the
> Authentication Option as specified in Section 22.11 of RFC3315"
>
> I realise that there are conflicting requirements between zeroconf and
> knowing precisely which CPE is related to which customer.
>
>
Section 9.2 mentions already mentions
"In fact, the channel MUST be secured because the CPE provides
authentication credentials. Unsecured channel may result in CPE
impersonation attacks."

and there is a reference to the RFC3315. Maybe that would be clearer to
have this sentence in the begining of the section. Is that fine for you?



> 3. Is there a need here for potentially further authentication/validation
> of the public key update option itself?
>
> A number of mechanisms come to mind for consideration:
> - no additional security
> - server enforces a strong coupling between DHCP DUID <-> CPE
> authentication and customer related data (domain names, CPE public key)
> - identifying a CPE by physical port of the inbound DHCP message and
> rejecting messages received on other physical ports
> - locking updates on the server for public key records whilst an existing
> key is valid for this DUID/ DHCP Authentication pairing
> - magic trust bootstrap via an out of band exchange leading to a nonce to
> be included with the OPTION_PUBLIC_KEY option
>
> The first four items on the list would be server specific implementation
> choices, whereas the last would require an additional DHCP option to
> transport any nonce.
>
> I agree, however, it appears to me as a whole topic in itself. I would
suggest we leave that for future work.


> regards,
> RayH
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

--f46d043c7f1e0324870518a95362
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi Ray, <br><br>Thank you for the comments. Plea=
se see inline my response.<br><br></div>BR, <br></div>Daniel<br><div><div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
I have just read through <a href=3D"https://tools.ietf.org/html/draft-ietf-=
homenet-naming-architecture-dhc-options-02" rel=3D"noreferrer" target=3D"_b=
lank">https://tools.ietf.org/html/draft-ietf-homenet-naming-architecture-dh=
c-options-02</a> again<br>
<br>
Generally, it is looking pretty good.<br>
<br>
A couple of comments:<br>
<br>
1. The use of the name &quot;Security Field&quot; in section 6.1 this draft=
 is rather unfortunate IMHO.<br>
<br>
Humbly suggest &quot;Supported Authentication Methods&quot;? [to match term=
inology in <a href=3D"https://tools.ietf.org/html/draft-ietf-homenet-front-=
end-naming-delegation-02" rel=3D"noreferrer" target=3D"_blank">https://tool=
s.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-02</a> ]<br>
<br>
Plus s/Security/Supported Authentication Methods/g in other sections.<br>
<br></blockquote><div>I agree we may have had a better terminology. I chang=
ed Security to Supported Authentication.<br><br></div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">
2. I miss more detailed discussion in Section 7.1 about when/if a server sh=
ould accept an update of the public key record from a CPE.<br></blockquote>=
<div><br></div><div>I do not see any issue as long as the link between the =
DHCP Server an dthe CPE is trusted. I have added the following text:<br><br=
>&quot; <span style=3D"font-size:14.6667px;font-family:&quot;Courier New&qu=
ot;;color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-s=
tyle:normal;font-variant:normal;text-decoration:none;vertical-align:baselin=
e" id=3D"docs-internal-guid-06a46abc-fe3d-ea57-f2d9-0098fdfc0fd3">A CPE may=
 update its Public Key by sending a new value in the </span><span style=3D"=
font-size:14.6667px;font-family:&quot;Courier New&quot;;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:normal;font-style:normal;font-varian=
t:normal;text-decoration:none;vertical-align:baseline">DHCP Public Key Opti=
on (OPTION_PUBLIC_KEY) as this document assumes the link between the CPE an=
d the DHCP Server is considered authenticated and trusted.&quot;</span></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 9.2 notes this problem but doesn&#39;t address the problem further.=
<br>
<br>
Section 9.2 should also probably note:<br>
&quot;The initial update of the public key between the CPE to the ISP infra=
structure is fundamental to the security of the entire name delegation proc=
ess. If an attacker can subvert the initial public key update, then all fur=
ther security and encryption mechanisms may also be subverted.&quot;<br>
=C2=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Shouldn&#39;t section 9.2 of the draft &quot; It is therefore RECOMMENDED t=
o use the Authentication Option as specified in Section 22.11 of RFC3315&qu=
ot;<br>
<br>
I realise that there are conflicting requirements between zeroconf and know=
ing precisely which CPE is related to which customer.<br>
<br></blockquote><div><br></div><div>Section 9.2 mentions already mentions =
<br><span style=3D"font-size:14.6667px;font-family:&quot;Courier New&quot;;=
color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-style=
:normal;font-variant:normal;text-decoration:none;vertical-align:baseline" i=
d=3D"docs-internal-guid-06a46abc-fe46-62c1-af29-6756b0fc3b0a">&quot;In fact=
, the channel MUST be secured because the CPE provides authentication crede=
ntials. Unsecured channel may result in CPE impersonation attacks.&quot;<br=
><br></span></div><div><span style=3D"font-size:14.6667px;font-family:&quot=
;Courier New&quot;;color:rgb(0,0,0);background-color:transparent;font-weigh=
t:normal;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline" id=3D"docs-internal-guid-06a46abc-fe46-62c1-af29-6756b0fc=
3b0a">and there is a reference to the RFC3315. Maybe that would be clearer =
to have this sentence in the begining of the section. Is that fine for you?=
<br></span></div><div><span style=3D"font-size:14.6667px;font-family:&quot;=
Courier New&quot;;color:rgb(0,0,0);background-color:transparent;font-weight=
:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical=
-align:baseline" id=3D"docs-internal-guid-06a46abc-fe46-62c1-af29-6756b0fc3=
b0a"><br></span></div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">
3. Is there a need here for potentially further authentication/validation o=
f the public key update option itself?<br>
<br>
A number of mechanisms come to mind for consideration:<br>
- no additional security<br>
- server enforces a strong coupling between DHCP DUID &lt;-&gt; CPE authent=
ication and customer related data (domain names, CPE public key)<br>
- identifying a CPE by physical port of the inbound DHCP message and reject=
ing messages received on other physical ports<br>
- locking updates on the server for public key records whilst an existing k=
ey is valid for this DUID/ DHCP Authentication pairing<br>
- magic trust bootstrap via an out of band exchange leading to a nonce to b=
e included with the OPTION_PUBLIC_KEY option<br>
<br>
The first four items on the list would be server specific implementation ch=
oices, whereas the last would require an additional DHCP option to transpor=
t any nonce.<br>
<br></blockquote><div>I agree, however, it appears to me as a whole topic i=
n itself. I would suggest we leave that for future work.<br>=C2=A0<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">
regards,<br>
RayH<div class=3D""><div class=3D"h5"><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</div></div></blockquote></div><br></div></div></div></div>

--f46d043c7f1e0324870518a95362--


From nobody Wed Jun 17 00:08:08 2015
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86B9C1A1A77 for <homenet@ietfa.amsl.com>; Wed, 17 Jun 2015 00:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.977
X-Spam-Level: 
X-Spam-Status: No, score=-3.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
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 amhN9AKiWBVY for <homenet@ietfa.amsl.com>; Wed, 17 Jun 2015 00:07:54 -0700 (PDT)
Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171]) (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 61BEA1A1A6D for <homenet@ietf.org>; Wed, 17 Jun 2015 00:07:54 -0700 (PDT)
Received: by igblz2 with SMTP id lz2so30607791igb.1 for <homenet@ietf.org>; Wed, 17 Jun 2015 00:07:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=X5Qc3epiNmUW3AaDlqeXcRjq6AexRHICZpUJP0q4DG0=; b=P5ig0MmuqPXkZJbsk/ia6fxhBCcw5Uobwf3xIScAYRrSzNASQxAku+JZ7GJao83I0i tFwX+nZtu/81Ntc39r9slKraUBdEFid5Cst95TI43AflNnNOQujF2etNgD9UlWaQKsoE /K84oG+uBffYzScuHZQkHO0DVM92VjYAylBwaxpo2i632yrUh5z4czprIqkU8GLobpT3 K4mHO4MDpgSmPvXwl6nHcXbnk0gyBWs+5AL5/Zw/7zdCMHmWP1uiuHc9kG16pcc3Qlca G7hMQpCeLUhUsobaEI9YXLopaa6M1rBiB6bCMhEdPBby/340p4Z3JJygvlkj1EQMMmS9 5yJA==
X-Gm-Message-State: ALoCoQm2phrYJSZPvwlp8u6yQk8xC6erIHOrs90gs7r+dVV6Nhak8Gtc6TQrjyxWGNGH4AVjjhTf
MIME-Version: 1.0
X-Received: by 10.107.137.42 with SMTP id l42mr5568411iod.60.1434524873656; Wed, 17 Jun 2015 00:07:53 -0700 (PDT)
Received: by 10.36.2.84 with HTTP; Wed, 17 Jun 2015 00:07:53 -0700 (PDT)
In-Reply-To: <BA8A243F-70C3-43C8-8B5E-B813942BA590@thomasclausen.org>
References: <BA8A243F-70C3-43C8-8B5E-B813942BA590@thomasclausen.org>
Date: Wed, 17 Jun 2015 09:07:53 +0200
Message-ID: <CAESTAVvqETcJDsYTkUX2gBosCcXEtFt_eApeTDLHx3nLe6V_ww@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: Thomas Clausen <ietf@thomasclausen.org>
Content-Type: multipart/alternative; boundary=001a113ed24c8434ce0518b1595a
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nKOibby0u3LQuzXXLDgi_Y3RgW0>
Cc: "<rtg-dir@ietf.org>" <rtg-dir@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, draft-ietf-homenet-dncp.all@tools.ietf.org, "<rtg-ads@tools.ietf.org>" <rtg-ads@tools.ietf.org>
Subject: Re: [homenet] RtgDir review: draft-ietf-homenet-dncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2015 07:08:06 -0000

--001a113ed24c8434ce0518b1595a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thomas,

Thank you for such an exhaustive and thorough review!

We will certainly ask the WG and authors to consider these in a new
revision to be published before IETF LC officially begins (though
technically that's Terry's call at this stage).

- Mark


On Tue, Jun 16, 2015 at 5:45 PM, Thomas Clausen <ietf@thomasclausen.org>
wrote:

> Hello,
>
> I have been selected as the Routing Directorate reviewer for this draft.
> The Routing Directorate seeks to review all routing or routing-related
> drafts as they pass through IETF last call and IESG review, and sometimes
> on special request. The purpose of the review is to provide assistance to
> the Routing ADs. For more information about the Routing Directorate, plea=
se
> see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
>
> Although these comments are primarily for the use of the Routing ADs, it
> would be helpful if you could consider them along with any other IETF Las=
t
> Call comments that you receive, and strive to resolve them through
> discussion or by updating the draft.
>
> Document: draft-ietf-homenet-dncp-05.txt
> Reviewer: Thomas Heide Clausen
> Review Date: June 16, 2015
> IETF LC End Date: <Reviewed during (just after - apologies) WGLC>
>
> Intended Status: Standards Track
>
> Summary:
>
>         o       I have significant concerns about this document and
> recommend that the
>                 Routing ADs discuss these issues further with the authors=
.
>
> Comments:
>
>         o       Is there any good reason why the authors have no listed
> affiliation?
>
>         o       It is somewhat contradictory that the abstract talks abou=
t
>                 "...describes a protocol" and then later "...leaves some
> details
>                  to be specified in profiles, which define actual
> implementable DNCP
>                  based protocols"
>
>                  Does that not mean, then, that this document specifies a=
n
> algorithm,
>                  a framework, and not a protocol?
>
>         o       On that, I see "DNCP protocol" several places. Expanded,
> that becomes
>                 "Dynamic Network Configuration Protocol Protocol" ...
>
>         o       In general, and despite actually knowing some of the core
> algorithms
>                 somewhat before this review, I found the document really
> tough to
>                 read, with convoluted sentences, inconsistent
> requirements-language,
>                 and a lack of introductory "here's the 1000ft view of the
> protocol,
>                 what it does, how it works, and under which conditions it
> works".
>
>         o       On that, I do not find the chosen structure of the
> document to be
>                 optimal for conveying an unambiguous protocol
> specification. For one,
>                 the same concepts are occasionally described slightly
> differently.
>                 For another, it is often hard to find the information
> needed to
>                 parse a specific mandated processing (for example). I
> provide an
>                 example of what I would suggest a better structure in the
> below.
>
>                 The goal is to provide first concepts and an overview,
> followed by a
>                 single, easy to identify place for "precise and
> unambiguous definitions
>                 of concepts", and then use those in the detailed
> expression of the
>                 protocol. Note that this is just an example, of course:
>
>                         Section "Terminology:"
>                                 The Network State Hash is a hash value
> which represents the
>                                 current state of the network, as known by
> a node.
>
>                         Section "Protocol Overview and Functioning"
>
>                                 When receiving a FOO TLV, the DNCP node
> compares the received
>                                 Network State Hash with its own Network
> State Hash. This
>                                 represents the consistency check rom
> RFC6206. If same,
>                                 then...if not, then ....
>
>                         Section "Protocol Information Bases"
>                                 For the purpose of this specification, th=
e
> Protocol
>                                 Information Bases are orgnaized as sets o=
f
> tuples ... any
>                                         implementation can chose whatever
> representation it wants.
>
>                                         The Network State Information Bas=
e
> in a DNCP node is a set
>                                         of tuples:
>                                                 (x, y, z, w)
>
>                                         where x is ..., y is ..., z is
> ..., and w is ...
>
>                         Section "How to calculate the Network State Hash"=
:
>
>                                  The network State Hash is calculated
> using the information
>                                  from the Network State Information Base,
> as follows:
>
>                                                 1. First, the tuples in
> that information base are sorted
>                                                    in ascending order
> based on ....
>
>                                                 2. Second, ....
> (concatenation)
>
>                                                 3. Third, the hash
> function from <profile> is used
>
>                                                 4. Fourth, the first n
> bits of the resulting hash value,
>                                                    are retained, witn n
> being from <profile>.
>
>                         And then, in remaining sections simply reference
> the Network
>                         State Hash, which is now ubiquitously defined in =
a
> single place.
>
>                         I am taking this example, since when reading
> section 5.3 I found
>                         myself chasing through the document, finding
> multiple slightly
>                         different definitions of "Network State Hash" --
> but beyond this
>                         example, it generally does apply to the document
> as a whole, and
>                         certainly to all of the processing and generation
> considerations in
>                         section 5.
>
>         o       As a general comment, the document would do well with a
> good editorial
>                 overhaul to bring consistency in language usage,
> consistency in 2119
>                 terminology, coherence in defined terms and their
> definition, document
>                 structure, etc.
>
> Major Issues:
>
>         o       The introduction does not read well; it contains parts of
> something that
>                 could be considered as part of an applicability statement
> (without it
>                 being called out as such, and without forming a complete
> applicability
>                 statement), and does not actually introduce the protocol.
> Reading just
>                 the introduction and the abstract, it is very obscure if
>                 this is a framework, a protocol, a building block, an
> architecture, an
>                 algorithm -- and, if either of those, what it is actually
> accomplishing,
>                 and why one would chose to use DNCP. It does, however,
> transpire that
>                 "whatever it is", it has two "modes" and that it requires
> something
>                 (presumably a routing protocol) to provide each "node"
> with a topology
>                 map.
>
>                 Suggest that a proper introduction consisting of three
> parts would be
>                 beneficial: (i) what this document is, (ii) what doing
> DNCP actually
>                 gets you, and (iii) the operating conditions under which
> the
>                 DNCP is applicable.
>
>                 On the latter point, given that you state that DNCP
> requires profiles
>                 to provide "actual implementable DNCP based protocols", i=
t
> appears
>                 important to understand what the limits for "what a
> profile can give
>                 you" are.
>
>                 I am calling this out as a major issue, since I believe
> that it is
>                 not just editorial, but is a matter of scoping this
> document correctly,
>                 and in particular not falling into the trap of "claiming
> applicability
>                 where it's not".
>
>         o       The document, in my understanding, defines an exchange
> format with
>                 limited ability to evolve, as simply "a steam of TLVs".
>
>                 As long as there's never a need to evolve the TLV format
> itself, and
>                 as long as you do not run out of TLV types, that's not
> going to be
>                 a problem. The doc sets aside a 16bit TLV type space,
> that's reasonable
>                 enough, but I worry if eventually a DNCPv2 will need to
> evolve the
>                 format. One purely hypothetical example could be if a
> "sequence number"
>                 would be needed in each DNCP message to detect "link
> success rates", or
>                 something of that sort.
>
>                 I do not have an actual example in mind -- and that's
> exactly the point:
>                 to be evolutive for the unknown future and (at the very
> least) be able
>                 to discriminate between "old" and "new".
>
>                 A discussion could be had if a "version number" in each
> TLV would do,
>                 or if a concept of "protocol message with a version
> number" is
>                 preferential. I do not believe, however, that "no version
> number" is
>                 viable.
>
>         o       Noting that the "overhearing n reduncant transmissions" i=
s
> a key
>                 retransmission suppression mechanism in Trickle, and that
> this
>                 seems to assume broad/multicast, using unicast seems to
> contradict
>                 the statement of "consists of Trickle", at least in the
> way the
>                 algorithm is defined in RFC6206. Note: it's fine to use a=
n
> algorithm
>                 outside of its initial scope, but it should be with the
> caveat of
>                 "which of the characteristics still hold, and which do no=
t"
>
>         o       DNCP claims to be trickle based, yet supports unicast. It
> also
>                 (apparently) is a request/reply protocol.  It doesn't hav=
e
> messages.
>                 This document needs a good, and pedagogical, "protocol
> overview and
>                 functioning" section somewhere: one needs to get through
> the end of
>                 Section 5 before having even a vague idea of how DNCP
> works.
>
>         o       The use of normative language is not as tight as could be
> desired.
>                 For example, a number of SHOULDs seem to really ought to
> be "MAYs" since
>                 not following the SHOULD won't break the algorithm. It
> would be good
>                 to walk through the document and take a careful look at
> these to
>                 either MUST/MAY the SHOULDs, or to qualify the SHOULDs
> remaining.
>
>         o       I am going to go out on a limb here, and say that "the
> protocol is
>                 underspecified". That's a deliberately provocative
> statement, but it
>                 was honestly how I felt upon having completed the review.
>
>                 The document does not help the reader get an intuitive
> understanding
>                 of the protocol functioning, but jumps right into minute
> details --
>                 requiring the reader to "build up her or his own model of
> how DNCP
>                 works". On having read the document a few times, I think
> that I
>                 understand it -- but there's nothing permitting me to
> verify my
>                 understanding, and thereby I'd not feel confident to be
> able to
>                 provide an interoperable and independent implementation.
> I've given
>                 some comments in the "Comments" section as to what I thin=
k
> would be
>                 viable ways to improve this point.
>
>          o      Section 5.3, penultimate paragraph:
>
>                         "If keep-alives specified in Section 6.1 are NOT
> sent by the peer
>                      (either the DNCP profile does not specify the use of
> keep-alives or
>                      the particular peer chooses not to send keep-alives)=
,
> some other
>                      means MUST be employed to ensure its presence.  When
> the peer is no
>                      longer present, the Neighbor TLV and the local DNCP
> peer state MUST
>                      be removed."
>
>                 "...some other means MUST be employed to ensure its
> presence." --
>                 followed by more MUST verage when a peer disappears...I a=
m
> not sure that
>                 that's conductive to interoperable implementations.
>
>                 Two implementatons may chose different "means" and then
> turn off keep-
>                 alives - and be non-interoperable.
>
>                 For interoperability, we need:
>
>                                 o       A mandatory to implement
> mechanism, that always is
>                                         present, but can be complemented
> by another "means", or
>
>                                 o       A mandatory to implement
> mechanism, which by way of a
>                                         specified negotiation mechanism
> can be turned off between
>                                         two peers, to allow them to use
> another "means".
>
>                 If you argument is "...this will be specified in the
> profile", then
>                 you still should provide the two above in this document,
> with the note
>                 that "...and a profile may specify which from among these
> MUST be
>                 used in a given deployment"
>
>         o       Section 8:
>                 Interesting; I am not a security expert, but I am very
> curious to
>                 see the SEC-DIR review of this document. That said,
> section 8.3.1
>                 contains normative verbage:
>
>                         "A node MUST be trusted for participating in the
> DNCP network if and
>                         only if..."
>
>                 Which I think needs a qualifier of the "If the certificat=
e
> based
>                 trust model is used, then a node must be trusted for ....=
"
>
>                 Same goes for the subsequent SHOULD - it really reads
> as-if this
>                 certificate based mechanism initially was intended as MTI=
,
> but then
>                 was backed away from subsequently without a complete
> cleanup of the
>                 text?
>
>                 I do actually question the value of having a laundry-list
> of trust
>                 management methods, and for one of those (certs) a
> laundry-list
>                 of all sorts of trust relationship establishment methods,
> in this
>                 document; this in no small part as the lists are
> explicitly indicated
>                 as "non-exhaustive" and that none are listed as "mandator=
y
> to
>                 implement". Was any thought given to factoring this into =
a
> seperate
>                 document, and focusing in this document on one,
> mandatory-to-implement,
>                 security mechanism?
>
> Minor Issues:
>
>         Introduction:
>                 o       1st paragraph: "reachable nodes"; two things:
>
>                                 -       I always have a problem with the
> term "node"; it is often
>                                         used as a shorthand for "routers
> and hosts, both". I was
>                                         given to understand that homenet
> specifically did not want
>                                         to consider host changes?
>
>                                 -       "Reachable" - does that mean
> something as in "radio range",
>                                         does it mean "on the same link",
> does it mean within a
>                                         specific (DNCP?) domain, or does
> it mean simply "on the
>                                         Internet somewhere"?
>
>                 o       2nd paragraph: "nodes that are currently accounte=
d
> for":
>                                 -       What does that mean?
>
>                                 -       Also, the conclusion "Therefore
> unlike Time-To-Live (TTL)
>                                         based solutions, it does not
> require periodic re-publishing
>                                         of the data by the nodes" does
> actually not follow from
>                                         the previous sentence in that
> paragraph.
>
>                                 -       I actually do not think that the
> introduction describes
>                                         what DNCP does, and so the
> comparison to TTL-based
>                                         solutions is rather hard to get
> here.
>
>                                 -       Continuing:
>
>                                                 "On the other hand, it
> does require the topology
>                                                 to be visible to every
> node that wants to be able to
>                                                 identify unreachable node=
s
> and therefore remove old,
>                                                 stale data."
>
>                                         This reads a lot more like an
> applicability statement than
>                                         an introduction; the take-away
> when reading this is:
>
>                                                 "Each node must have
> something that maintains
>                                                  a topology map of the
> entire network, such as
>                                                  a (LS) routing protocol,
> for DNCP to function"
>
>                                         Is that actually the intent here?
>
>                                 -       "DNCP is most suitable for data
> that changes only gradually"
>                                         How is the reader to interpret
> "gradually"? Do you mean
>                                         "infrequently", or do you really
> mean "gradualy"?
>
>                 o Last paragraph:
>                                 "DNCP has relatively few requirements for
> the underlying
>                                  transport; it requires some way of
> transmitting either unicast
>                                  datagram or stream data to a peer"
>
>                         This is a bit of a forward comment, but we now
> have "nodes
>                         that are accounted for" and "peers". I see neithe=
r
> defined in
>                         the terminology section.
>
>                                 "and, if used in multicast mode, a way of
>                                  sending multicast datagrams."
>
>                         This is the first mention of two "modes" of this
> protocol. This
>                         loops back to an earlier comment, that the
> introduction actually
>                         does not introduce the protocol, but rather is an
> incomplete
>                         applicability statement.
>
>                                 "If security is desired and one of the
>                                  built-in security methods is to be used,
> support for some
>                                 TLS-derived transport scheme - such as TL=
S
> [RFC5246] on top of
>                                 TCP or DTLS [RFC6347] on top of UDP - is
> also required."
>
>                         I am not pretending to be a security expert, but
> "some
>                         TLS-derived...such as ... on top of TCP or
> DTLS..." (i) does not
>                         sound like it could lead to interoperable
> implementations, and (ii)
>                         does not sound sufficiently tight as a MTI
> security mechanism to
>                         pass security reviews. Again, I am no security
> expert, but perhaps
>                         getting one looped in early would be advicable?
>
>         Terminology:
>                 o       Suggest adding "In this document ..." somewhere t=
o
> this text:
>
>                                 "For readability, any DNCP profile specif=
ic
>                                  parameters with a profile-specific fixed
> value are
>                                  prefixed with DNCP_."
>
>                 o       DNCP network: I read this twice, and came away
> with two different
>                         understandings, perhaps you can clarify which it
> is:
>
>                                 o       A set of nodes running DNCP,
> within the same domain, and
>                                         for which a path betwen any two
> DNCP nodes includes only
>                                         other DNCP nodes; i.e., a DNCP
> network forms a connected
>                                         component with only other DNCP
> nodes.
>
>                                 o       A set of nodes running DNCP. They
> may be anywhere on the
>                                         Internet, they are part of the
> same DNCP network as long
>                                         as they (through other means) hav=
e
> learned of each others
>                                         addresses.
>
>                         In the former, that'd be (for example) a
> deployment within my
>                         home -- in the latter, it could be a node in my
> home and a node in
>                         your home forming a DNCP network.
>
>                         The text is not quite clear on this point.
>
>                 o       Link: a point of clarification here. In "DNCP
> network", there was
>                         talk about "unidirectional links" and
> "bidirectional links"; in
>                         "Link" the definition is somewhat vague "directly
> connected" and
>                         "can communicate". Could something like "without
> decrementing TTL/
>                         hop-count" be added, and could a statement on
> bidirectionality
>                         (IOW, that this is just an IP link) be added?
>
>
>                 o       "Interface" is overloading the term "port" (IP
> port) which can be
>                         confusing
>
>                 o       "Endpoint" - The definition "locally configured
> use of DNCP" is not
>                         clear -- are you really not talking about a DNCP
> process?
>
>                         I am not sure that it is clear how a DNCP process
> can be "attached
>                         to  ... a specific remote unicast address, or to =
a
> range of unicast
>                         addresses that are allowed to contact"
>
>                         I can see how a DNCP process can be configured to
> allow connections
>                         from a specific range of addresses, or can be
> configured to connect
>                         to a specific remote unicast address. Is that wha=
t
> you mean instead?
>
>
>                 o       "Peer" - states that two peers "communicate
> directly". For link,
>                         the definition is "directly connected nodes can
> communicate".
>                         Would it then not be easier to say "a DNCP node o=
n
> the same link
>                         as ..." ?
>
>                 o       "Node state"
>                                 "The hash function and the number of bits
> used are defined
>                                  in the DNCP profile."
>
>                         Suggest:
>                                 "The hash function and the length of the
> hash value are defined
>                                  in the DNCP profile."
>
>
>                 o       "Network state hash" - same comment as for node
> state (above)
>
>         Data model:
>                 o       "Latest update sequence number"
>                         This may just be my personal taste, but does it
> hurt to mandate
>                         a specific way of doing the looping comparison?
> The reason I
>                         suggest this is, that it's one of those things
> where creativity
>                         in an implementation seems to simply be an
> invitation for bugs,
>                         and for little gain
>
>                 o       "Relative time delta"
>                         Document talks about "a 32 bit number on the wire=
"
> -- does that
>                         mean that wireless links are excluded?
>
>                 o       Related to terminology, there seems to be some
> fuzzyness around
>                         node and endpoint. For example, in data model one
> of the things that
>                         a DNCP node may have is:
>
>                                 "Unicast address: the DNCP node it should
> connect with"
>
>                         Does that mean *any* DNCP process (i.e., *any*
> endpoint) at that
>                         address, or a *specific* DNCP process at that
> address?
>
>                         The same, but inverse, for "Range of addresses:
> the DNCP nodes that
>                         are allowed to connect" - is this "any DHCP
> process (i.e., *any*
>                         endpoint) on any of these addresses?
>
>                         Following, the same section reads:
>
>                                 "For each remote (peer, endpoint) pair
> detected on a local
>                                 endpoint, a DNCP node has..."
>
>                         the following text indicating that there's some
> sort of distinction
>                         between which endpoint.
>
>                         This whole thing needs some clarification.
>
>         Operation
>
>                 o       First a generic comment that Trickle itself has
> some operating
>                         conditions which scopes its applicability, and it
> would behove
>                         this document to, in its own applicability
> statement, call out
>                         those.
>
>                 o       On the same token, while the use of Trickle in an
> unicast fashion
>                         is possible, I wonder if (in general) unicast use
> is advicable. I
>                         appreciate that some links are point-to-point and
> so a broadcast
>                         across it becomes an unicast -- but, does that
> necessitate being
>                         called out?
>
>                         IF the reason for this "because we can use TCP",
> then be explicit
>                         about this - but, also, that you're then not
> exactly using Trickle
>                         where and how it was intended. I wonder if you
> could be explicit
>                         as to what consequences this "alternate use of
> Trickle" have? It
>                         seems that the use of unicast is directly
> contradicting the main
>                         operating consideration of Trickle?
>
>                 o       2nd paragraph states:
>
>                                 "the multicast transport does not have to
> be particularly
>                                  secure"
>
>                         What is the definition of "not have to be
> particularly secure"?
>                         Is cleartext OK? Authentication? Encryption?
>                         Should I do something more?
>
>         5.1 Trickle-driven status updates
>                 o       First paragraph:
>
>                                 "Multicast MUST be employed on a
> multicast-capable interface;
>                                  otherwise, unicast can be used as well"
>
>                         If the interface is not multicast-capable, then
> unicast can be
>                         used as well as what? Certainly not multicast,
> since the interface
>                         is not multicast capable...?
>
>                 o       Continuing:
>
>                                 "If possible, most recent,"
>
>                         What would make it "not possible"?
>
>                                 "recently changed, or best of all, all
> known Node State TLVs"
>
>                         OK, so assuming that for some reason (MTU
> limitation) it is not
>                         possible, does the above represent an order that =
I
> MUST respect,
>                         or is it "take a pick from among these, according
> to your whim of
>                         the day"?
>
>                                 "(Section 7.2.3) SHOULD be also included,=
"
>
>                         SHOULD is a strong statement, especially when
> prefixed by
>                         "if possible". That, essentially, renders it a MA=
Y.
>
>                                 "unless it is defined as undesirable for
> some reason
>                                  by the DNCP profile
>
>                         Now it DEFINITELY is a MAY since apparently a
> profile can state
>                         that these TLVs MUST NOT be included -- and, I
> assume, since the
>                         document permits it to do so, it is possible
> without breaking the
>                         algorithm.
>
>                 o       And, continuing again:
>
>                                 "If the
>                                  DNCP profile supports dense broadcast
> link optimization
>                                  (Section 6.2), and if a node does not
> have the highest node
>                                  identifier on a link, the endpoint may b=
e
> in a unicast mode in
>                                  which multicast traffic is only listened
> to.  In that mode,
>                                  multicast updates MUST NOT be sent."
>
>                         Really hard to parse. Is that not equivalent to
> saying:
>
>                                 "If a DNCP endpoint is not configured to
> be in multicast
>                                   mode, then it MUST NOT send multicast
> updates"
>
>                         ?
>
>                         If it is, then say that -- if it is not, then a
> rewrite is needed,
>                         as that's what I manage to extract from the text.
>
>
>         5.2.  Processing of Received TLVs
>                 o       First paragraph reads:
>
>                                 "The DNCP profile may specify criteria
> based on which particular
>                                  TLVs are ignored."
>
>                         Criteria for what? Do you perhaps mean:
>
>                                 "The DNCP profile may specify which TLVs
> to process, and
>                                  which to ignore"?
>
>                         Auxiliary question, then, and related to my
> penultimate comment
>                         to 5.1, are there any constraints on that, any
> risks from ignoring
>                         (or not) specific TLVs to the operation of the
> network?
>
>                 o       I am also confused by the 3rd sentence in the
> first paragraph:
>
>                                 "Any =E2=80=99reply=E2=80=99 mentioned in=
 the steps below
> denotes sending of
>                                  the specified TLV(s) via unicast to the
> originator of the TLV
>                                  being processed."
>
>                          This confusion is likely due to the lack of a
> "protocol overview
>                          and functioning" description [either as its own
> section, or as part
>                          of the introduction].
>
>                          I know how trickle works. Trickle is a
> distributed consistency
>                          algorithm. When an inconsistency is detected,
> then an action is
>                          triggered that rectifies that inconsistency.
> DNCP claims to be trickle based, but apparently also a sort of request/re=
ply
>                          mechanism. Combined with
> trickle-over-unicast-links, I am not sure
>                          what the protocol logic actually is. Reading
> through to the end of
>                          Section 5, I think that I understand the idea,
> but I am not sure.
>
>                          And the old "when in doubt, look at the state
> machines" didn't help
>                          either, there aren't any.
>
>                          The point to this comment is, that the document
> immediately jumps
>                          into the details -- but forgets to give the
> "10000ft view" of the
>                          protocol functioning.
>
>                 o       First paragraph states two SHOULD. Would those no=
t
> be MUST? What
>                         breaks if not respecting those criteria?
>
>                 o       2nd paragraph, a "valid address", that definition
> is rather unclear.
>                         I understand that that's something specified in
> "the profile", but
>                         what is the relationship to the different
> addresses discussed in
>                         the data model section?
>
>                         It is not clear what the parenthesis to this
> paragraph means,
>                         but that is probably again a case of the "use
> case" and "protocol
>                         overview" not being documented - the document so
> far has nowhere
>                         described interaction with outside processes.
>
>                 o       First bullet, but generally through these, and
> other, bullets:
>
>                         I had a really hard time deciphering this. First:
>
>                                 "The receiver MUST reply
>                          with a Network State TLV (Section 7.2.2) and a
> Node State TLV
>                          (Section 7.2.3) for each node data used to
> calculate the
>                          network state hash"
>
>                     Alright, off to find "network state hash".
>
>                     The terminology tells me that it is:
>
>                         "a hash value which represents the current state =
of
>                                  the network.  The hash function and the
> number of
>                  bits used are defined in the DNCP profile.
>                  Whenever a node is added, removed or updates its
>                  published node data this hash value changes as
>                  well. It is calculated over each reachable nodes'
>                  update number concatenated with the hash value of
>                  its node data. For calculation these tuples are
>                  sorted in ascending order of the respective node's
>                  node identifier.
>
>                     Searching further, I find Section 5.1, but that simpl=
y
> states:
>
>                         "The Trickle state for all endpoints is
>                              considered inconsistent and reset if and onl=
y
> if the locally
>                              calculated network state hash changes."
>
>                         Next occurence is in these bullets, and then just
> before Section 6,
>
>                                 "During
>                              the grace period, the nodes that were not
> marked reachable
>                              in the most recent graph traversal MUST NOT
> be used for
>                              calculation of the network state hash, be
> provided to any
>                              applications that need to use the whole TLV
> graph, or be
>                              provided to remote nodes."
>
>                         Alright, now I know what I can't use for
> calculating it.
>
>                         A few occurences later, in section 7.2.2, in what
> looks like a
>                         section laying out the packet -- sorry, TLV --
> format, I see for
>                         "Network State TLV":
>
>                                 "This TLV contains the current locally
> calculated network state
>                                 hash. It is calculated over each reachabl=
e
> nodes' update number
>                                 concatenated with the hash value of its
> node data in ascending
>                                 order of the respective node identifiers"
>
>                         Phew. Now, it does seem a little at odds with the
> terminology. The
>                         terminology states something about tuples that ar=
e
> ordered. While
>                         those tuples are not defined (they should be), at
> least what is
>                         described is clear and possibly can be
> implemented. What is in 7.2.2
>                         is not ant cannot.
>
>                         This is an instance of a general issue that I hav=
e
> with this
>                         document: that it doesn't take a step back, and
> properly define
>                         things in a proper order, but dives into (and
> repeats) details.
>
>
>                 o       Also to section 5.2, for each of the cases that
> are described, could
>                         a conceptual description of "what this correspond=
s
> to" be added? For
>                         example:
>
>                                 Upon reciept of a Node State TLV:
>                                         If the node identifier matches th=
e
> local node identifier and
>                                         the TLV has a higher update
> sequence number than its current
>                         local value, or the same update sequence number
> and a
>                         different hash, the node SHOULD re-publish its ow=
n
> node data
>                         with an update sequence number 1000 higher than
> the received
>                         one.
>
>                         It's not clear why it is a "SHOULD re-publish"
> (not MUST, nor what
>                         happens if SHOULD is not followed). And it is not
> clear why 1000 ...
>
>                         [I just pick this example, but it applies to all
> processing bullets]
>
>         o       In the same cases, it is a lot more readable (IMO) to do
> nested bullets:
>
>                 o       If FOO; and either of:
>                                 - BAR
>                                 - GNYF
>                                 - BLAB
>                         Then do all of the following:
>                                 - ...
>                                 - ...
>                                 - ...
>                 o       Otherwise, if not-FOO, ...
>
>                 That's a personal preference, though, so feel free to
> disregard this
>                 comment.
>
>          o      Section 5.3 and elsewhere, suggest replacing:
>
>                         "If it comes via..."
>
>                 by:
>
>                         "If received over ..."
>
>
>         o       Last paragraph in 5.3:
>                         Same comment as 3rd comment to 5.1 made above.
>
>         o       Section 5.4, first sentence:
>                         "DNCP validates the set of data within it ..."
>
>                 Should that not be:
>                         "A DNCP instance validates the data within its
> data sets ..."
>
>                 ?
>
>                 Also, "nodes that are currently accounted for; what's the
> definition
>                 of "accounted for"?
>
>         o       Section 5.4, first paragraph
>                 The statement:
>
>                         "therefore,
>                          unlike Time-To-Live (TTL) based solutions, it
> does not require
>                      periodic re-publishing of the data by the nodes.  On
> the other
>                      hand, it does require the topology to be visible to
> every node that
>                      wants to be able to identify unreachable nodes and
> therefore remove
>                      old, stale data."
>
>                 which also appeared in the introduction, is copied
> verbatimly. Once
>                 more, the statement is a claim which is not supported, an=
d
> that which
>                 follows "therefore" is not a consequence of that which
> comes before
>                 "therefore".
>
>         o       Section 5.4, first paragraph
>
>                         "When a Neighbor TLV or a whole node is added or
> removed, the
>                         neighbor graph SHOULD be traversed, starting from
> the local node.
>                         The edges to be traversed are identified by
> looking for Neighbor
>                         TLVs on both nodes, that have the other node=E2=
=80=99s
> identifier in the
>                         neighbor node identifier, and local and neighbor
> endpoint
>                         identifiers swapped. Each node reached should be
> marked currently
>                         reachable."
>
>                 First comment, why SHOULD and not MUST?
>
>                 Second comment, and now you made me go look...."neighbor"
> sounds like
>                 "someone on the same link as me" so  the "neighbor graph"
> is really just
>                 a set relating "this node" and "another node which is on
> the same link
>                 as this node".
>
>                 Yet, looking in the terminology, I see "Neighbor graph"
> defined as:
>                                 "the undirected graph of DNCP nodes
> produced by
>                  retaining only bidirectional peer relationships
>                  between nodes.
>
>                 Which doesn't sound as much like a "neighbor graph" as it
> does a
>                 "topology graph" for the whole network.
>
>                 So, is the terminology wrong, or is the definition wrong?
>
>         o       Section 5.4, 3rd paragraph
>
>                 Is it actually important that the content of that graph b=
e
> "purged"?
>                 That sounds like an implementation detail -- rather, it
> sounds like
>                 the elements of the graph should "not be used for
> calculations and
>                 MAY be removed". Or, is there a specific requirement that
> I am
>                 missing?
>
>         o       Section 6.1, I do not understand the parenthesis in this
> sentence:
>
>                         Trickle-driven status updates (Section 5.1)
> provide a mechanism for
>                         handling of new peer detection (if applicable) on
> an endpoint
>
>                 Under what conditions is that applicable, and under which
> is it not?
>
>         o       Section 6.2:
>
>                         "An upper bound for the number of neighbors that
> are allowed for a
>                          (particular type of) link that an endpoint runs
> on SHOULD be
>                          provided by a DNCP profile, user configuration,
> or some hardcoded
>                          default in the implementation."
>
>                 A couple of things to that:
>                         1)      Can you explain the parenthesis? What typ=
e
> of link?
>                         2)      How does "an endpoint runs on" a link?
>                         3)      Why SHOULD?
>                         4)      Is this specification seriously suggestin=
g
> "some hardcoded
>                                 default in the implementation" as a SHOUL=
D?
>
>                 [I am tempted to upgrade this to a "Major issue" simply
> because of 4) ]
>
>
>                 Also to 6.2, this particular optimization, do you have an=
y
>                 quantification of its actual benefit? What should I look
> for to
>                 determine if this "optimization" yields a benefit or not?
> What are
>                 you trying to optimize? Over what link types does this
> function?
>                 I am dubious that it "optimizes" much, if anything, acros=
s
> an Ethernet, for example ...
>
>         o       Section 7
>                 As indicated previously, having to search through the
> frame format
>                 diagrams for "how to calculate the value" isn't ideal.
>
>         o       Section 7.2.3, I worry when I see something like this:
>
>                         "The whole network should have roughly the same
> idea about the time
>                          since origination of any particular published
> state."
>
>                 What is the definition of "roughly"?
>                 Is the "should" intentionally in non-caps?
>                 What're the consequences if not?
>                 [Note that trickle almost mechanically makes information
> propagate
>                 with non-trivial jitter across a network, so how do you
> ensure this?]
>
>         o       Section 7.2.4, CUSTOM-DATA TLV.
>
>                 Given the description:
>                         "This TLV can be used to contain anything; the UR=
I
> used should be
>                          under control of the author of that
> specification."
>
>                 It seems that (i) the description is self-contradictory:
> it cannot
>                 contain *anything* but can contain an URI?
>
>                 Secondly, how is this supposed to work, what does it mean
> [for DNCP]
>                 that "the URI is under control of the author"?
>
>                 Thirdly, what does "that specification" refer to?
>
>                 Fourthly, why lower-case should? Indeed, why is the
> "control" of the
>                 URI of any importance to DNCP?
>
>         o       Section 9, the bullet:
>
>                         "When receiving messages, what sort of messages
> are dropped, as
>                         specified in Section 5.2"
>
>                 Seems at odds with Section 5.2, which discusses TLV
> processing.
>
>
> Nits:
>
>         Requirement Language:
>                 o       Please reflect Errata 499 for RFC2119 in the
> boilerplate
>
>                 o       The RFC2119 boilerplate could conveniently be in
> the terminology
>                         section, given that it is terminology.
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

--001a113ed24c8434ce0518b1595a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PGRpdiBkaXI9Imx0ciI+PGRpdj48YnI+PC9kaXY+PGRpdj5UaG9tYXMsPC9kaXY+PGRpdj48YnI+
PC9kaXY+PGRpdj5UaGFuayB5b3UgZm9yIHN1Y2ggYW4gZXhoYXVzdGl2ZSBhbmQgdGhvcm91Z2gg
cmV2aWV3IcKgPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5XZSB3aWxsIGNlcnRhaW5seSBhc2sg
dGhlIFdHIGFuZCBhdXRob3JzIHRvIGNvbnNpZGVyIHRoZXNlIGluIGEgbmV3IHJldmlzaW9uIHRv
IGJlIHB1Ymxpc2hlZCBiZWZvcmUgSUVURiBMQyBvZmZpY2lhbGx5IGJlZ2lucyAodGhvdWdoIHRl
Y2huaWNhbGx5IHRoYXQmIzM5O3MgVGVycnkmIzM5O3MgY2FsbCBhdCB0aGlzIHN0YWdlKS7CoDwv
ZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+LSBNYXJrPC9kaXY+PGJyPjxkaXYgY2xhc3M9ImdtYWls
X2V4dHJhIj48YnI+PGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPk9uIFR1ZSwgSnVuIDE2LCAyMDE1
IGF0IDU6NDUgUE0sIFRob21hcyBDbGF1c2VuIDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0i
bWFpbHRvOmlldGZAdGhvbWFzY2xhdXNlbi5vcmciIHRhcmdldD0iX2JsYW5rIj5pZXRmQHRob21h
c2NsYXVzZW4ub3JnPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj48YmxvY2txdW90ZSBjbGFzcz0i
Z21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2Nj
YyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij5IZWxsbyw8YnI+DQo8YnI+DQpJIGhhdmUgYmVlbiBz
ZWxlY3RlZCBhcyB0aGUgUm91dGluZyBEaXJlY3RvcmF0ZSByZXZpZXdlciBmb3IgdGhpcyBkcmFm
dC4gVGhlIFJvdXRpbmcgRGlyZWN0b3JhdGUgc2Vla3MgdG8gcmV2aWV3IGFsbCByb3V0aW5nIG9y
IHJvdXRpbmctcmVsYXRlZCBkcmFmdHMgYXMgdGhleSBwYXNzIHRocm91Z2ggSUVURiBsYXN0IGNh
bGwgYW5kIElFU0cgcmV2aWV3LCBhbmQgc29tZXRpbWVzIG9uIHNwZWNpYWwgcmVxdWVzdC4gVGhl
IHB1cnBvc2Ugb2YgdGhlIHJldmlldyBpcyB0byBwcm92aWRlIGFzc2lzdGFuY2UgdG8gdGhlIFJv
dXRpbmcgQURzLiBGb3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCB0aGUgUm91dGluZyBEaXJlY3Rv
cmF0ZSwgcGxlYXNlIHNlZSA8YSBocmVmPSJodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy9hcmVh
L3J0Zy90cmFjL3dpa2kvUnRnRGlyIiByZWw9Im5vcmVmZXJyZXIiIHRhcmdldD0iX2JsYW5rIj5o
dHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy9hcmVhL3J0Zy90cmFjL3dpa2kvUnRnRGlyPC9hPjxi
cj4NCjxicj4NCkFsdGhvdWdoIHRoZXNlIGNvbW1lbnRzIGFyZSBwcmltYXJpbHkgZm9yIHRoZSB1
c2Ugb2YgdGhlIFJvdXRpbmcgQURzLCBpdCB3b3VsZCBiZSBoZWxwZnVsIGlmIHlvdSBjb3VsZCBj
b25zaWRlciB0aGVtIGFsb25nIHdpdGggYW55IG90aGVyIElFVEYgTGFzdCBDYWxsIGNvbW1lbnRz
IHRoYXQgeW91IHJlY2VpdmUsIGFuZCBzdHJpdmUgdG8gcmVzb2x2ZSB0aGVtIHRocm91Z2ggZGlz
Y3Vzc2lvbiBvciBieSB1cGRhdGluZyB0aGUgZHJhZnQuPGJyPg0KPGJyPg0KRG9jdW1lbnQ6IGRy
YWZ0LWlldGYtaG9tZW5ldC1kbmNwLTA1LnR4dDxicj4NClJldmlld2VyOiBUaG9tYXMgSGVpZGUg
Q2xhdXNlbjxicj4NClJldmlldyBEYXRlOiBKdW5lIDE2LCAyMDE1PGJyPg0KSUVURiBMQyBFbmQg
RGF0ZTogJmx0O1Jldmlld2VkIGR1cmluZyAoanVzdCBhZnRlciAtIGFwb2xvZ2llcykgV0dMQyZn
dDs8YnI+DQo8YnI+DQpJbnRlbmRlZCBTdGF0dXM6IFN0YW5kYXJkcyBUcmFjazxicj4NCjxicj4N
ClN1bW1hcnk6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgSSBoYXZlIHNpZ25p
ZmljYW50IGNvbmNlcm5zIGFib3V0IHRoaXMgZG9jdW1lbnQgYW5kIHJlY29tbWVuZCB0aGF0IHRo
ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFJvdXRpbmcgQURzIGRpc2N1c3MgdGhlc2Ug
aXNzdWVzIGZ1cnRoZXIgd2l0aCB0aGUgYXV0aG9ycy48YnI+DQo8YnI+DQpDb21tZW50czo8YnI+
DQo8YnI+DQrCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBJcyB0aGVyZSBhbnkgZ29vZCByZWFzb24g
d2h5IHRoZSBhdXRob3JzIGhhdmUgbm8gbGlzdGVkIGFmZmlsaWF0aW9uPzxicj4NCjxicj4NCsKg
IMKgIMKgIMKgIG/CoCDCoCDCoCDCoEl0IGlzIHNvbWV3aGF0IGNvbnRyYWRpY3RvcnkgdGhhdCB0
aGUgYWJzdHJhY3QgdGFsa3MgYWJvdXQ8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVv
dDsuLi5kZXNjcmliZXMgYSBwcm90b2NvbCZxdW90OyBhbmQgdGhlbiBsYXRlciAmcXVvdDsuLi5s
ZWF2ZXMgc29tZSBkZXRhaWxzPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqB0byBiZSBz
cGVjaWZpZWQgaW4gcHJvZmlsZXMsIHdoaWNoIGRlZmluZSBhY3R1YWwgaW1wbGVtZW50YWJsZSBE
TkNQPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBiYXNlZCBwcm90b2NvbHMmcXVvdDs8
YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoERvZXMgdGhhdCBub3QgbWVhbiwg
dGhlbiwgdGhhdCB0aGlzIGRvY3VtZW50IHNwZWNpZmllcyBhbiBhbGdvcml0aG0sPGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBhIGZyYW1ld29yaywgYW5kIG5vdCBhIHByb3RvY29sPzxi
cj4NCjxicj4NCsKgIMKgIMKgIMKgIG/CoCDCoCDCoCDCoE9uIHRoYXQsIEkgc2VlICZxdW90O0RO
Q1AgcHJvdG9jb2wmcXVvdDsgc2V2ZXJhbCBwbGFjZXMuIEV4cGFuZGVkLCB0aGF0IGJlY29tZXM8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtEeW5hbWljIE5ldHdvcmsgQ29uZmln
dXJhdGlvbiBQcm90b2NvbCBQcm90b2NvbCZxdW90OyAuLi48YnI+DQo8YnI+DQrCoCDCoCDCoCDC
oCBvwqAgwqAgwqAgwqBJbiBnZW5lcmFsLCBhbmQgZGVzcGl0ZSBhY3R1YWxseSBrbm93aW5nIHNv
bWUgb2YgdGhlIGNvcmUgYWxnb3JpdGhtczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHNv
bWV3aGF0IGJlZm9yZSB0aGlzIHJldmlldywgSSBmb3VuZCB0aGUgZG9jdW1lbnQgcmVhbGx5IHRv
dWdoIHRvPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgcmVhZCwgd2l0aCBjb252b2x1dGVk
IHNlbnRlbmNlcywgaW5jb25zaXN0ZW50IHJlcXVpcmVtZW50cy1sYW5ndWFnZSw8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCBhbmQgYSBsYWNrIG9mIGludHJvZHVjdG9yeSAmcXVvdDtoZXJl
JiMzOTtzIHRoZSAxMDAwZnQgdmlldyBvZiB0aGUgcHJvdG9jb2wsPGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgd2hhdCBpdCBkb2VzLCBob3cgaXQgd29ya3MsIGFuZCB1bmRlciB3aGljaCBj
b25kaXRpb25zIGl0IHdvcmtzJnF1b3Q7Ljxicj4NCjxicj4NCsKgIMKgIMKgIMKgIG/CoCDCoCDC
oCDCoE9uIHRoYXQsIEkgZG8gbm90IGZpbmQgdGhlIGNob3NlbiBzdHJ1Y3R1cmUgb2YgdGhlIGRv
Y3VtZW50IHRvIGJlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb3B0aW1hbCBmb3IgY29u
dmV5aW5nIGFuIHVuYW1iaWd1b3VzIHByb3RvY29sIHNwZWNpZmljYXRpb24uIEZvciBvbmUsPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhlIHNhbWUgY29uY2VwdHMgYXJlIG9jY2FzaW9u
YWxseSBkZXNjcmliZWQgc2xpZ2h0bHkgZGlmZmVyZW50bHkuPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgRm9yIGFub3RoZXIsIGl0IGlzIG9mdGVuIGhhcmQgdG8gZmluZCB0aGUgaW5mb3Jt
YXRpb24gbmVlZGVkIHRvPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgcGFyc2UgYSBzcGVj
aWZpYyBtYW5kYXRlZCBwcm9jZXNzaW5nIChmb3IgZXhhbXBsZSkuIEkgcHJvdmlkZSBhbjxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGV4YW1wbGUgb2Ygd2hhdCBJIHdvdWxkIHN1Z2dlc3Qg
YSBiZXR0ZXIgc3RydWN0dXJlIGluIHRoZSBiZWxvdy48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBUaGUgZ29hbCBpcyB0byBwcm92aWRlIGZpcnN0IGNvbmNlcHRzIGFuZCBhbiBv
dmVydmlldywgZm9sbG93ZWQgYnkgYTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHNpbmds
ZSwgZWFzeSB0byBpZGVudGlmeSBwbGFjZSBmb3IgJnF1b3Q7cHJlY2lzZSBhbmQgdW5hbWJpZ3Vv
dXMgZGVmaW5pdGlvbnM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvZiBjb25jZXB0cyZx
dW90OywgYW5kIHRoZW4gdXNlIHRob3NlIGluIHRoZSBkZXRhaWxlZCBleHByZXNzaW9uIG9mIHRo
ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHByb3RvY29sLiBOb3RlIHRoYXQgdGhpcyBp
cyBqdXN0IGFuIGV4YW1wbGUsIG9mIGNvdXJzZTo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCBTZWN0aW9uICZxdW90O1Rlcm1pbm9sb2d5OiZxdW90Ozxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFRoZSBOZXR3
b3JrIFN0YXRlIEhhc2ggaXMgYSBoYXNoIHZhbHVlIHdoaWNoIHJlcHJlc2VudHMgdGhlPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgY3VycmVudCBz
dGF0ZSBvZiB0aGUgbmV0d29yaywgYXMga25vd24gYnkgYSBub2RlLjxicj4NCjxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFNlY3Rpb24gJnF1b3Q7UHJvdG9jb2wgT3Zl
cnZpZXcgYW5kIEZ1bmN0aW9uaW5nJnF1b3Q7PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgV2hlbiByZWNlaXZpbmcgYSBGT08gVExWLCB0
aGUgRE5DUCBub2RlIGNvbXBhcmVzIHRoZSByZWNlaXZlZDxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIE5ldHdvcmsgU3RhdGUgSGFzaCB3aXRoIGl0
cyBvd24gTmV0d29yayBTdGF0ZSBIYXNoLiBUaGlzPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgcmVwcmVzZW50cyB0aGUgY29uc2lzdGVuY3kgY2hl
Y2sgcm9tIFJGQzYyMDYuIElmIHNhbWUsPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhlbi4uLmlmIG5vdCwgdGhlbiAuLi4uPGJyPg0KPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgU2VjdGlvbiAmcXVvdDtQcm90b2Nv
bCBJbmZvcm1hdGlvbiBCYXNlcyZxdW90Ozxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIEZvciB0aGUgcHVycG9zZSBvZiB0aGlzIHNwZWNpZmljYXRp
b24sIHRoZSBQcm90b2NvbDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIEluZm9ybWF0aW9uIEJhc2VzIGFyZSBvcmduYWl6ZWQgYXMgc2V0cyBvZiB0
dXBsZXMgLi4uIGFueTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIGltcGxlbWVudGF0aW9uIGNhbiBjaG9zZSB3aGF0ZXZlciBy
ZXByZXNlbnRhdGlvbiBpdCB3YW50cy48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBUaGUgTmV0d29yayBTdGF0ZSBJ
bmZvcm1hdGlvbiBCYXNlIGluIGEgRE5DUCBub2RlIGlzIGEgc2V0PGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb2YgdHVwbGVz
Ojxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgICh4LCB5LCB6LCB3KTxicj4NCjxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHdoZXJlIHgg
aXMgLi4uLCB5IGlzIC4uLiwgeiBpcyAuLi4sIGFuZCB3IGlzIC4uLjxicj4NCjxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFNlY3Rpb24gJnF1b3Q7SG93IHRvIGNhbGN1
bGF0ZSB0aGUgTmV0d29yayBTdGF0ZSBIYXNoJnF1b3Q7Ojxicj4NCjxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgVGhlIG5ldHdvcmsgU3RhdGUg
SGFzaCBpcyBjYWxjdWxhdGVkIHVzaW5nIHRoZSBpbmZvcm1hdGlvbjxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgZnJvbSB0aGUgTmV0d29yayBT
dGF0ZSBJbmZvcm1hdGlvbiBCYXNlLCBhcyBmb2xsb3dzOjxicj4NCjxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIDEuIEZpcnN0LCB0aGUgdHVwbGVzIGluIHRoYXQgaW5mb3JtYXRpb24gYmFzZSBhcmUgc29y
dGVkPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBpbiBhc2NlbmRpbmcgb3JkZXIgYmFzZWQgb24g
Li4uLjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIDIuIFNlY29uZCwgLi4uLiAoY29uY2F0ZW5h
dGlvbik8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAzLiBUaGlyZCwgdGhlIGhhc2ggZnVuY3Rp
b24gZnJvbSAmbHQ7cHJvZmlsZSZndDsgaXMgdXNlZDxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IDQuIEZvdXJ0aCwgdGhlIGZpcnN0IG4gYml0cyBvZiB0aGUgcmVzdWx0aW5nIGhhc2ggdmFsdWUs
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBhcmUgcmV0YWluZWQsIHdpdG4gbiBiZWluZyBmcm9t
ICZsdDtwcm9maWxlJmd0Oy48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCBBbmQgdGhlbiwgaW4gcmVtYWluaW5nIHNlY3Rpb25zIHNpbXBseSByZWZlcmVuY2Ug
dGhlIE5ldHdvcms8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBTdGF0
ZSBIYXNoLCB3aGljaCBpcyBub3cgdWJpcXVpdG91c2x5IGRlZmluZWQgaW4gYSBzaW5nbGUgcGxh
Y2UuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgSSBhbSB0
YWtpbmcgdGhpcyBleGFtcGxlLCBzaW5jZSB3aGVuIHJlYWRpbmcgc2VjdGlvbiA1LjMgSSBmb3Vu
ZDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG15c2VsZiBjaGFzaW5n
IHRocm91Z2ggdGhlIGRvY3VtZW50LCBmaW5kaW5nIG11bHRpcGxlIHNsaWdodGx5PGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgZGlmZmVyZW50IGRlZmluaXRpb25zIG9m
ICZxdW90O05ldHdvcmsgU3RhdGUgSGFzaCZxdW90OyAtLcKgIGJ1dCBiZXlvbmQgdGhpczxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGV4YW1wbGUsIGl0IGdlbmVyYWxs
eSBkb2VzIGFwcGx5IHRvIHRoZSBkb2N1bWVudCBhcyBhIHdob2xlLCBhbmQ8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBjZXJ0YWlubHkgdG8gYWxsIG9mIHRoZSBwcm9j
ZXNzaW5nIGFuZCBnZW5lcmF0aW9uIGNvbnNpZGVyYXRpb25zIGluPGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgc2VjdGlvbiA1Ljxicj4NCjxicj4NCsKgIMKgIMKgIMKg
IG/CoCDCoCDCoCDCoEFzIGEgZ2VuZXJhbCBjb21tZW50LCB0aGUgZG9jdW1lbnQgd291bGQgZG8g
d2VsbCB3aXRoIGEgZ29vZCBlZGl0b3JpYWw8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBv
dmVyaGF1bCB0byBicmluZyBjb25zaXN0ZW5jeSBpbiBsYW5ndWFnZSB1c2FnZSwgY29uc2lzdGVu
Y3kgaW4gMjExOTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRlcm1pbm9sb2d5LCBjb2hl
cmVuY2UgaW4gZGVmaW5lZCB0ZXJtcyBhbmQgdGhlaXIgZGVmaW5pdGlvbiwgZG9jdW1lbnQ8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBzdHJ1Y3R1cmUsIGV0Yy48YnI+DQo8YnI+DQpNYWpv
ciBJc3N1ZXM6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgVGhlIGludHJvZHVj
dGlvbiBkb2VzIG5vdCByZWFkIHdlbGw7IGl0IGNvbnRhaW5zIHBhcnRzIG9mIHNvbWV0aGluZyB0
aGF0PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgY291bGQgYmUgY29uc2lkZXJlZCBhcyBw
YXJ0IG9mIGFuIGFwcGxpY2FiaWxpdHkgc3RhdGVtZW50ICh3aXRob3V0IGl0PGJyPg0KwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgYmVpbmcgY2FsbGVkIG91dCBhcyBzdWNoLCBhbmQgd2l0aG91dCBm
b3JtaW5nIGEgY29tcGxldGUgYXBwbGljYWJpbGl0eTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIHN0YXRlbWVudCksIGFuZCBkb2VzIG5vdCBhY3R1YWxseSBpbnRyb2R1Y2UgdGhlIHByb3Rv
Y29sLiBSZWFkaW5nIGp1c3Q8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB0aGUgaW50cm9k
dWN0aW9uIGFuZCB0aGUgYWJzdHJhY3QsIGl0IGlzIHZlcnkgb2JzY3VyZSBpZjxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIHRoaXMgaXMgYSBmcmFtZXdvcmssIGEgcHJvdG9jb2wsIGEgYnVp
bGRpbmcgYmxvY2ssIGFuIGFyY2hpdGVjdHVyZSwgYW48YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCBhbGdvcml0aG0gLS0gYW5kLCBpZiBlaXRoZXIgb2YgdGhvc2UsIHdoYXQgaXQgaXMgYWN0
dWFsbHkgYWNjb21wbGlzaGluZyw8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBhbmQgd2h5
IG9uZSB3b3VsZCBjaG9zZSB0byB1c2UgRE5DUC4gSXQgZG9lcywgaG93ZXZlciwgdHJhbnNwaXJl
IHRoYXQ8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDt3aGF0ZXZlciBpdCBpcyZx
dW90OywgaXQgaGFzIHR3byAmcXVvdDttb2RlcyZxdW90OyBhbmQgdGhhdCBpdCByZXF1aXJlcyBz
b21ldGhpbmc8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAocHJlc3VtYWJseSBhIHJvdXRp
bmcgcHJvdG9jb2wpIHRvIHByb3ZpZGUgZWFjaCAmcXVvdDtub2RlJnF1b3Q7IHdpdGggYSB0b3Bv
bG9neTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG1hcC48YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCBTdWdnZXN0IHRoYXQgYSBwcm9wZXIgaW50cm9kdWN0aW9uIGNvbnNp
c3Rpbmcgb2YgdGhyZWUgcGFydHMgd291bGQgYmU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCBiZW5lZmljaWFsOiAoaSkgd2hhdCB0aGlzIGRvY3VtZW50IGlzLCAoaWkpIHdoYXQgZG9pbmcg
RE5DUCBhY3R1YWxseTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGdldHMgeW91LCBhbmQg
KGlpaSkgdGhlIG9wZXJhdGluZyBjb25kaXRpb25zIHVuZGVyIHdoaWNoIHRoZTxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIEROQ1AgaXMgYXBwbGljYWJsZS48YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCBPbiB0aGUgbGF0dGVyIHBvaW50LCBnaXZlbiB0aGF0IHlvdSBzdGF0
ZSB0aGF0IEROQ1AgcmVxdWlyZXMgcHJvZmlsZXM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCB0byBwcm92aWRlICZxdW90O2FjdHVhbCBpbXBsZW1lbnRhYmxlIEROQ1AgYmFzZWQgcHJvdG9j
b2xzJnF1b3Q7LCBpdCBhcHBlYXJzPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgaW1wb3J0
YW50IHRvIHVuZGVyc3RhbmQgd2hhdCB0aGUgbGltaXRzIGZvciAmcXVvdDt3aGF0IGEgcHJvZmls
ZSBjYW4gZ2l2ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHlvdSZxdW90OyBhcmUuPGJy
Pg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgSSBhbSBjYWxsaW5nIHRoaXMgb3V0IGFz
IGEgbWFqb3IgaXNzdWUsIHNpbmNlIEkgYmVsaWV2ZSB0aGF0IGl0IGlzPGJyPg0KwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgbm90IGp1c3QgZWRpdG9yaWFsLCBidXQgaXMgYSBtYXR0ZXIgb2Ygc2Nv
cGluZyB0aGlzIGRvY3VtZW50IGNvcnJlY3RseSw8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCBhbmQgaW4gcGFydGljdWxhciBub3QgZmFsbGluZyBpbnRvIHRoZSB0cmFwIG9mICZxdW90O2Ns
YWltaW5nIGFwcGxpY2FiaWxpdHk8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB3aGVyZSBp
dCYjMzk7cyBub3QmcXVvdDsuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgVGhl
IGRvY3VtZW50LCBpbiBteSB1bmRlcnN0YW5kaW5nLCBkZWZpbmVzIGFuIGV4Y2hhbmdlIGZvcm1h
dCB3aXRoPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgbGltaXRlZCBhYmlsaXR5IHRvIGV2
b2x2ZSwgYXMgc2ltcGx5ICZxdW90O2Egc3RlYW0gb2YgVExWcyZxdW90Oy48YnI+DQo8YnI+DQrC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBBcyBsb25nIGFzIHRoZXJlJiMzOTtzIG5ldmVyIGEgbmVl
ZCB0byBldm9sdmUgdGhlIFRMViBmb3JtYXQgaXRzZWxmLCBhbmQ8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBhcyBsb25nIGFzIHlvdSBkbyBub3QgcnVuIG91dCBvZiBUTFYgdHlwZXMsIHRo
YXQmIzM5O3Mgbm90IGdvaW5nIHRvIGJlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYSBw
cm9ibGVtLiBUaGUgZG9jIHNldHMgYXNpZGUgYSAxNmJpdCBUTFYgdHlwZSBzcGFjZSwgdGhhdCYj
Mzk7cyByZWFzb25hYmxlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgZW5vdWdoLCBidXQg
SSB3b3JyeSBpZiBldmVudHVhbGx5IGEgRE5DUHYyIHdpbGwgbmVlZCB0byBldm9sdmUgdGhlPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgZm9ybWF0LiBPbmUgcHVyZWx5IGh5cG90aGV0aWNh
bCBleGFtcGxlIGNvdWxkIGJlIGlmIGEgJnF1b3Q7c2VxdWVuY2UgbnVtYmVyJnF1b3Q7PGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgd291bGQgYmUgbmVlZGVkIGluIGVhY2ggRE5DUCBtZXNz
YWdlIHRvIGRldGVjdCAmcXVvdDtsaW5rIHN1Y2Nlc3MgcmF0ZXMmcXVvdDssIG9yPGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgc29tZXRoaW5nIG9mIHRoYXQgc29ydC48YnI+DQo8YnI+DQrC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBJIGRvIG5vdCBoYXZlIGFuIGFjdHVhbCBleGFtcGxlIGlu
IG1pbmQgLS0gYW5kIHRoYXQmIzM5O3MgZXhhY3RseSB0aGUgcG9pbnQ6PGJyPg0KwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgdG8gYmUgZXZvbHV0aXZlIGZvciB0aGUgdW5rbm93biBmdXR1cmUgYW5k
IChhdCB0aGUgdmVyeSBsZWFzdCkgYmUgYWJsZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IHRvIGRpc2NyaW1pbmF0ZSBiZXR3ZWVuICZxdW90O29sZCZxdW90OyBhbmQgJnF1b3Q7bmV3JnF1
b3Q7Ljxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIEEgZGlzY3Vzc2lvbiBjb3Vs
ZCBiZSBoYWQgaWYgYSAmcXVvdDt2ZXJzaW9uIG51bWJlciZxdW90OyBpbiBlYWNoIFRMViB3b3Vs
ZCBkbyw8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvciBpZiBhIGNvbmNlcHQgb2YgJnF1
b3Q7cHJvdG9jb2wgbWVzc2FnZSB3aXRoIGEgdmVyc2lvbiBudW1iZXImcXVvdDsgaXM8YnI+DQrC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBwcmVmZXJlbnRpYWwuIEkgZG8gbm90IGJlbGlldmUsIGhv
d2V2ZXIsIHRoYXQgJnF1b3Q7bm8gdmVyc2lvbiBudW1iZXImcXVvdDsgaXM8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCB2aWFibGUuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKg
IMKgTm90aW5nIHRoYXQgdGhlICZxdW90O292ZXJoZWFyaW5nIG4gcmVkdW5jYW50IHRyYW5zbWlz
c2lvbnMmcXVvdDsgaXMgYSBrZXk8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCByZXRyYW5z
bWlzc2lvbiBzdXBwcmVzc2lvbiBtZWNoYW5pc20gaW4gVHJpY2tsZSwgYW5kIHRoYXQgdGhpczxi
cj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHNlZW1zIHRvIGFzc3VtZSBicm9hZC9tdWx0aWNh
c3QsIHVzaW5nIHVuaWNhc3Qgc2VlbXMgdG8gY29udHJhZGljdDxicj4NCsKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIHRoZSBzdGF0ZW1lbnQgb2YgJnF1b3Q7Y29uc2lzdHMgb2YgVHJpY2tsZSZxdW90
OywgYXQgbGVhc3QgaW4gdGhlIHdheSB0aGU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBh
bGdvcml0aG0gaXMgZGVmaW5lZCBpbiBSRkM2MjA2LiBOb3RlOiBpdCYjMzk7cyBmaW5lIHRvIHVz
ZSBhbiBhbGdvcml0aG08YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvdXRzaWRlIG9mIGl0
cyBpbml0aWFsIHNjb3BlLCBidXQgaXQgc2hvdWxkIGJlIHdpdGggdGhlIGNhdmVhdCBvZjxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O3doaWNoIG9mIHRoZSBjaGFyYWN0ZXJpc3Rp
Y3Mgc3RpbGwgaG9sZCwgYW5kIHdoaWNoIGRvIG5vdCZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIG/CoCDCoCDCoCDCoEROQ1AgY2xhaW1zIHRvIGJlIHRyaWNrbGUgYmFzZWQsIHlldCBzdXBw
b3J0cyB1bmljYXN0LiBJdCBhbHNvPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgKGFwcGFy
ZW50bHkpIGlzIGEgcmVxdWVzdC9yZXBseSBwcm90b2NvbC7CoCBJdCBkb2VzbiYjMzk7dCBoYXZl
IG1lc3NhZ2VzLjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFRoaXMgZG9jdW1lbnQgbmVl
ZHMgYSBnb29kLCBhbmQgcGVkYWdvZ2ljYWwsICZxdW90O3Byb3RvY29sIG92ZXJ2aWV3IGFuZDxi
cj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGZ1bmN0aW9uaW5nJnF1b3Q7IHNlY3Rpb24gc29t
ZXdoZXJlOiBvbmUgbmVlZHMgdG8gZ2V0IHRocm91Z2ggdGhlIGVuZCBvZjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIFNlY3Rpb24gNSBiZWZvcmUgaGF2aW5nIGV2ZW4gYSB2YWd1ZSBpZGVh
IG9mIGhvdyBETkNQIHdvcmtzLjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIG/CoCDCoCDCoCDCoFRo
ZSB1c2Ugb2Ygbm9ybWF0aXZlIGxhbmd1YWdlIGlzIG5vdCBhcyB0aWdodCBhcyBjb3VsZCBiZSBk
ZXNpcmVkLjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIEZvciBleGFtcGxlLCBhIG51bWJl
ciBvZiBTSE9VTERzIHNlZW0gdG8gcmVhbGx5IG91Z2h0IHRvIGJlICZxdW90O01BWXMmcXVvdDsg
c2luY2U8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBub3QgZm9sbG93aW5nIHRoZSBTSE9V
TEQgd29uJiMzOTt0IGJyZWFrIHRoZSBhbGdvcml0aG0uIEl0IHdvdWxkIGJlIGdvb2Q8YnI+DQrC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB0byB3YWxrIHRocm91Z2ggdGhlIGRvY3VtZW50IGFuZCB0
YWtlIGEgY2FyZWZ1bCBsb29rIGF0IHRoZXNlIHRvPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgZWl0aGVyIE1VU1QvTUFZIHRoZSBTSE9VTERzLCBvciB0byBxdWFsaWZ5IHRoZSBTSE9VTERz
IHJlbWFpbmluZy48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBJIGFtIGdvaW5n
IHRvIGdvIG91dCBvbiBhIGxpbWIgaGVyZSwgYW5kIHNheSB0aGF0ICZxdW90O3RoZSBwcm90b2Nv
bCBpczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHVuZGVyc3BlY2lmaWVkJnF1b3Q7LiBU
aGF0JiMzOTtzIGEgZGVsaWJlcmF0ZWx5IHByb3ZvY2F0aXZlIHN0YXRlbWVudCwgYnV0IGl0PGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgd2FzIGhvbmVzdGx5IGhvdyBJIGZlbHQgdXBvbiBo
YXZpbmcgY29tcGxldGVkIHRoZSByZXZpZXcuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgVGhlIGRvY3VtZW50IGRvZXMgbm90IGhlbHAgdGhlIHJlYWRlciBnZXQgYW4gaW50dWl0
aXZlIHVuZGVyc3RhbmRpbmc8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvZiB0aGUgcHJv
dG9jb2wgZnVuY3Rpb25pbmcsIGJ1dCBqdW1wcyByaWdodCBpbnRvIG1pbnV0ZSBkZXRhaWxzIC0t
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgcmVxdWlyaW5nIHRoZSByZWFkZXIgdG8gJnF1
b3Q7YnVpbGQgdXAgaGVyIG9yIGhpcyBvd24gbW9kZWwgb2YgaG93IEROQ1A8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCB3b3JrcyZxdW90Oy4gT24gaGF2aW5nIHJlYWQgdGhlIGRvY3VtZW50
IGEgZmV3IHRpbWVzLCBJIHRoaW5rIHRoYXQgSTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IHVuZGVyc3RhbmQgaXQgLS0gYnV0IHRoZXJlJiMzOTtzIG5vdGhpbmcgcGVybWl0dGluZyBtZSB0
byB2ZXJpZnkgbXk8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB1bmRlcnN0YW5kaW5nLCBh
bmQgdGhlcmVieSBJJiMzOTtkIG5vdCBmZWVsIGNvbmZpZGVudCB0byBiZSBhYmxlIHRvPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgcHJvdmlkZSBhbiBpbnRlcm9wZXJhYmxlIGFuZCBpbmRl
cGVuZGVudCBpbXBsZW1lbnRhdGlvbi4gSSYjMzk7dmUgZ2l2ZW48YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBzb21lIGNvbW1lbnRzIGluIHRoZSAmcXVvdDtDb21tZW50cyZxdW90OyBzZWN0
aW9uIGFzIHRvIHdoYXQgSSB0aGluayB3b3VsZCBiZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIHZpYWJsZSB3YXlzIHRvIGltcHJvdmUgdGhpcyBwb2ludC48YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoG/CoCDCoCDCoCBTZWN0aW9uIDUuMywgcGVudWx0aW1hdGUgcGFyYWdyYXBoOjxicj4N
Cjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O0lmIGtlZXAt
YWxpdmVzIHNwZWNpZmllZCBpbiBTZWN0aW9uIDYuMSBhcmUgTk9UIHNlbnQgYnkgdGhlIHBlZXI8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoChlaXRoZXIgdGhlIEROQ1AgcHJv
ZmlsZSBkb2VzIG5vdCBzcGVjaWZ5IHRoZSB1c2Ugb2Yga2VlcC1hbGl2ZXMgb3I8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoHRoZSBwYXJ0aWN1bGFyIHBlZXIgY2hvb3NlcyBu
b3QgdG8gc2VuZCBrZWVwLWFsaXZlcyksIHNvbWUgb3RoZXI8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoG1lYW5zIE1VU1QgYmUgZW1wbG95ZWQgdG8gZW5zdXJlIGl0cyBwcmVz
ZW5jZS7CoCBXaGVuIHRoZSBwZWVyIGlzIG5vPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqBsb25nZXIgcHJlc2VudCwgdGhlIE5laWdoYm9yIFRMViBhbmQgdGhlIGxvY2FsIERO
Q1AgcGVlciBzdGF0ZSBNVVNUPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBi
ZSByZW1vdmVkLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90
Oy4uLnNvbWUgb3RoZXIgbWVhbnMgTVVTVCBiZSBlbXBsb3llZCB0byBlbnN1cmUgaXRzIHByZXNl
bmNlLiZxdW90OyAtLTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGZvbGxvd2VkIGJ5IG1v
cmUgTVVTVCB2ZXJhZ2Ugd2hlbiBhIHBlZXIgZGlzYXBwZWFycy4uLkkgYW0gbm90IHN1cmUgdGhh
dDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRoYXQmIzM5O3MgY29uZHVjdGl2ZSB0byBp
bnRlcm9wZXJhYmxlIGltcGxlbWVudGF0aW9ucy48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCBUd28gaW1wbGVtZW50YXRvbnMgbWF5IGNob3NlIGRpZmZlcmVudCAmcXVvdDttZWFu
cyZxdW90OyBhbmQgdGhlbiB0dXJuIG9mZiBrZWVwLTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIGFsaXZlcyAtIGFuZCBiZSBub24taW50ZXJvcGVyYWJsZS48YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCBGb3IgaW50ZXJvcGVyYWJpbGl0eSwgd2UgbmVlZDo8YnI+DQo8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAg
wqAgwqBBIG1hbmRhdG9yeSB0byBpbXBsZW1lbnQgbWVjaGFuaXNtLCB0aGF0IGFsd2F5cyBpczxi
cj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIHByZXNlbnQsIGJ1dCBjYW4gYmUgY29tcGxlbWVudGVkIGJ5IGFub3RoZXIgJnF1b3Q7
bWVhbnMmcXVvdDssIG9yPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgQSBtYW5kYXRvcnkgdG8gaW1wbGVtZW50IG1l
Y2hhbmlzbSwgd2hpY2ggYnkgd2F5IG9mIGE8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBzcGVjaWZpZWQgbmVnb3RpYXRpb24g
bWVjaGFuaXNtIGNhbiBiZSB0dXJuZWQgb2ZmIGJldHdlZW48YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB0d28gcGVlcnMsIHRv
IGFsbG93IHRoZW0gdG8gdXNlIGFub3RoZXIgJnF1b3Q7bWVhbnMmcXVvdDsuPGJyPg0KPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgSWYgeW91IGFyZ3VtZW50IGlzICZxdW90Oy4uLnRoaXMg
d2lsbCBiZSBzcGVjaWZpZWQgaW4gdGhlIHByb2ZpbGUmcXVvdDssIHRoZW48YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCB5b3Ugc3RpbGwgc2hvdWxkIHByb3ZpZGUgdGhlIHR3byBhYm92ZSBp
biB0aGlzIGRvY3VtZW50LCB3aXRoIHRoZSBub3RlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgdGhhdCAmcXVvdDsuLi5hbmQgYSBwcm9maWxlIG1heSBzcGVjaWZ5IHdoaWNoIGZyb20gYW1v
bmcgdGhlc2UgTVVTVCBiZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHVzZWQgaW4gYSBn
aXZlbiBkZXBsb3ltZW50JnF1b3Q7PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKg
U2VjdGlvbiA4Ojxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIEludGVyZXN0aW5nOyBJIGFt
IG5vdCBhIHNlY3VyaXR5IGV4cGVydCwgYnV0IEkgYW0gdmVyeSBjdXJpb3VzIHRvPGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgc2VlIHRoZSBTRUMtRElSIHJldmlldyBvZiB0aGlzIGRvY3Vt
ZW50LiBUaGF0IHNhaWQsIHNlY3Rpb24gOC4zLjE8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCBjb250YWlucyBub3JtYXRpdmUgdmVyYmFnZTo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtBIG5vZGUgTVVTVCBiZSB0cnVzdGVkIGZvciBwYXJ0
aWNpcGF0aW5nIGluIHRoZSBETkNQIG5ldHdvcmsgaWYgYW5kPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgb25seSBpZi4uLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIFdoaWNoIEkgdGhpbmsgbmVlZHMgYSBxdWFsaWZpZXIgb2YgdGhlICZx
dW90O0lmIHRoZSBjZXJ0aWZpY2F0ZSBiYXNlZDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IHRydXN0IG1vZGVsIGlzIHVzZWQsIHRoZW4gYSBub2RlIG11c3QgYmUgdHJ1c3RlZCBmb3IgLi4u
LiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFNhbWUgZ29lcyBmb3Ig
dGhlIHN1YnNlcXVlbnQgU0hPVUxEIC0gaXQgcmVhbGx5IHJlYWRzIGFzLWlmIHRoaXM8YnI+DQrC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBjZXJ0aWZpY2F0ZSBiYXNlZCBtZWNoYW5pc20gaW5pdGlh
bGx5IHdhcyBpbnRlbmRlZCBhcyBNVEksIGJ1dCB0aGVuPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgd2FzIGJhY2tlZCBhd2F5IGZyb20gc3Vic2VxdWVudGx5IHdpdGhvdXQgYSBjb21wbGV0
ZSBjbGVhbnVwIG9mIHRoZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRleHQ/PGJyPg0K
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgSSBkbyBhY3R1YWxseSBxdWVzdGlvbiB0aGUg
dmFsdWUgb2YgaGF2aW5nIGEgbGF1bmRyeS1saXN0IG9mIHRydXN0PGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgbWFuYWdlbWVudCBtZXRob2RzLCBhbmQgZm9yIG9uZSBvZiB0aG9zZSAoY2Vy
dHMpIGEgbGF1bmRyeS1saXN0PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb2YgYWxsIHNv
cnRzIG9mIHRydXN0IHJlbGF0aW9uc2hpcCBlc3RhYmxpc2htZW50IG1ldGhvZHMsIGluIHRoaXM8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBkb2N1bWVudDsgdGhpcyBpbiBubyBzbWFsbCBw
YXJ0IGFzIHRoZSBsaXN0cyBhcmUgZXhwbGljaXRseSBpbmRpY2F0ZWQ8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCBhcyAmcXVvdDtub24tZXhoYXVzdGl2ZSZxdW90OyBhbmQgdGhhdCBub25l
IGFyZSBsaXN0ZWQgYXMgJnF1b3Q7bWFuZGF0b3J5IHRvPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgaW1wbGVtZW50JnF1b3Q7LiBXYXMgYW55IHRob3VnaHQgZ2l2ZW4gdG8gZmFjdG9yaW5n
IHRoaXMgaW50byBhIHNlcGVyYXRlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgZG9jdW1l
bnQsIGFuZCBmb2N1c2luZyBpbiB0aGlzIGRvY3VtZW50IG9uIG9uZSwgbWFuZGF0b3J5LXRvLWlt
cGxlbWVudCw8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBzZWN1cml0eSBtZWNoYW5pc20/
PGJyPg0KPGJyPg0KTWlub3IgSXNzdWVzOjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIEludHJvZHVj
dGlvbjo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqAxc3QgcGFyYWdy
YXBoOiAmcXVvdDtyZWFjaGFibGUgbm9kZXMmcXVvdDs7IHR3byB0aGluZ3M6PGJyPg0KPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgLcKgIMKgIMKg
IMKgSSBhbHdheXMgaGF2ZSBhIHByb2JsZW0gd2l0aCB0aGUgdGVybSAmcXVvdDtub2RlJnF1b3Q7
OyBpdCBpcyBvZnRlbjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIHVzZWQgYXMgYSBzaG9ydGhhbmQgZm9yICZxdW90O3JvdXRl
cnMgYW5kIGhvc3RzLCBib3RoJnF1b3Q7LiBJIHdhczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGdpdmVuIHRvIHVuZGVyc3Rh
bmQgdGhhdCBob21lbmV0IHNwZWNpZmljYWxseSBkaWQgbm90IHdhbnQ8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB0byBjb25z
aWRlciBob3N0IGNoYW5nZXM/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgLcKgIMKgIMKgIMKgJnF1b3Q7UmVhY2hhYmxlJnF1b3Q7IC0g
ZG9lcyB0aGF0IG1lYW4gc29tZXRoaW5nIGFzIGluICZxdW90O3JhZGlvIHJhbmdlJnF1b3Q7LDxi
cj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIGRvZXMgaXQgbWVhbiAmcXVvdDtvbiB0aGUgc2FtZSBsaW5rJnF1b3Q7LCBkb2VzIGl0
IG1lYW4gd2l0aGluIGE8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBzcGVjaWZpYyAoRE5DUD8pIGRvbWFpbiwgb3IgZG9lcyBp
dCBtZWFuIHNpbXBseSAmcXVvdDtvbiB0aGU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBJbnRlcm5ldCBzb21ld2hlcmUmcXVv
dDs/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgMm5kIHBh
cmFncmFwaDogJnF1b3Q7bm9kZXMgdGhhdCBhcmUgY3VycmVudGx5IGFjY291bnRlZCBmb3ImcXVv
dDs6PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
LcKgIMKgIMKgIMKgV2hhdCBkb2VzIHRoYXQgbWVhbj88YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAtwqAgwqAgwqAgwqBBbHNvLCB0aGUg
Y29uY2x1c2lvbiAmcXVvdDtUaGVyZWZvcmUgdW5saWtlIFRpbWUtVG8tTGl2ZSAoVFRMKTxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIGJhc2VkIHNvbHV0aW9ucywgaXQgZG9lcyBub3QgcmVxdWlyZSBwZXJpb2RpYyByZS1wdWJs
aXNoaW5nPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgb2YgdGhlIGRhdGEgYnkgdGhlIG5vZGVzJnF1b3Q7IGRvZXMgYWN0dWFs
bHkgbm90IGZvbGxvdyBmcm9tPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhlIHByZXZpb3VzIHNlbnRlbmNlIGluIHRoYXQg
cGFyYWdyYXBoLjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIC3CoCDCoCDCoCDCoEkgYWN0dWFsbHkgZG8gbm90IHRoaW5rIHRoYXQgdGhl
IGludHJvZHVjdGlvbiBkZXNjcmliZXM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB3aGF0IEROQ1AgZG9lcywgYW5kIHNvIHRo
ZSBjb21wYXJpc29uIHRvIFRUTC1iYXNlZDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHNvbHV0aW9ucyBpcyByYXRoZXIgaGFy
ZCB0byBnZXQgaGVyZS48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCAtwqAgwqAgwqAgwqBDb250aW51aW5nOjxicj4NCjxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgICZxdW90O09uIHRoZSBvdGhlciBoYW5kLCBpdCBkb2VzIHJlcXVpcmUgdGhlIHRv
cG9sb2d5PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdG8gYmUgdmlzaWJsZSB0byBldmVyeSBub2RlIHRo
YXQgd2FudHMgdG8gYmUgYWJsZSB0bzxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGlkZW50aWZ5IHVucmVh
Y2hhYmxlIG5vZGVzIGFuZCB0aGVyZWZvcmUgcmVtb3ZlIG9sZCw8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCBzdGFsZSBkYXRhLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFRoaXMgcmVhZHMgYSBsb3QgbW9yZSBs
aWtlIGFuIGFwcGxpY2FiaWxpdHkgc3RhdGVtZW50IHRoYW48YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBhbiBpbnRyb2R1Y3Rp
b247IHRoZSB0YWtlLWF3YXkgd2hlbiByZWFkaW5nIHRoaXMgaXM6PGJyPg0KPGJyPg0KwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgJnF1b3Q7RWFjaCBub2RlIG11c3QgaGF2ZSBzb21ldGhpbmcgdGhhdCBtYWludGFp
bnM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoGEgdG9wb2xvZ3kgbWFwIG9mIHRoZSBlbnRpcmUgbmV0
d29yaywgc3VjaCBhczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgYSAoTFMpIHJvdXRpbmcgcHJvdG9j
b2wsIGZvciBETkNQIHRvIGZ1bmN0aW9uJnF1b3Q7PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgSXMgdGhhdCBhY3R1
YWxseSB0aGUgaW50ZW50IGhlcmU/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgLcKgIMKgIMKgIMKgJnF1b3Q7RE5DUCBpcyBtb3N0IHN1
aXRhYmxlIGZvciBkYXRhIHRoYXQgY2hhbmdlcyBvbmx5IGdyYWR1YWxseSZxdW90Ozxicj4NCsKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IEhvdyBpcyB0aGUgcmVhZGVyIHRvIGludGVycHJldCAmcXVvdDtncmFkdWFsbHkmcXVvdDs/IERv
IHlvdSBtZWFuPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7aW5mcmVxdWVudGx5JnF1b3Q7LCBvciBkbyB5b3UgcmVh
bGx5IG1lYW4gJnF1b3Q7Z3JhZHVhbHkmcXVvdDs/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgbyBMYXN0IHBhcmFncmFwaDo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtETkNQIGhhcyByZWxhdGl2ZWx5IGZldyByZXF1
aXJlbWVudHMgZm9yIHRoZSB1bmRlcmx5aW5nPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqB0cmFuc3BvcnQ7IGl0IHJlcXVpcmVzIHNvbWUgd2F5
IG9mIHRyYW5zbWl0dGluZyBlaXRoZXIgdW5pY2FzdDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgZGF0YWdyYW0gb3Igc3RyZWFtIGRhdGEgdG8g
YSBwZWVyJnF1b3Q7PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgVGhpcyBpcyBhIGJpdCBvZiBhIGZvcndhcmQgY29tbWVudCwgYnV0IHdlIG5vdyBoYXZlICZx
dW90O25vZGVzPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhhdCBh
cmUgYWNjb3VudGVkIGZvciZxdW90OyBhbmQgJnF1b3Q7cGVlcnMmcXVvdDsuIEkgc2VlIG5laXRo
ZXIgZGVmaW5lZCBpbjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRo
ZSB0ZXJtaW5vbG9neSBzZWN0aW9uLjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O2FuZCwgaWYgdXNlZCBpbiBtdWx0aWNhc3Qg
bW9kZSwgYSB3YXkgb2Y8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoHNlbmRpbmcgbXVsdGljYXN0IGRhdGFncmFtcy4mcXVvdDs8YnI+DQo8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBUaGlzIGlzIHRoZSBmaXJzdCBt
ZW50aW9uIG9mIHR3byAmcXVvdDttb2RlcyZxdW90OyBvZiB0aGlzIHByb3RvY29sLiBUaGlzPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgbG9vcHMgYmFjayB0byBhbiBl
YXJsaWVyIGNvbW1lbnQsIHRoYXQgdGhlIGludHJvZHVjdGlvbiBhY3R1YWxseTxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGRvZXMgbm90IGludHJvZHVjZSB0aGUgcHJv
dG9jb2wsIGJ1dCByYXRoZXIgaXMgYW4gaW5jb21wbGV0ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIGFwcGxpY2FiaWxpdHkgc3RhdGVtZW50Ljxicj4NCjxicj4NCsKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O0lmIHNl
Y3VyaXR5IGlzIGRlc2lyZWQgYW5kIG9uZSBvZiB0aGU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoGJ1aWx0LWluIHNlY3VyaXR5IG1ldGhvZHMg
aXMgdG8gYmUgdXNlZCwgc3VwcG9ydCBmb3Igc29tZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFRMUy1kZXJpdmVkIHRyYW5zcG9ydCBzY2hlbWUg
LSBzdWNoIGFzIFRMUyBbUkZDNTI0Nl0gb24gdG9wIG9mPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgVENQIG9yIERUTFMgW1JGQzYzNDddIG9uIHRv
cCBvZiBVRFAgLSBpcyBhbHNvIHJlcXVpcmVkLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIEkgYW0gbm90IHByZXRlbmRpbmcgdG8gYmUgYSBzZWN1
cml0eSBleHBlcnQsIGJ1dCAmcXVvdDtzb21lPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgVExTLWRlcml2ZWQuLi5zdWNoIGFzIC4uLiBvbiB0b3Agb2YgVENQIG9yIERU
TFMuLi4mcXVvdDsgKGkpIGRvZXMgbm90PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgc291bmQgbGlrZSBpdCBjb3VsZCBsZWFkIHRvIGludGVyb3BlcmFibGUgaW1wbGVt
ZW50YXRpb25zLCBhbmQgKGlpKTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIGRvZXMgbm90IHNvdW5kIHN1ZmZpY2llbnRseSB0aWdodCBhcyBhIE1USSBzZWN1cml0eSBt
ZWNoYW5pc20gdG88YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBwYXNz
IHNlY3VyaXR5IHJldmlld3MuIEFnYWluLCBJIGFtIG5vIHNlY3VyaXR5IGV4cGVydCwgYnV0IHBl
cmhhcHM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBnZXR0aW5nIG9u
ZSBsb29wZWQgaW4gZWFybHkgd291bGQgYmUgYWR2aWNhYmxlPzxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIFRlcm1pbm9sb2d5Ojxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/CoCDCoCDCoCDC
oFN1Z2dlc3QgYWRkaW5nICZxdW90O0luIHRoaXMgZG9jdW1lbnQgLi4uJnF1b3Q7IHNvbWV3aGVy
ZSB0byB0aGlzIHRleHQ6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7Rm9yIHJlYWRhYmlsaXR5LCBhbnkgRE5DUCBwcm9maWxl
IHNwZWNpZmljPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqBwYXJhbWV0ZXJzIHdpdGggYSBwcm9maWxlLXNwZWNpZmljIGZpeGVkIHZhbHVlIGFy
ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
cHJlZml4ZWQgd2l0aCBETkNQXy4mcXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCBvwqAgwqAgwqAgwqBETkNQIG5ldHdvcms6IEkgcmVhZCB0aGlzIHR3aWNlLCBhbmQgY2Ft
ZSBhd2F5IHdpdGggdHdvIGRpZmZlcmVudDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIHVuZGVyc3RhbmRpbmdzLCBwZXJoYXBzIHlvdSBjYW4gY2xhcmlmeSB3aGljaCBp
dCBpczo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCBvwqAgwqAgwqAgwqBBIHNldCBvZiBub2RlcyBydW5uaW5nIEROQ1AsIHdpdGhpbiB0
aGUgc2FtZSBkb21haW4sIGFuZDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGZvciB3aGljaCBhIHBhdGggYmV0d2VuIGFueSB0
d28gRE5DUCBub2RlcyBpbmNsdWRlcyBvbmx5PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb3RoZXIgRE5DUCBub2RlczsgaS5l
LiwgYSBETkNQIG5ldHdvcmsgZm9ybXMgYSBjb25uZWN0ZWQ8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBjb21wb25lbnQgd2l0
aCBvbmx5IG90aGVyIEROQ1Agbm9kZXMuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgQSBzZXQgb2Ygbm9kZXMgcnVu
bmluZyBETkNQLiBUaGV5IG1heSBiZSBhbnl3aGVyZSBvbiB0aGU8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBJbnRlcm5ldCwg
dGhleSBhcmUgcGFydCBvZiB0aGUgc2FtZSBETkNQIG5ldHdvcmsgYXMgbG9uZzxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGFz
IHRoZXkgKHRocm91Z2ggb3RoZXIgbWVhbnMpIGhhdmUgbGVhcm5lZCBvZiBlYWNoIG90aGVyczxi
cj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIGFkZHJlc3Nlcy48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCBJbiB0aGUgZm9ybWVyLCB0aGF0JiMzOTtkIGJlIChmb3IgZXhhbXBsZSkgYSBkZXBs
b3ltZW50IHdpdGhpbiBteTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IGhvbWUgLS0gaW4gdGhlIGxhdHRlciwgaXQgY291bGQgYmUgYSBub2RlIGluIG15IGhvbWUgYW5k
IGEgbm9kZSBpbjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHlvdXIg
aG9tZSBmb3JtaW5nIGEgRE5DUCBuZXR3b3JrLjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIFRoZSB0ZXh0IGlzIG5vdCBxdWl0ZSBjbGVhciBvbiB0aGlzIHBv
aW50Ljxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/CoCDCoCDCoCDCoExpbms6
IGEgcG9pbnQgb2YgY2xhcmlmaWNhdGlvbiBoZXJlLiBJbiAmcXVvdDtETkNQIG5ldHdvcmsmcXVv
dDssIHRoZXJlIHdhczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRh
bGsgYWJvdXQgJnF1b3Q7dW5pZGlyZWN0aW9uYWwgbGlua3MmcXVvdDsgYW5kICZxdW90O2JpZGly
ZWN0aW9uYWwgbGlua3MmcXVvdDs7IGluPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgJnF1b3Q7TGluayZxdW90OyB0aGUgZGVmaW5pdGlvbiBpcyBzb21ld2hhdCB2YWd1
ZSAmcXVvdDtkaXJlY3RseSBjb25uZWN0ZWQmcXVvdDsgYW5kPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7Y2FuIGNvbW11bmljYXRlJnF1b3Q7LiBDb3VsZCBz
b21ldGhpbmcgbGlrZSAmcXVvdDt3aXRob3V0IGRlY3JlbWVudGluZyBUVEwvPGJyPg0KwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgaG9wLWNvdW50JnF1b3Q7IGJlIGFkZGVkLCBh
bmQgY291bGQgYSBzdGF0ZW1lbnQgb24gYmlkaXJlY3Rpb25hbGl0eTxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIChJT1csIHRoYXQgdGhpcyBpcyBqdXN0IGFuIElQIGxp
bmspIGJlIGFkZGVkPzxicj4NCjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/C
oCDCoCDCoCDCoCZxdW90O0ludGVyZmFjZSZxdW90OyBpcyBvdmVybG9hZGluZyB0aGUgdGVybSAm
cXVvdDtwb3J0JnF1b3Q7IChJUCBwb3J0KSB3aGljaCBjYW4gYmU8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBjb25mdXNpbmc8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBvwqAgwqAgwqAgwqAmcXVvdDtFbmRwb2ludCZxdW90OyAtIFRoZSBkZWZpbml0
aW9uICZxdW90O2xvY2FsbHkgY29uZmlndXJlZCB1c2Ugb2YgRE5DUCZxdW90OyBpcyBub3Q8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBjbGVhciAtLSBhcmUgeW91IHJl
YWxseSBub3QgdGFsa2luZyBhYm91dCBhIEROQ1AgcHJvY2Vzcz88YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBJIGFtIG5vdCBzdXJlIHRoYXQgaXQgaXMgY2xl
YXIgaG93IGEgRE5DUCBwcm9jZXNzIGNhbiBiZSAmcXVvdDthdHRhY2hlZDxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRvwqAgLi4uIGEgc3BlY2lmaWMgcmVtb3RlIHVu
aWNhc3QgYWRkcmVzcywgb3IgdG8gYSByYW5nZSBvZiB1bmljYXN0PGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYWRkcmVzc2VzIHRoYXQgYXJlIGFsbG93ZWQgdG8gY29u
dGFjdCZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IEkgY2FuIHNlZSBob3cgYSBETkNQIHByb2Nlc3MgY2FuIGJlIGNvbmZpZ3VyZWQgdG8gYWxsb3cg
Y29ubmVjdGlvbnM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBmcm9t
IGEgc3BlY2lmaWMgcmFuZ2Ugb2YgYWRkcmVzc2VzLCBvciBjYW4gYmUgY29uZmlndXJlZCB0byBj
b25uZWN0PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdG8gYSBzcGVj
aWZpYyByZW1vdGUgdW5pY2FzdCBhZGRyZXNzLiBJcyB0aGF0IHdoYXQgeW91IG1lYW4gaW5zdGVh
ZD88YnI+DQo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqAm
cXVvdDtQZWVyJnF1b3Q7IC0gc3RhdGVzIHRoYXQgdHdvIHBlZXJzICZxdW90O2NvbW11bmljYXRl
IGRpcmVjdGx5JnF1b3Q7LiBGb3IgbGluayw8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCB0aGUgZGVmaW5pdGlvbiBpcyAmcXVvdDtkaXJlY3RseSBjb25uZWN0ZWQgbm9k
ZXMgY2FuIGNvbW11bmljYXRlJnF1b3Q7Ljxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIFdvdWxkIGl0IHRoZW4gbm90IGJlIGVhc2llciB0byBzYXkgJnF1b3Q7YSBETkNQ
IG5vZGUgb24gdGhlIHNhbWUgbGluazxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIGFzIC4uLiZxdW90OyA/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
b8KgIMKgIMKgIMKgJnF1b3Q7Tm9kZSBzdGF0ZSZxdW90Ozxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O1RoZSBoYXNoIGZ1bmN0aW9uIGFu
ZCB0aGUgbnVtYmVyIG9mIGJpdHMgdXNlZCBhcmUgZGVmaW5lZDxicj4NCsKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgaW4gdGhlIEROQ1AgcHJvZmlsZS4m
cXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBTdWdn
ZXN0Ojxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
ICZxdW90O1RoZSBoYXNoIGZ1bmN0aW9uIGFuZCB0aGUgbGVuZ3RoIG9mIHRoZSBoYXNoIHZhbHVl
IGFyZSBkZWZpbmVkPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqBpbiB0aGUgRE5DUCBwcm9maWxlLiZxdW90Ozxicj4NCjxicj4NCjxicj4NCsKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/CoCDCoCDCoCDCoCZxdW90O05ldHdvcmsgc3RhdGUgaGFz
aCZxdW90OyAtIHNhbWUgY29tbWVudCBhcyBmb3Igbm9kZSBzdGF0ZSAoYWJvdmUpPGJyPg0KPGJy
Pg0KwqAgwqAgwqAgwqAgRGF0YSBtb2RlbDo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBv
wqAgwqAgwqAgwqAmcXVvdDtMYXRlc3QgdXBkYXRlIHNlcXVlbmNlIG51bWJlciZxdW90Ozxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFRoaXMgbWF5IGp1c3QgYmUgbXkg
cGVyc29uYWwgdGFzdGUsIGJ1dCBkb2VzIGl0IGh1cnQgdG8gbWFuZGF0ZTxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGEgc3BlY2lmaWMgd2F5IG9mIGRvaW5nIHRoZSBs
b29waW5nIGNvbXBhcmlzb24/IFRoZSByZWFzb24gSTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIHN1Z2dlc3QgdGhpcyBpcywgdGhhdCBpdCYjMzk7cyBvbmUgb2YgdGhv
c2UgdGhpbmdzIHdoZXJlIGNyZWF0aXZpdHk8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBpbiBhbiBpbXBsZW1lbnRhdGlvbiBzZWVtcyB0byBzaW1wbHkgYmUgYW4gaW52
aXRhdGlvbiBmb3IgYnVncyw8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCBhbmQgZm9yIGxpdHRsZSBnYWluPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
b8KgIMKgIMKgIMKgJnF1b3Q7UmVsYXRpdmUgdGltZSBkZWx0YSZxdW90Ozxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIERvY3VtZW50IHRhbGtzIGFib3V0ICZxdW90O2Eg
MzIgYml0IG51bWJlciBvbiB0aGUgd2lyZSZxdW90OyAtLSBkb2VzIHRoYXQ8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBtZWFuIHRoYXQgd2lyZWxlc3MgbGlua3MgYXJl
IGV4Y2x1ZGVkPzxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/CoCDCoCDCoCDC
oFJlbGF0ZWQgdG8gdGVybWlub2xvZ3ksIHRoZXJlIHNlZW1zIHRvIGJlIHNvbWUgZnV6enluZXNz
IGFyb3VuZDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG5vZGUgYW5k
IGVuZHBvaW50LiBGb3IgZXhhbXBsZSwgaW4gZGF0YSBtb2RlbCBvbmUgb2YgdGhlIHRoaW5ncyB0
aGF0PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYSBETkNQIG5vZGUg
bWF5IGhhdmUgaXM6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgJnF1b3Q7VW5pY2FzdCBhZGRyZXNzOiB0aGUgRE5DUCBub2RlIGl0IHNo
b3VsZCBjb25uZWN0IHdpdGgmcXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCBEb2VzIHRoYXQgbWVhbiAqYW55KiBETkNQIHByb2Nlc3MgKGkuZS4sICph
bnkqIGVuZHBvaW50KSBhdCB0aGF0PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgYWRkcmVzcywgb3IgYSAqc3BlY2lmaWMqIEROQ1AgcHJvY2VzcyBhdCB0aGF0IGFkZHJl
c3M/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgVGhlIHNh
bWUsIGJ1dCBpbnZlcnNlLCBmb3IgJnF1b3Q7UmFuZ2Ugb2YgYWRkcmVzc2VzOiB0aGUgRE5DUCBu
b2RlcyB0aGF0PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYXJlIGFs
bG93ZWQgdG8gY29ubmVjdCZxdW90OyAtIGlzIHRoaXMgJnF1b3Q7YW55IERIQ1AgcHJvY2VzcyAo
aS5lLiwgKmFueSo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBlbmRw
b2ludCkgb24gYW55IG9mIHRoZXNlIGFkZHJlc3Nlcz88YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBGb2xsb3dpbmcsIHRoZSBzYW1lIHNlY3Rpb24gcmVhZHM6
PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgJnF1b3Q7Rm9yIGVhY2ggcmVtb3RlIChwZWVyLCBlbmRwb2ludCkgcGFpciBkZXRlY3RlZCBv
biBhIGxvY2FsPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgZW5kcG9pbnQsIGEgRE5DUCBub2RlIGhhcy4uLiZxdW90Ozxicj4NCjxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRoZSBmb2xsb3dpbmcgdGV4dCBpbmRpY2F0
aW5nIHRoYXQgdGhlcmUmIzM5O3Mgc29tZSBzb3J0IG9mIGRpc3RpbmN0aW9uPGJyPg0KwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYmV0d2VlbiB3aGljaCBlbmRwb2ludC48YnI+
DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBUaGlzIHdob2xlIHRo
aW5nIG5lZWRzIHNvbWUgY2xhcmlmaWNhdGlvbi48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCBPcGVy
YXRpb248YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBGaXJz
dCBhIGdlbmVyaWMgY29tbWVudCB0aGF0IFRyaWNrbGUgaXRzZWxmIGhhcyBzb21lIG9wZXJhdGlu
Zzxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGNvbmRpdGlvbnMgd2hp
Y2ggc2NvcGVzIGl0cyBhcHBsaWNhYmlsaXR5LCBhbmQgaXQgd291bGQgYmVob3ZlPGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhpcyBkb2N1bWVudCB0bywgaW4gaXRz
IG93biBhcHBsaWNhYmlsaXR5IHN0YXRlbWVudCwgY2FsbCBvdXQ8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB0aG9zZS48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCBvwqAgwqAgwqAgwqBPbiB0aGUgc2FtZSB0b2tlbiwgd2hpbGUgdGhlIHVzZSBvZiBU
cmlja2xlIGluIGFuIHVuaWNhc3QgZmFzaGlvbjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIGlzIHBvc3NpYmxlLCBJIHdvbmRlciBpZiAoaW4gZ2VuZXJhbCkgdW5pY2Fz
dCB1c2UgaXMgYWR2aWNhYmxlLiBJPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgYXBwcmVjaWF0ZSB0aGF0IHNvbWUgbGlua3MgYXJlIHBvaW50LXRvLXBvaW50IGFuZCBz
byBhIGJyb2FkY2FzdDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGFj
cm9zcyBpdCBiZWNvbWVzIGFuIHVuaWNhc3QgLS0gYnV0LCBkb2VzIHRoYXQgbmVjZXNzaXRhdGUg
YmVpbmc8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBjYWxsZWQgb3V0
Pzxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIElGIHRoZSBy
ZWFzb24gZm9yIHRoaXMgJnF1b3Q7YmVjYXVzZSB3ZSBjYW4gdXNlIFRDUCZxdW90OywgdGhlbiBi
ZSBleHBsaWNpdDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGFib3V0
IHRoaXMgLSBidXQsIGFsc28sIHRoYXQgeW91JiMzOTtyZSB0aGVuIG5vdCBleGFjdGx5IHVzaW5n
IFRyaWNrbGU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB3aGVyZSBh
bmQgaG93IGl0IHdhcyBpbnRlbmRlZC4gSSB3b25kZXIgaWYgeW91IGNvdWxkIGJlIGV4cGxpY2l0
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYXMgdG8gd2hhdCBjb25z
ZXF1ZW5jZXMgdGhpcyAmcXVvdDthbHRlcm5hdGUgdXNlIG9mIFRyaWNrbGUmcXVvdDsgaGF2ZT8g
SXQ8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBzZWVtcyB0aGF0IHRo
ZSB1c2Ugb2YgdW5pY2FzdCBpcyBkaXJlY3RseSBjb250cmFkaWN0aW5nIHRoZSBtYWluPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb3BlcmF0aW5nIGNvbnNpZGVyYXRp
b24gb2YgVHJpY2tsZT88YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAg
wqAgwqAybmQgcGFyYWdyYXBoIHN0YXRlczo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDt0aGUgbXVsdGljYXN0IHRyYW5zcG9y
dCBkb2VzIG5vdCBoYXZlIHRvIGJlIHBhcnRpY3VsYXJseTxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgc2VjdXJlJnF1b3Q7PGJyPg0KPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgV2hhdCBpcyB0aGUgZGVmaW5pdGlv
biBvZiAmcXVvdDtub3QgaGF2ZSB0byBiZSBwYXJ0aWN1bGFybHkgc2VjdXJlJnF1b3Q7Pzxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIElzIGNsZWFydGV4dCBPSz8gQXV0
aGVudGljYXRpb24/IEVuY3J5cHRpb24/PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgU2hvdWxkIEkgZG8gc29tZXRoaW5nIG1vcmU/PGJyPg0KPGJyPg0KwqAgwqAgwqAg
wqAgNS4xIFRyaWNrbGUtZHJpdmVuIHN0YXR1cyB1cGRhdGVzPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgb8KgIMKgIMKgIMKgRmlyc3QgcGFyYWdyYXBoOjxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O011bHRpY2FzdCBN
VVNUIGJlIGVtcGxveWVkIG9uIGEgbXVsdGljYXN0LWNhcGFibGUgaW50ZXJmYWNlOzxicj4NCsKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgb3RoZXJ3aXNl
LCB1bmljYXN0IGNhbiBiZSB1c2VkIGFzIHdlbGwmcXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBJZiB0aGUgaW50ZXJmYWNlIGlzIG5vdCBtdWx0aWNh
c3QtY2FwYWJsZSwgdGhlbiB1bmljYXN0IGNhbiBiZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIHVzZWQgYXMgd2VsbCBhcyB3aGF0PyBDZXJ0YWlubHkgbm90IG11bHRp
Y2FzdCwgc2luY2UgdGhlIGludGVyZmFjZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIGlzIG5vdCBtdWx0aWNhc3QgY2FwYWJsZS4uLj88YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBDb250aW51aW5nOjxicj4NCjxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O0lmIHBvc3Np
YmxlLCBtb3N0IHJlY2VudCwmcXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCBXaGF0IHdvdWxkIG1ha2UgaXQgJnF1b3Q7bm90IHBvc3NpYmxlJnF1b3Q7
Pzxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgICZxdW90O3JlY2VudGx5IGNoYW5nZWQsIG9yIGJlc3Qgb2YgYWxsLCBhbGwga25vd24gTm9k
ZSBTdGF0ZSBUTFZzJnF1b3Q7PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgT0ssIHNvIGFzc3VtaW5nIHRoYXQgZm9yIHNvbWUgcmVhc29uIChNVFUgbGltaXRh
dGlvbikgaXQgaXMgbm90PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
cG9zc2libGUsIGRvZXMgdGhlIGFib3ZlIHJlcHJlc2VudCBhbiBvcmRlciB0aGF0IEkgTVVTVCBy
ZXNwZWN0LDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG9yIGlzIGl0
ICZxdW90O3Rha2UgYSBwaWNrIGZyb20gYW1vbmcgdGhlc2UsIGFjY29yZGluZyB0byB5b3VyIHdo
aW0gb2Y8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB0aGUgZGF5JnF1
b3Q7Pzxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgICZxdW90OyhTZWN0aW9uIDcuMi4zKSBTSE9VTEQgYmUgYWxzbyBpbmNsdWRlZCwmcXVv
dDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBTSE9VTEQg
aXMgYSBzdHJvbmcgc3RhdGVtZW50LCBlc3BlY2lhbGx5IHdoZW4gcHJlZml4ZWQgYnk8YnI+DQrC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtpZiBwb3NzaWJsZSZxdW90
Oy4gVGhhdCwgZXNzZW50aWFsbHksIHJlbmRlcnMgaXQgYSBNQVkuPGJyPg0KPGJyPg0KwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7dW5sZXNzIGl0
IGlzIGRlZmluZWQgYXMgdW5kZXNpcmFibGUgZm9yIHNvbWUgcmVhc29uPGJyPg0KwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBieSB0aGUgRE5DUCBwcm9m
aWxlPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgTm93IGl0
IERFRklOSVRFTFkgaXMgYSBNQVkgc2luY2UgYXBwYXJlbnRseSBhIHByb2ZpbGUgY2FuIHN0YXRl
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhhdCB0aGVzZSBUTFZz
IE1VU1QgTk9UIGJlIGluY2x1ZGVkIC0tIGFuZCwgSSBhc3N1bWUsIHNpbmNlIHRoZTxicj4NCsKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGRvY3VtZW50IHBlcm1pdHMgaXQgdG8g
ZG8gc28sIGl0IGlzIHBvc3NpYmxlIHdpdGhvdXQgYnJlYWtpbmcgdGhlPGJyPg0KwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYWxnb3JpdGhtLjxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIG/CoCDCoCDCoCDCoEFuZCwgY29udGludWluZyBhZ2Fpbjo8YnI+DQo8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVv
dDtJZiB0aGU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoEROQ1AgcHJvZmlsZSBzdXBwb3J0cyBkZW5zZSBicm9hZGNhc3QgbGluayBvcHRpbWl6
YXRpb248YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoChTZWN0aW9uIDYuMiksIGFuZCBpZiBhIG5vZGUgZG9lcyBub3QgaGF2ZSB0aGUgaGlnaGVz
dCBub2RlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqBpZGVudGlmaWVyIG9uIGEgbGluaywgdGhlIGVuZHBvaW50IG1heSBiZSBpbiBhIHVuaWNh
c3QgbW9kZSBpbjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgd2hpY2ggbXVsdGljYXN0IHRyYWZmaWMgaXMgb25seSBsaXN0ZW5lZCB0by7CoCBJ
biB0aGF0IG1vZGUsPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqBtdWx0aWNhc3QgdXBkYXRlcyBNVVNUIE5PVCBiZSBzZW50LiZxdW90Ozxicj4N
Cjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFJlYWxseSBoYXJkIHRv
IHBhcnNlLiBJcyB0aGF0IG5vdCBlcXVpdmFsZW50IHRvIHNheWluZzo8YnI+DQo8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtJZiBhIERO
Q1AgZW5kcG9pbnQgaXMgbm90IGNvbmZpZ3VyZWQgdG8gYmUgaW4gbXVsdGljYXN0PGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgbW9kZSwgdGhl
biBpdCBNVVNUIE5PVCBzZW5kIG11bHRpY2FzdCB1cGRhdGVzJnF1b3Q7PGJyPg0KPGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgPzxicj4NCjxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIElmIGl0IGlzLCB0aGVuIHNheSB0aGF0IC0tIGlmIGl0
IGlzIG5vdCwgdGhlbiBhIHJld3JpdGUgaXMgbmVlZGVkLDxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIGFzIHRoYXQmIzM5O3Mgd2hhdCBJIG1hbmFnZSB0byBleHRyYWN0
IGZyb20gdGhlIHRleHQuPGJyPg0KPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgNS4yLsKgIFByb2Nl
c3Npbmcgb2YgUmVjZWl2ZWQgVExWczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/CoCDC
oCDCoCDCoEZpcnN0IHBhcmFncmFwaCByZWFkczo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtUaGUgRE5DUCBwcm9maWxlIG1h
eSBzcGVjaWZ5IGNyaXRlcmlhIGJhc2VkIG9uIHdoaWNoIHBhcnRpY3VsYXI8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoFRMVnMgYXJlIGlnbm9y
ZWQuJnF1b3Q7PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
Q3JpdGVyaWEgZm9yIHdoYXQ/IERvIHlvdSBwZXJoYXBzIG1lYW46PGJyPg0KPGJyPg0KwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7VGhlIEROQ1Ag
cHJvZmlsZSBtYXkgc3BlY2lmeSB3aGljaCBUTFZzIHRvIHByb2Nlc3MsIGFuZDxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgd2hpY2ggdG8gaWdu
b3JlJnF1b3Q7Pzxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IEF1eGlsaWFyeSBxdWVzdGlvbiwgdGhlbiwgYW5kIHJlbGF0ZWQgdG8gbXkgcGVudWx0aW1hdGUg
Y29tbWVudDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHRvIDUuMSwg
YXJlIHRoZXJlIGFueSBjb25zdHJhaW50cyBvbiB0aGF0LCBhbnkgcmlza3MgZnJvbSBpZ25vcmlu
Zzxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIChvciBub3QpIHNwZWNp
ZmljIFRMVnMgdG8gdGhlIG9wZXJhdGlvbiBvZiB0aGUgbmV0d29yaz88YnI+DQo8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBJIGFtIGFsc28gY29uZnVzZWQgYnkgdGhl
IDNyZCBzZW50ZW5jZSBpbiB0aGUgZmlyc3QgcGFyYWdyYXBoOjxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O0FueSDigJlyZXBs
eeKAmSBtZW50aW9uZWQgaW4gdGhlIHN0ZXBzIGJlbG93IGRlbm90ZXMgc2VuZGluZyBvZjxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgdGhlIHNw
ZWNpZmllZCBUTFYocykgdmlhIHVuaWNhc3QgdG8gdGhlIG9yaWdpbmF0b3Igb2YgdGhlIFRMVjxi
cj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgYmVp
bmcgcHJvY2Vzc2VkLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgVGhpcyBjb25mdXNpb24gaXMgbGlrZWx5IGR1ZSB0byB0aGUgbGFjayBvZiBh
ICZxdW90O3Byb3RvY29sIG92ZXJ2aWV3PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqBhbmQgZnVuY3Rpb25pbmcmcXVvdDsgZGVzY3JpcHRpb24gW2VpdGhlciBhcyBp
dHMgb3duIHNlY3Rpb24sIG9yIGFzIHBhcnQ8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoG9mIHRoZSBpbnRyb2R1Y3Rpb25dLjxicj4NCjxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgSSBrbm93IGhvdyB0cmlja2xlIHdvcmtzLiBUcmlj
a2xlIGlzIGEgZGlzdHJpYnV0ZWQgY29uc2lzdGVuY3k8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoGFsZ29yaXRobS4gV2hlbiBhbiBpbmNvbnNpc3RlbmN5IGlzIGRl
dGVjdGVkLCB0aGVuIGFuIGFjdGlvbiBpczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgdHJpZ2dlcmVkIHRoYXQgcmVjdGlmaWVzIHRoYXQgaW5jb25zaXN0ZW5jeS7C
oCBETkNQIGNsYWltcyB0byBiZSB0cmlja2xlIGJhc2VkLCBidXQgYXBwYXJlbnRseSBhbHNvIGEg
c29ydCBvZiByZXF1ZXN0L3JlcGx5PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqBtZWNoYW5pc20uIENvbWJpbmVkIHdpdGggdHJpY2tsZS1vdmVyLXVuaWNhc3QtbGlu
a3MsIEkgYW0gbm90IHN1cmU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoHdoYXQgdGhlIHByb3RvY29sIGxvZ2ljIGFjdHVhbGx5IGlzLiBSZWFkaW5nIHRocm91Z2gg
dG8gdGhlIGVuZCBvZjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
U2VjdGlvbiA1LCBJIHRoaW5rIHRoYXQgSSB1bmRlcnN0YW5kIHRoZSBpZGVhLCBidXQgSSBhbSBu
b3Qgc3VyZS48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oEFuZCB0aGUgb2xkICZxdW90O3doZW4gaW4gZG91YnQsIGxvb2sgYXQgdGhlIHN0YXRlIG1hY2hp
bmVzJnF1b3Q7IGRpZG4mIzM5O3QgaGVscDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgZWl0aGVyLCB0aGVyZSBhcmVuJiMzOTt0IGFueS48YnI+DQo8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoFRoZSBwb2ludCB0byB0aGlzIGNvbW1l
bnQgaXMsIHRoYXQgdGhlIGRvY3VtZW50IGltbWVkaWF0ZWx5IGp1bXBzPGJyPg0KwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBpbnRvIHRoZSBkZXRhaWxzIC0tIGJ1dCBmb3Jn
ZXRzIHRvIGdpdmUgdGhlICZxdW90OzEwMDAwZnQgdmlldyZxdW90OyBvZiB0aGU8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoHByb3RvY29sIGZ1bmN0aW9uaW5nLjxi
cj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/CoCDCoCDCoCDCoEZpcnN0IHBhcmFn
cmFwaCBzdGF0ZXMgdHdvIFNIT1VMRC4gV291bGQgdGhvc2Ugbm90IGJlIE1VU1Q/IFdoYXQ8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBicmVha3MgaWYgbm90IHJlc3Bl
Y3RpbmcgdGhvc2UgY3JpdGVyaWE/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
b8KgIMKgIMKgIMKgMm5kIHBhcmFncmFwaCwgYSAmcXVvdDt2YWxpZCBhZGRyZXNzJnF1b3Q7LCB0
aGF0IGRlZmluaXRpb24gaXMgcmF0aGVyIHVuY2xlYXIuPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgSSB1bmRlcnN0YW5kIHRoYXQgdGhhdCYjMzk7cyBzb21ldGhpbmcg
c3BlY2lmaWVkIGluICZxdW90O3RoZSBwcm9maWxlJnF1b3Q7LCBidXQ8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB3aGF0IGlzIHRoZSByZWxhdGlvbnNoaXAgdG8gdGhl
IGRpZmZlcmVudCBhZGRyZXNzZXMgZGlzY3Vzc2VkIGluPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgdGhlIGRhdGEgbW9kZWwgc2VjdGlvbj88YnI+DQo8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBJdCBpcyBub3QgY2xlYXIgd2hhdCB0aGUg
cGFyZW50aGVzaXMgdG8gdGhpcyBwYXJhZ3JhcGggbWVhbnMsPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgYnV0IHRoYXQgaXMgcHJvYmFibHkgYWdhaW4gYSBjYXNlIG9m
IHRoZSAmcXVvdDt1c2UgY2FzZSZxdW90OyBhbmQgJnF1b3Q7cHJvdG9jb2w8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvdmVydmlldyZxdW90OyBub3QgYmVpbmcgZG9j
dW1lbnRlZCAtIHRoZSBkb2N1bWVudCBzbyBmYXIgaGFzIG5vd2hlcmU8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBkZXNjcmliZWQgaW50ZXJhY3Rpb24gd2l0aCBvdXRz
aWRlIHByb2Nlc3Nlcy48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAg
wqAgwqBGaXJzdCBidWxsZXQsIGJ1dCBnZW5lcmFsbHkgdGhyb3VnaCB0aGVzZSwgYW5kIG90aGVy
LCBidWxsZXRzOjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IEkgaGFkIGEgcmVhbGx5IGhhcmQgdGltZSBkZWNpcGhlcmluZyB0aGlzLiBGaXJzdDo8YnI+DQo8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVv
dDtUaGUgcmVjZWl2ZXIgTVVTVCByZXBseTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgd2l0aCBhIE5ldHdvcmsgU3RhdGUgVExWIChTZWN0aW9uIDcuMi4yKSBhbmQg
YSBOb2RlIFN0YXRlIFRMVjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgKFNlY3Rpb24gNy4yLjMpIGZvciBlYWNoIG5vZGUgZGF0YSB1c2VkIHRvIGNhbGN1bGF0ZSB0
aGU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoG5ldHdvcmsgc3Rh
dGUgaGFzaCZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIEFs
cmlnaHQsIG9mZiB0byBmaW5kICZxdW90O25ldHdvcmsgc3RhdGUgaGFzaCZxdW90Oy48YnI+DQo8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBUaGUgdGVybWlub2xvZ3kgdGVsbHMg
bWUgdGhhdCBpdCBpczo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCAmcXVvdDthIGhhc2ggdmFsdWUgd2hpY2ggcmVwcmVzZW50cyB0aGUgY3VycmVudCBzdGF0
ZSBvZjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgdGhlIG5ldHdvcmsuwqAgVGhlIGhhc2ggZnVuY3Rpb24gYW5kIHRoZSBudW1iZXIgb2Y8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoGJpdHMgdXNlZCBhcmUgZGVmaW5lZCBpbiB0aGUg
RE5DUCBwcm9maWxlLjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgV2hlbmV2ZXIgYSBu
b2RlIGlzIGFkZGVkLCByZW1vdmVkIG9yIHVwZGF0ZXMgaXRzPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqBwdWJsaXNoZWQgbm9kZSBkYXRhIHRoaXMgaGFzaCB2YWx1ZSBjaGFuZ2VzIGFz
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqB3ZWxsLiBJdCBpcyBjYWxjdWxhdGVkIG92
ZXIgZWFjaCByZWFjaGFibGUgbm9kZXMmIzM5Ozxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgdXBkYXRlIG51bWJlciBjb25jYXRlbmF0ZWQgd2l0aCB0aGUgaGFzaCB2YWx1ZSBvZjxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgaXRzIG5vZGUgZGF0YS4gRm9yIGNhbGN1bGF0aW9u
IHRoZXNlIHR1cGxlcyBhcmU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoHNvcnRlZCBp
biBhc2NlbmRpbmcgb3JkZXIgb2YgdGhlIHJlc3BlY3RpdmUgbm9kZSYjMzk7czxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgbm9kZSBpZGVudGlmaWVyLjxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIFNlYXJjaGluZyBmdXJ0aGVyLCBJIGZpbmQgU2VjdGlvbiA1
LjEsIGJ1dCB0aGF0IHNpbXBseSBzdGF0ZXM6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7VGhlIFRyaWNrbGUgc3RhdGUgZm9yIGFsbCBlbmRwb2lu
dHMgaXM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoGNv
bnNpZGVyZWQgaW5jb25zaXN0ZW50IGFuZCByZXNldCBpZiBhbmQgb25seSBpZiB0aGUgbG9jYWxs
eTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgY2FsY3Vs
YXRlZCBuZXR3b3JrIHN0YXRlIGhhc2ggY2hhbmdlcy4mcXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBOZXh0IG9jY3VyZW5jZSBpcyBpbiB0aGVzZSBi
dWxsZXRzLCBhbmQgdGhlbiBqdXN0IGJlZm9yZSBTZWN0aW9uIDYsPGJyPg0KPGJyPg0KwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7RHVyaW5nPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqB0aGUgZ3JhY2Ug
cGVyaW9kLCB0aGUgbm9kZXMgdGhhdCB3ZXJlIG5vdCBtYXJrZWQgcmVhY2hhYmxlPGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBpbiB0aGUgbW9zdCByZWNl
bnQgZ3JhcGggdHJhdmVyc2FsIE1VU1QgTk9UIGJlIHVzZWQgZm9yPGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBjYWxjdWxhdGlvbiBvZiB0aGUgbmV0d29y
ayBzdGF0ZSBoYXNoLCBiZSBwcm92aWRlZCB0byBhbnk8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoGFwcGxpY2F0aW9ucyB0aGF0IG5lZWQgdG8gdXNlIHRo
ZSB3aG9sZSBUTFYgZ3JhcGgsIG9yIGJlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqBwcm92aWRlZCB0byByZW1vdGUgbm9kZXMuJnF1b3Q7PGJyPg0KPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgQWxyaWdodCwgbm93IEkga25v
dyB3aGF0IEkgY2FuJiMzOTt0IHVzZSBmb3IgY2FsY3VsYXRpbmcgaXQuPGJyPg0KPGJyPg0KwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgQSBmZXcgb2NjdXJlbmNlcyBsYXRlciwg
aW4gc2VjdGlvbiA3LjIuMiwgaW4gd2hhdCBsb29rcyBsaWtlIGE8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBzZWN0aW9uIGxheWluZyBvdXQgdGhlIHBhY2tldCAtLSBz
b3JyeSwgVExWIC0tIGZvcm1hdCwgSSBzZWUgZm9yPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgJnF1b3Q7TmV0d29yayBTdGF0ZSBUTFYmcXVvdDs6PGJyPg0KPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7VGhp
cyBUTFYgY29udGFpbnMgdGhlIGN1cnJlbnQgbG9jYWxseSBjYWxjdWxhdGVkIG5ldHdvcmsgc3Rh
dGU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBo
YXNoLiBJdCBpcyBjYWxjdWxhdGVkIG92ZXIgZWFjaCByZWFjaGFibGUgbm9kZXMmIzM5OyB1cGRh
dGUgbnVtYmVyPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgY29uY2F0ZW5hdGVkIHdpdGggdGhlIGhhc2ggdmFsdWUgb2YgaXRzIG5vZGUgZGF0YSBp
biBhc2NlbmRpbmc8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCBvcmRlciBvZiB0aGUgcmVzcGVjdGl2ZSBub2RlIGlkZW50aWZpZXJzJnF1b3Q7PGJy
Pg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgUGhldy4gTm93LCBp
dCBkb2VzIHNlZW0gYSBsaXR0bGUgYXQgb2RkcyB3aXRoIHRoZSB0ZXJtaW5vbG9neS4gVGhlPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGVybWlub2xvZ3kgc3RhdGVz
IHNvbWV0aGluZyBhYm91dCB0dXBsZXMgdGhhdCBhcmUgb3JkZXJlZC4gV2hpbGU8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB0aG9zZSB0dXBsZXMgYXJlIG5vdCBkZWZp
bmVkICh0aGV5IHNob3VsZCBiZSksIGF0IGxlYXN0IHdoYXQgaXM8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBkZXNjcmliZWQgaXMgY2xlYXIgYW5kIHBvc3NpYmx5IGNh
biBiZSBpbXBsZW1lbnRlZC4gV2hhdCBpcyBpbiA3LjIuMjxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIGlzIG5vdCBhbnQgY2Fubm90Ljxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFRoaXMgaXMgYW4gaW5zdGFuY2Ugb2YgYSBnZW5l
cmFsIGlzc3VlIHRoYXQgSSBoYXZlIHdpdGggdGhpczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIGRvY3VtZW50OiB0aGF0IGl0IGRvZXNuJiMzOTt0IHRha2UgYSBzdGVw
IGJhY2ssIGFuZCBwcm9wZXJseSBkZWZpbmU8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCB0aGluZ3MgaW4gYSBwcm9wZXIgb3JkZXIsIGJ1dCBkaXZlcyBpbnRvIChhbmQg
cmVwZWF0cykgZGV0YWlscy48YnI+DQo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCBvwqAgwqAgwqAgwqBBbHNvIHRvIHNlY3Rpb24gNS4yLCBmb3IgZWFjaCBvZiB0aGUgY2FzZXMg
dGhhdCBhcmUgZGVzY3JpYmVkLCBjb3VsZDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIGEgY29uY2VwdHVhbCBkZXNjcmlwdGlvbiBvZiAmcXVvdDt3aGF0IHRoaXMgY29y
cmVzcG9uZHMgdG8mcXVvdDsgYmUgYWRkZWQ/IEZvcjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIGV4YW1wbGU6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgVXBvbiByZWNpZXB0IG9mIGEgTm9kZSBTdGF0ZSBU
TFY6PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgSWYgdGhlIG5vZGUgaWRlbnRpZmllciBtYXRjaGVzIHRoZSBsb2NhbCBub2Rl
IGlkZW50aWZpZXIgYW5kPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhlIFRMViBoYXMgYSBoaWdoZXIgdXBkYXRlIHNlcXVl
bmNlIG51bWJlciB0aGFuIGl0cyBjdXJyZW50PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgbG9jYWwgdmFsdWUsIG9yIHRoZSBzYW1lIHVwZGF0ZSBzZXF1ZW5jZSBudW1i
ZXIgYW5kIGE8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBkaWZmZXJl
bnQgaGFzaCwgdGhlIG5vZGUgU0hPVUxEIHJlLXB1Ymxpc2ggaXRzIG93biBub2RlIGRhdGE8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCB3aXRoIGFuIHVwZGF0ZSBzZXF1
ZW5jZSBudW1iZXIgMTAwMCBoaWdoZXIgdGhhbiB0aGUgcmVjZWl2ZWQ8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvbmUuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgSXQmIzM5O3Mgbm90IGNsZWFyIHdoeSBpdCBpcyBhICZxdW90
O1NIT1VMRCByZS1wdWJsaXNoJnF1b3Q7IChub3QgTVVTVCwgbm9yIHdoYXQ8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBoYXBwZW5zIGlmIFNIT1VMRCBpcyBub3QgZm9s
bG93ZWQpLiBBbmQgaXQgaXMgbm90IGNsZWFyIHdoeSAxMDAwIC4uLjxicj4NCjxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFtJIGp1c3QgcGljayB0aGlzIGV4YW1wbGUs
IGJ1dCBpdCBhcHBsaWVzIHRvIGFsbCBwcm9jZXNzaW5nIGJ1bGxldHNdPGJyPg0KPGJyPg0KwqAg
wqAgwqAgwqAgb8KgIMKgIMKgIMKgSW4gdGhlIHNhbWUgY2FzZXMsIGl0IGlzIGEgbG90IG1vcmUg
cmVhZGFibGUgKElNTykgdG8gZG8gbmVzdGVkIGJ1bGxldHM6PGJyPg0KPGJyPg0KwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgSWYgRk9POyBhbmQgZWl0aGVyIG9mOjxicj4NCsKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIC0gQkFSPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgLSBHTllGPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgLSBCTEFC
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgVGhlbiBkbyBhbGwgb2Yg
dGhlIGZvbGxvd2luZzo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCAtIC4uLjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIC0gLi4uPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgLSAuLi48YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBvwqAgwqAg
wqAgwqBPdGhlcndpc2UsIGlmIG5vdC1GT08sIC4uLjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIFRoYXQmIzM5O3MgYSBwZXJzb25hbCBwcmVmZXJlbmNlLCB0aG91Z2gsIHNvIGZl
ZWwgZnJlZSB0byBkaXNyZWdhcmQgdGhpczxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIGNv
bW1lbnQuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqBvwqAgwqAgwqAgU2VjdGlvbiA1LjMgYW5k
IGVsc2V3aGVyZSwgc3VnZ2VzdCByZXBsYWNpbmc6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7SWYgaXQgY29tZXMgdmlhLi4uJnF1b3Q7PGJyPg0K
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgYnk6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7SWYgcmVjZWl2ZWQgb3ZlciAuLi4mcXVvdDs8
YnI+DQo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBMYXN0IHBhcmFncmFwaCBp
biA1LjM6PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgU2FtZSBjb21t
ZW50IGFzIDNyZCBjb21tZW50IHRvIDUuMSBtYWRlIGFib3ZlLjxicj4NCjxicj4NCsKgIMKgIMKg
IMKgIG/CoCDCoCDCoCDCoFNlY3Rpb24gNS40LCBmaXJzdCBzZW50ZW5jZTo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtETkNQIHZhbGlkYXRlcyB0aGUgc2V0
IG9mIGRhdGEgd2l0aGluIGl0IC4uLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIFNob3VsZCB0aGF0IG5vdCBiZTo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCAmcXVvdDtBIEROQ1AgaW5zdGFuY2UgdmFsaWRhdGVzIHRoZSBkYXRhIHdpdGhp
biBpdHMgZGF0YSBzZXRzIC4uLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgID88YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBBbHNvLCAmcXVvdDtub2Rl
cyB0aGF0IGFyZSBjdXJyZW50bHkgYWNjb3VudGVkIGZvcjsgd2hhdCYjMzk7cyB0aGUgZGVmaW5p
dGlvbjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG9mICZxdW90O2FjY291bnRlZCBmb3Im
cXVvdDs/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgU2VjdGlvbiA1LjQsIGZp
cnN0IHBhcmFncmFwaDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFRoZSBzdGF0ZW1lbnQ6
PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7dGhl
cmVmb3JlLDxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgdW5saWtl
IFRpbWUtVG8tTGl2ZSAoVFRMKSBiYXNlZCBzb2x1dGlvbnMsIGl0IGRvZXMgbm90IHJlcXVpcmU8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoHBlcmlvZGljIHJlLXB1Ymxpc2hp
bmcgb2YgdGhlIGRhdGEgYnkgdGhlIG5vZGVzLsKgIE9uIHRoZSBvdGhlcjxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgaGFuZCwgaXQgZG9lcyByZXF1aXJlIHRoZSB0b3BvbG9n
eSB0byBiZSB2aXNpYmxlIHRvIGV2ZXJ5IG5vZGUgdGhhdDxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgd2FudHMgdG8gYmUgYWJsZSB0byBpZGVudGlmeSB1bnJlYWNoYWJsZSBu
b2RlcyBhbmQgdGhlcmVmb3JlIHJlbW92ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgb2xkLCBzdGFsZSBkYXRhLiZxdW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIHdoaWNoIGFsc28gYXBwZWFyZWQgaW4gdGhlIGludHJvZHVjdGlvbiwgaXMgY29waWVk
IHZlcmJhdGltbHkuIE9uY2U8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBtb3JlLCB0aGUg
c3RhdGVtZW50IGlzIGEgY2xhaW0gd2hpY2ggaXMgbm90IHN1cHBvcnRlZCwgYW5kIHRoYXQgd2hp
Y2g8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBmb2xsb3dzICZxdW90O3RoZXJlZm9yZSZx
dW90OyBpcyBub3QgYSBjb25zZXF1ZW5jZSBvZiB0aGF0IHdoaWNoIGNvbWVzIGJlZm9yZTxicj4N
CsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgICZxdW90O3RoZXJlZm9yZSZxdW90Oy48YnI+DQo8YnI+
DQrCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBTZWN0aW9uIDUuNCwgZmlyc3QgcGFyYWdyYXBoPGJy
Pg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7V2hlbiBh
IE5laWdoYm9yIFRMViBvciBhIHdob2xlIG5vZGUgaXMgYWRkZWQgb3IgcmVtb3ZlZCwgdGhlPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgbmVpZ2hib3IgZ3JhcGggU0hP
VUxEIGJlIHRyYXZlcnNlZCwgc3RhcnRpbmcgZnJvbSB0aGUgbG9jYWwgbm9kZS48YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBUaGUgZWRnZXMgdG8gYmUgdHJhdmVyc2Vk
IGFyZSBpZGVudGlmaWVkIGJ5IGxvb2tpbmcgZm9yIE5laWdoYm9yPGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgVExWcyBvbiBib3RoIG5vZGVzLCB0aGF0IGhhdmUgdGhl
IG90aGVyIG5vZGXigJlzIGlkZW50aWZpZXIgaW4gdGhlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgbmVpZ2hib3Igbm9kZSBpZGVudGlmaWVyLCBhbmQgbG9jYWwgYW5k
IG5laWdoYm9yIGVuZHBvaW50PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgaWRlbnRpZmllcnMgc3dhcHBlZC4gRWFjaCBub2RlIHJlYWNoZWQgc2hvdWxkIGJlIG1hcmtl
ZCBjdXJyZW50bHk8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCByZWFj
aGFibGUuJnF1b3Q7PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgRmlyc3QgY29t
bWVudCwgd2h5IFNIT1VMRCBhbmQgbm90IE1VU1Q/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAg
wqAgwqAgwqAgU2Vjb25kIGNvbW1lbnQsIGFuZCBub3cgeW91IG1hZGUgbWUgZ28gbG9vay4uLi4m
cXVvdDtuZWlnaGJvciZxdW90OyBzb3VuZHMgbGlrZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgICZxdW90O3NvbWVvbmUgb24gdGhlIHNhbWUgbGluayBhcyBtZSZxdW90OyBzb8KgIHRoZSAm
cXVvdDtuZWlnaGJvciBncmFwaCZxdW90OyBpcyByZWFsbHkganVzdDxicj4NCsKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIGEgc2V0IHJlbGF0aW5nICZxdW90O3RoaXMgbm9kZSZxdW90OyBhbmQgJnF1
b3Q7YW5vdGhlciBub2RlIHdoaWNoIGlzIG9uIHRoZSBzYW1lIGxpbms8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCBhcyB0aGlzIG5vZGUmcXVvdDsuPGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgWWV0LCBsb29raW5nIGluIHRoZSB0ZXJtaW5vbG9neSwgSSBzZWUgJnF1b3Q7
TmVpZ2hib3IgZ3JhcGgmcXVvdDsgZGVmaW5lZCBhczo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDt0aGUgdW5kaXJlY3RlZCBncmFwaCBv
ZiBETkNQIG5vZGVzIHByb2R1Y2VkIGJ5PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqBy
ZXRhaW5pbmcgb25seSBiaWRpcmVjdGlvbmFsIHBlZXIgcmVsYXRpb25zaGlwczxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgYmV0d2VlbiBub2Rlcy48YnI+DQo8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCBXaGljaCBkb2VzbiYjMzk7dCBzb3VuZCBhcyBtdWNoIGxpa2UgYSAmcXVv
dDtuZWlnaGJvciBncmFwaCZxdW90OyBhcyBpdCBkb2VzIGE8YnI+DQrCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCAmcXVvdDt0b3BvbG9neSBncmFwaCZxdW90OyBmb3IgdGhlIHdob2xlIG5ldHdvcmsu
PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgU28sIGlzIHRoZSB0ZXJtaW5vbG9n
eSB3cm9uZywgb3IgaXMgdGhlIGRlZmluaXRpb24gd3Jvbmc/PGJyPg0KPGJyPg0KwqAgwqAgwqAg
wqAgb8KgIMKgIMKgIMKgU2VjdGlvbiA1LjQsIDNyZCBwYXJhZ3JhcGg8YnI+DQo8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCBJcyBpdCBhY3R1YWxseSBpbXBvcnRhbnQgdGhhdCB0aGUgY29u
dGVudCBvZiB0aGF0IGdyYXBoIGJlICZxdW90O3B1cmdlZCZxdW90Oz88YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCBUaGF0IHNvdW5kcyBsaWtlIGFuIGltcGxlbWVudGF0aW9uIGRldGFpbCAt
LSByYXRoZXIsIGl0IHNvdW5kcyBsaWtlPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgdGhl
IGVsZW1lbnRzIG9mIHRoZSBncmFwaCBzaG91bGQgJnF1b3Q7bm90IGJlIHVzZWQgZm9yIGNhbGN1
bGF0aW9ucyBhbmQ8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBNQVkgYmUgcmVtb3ZlZCZx
dW90Oy4gT3IsIGlzIHRoZXJlIGEgc3BlY2lmaWMgcmVxdWlyZW1lbnQgdGhhdCBJIGFtPGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgbWlzc2luZz88YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCBv
wqAgwqAgwqAgwqBTZWN0aW9uIDYuMSwgSSBkbyBub3QgdW5kZXJzdGFuZCB0aGUgcGFyZW50aGVz
aXMgaW4gdGhpcyBzZW50ZW5jZTo8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBUcmlja2xlLWRyaXZlbiBzdGF0dXMgdXBkYXRlcyAoU2VjdGlvbiA1LjEpIHBy
b3ZpZGUgYSBtZWNoYW5pc20gZm9yPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgwqAgaGFuZGxpbmcgb2YgbmV3IHBlZXIgZGV0ZWN0aW9uIChpZiBhcHBsaWNhYmxlKSBvbiBh
biBlbmRwb2ludDxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFVuZGVyIHdoYXQg
Y29uZGl0aW9ucyBpcyB0aGF0IGFwcGxpY2FibGUsIGFuZCB1bmRlciB3aGljaCBpcyBpdCBub3Q/
PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgU2VjdGlvbiA2LjI6PGJyPg0KPGJy
Pg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7QW4gdXBwZXIgYm91
bmQgZm9yIHRoZSBudW1iZXIgb2YgbmVpZ2hib3JzIHRoYXQgYXJlIGFsbG93ZWQgZm9yIGE8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoChwYXJ0aWN1bGFyIHR5cGUg
b2YpIGxpbmsgdGhhdCBhbiBlbmRwb2ludCBydW5zIG9uIFNIT1VMRCBiZTxicj4NCsKgIMKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgcHJvdmlkZWQgYnkgYSBETkNQIHByb2ZpbGUs
IHVzZXIgY29uZmlndXJhdGlvbiwgb3Igc29tZSBoYXJkY29kZWQ8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoGRlZmF1bHQgaW4gdGhlIGltcGxlbWVudGF0aW9uLiZx
dW90Ozxicj4NCjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIEEgY291cGxlIG9mIHRoaW5n
cyB0byB0aGF0Ojxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIDEpwqAg
wqAgwqAgQ2FuIHlvdSBleHBsYWluIHRoZSBwYXJlbnRoZXNpcz8gV2hhdCB0eXBlIG9mIGxpbms/
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgMinCoCDCoCDCoCBIb3cg
ZG9lcyAmcXVvdDthbiBlbmRwb2ludCBydW5zIG9uJnF1b3Q7IGEgbGluaz88YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAzKcKgIMKgIMKgIFdoeSBTSE9VTEQ/PGJyPg0K
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgNCnCoCDCoCDCoCBJcyB0aGlzIHNw
ZWNpZmljYXRpb24gc2VyaW91c2x5IHN1Z2dlc3RpbmcgJnF1b3Q7c29tZSBoYXJkY29kZWQ8YnI+
DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBkZWZhdWx0
IGluIHRoZSBpbXBsZW1lbnRhdGlvbiZxdW90OyBhcyBhIFNIT1VMRD88YnI+DQo8YnI+DQrCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCBbSSBhbSB0ZW1wdGVkIHRvIHVwZ3JhZGUgdGhpcyB0byBhICZx
dW90O01ham9yIGlzc3VlJnF1b3Q7IHNpbXBseSBiZWNhdXNlIG9mIDQpIF08YnI+DQo8YnI+DQo8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBBbHNvIHRvIDYuMiwgdGhpcyBwYXJ0aWN1bGFy
IG9wdGltaXphdGlvbiwgZG8geW91IGhhdmUgYW55PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAg
wqAgcXVhbnRpZmljYXRpb24gb2YgaXRzIGFjdHVhbCBiZW5lZml0PyBXaGF0IHNob3VsZCBJIGxv
b2sgZm9yIHRvPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgZGV0ZXJtaW5lIGlmIHRoaXMg
JnF1b3Q7b3B0aW1pemF0aW9uJnF1b3Q7IHlpZWxkcyBhIGJlbmVmaXQgb3Igbm90PyBXaGF0IGFy
ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHlvdSB0cnlpbmcgdG8gb3B0aW1pemU/IE92
ZXIgd2hhdCBsaW5rIHR5cGVzIGRvZXMgdGhpcyBmdW5jdGlvbj88YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBJIGFtIGR1YmlvdXMgdGhhdCBpdCAmcXVvdDtvcHRpbWl6ZXMmcXVvdDsgbXVj
aCwgaWYgYW55dGhpbmcsIGFjcm9zcyBhbiBFdGhlcm5ldCwgZm9yIGV4YW1wbGUgLi4uPGJyPg0K
PGJyPg0KwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgU2VjdGlvbiA3PGJyPg0KwqAgwqAgwqAgwqAg
wqAgwqAgwqAgwqAgQXMgaW5kaWNhdGVkIHByZXZpb3VzbHksIGhhdmluZyB0byBzZWFyY2ggdGhy
b3VnaCB0aGUgZnJhbWUgZm9ybWF0PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgZGlhZ3Jh
bXMgZm9yICZxdW90O2hvdyB0byBjYWxjdWxhdGUgdGhlIHZhbHVlJnF1b3Q7IGlzbiYjMzk7dCBp
ZGVhbC48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBTZWN0aW9uIDcuMi4zLCBJ
IHdvcnJ5IHdoZW4gSSBzZWUgc29tZXRoaW5nIGxpa2UgdGhpczo8YnI+DQo8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCAmcXVvdDtUaGUgd2hvbGUgbmV0d29yayBzaG91
bGQgaGF2ZSByb3VnaGx5IHRoZSBzYW1lIGlkZWEgYWJvdXQgdGhlIHRpbWU8YnI+DQrCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoHNpbmNlIG9yaWdpbmF0aW9uIG9mIGFueSBw
YXJ0aWN1bGFyIHB1Ymxpc2hlZCBzdGF0ZS4mcXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCBXaGF0IGlzIHRoZSBkZWZpbml0aW9uIG9mICZxdW90O3JvdWdobHkmcXVvdDs/
PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgSXMgdGhlICZxdW90O3Nob3VsZCZxdW90OyBp
bnRlbnRpb25hbGx5IGluIG5vbi1jYXBzPzxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIFdo
YXQmIzM5O3JlIHRoZSBjb25zZXF1ZW5jZXMgaWYgbm90Pzxicj4NCsKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIFtOb3RlIHRoYXQgdHJpY2tsZSBhbG1vc3QgbWVjaGFuaWNhbGx5IG1ha2VzIGluZm9y
bWF0aW9uIHByb3BhZ2F0ZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHdpdGggbm9uLXRy
aXZpYWwgaml0dGVyIGFjcm9zcyBhIG5ldHdvcmssIHNvIGhvdyBkbyB5b3UgZW5zdXJlIHRoaXM/
XTxicj4NCjxicj4NCsKgIMKgIMKgIMKgIG/CoCDCoCDCoCDCoFNlY3Rpb24gNy4yLjQsIENVU1RP
TS1EQVRBIFRMVi48YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBHaXZlbiB0aGUg
ZGVzY3JpcHRpb246PGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1
b3Q7VGhpcyBUTFYgY2FuIGJlIHVzZWQgdG8gY29udGFpbiBhbnl0aGluZzsgdGhlIFVSSSB1c2Vk
IHNob3VsZCBiZTxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgdW5k
ZXIgY29udHJvbCBvZiB0aGUgYXV0aG9yIG9mIHRoYXQgc3BlY2lmaWNhdGlvbi4mcXVvdDs8YnI+
DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBJdCBzZWVtcyB0aGF0IChpKSB0aGUgZGVz
Y3JpcHRpb24gaXMgc2VsZi1jb250cmFkaWN0b3J5OiBpdCBjYW5ub3Q8YnI+DQrCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCBjb250YWluICphbnl0aGluZyogYnV0IGNhbiBjb250YWluIGFuIFVSST88
YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBTZWNvbmRseSwgaG93IGlzIHRoaXMg
c3VwcG9zZWQgdG8gd29yaywgd2hhdCBkb2VzIGl0IG1lYW4gW2ZvciBETkNQXTxicj4NCsKgIMKg
IMKgIMKgIMKgIMKgIMKgIMKgIHRoYXQgJnF1b3Q7dGhlIFVSSSBpcyB1bmRlciBjb250cm9sIG9m
IHRoZSBhdXRob3ImcXVvdDs/PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgVGhp
cmRseSwgd2hhdCBkb2VzICZxdW90O3RoYXQgc3BlY2lmaWNhdGlvbiZxdW90OyByZWZlciB0bz88
YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBGb3VydGhseSwgd2h5IGxvd2VyLWNh
c2Ugc2hvdWxkPyBJbmRlZWQsIHdoeSBpcyB0aGUgJnF1b3Q7Y29udHJvbCZxdW90OyBvZiB0aGU8
YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBVUkkgb2YgYW55IGltcG9ydGFuY2UgdG8gRE5D
UD88YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCBvwqAgwqAgwqAgwqBTZWN0aW9uIDksIHRoZSBidWxs
ZXQ6PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgJnF1b3Q7
V2hlbiByZWNlaXZpbmcgbWVzc2FnZXMsIHdoYXQgc29ydCBvZiBtZXNzYWdlcyBhcmUgZHJvcHBl
ZCwgYXM8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBzcGVjaWZpZWQg
aW4gU2VjdGlvbiA1LjImcXVvdDs8YnI+DQo8YnI+DQrCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBT
ZWVtcyBhdCBvZGRzIHdpdGggU2VjdGlvbiA1LjIsIHdoaWNoIGRpc2N1c3NlcyBUTFYgcHJvY2Vz
c2luZy48YnI+DQo8YnI+DQo8YnI+DQpOaXRzOjxicj4NCjxicj4NCsKgIMKgIMKgIMKgIFJlcXVp
cmVtZW50IExhbmd1YWdlOjxicj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIG/CoCDCoCDCoCDC
oFBsZWFzZSByZWZsZWN0IEVycmF0YSA0OTkgZm9yIFJGQzIxMTkgaW4gdGhlIGJvaWxlcnBsYXRl
PGJyPg0KPGJyPg0KwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgb8KgIMKgIMKgIMKgVGhlIFJGQzIx
MTkgYm9pbGVycGxhdGUgY291bGQgY29udmVuaWVudGx5IGJlIGluIHRoZSB0ZXJtaW5vbG9neTxi
cj4NCsKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIHNlY3Rpb24sIGdpdmVuIHRo
YXQgaXQgaXMgdGVybWlub2xvZ3kuPGJyPg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX188YnI+DQpob21lbmV0IG1haWxpbmcgbGlzdDxicj4NCjxh
IGhyZWY9Im1haWx0bzpob21lbmV0QGlldGYub3JnIj5ob21lbmV0QGlldGYub3JnPC9hPjxicj4N
CjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaG9tZW5ldCIg
cmVsPSJub3JlZmVycmVyIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9ob21lbmV0PC9hPjxicj4NCjwvYmxvY2txdW90ZT48L2Rpdj48YnI+PC9k
aXY+PC9kaXY+DQo=
--001a113ed24c8434ce0518b1595a--


From nobody Wed Jun 17 09:37:52 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2651B29A9; Wed, 17 Jun 2015 09:37:49 -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
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 UllwoJqe2RXn; Wed, 17 Jun 2015 09:37:48 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0781B29D5; Wed, 17 Jun 2015 09:37:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150617163747.22885.8743.idtracker@ietfa.amsl.com>
Date: Wed, 17 Jun 2015 09:37:47 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Hm8dJfoHqk2bSw11aOJgtD6_8io>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2015 16:37:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Home Networking Control Protocol
        Authors         : Markus Stenberg
                          Steven Barth
                          Pierre Pfister
	Filename        : draft-ietf-homenet-hncp-06.txt
	Pages           : 31
	Date            : 2015-06-17

Abstract:
   This document describes the Home Networking Control Protocol (HNCP),
   an extensible configuration protocol and a set of requirements for
   home network devices on top of the Distributed Node Consensus
   Protocol (DNCP).  It enables automated configuration of addresses,
   naming, network borders and the seamless use of a routing protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-hncp/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-hncp-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-hncp-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Jun 17 09:40:33 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A13D71B2A74 for <homenet@ietfa.amsl.com>; Wed, 17 Jun 2015 09:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=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 zVC6qNQeI_MY for <homenet@ietfa.amsl.com>; Wed, 17 Jun 2015 09:40:30 -0700 (PDT)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.229]) by ietfa.amsl.com (Postfix) with ESMTP id 54FCD1B2A73 for <homenet@ietf.org>; Wed, 17 Jun 2015 09:40:30 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 552B87C904D20312 for homenet@ietf.org; Wed, 17 Jun 2015 19:40:29 +0300
Message-ID: <5581A2FB.8010108@iki.fi>
Date: Wed, 17 Jun 2015 19:40:27 +0300
From: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com>
In-Reply-To: <20150617163747.22885.8743.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/05Eud7hrOnaZtvkTNzOXMp_5ZAE>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2015 16:40:32 -0000

On 17.6.2015 19.37, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Home Networking Working Group of the IETF.
>
>          Title           : Home Networking Control Protocol
>          Authors         : Markus Stenberg
>                            Steven Barth
>                            Pierre Pfister
> 	Filename        : draft-ietf-homenet-hncp-06.txt
> 	Pages           : 31
> 	Date            : 2015-06-17
>
> Abstract:
>     This document describes the Home Networking Control Protocol (HNCP),
>     an extensible configuration protocol and a set of requirements for
>     home network devices on top of the Distributed Node Consensus
>     Protocol (DNCP).  It enables automated configuration of addresses,
>     naming, network borders and the seamless use of a routing protocol.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-homenet-hncp/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-homenet-hncp-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-hncp-06
>

We updated the HNCP draft based on WG chairs' comments (and some 
others). No operational changes. We consider it ready for WGLC, although 
it still could use either direct editing or further review by more people.

Updated DNCP draft will follow later this week, based on feedback from 
Thomas Clausen and some internal review.

Cheers,

-Markus


From nobody Fri Jun 19 14:02:46 2015
Return-Path: <eckelcu@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 525FA1AD368; Fri, 19 Jun 2015 12:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.311
X-Spam-Level: 
X-Spam-Status: No, score=-13.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_47=0.6, J_CHICKENPOX_71=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 PJydV_SUZocs; Fri, 19 Jun 2015 12:34:30 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6C191AD367; Fri, 19 Jun 2015 12:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1998; q=dns/txt; s=iport; t=1434742471; x=1435952071; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=11qvbHyRK7I9OeRE4eAt7qk7oBQDdZX5ORtAT9CnwRw=; b=O/DpiFOxnBfPX7UVd9cA8KzV4zqDhDC2dXG7A04aQxHreQ6Wi2qjHDp8 5EWXouLw95y5NB4VWqlqG4gBq4UGjYly5hPERy6fDsr0c1sN9KZcc0pih XZ+XVl2bgLw64212GGkfp3xZ102hVnzWB4g2Mi3Ln8fOaGgGXpqfRpNQ4 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AuBADHbYRV/4MNJK1SCoMQVF8GvXwJgVwKhS5KAoE+OBQBAQEBAQEBgQqEIwEBBAEBAWsLEAIBCEYnCyUCBAENBRuIFA3GCwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLRYQpKjMHhCsFk3wBhFWGeIE6QZJYg1smg3lvgUaBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.13,644,1427760000";  d="scan'208";a="8746910"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP; 19 Jun 2015 19:34:30 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t5JJYTKf003043 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 19 Jun 2015 19:34:29 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Fri, 19 Jun 2015 14:34:29 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Markus Stenberg <markus.stenberg@iki.fi>, "hackathon@ietf.org" <hackathon@ietf.org>
Thread-Topic: [hackathon] homenet in Hackathon
Thread-Index: AQHQqda0GEdEch5XSEqRwn1krcP8yJ20GLQA
Date: Fri, 19 Jun 2015 19:34:29 +0000
Message-ID: <D1A9BBC4.505B5%eckelcu@cisco.com>
References: <04BCAC21-1D90-4D47-B96D-5DDCA04116C5@iki.fi>
In-Reply-To: <04BCAC21-1D90-4D47-B96D-5DDCA04116C5@iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-originating-ip: [10.154.176.41]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F3EF3B5455D3AC428C578DC3DC84D838@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/iqe3W0ny7PhrPkvjauZ3JSJWftM>
X-Mailman-Approved-At: Fri, 19 Jun 2015 14:02:42 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] [hackathon] homenet in Hackathon
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 19 Jun 2015 19:34:32 -0000

Hi Markus,

It would be great to have HOMENET included, and your sample projects look
good. I can add to the wiki, but we really need to identify one or more
people to champion who can be available to kick things off and help get
people going. I=B9ve cc=B9d the homenet list in hopes of finding volunteers=
.

Cheers,
Charles

On 6/18/15, 12:39 AM, "hackathon on behalf of Markus Stenberg"
<hackathon-bounces@ietf.org on behalf of markus.stenberg@iki.fi> wrote:

>Heya,
>
>due to personal reasons I will not able to be officially champion it as
>such (Fri arrival not an option, probably not around early on Sat either
>but will at least show up on Sat at some point and be there Sun) but I
>would like the homenet stuff in general to be added to wiki as a hacking
>option; I can help later if someone shows up. I know there are some
>people signing up (or already signed up) that have some interest in that
>direction too.
>
>http://tools.ietf.org/wg/homenet/
>
>What I would love to see:
>
>- implementation of DNCP[1] in some quick-n-dirty scripting language (I
>have two partial implementations done Python, for example, and it is
>probably easily doable in 2 days if you are motivated; unfortunately I do
>these in my copious spare time so haven=B9t been able to finish either so
>far)
>
>- _any_ improvement of hnetd, an open-source impelementation of
>DNCP+HNCP[2], issues list might provide starting point[3]
>
>- perhaps implementation of one of the other WG drafts
>
>- expanded version of the IETF92 BIER+homenet multicast stuff, or any
>other =8Cquick and dirty=B9 solution to homenet+X, e.g. X being multicast,
>Coap, ..
>
>Cheers,
>
>-Markus
>
>[1] https://datatracker.ietf.org/doc/draft-ietf-homenet-dncp/
>[2] https://github.com/sbyx/hnetd/
>[3] https://github.com/sbyx/hnetd/issues
>
>_______________________________________________
>hackathon mailing list
>hackathon@ietf.org
>https://www.ietf.org/mailman/listinfo/hackathon


From nobody Sat Jun 20 06:47:22 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2E91A8793; Sat, 20 Jun 2015 06:47:19 -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
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 ZvzXtCPvCrM5; Sat, 20 Jun 2015 06:47:18 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C011A0318; Sat, 20 Jun 2015 06:47:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150620134718.23519.59026.idtracker@ietfa.amsl.com>
Date: Sat, 20 Jun 2015 06:47:18 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/QlgYhqnZXJtr3gjhCbGm7LjpXTw>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-dncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 20 Jun 2015 13:47:19 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Distributed Node Consensus Protocol
        Authors         : Markus Stenberg
                          Steven Barth
	Filename        : draft-ietf-homenet-dncp-06.txt
	Pages           : 32
	Date            : 2015-06-20

Abstract:
   This document describes the Distributed Node Consensus Protocol
   (DNCP), a generic state synchronization protocol which uses Trickle
   and Merkle trees.  DNCP leaves some details unspecified or provides
   alternative options.  Therefore, only profiles which specify those
   missing parts define actual implementable DNCP based protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-dncp/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-homenet-dncp-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-dncp-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Jun 20 06:57:06 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2B3B1A87AE for <homenet@ietfa.amsl.com>; Sat, 20 Jun 2015 06:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.85
X-Spam-Level: 
X-Spam-Status: No, score=-0.85 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_INVITATION=-2, HELO_EQ_DE=0.35] autolearn=ham
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 oFY2A4t9CrlQ for <homenet@ietfa.amsl.com>; Sat, 20 Jun 2015 06:56:59 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 C037B1A879A for <homenet@ietf.org>; Sat, 20 Jun 2015 06:56:58 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1Z6JGQ-0000Je-R3 with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for ; Sat, 20 Jun 2015 15:56:55 +0200
Message-ID: <55857123.90205@openwrt.org>
Date: Sat, 20 Jun 2015 15:56:51 +0200
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: Thomas Clausen <ietf@thomasclausen.org>
References: <BA8A243F-70C3-43C8-8B5E-B813942BA590@thomasclausen.org>
In-Reply-To: <BA8A243F-70C3-43C8-8B5E-B813942BA590@thomasclausen.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/YvtgH2WQ_N3FnRi6Eh3dMVfb_5s>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] RtgDir review: draft-ietf-homenet-dncp-05.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 20 Jun 2015 13:57:05 -0000

Hello Thomas,

thanks a lot for your elaborate review, we have just pushed revision -06
of DNCP addressing your issues and comments and that of other reviewers.

Please see more detailed comments inline.


Cheers,

Steven & Markus



On 16.06.2015 17:45, Thomas Clausen wrote:
> Comments:
>
> 	o	Is there any good reason why the authors have no listed affiliation?
As we are independent consultants, an affiliation would probably not be
much more useful than our names themselves.

> 	
> 	o	It is somewhat contradictory that the abstract talks about
> 		"...describes a protocol" and then later "...leaves some details
> 		 to be specified in profiles, which define actual implementable DNCP
> 		 based protocols"
> 		
> 		 Does that not mean, then, that this document specifies an algorithm,
> 		 a framework, and not a protocol?
This was debated publicly and tbh. we are not sure what the correct
phrase would be, maybe “abstract protocol”, but even that was not liked
by everyone. Other than that we tried to clear up the introduction and
abstract in that regard.

>
> 	o	On that, I see "DNCP protocol" several places. Expanded, that becomes
> 		"Dynamic Network Configuration Protocol Protocol" ...
Fixed, found only one. (long form is wrong btw.)

> 		
> 	o	In general, and despite actually knowing some of the core algorithms
> 		somewhat before this review, I found the document really tough to
> 		read, with convoluted sentences, inconsistent requirements-language,
> 		and a lack of introductory "here's the 1000ft view of the protocol,
> 		what it does, how it works, and under which conditions it works".
> 		
> 	o	On that, I do not find the chosen structure of the document to be
> 		optimal for conveying an unambiguous protocol specification. For one,
> 		the same concepts are occasionally described slightly differently.
> 		For another, it is often hard to find the information needed to
> 		parse a specific mandated processing (for example). I provide an
> 		example of what I would suggest a better structure in the below.
> 			
> 		The goal is to provide first concepts and an overview, followed by a
> 		single, easy to identify place for "precise and unambiguous definitions
> 		of concepts", and then use those in the detailed expression of the
> 		protocol. Note that this is just an example, of course:
> 				
> 			Section "Terminology:"
> 				The Network State Hash is a hash value which represents the
> 				current state of the network, as known by a node.
> 				
> 			Section "Protocol Overview and Functioning"
> 			
> 				When receiving a FOO TLV, the DNCP node compares the received
> 				Network State Hash with its own Network State Hash. This
> 				represents the consistency check rom RFC6206. If same,
> 				then...if not, then ....
> 				
> 			Section "Protocol Information Bases"
> 				For the purpose of this specification, the Protocol
> 				Information Bases are orgnaized as sets of tuples ... any
> 					implementation can chose whatever representation it wants.
> 				
> 					The Network State Information Base in a DNCP node is a set
> 					of tuples:
> 						(x, y, z, w)
> 					
> 					where x is ..., y is ..., z is ..., and w is ...
> 					
> 			Section "How to calculate the Network State Hash":
> 				
> 				 The network State Hash is calculated using the information
> 				 from the Network State Information Base, as follows:
> 				
> 					 	1. First, the tuples in that information base are sorted
> 				 		   in ascending order based on ....
> 				 	
> 					 	2. Second, .... (concatenation)
> 				 	
> 					 	3. Third, the hash function from <profile> is used
> 				 	
> 					 	4. Fourth, the first n bits of the resulting hash value,
> 					 	   are retained, witn n being from <profile>.
>
> 			And then, in remaining sections simply reference the Network
> 			State Hash, which is now ubiquitously defined in a single place.
> 			
> 			I am taking this example, since when reading section 5.3 I found
> 			myself chasing through the document, finding multiple slightly
> 			different definitions of "Network State Hash" --  but beyond this
> 			example, it generally does apply to the document as a whole, and
> 			certainly to all of the processing and generation considerations in
> 			section 5.
>
We reorganised the document a bit, wrote a better abstract and
introduction and provided a “Protocol Overview” section, on top of that
we reorganised the details in an “Operations” section.

 	
> 	o	As a general comment, the document would do well with a good editorial
> 		overhaul to bring consistency in language usage, consistency in 2119
> 		terminology, coherence in defined terms and their definition, document
> 		structure, etc.

We did another editing round with focus on normative language.


> 		
> Major Issues:
> 	
> 	o	The introduction does not read well; it contains parts of something that
> 	 	could be considered as part of an applicability statement (without it
> 	 	being called out as such, and without forming a complete applicability
> 		statement), and does not actually introduce the protocol. Reading just
> 		the introduction and the abstract, it is very obscure if
> 		this is a framework, a protocol, a building block, an architecture, an
> 		algorithm -- and, if either of those, what it is actually accomplishing,
> 		and why one would chose to use DNCP. It does, however, transpire that
> 		"whatever it is", it has two "modes" and that it requires something
> 		(presumably a routing protocol) to provide each "node" with a topology
> 		map.
> 		
> 		Suggest that a proper introduction consisting of three parts would be
> 		beneficial: (i) what this document is, (ii) what doing DNCP actually
> 		gets you, and (iii) the operating conditions under which the
> 		DNCP is applicable.
> 		
> 		On the latter point, given that you state that DNCP requires profiles
> 		to provide "actual implementable DNCP based protocols", it appears
> 		important to understand what the limits for "what a profile can give
> 		you" are.
> 		
> 		I am calling this out as a major issue, since I believe that it is
> 		not just editorial, but is a matter of scoping this document correctly,
> 		and in particular not falling into the trap of "claiming applicability
> 		where it's not".

As noted earlier, the introduction has been reworded and separated from
protocol overview also considering your suggestions.


>
> 	o	The document, in my understanding, defines an exchange format with
> 		limited ability to evolve, as simply "a steam of TLVs".
>
> 		As long as there's never a need to evolve the TLV format itself, and
> 		as long as you do not run out of TLV types, that's not going to be
> 		a problem. The doc sets aside a 16bit TLV type space, that's reasonable
> 		enough, but I worry if eventually a DNCPv2 will need to evolve the
> 		format. One purely hypothetical example could be if a "sequence number"
> 		would be needed in each DNCP message to detect "link success rates", or
> 		something of that sort.

I think on this front we have to agree to disagree; as it is a stream of
_unrelated_ TLVs with some rare exceptions (node endpoint ID => network
state), a later spec such as DNCPv2 can specify if it wants to that
every DNCP 'message' contains TLV of type $FOO and uses disjoint set of
TLVs to do X. Hell, we do that in HNCP already.


> 		
> 		I do not have an actual example in mind -- and that's exactly the point:
> 		to be evolutive for the unknown future and (at the very least) be able
> 		to discriminate between "old" and "new".
> 		
> 		A discussion could be had if a "version number" in each TLV would do,
> 		or if a concept of "protocol message with a version number" is
> 		preferential. I do not believe, however, that "no version number" is
> 		viable.

Since DNCP is an abstract protocol, a concrete protocol on top of it
might probably want to do versioning for its own purposes (i.e.
different versions on top of the same DNCP version). In this case having
versioning in both DNCP and the derived protocol serves little purpose.
HNCP - as first derived protocol - defines a Version-TLV btw.

>
> 	o	Noting that the "overhearing n reduncant transmissions" is a key
> 		retransmission suppression mechanism in Trickle, and that this
> 		seems to assume broad/multicast, using unicast seems to contradict
> 		the statement of "consists of Trickle", at least in the way the
> 		algorithm is defined in RFC6206. Note: it's fine to use an algorithm
> 		outside of its initial scope, but it should be with the caveat of
> 		"which of the characteristics still hold, and which do not"
If k < 2, even on point-to-point link, Trickle does reap benefits and
provides exponential backoff timer. Obviously, we can spell this out
more explicitly if it helps.

>
> 	o	DNCP claims to be trickle based, yet supports unicast. It also
> 		(apparently) is a request/reply protocol.  It doesn't have messages.
> 		This document needs a good, and pedagogical, "protocol overview and
> 		functioning" section somewhere: one needs to get through the end of
> 		Section 5 before having even a vague idea of how DNCP works.
Protocol overview added.

> 		
> 	o	The use of normative language is not as tight as could be desired.
> 		For example, a number of SHOULDs seem to really ought to be "MAYs" since
> 		not following the SHOULD won't break the algorithm. It would be good
> 		to walk through the document and take a careful look at these to
> 		either MUST/MAY the SHOULDs, or to qualify the SHOULDs remaining.
> 		
Reworked.

> 	o	I am going to go out on a limb here, and say that "the protocol is
> 		underspecified". That's a deliberately provocative statement, but it
> 		was honestly how I felt upon having completed the review.
> 		
> 		The document does not help the reader get an intuitive understanding
> 		of the protocol functioning, but jumps right into minute details --
> 		requiring the reader to "build up her or his own model of how DNCP
> 		works". On having read the document a few times, I think that I
> 		understand it -- but there's nothing permitting me to verify my
> 		understanding, and thereby I'd not feel confident to be able to
> 		provide an interoperable and independent implementation. I've given
> 		some comments in the "Comments" section as to what I think would be
> 		viable ways to improve this point.
>
Addressed.

> 	 o	Section 5.3, penultimate paragraph:
> 	
> 	 		"If keep-alives specified in Section 6.1 are NOT sent by the peer
> 		     (either the DNCP profile does not specify the use of keep-alives or
> 		     the particular peer chooses not to send keep-alives), some other
> 		     means MUST be employed to ensure its presence.  When the peer is no
> 		     longer present, the Neighbor TLV and the local DNCP peer state MUST
> 		     be removed."
> 		
> 		"...some other means MUST be employed to ensure its presence." --
> 		followed by more MUST verage when a peer disappears...I am not sure that
> 		that's conductive to interoperable implementations.
> 		
> 		Two implementatons may chose different "means" and then turn off keep-
> 		alives - and be non-interoperable.
> 		
> 		For interoperability, we need:
> 		
> 				o	A mandatory to implement mechanism, that always is
> 					present, but can be complemented by another "means", or
> 					
> 				o	A mandatory to implement mechanism, which by way of a
> 					specified negotiation mechanism can be turned off between
> 					two peers, to allow them to use another "means".
> 					
> 		If you argument is "...this will be specified in the profile", then
> 		you still should provide the two above in this document, with the note
> 		that "...and a profile may specify which from among these MUST be
> 		used in a given deployment"

Clarified that “other means”, refers to existing transport-provided
mechanism, e.g. Ethernet carrier-detection, TCP keep-alives etc.

>
> 	o	Section 8:
> 		Interesting; I am not a security expert, but I am very curious to
> 		see the SEC-DIR review of this document. That said, section 8.3.1
> 		contains normative verbage:
> 		
> 			"A node MUST be trusted for participating in the DNCP network if and
> 			only if..."
> 			
> 		Which I think needs a qualifier of the "If the certificate based
> 		trust model is used, then a node must be trusted for ...."
> 	
> 		Same goes for the subsequent SHOULD - it really reads as-if this
> 		certificate based mechanism initially was intended as MTI, but then
> 		was backed away from subsequently without a complete cleanup of the
> 		text?

It was never intended to be MTI, the intention was that nodes not
participating in the mechanism would ignore the whole section (and
normative language), that is now explicitly stated in normative language
in the beginning.

> 		
> 		I do actually question the value of having a laundry-list of trust
> 		management methods, and for one of those (certs) a laundry-list
> 		of all sorts of trust relationship establishment methods, in this
> 		document; this in no small part as the lists are explicitly indicated
> 		as "non-exhaustive" and that none are listed as "mandatory to
> 		implement". Was any thought given to factoring this into a seperate
> 		document, and focusing in this document on one, mandatory-to-implement,
> 		security mechanism?

This set is a 'useful base set' that e.g. HNCP requires. While I agree
it is not exhaustive, as the original goal was just to split DNCP and
HNCP, I consider it a success.


> 		
> Minor Issues:
>
> 	Introduction:
> 		o	1st paragraph: "reachable nodes"; two things:
> 		
> 				-	I always have a problem with the term "node"; it is often
> 					used as a shorthand for "routers and hosts, both". I was
> 					given to understand that homenet specifically did not want
> 					to consider host changes?
DNCP is not strictly speaking about homenet (but a strict requirement
for HNCP which is). Also even in homenet-case non-routers may join the
network temporarily in order to e.g. do monitoring.

> 					
> 				-	"Reachable" - does that mean something as in "radio range",
> 					does it mean "on the same link", does it mean within a
> 					specific (DNCP?) domain, or does it mean simply "on the
> 					Internet somewhere"?

Clarified in the text as “bidirectionally reachable”, also added
fwd-references to actual definition.

> 					
> 		o	2nd paragraph: "nodes that are currently accounted for":
> 				-	What does that mean?
> 				
> 				-	Also, the conclusion "Therefore unlike Time-To-Live (TTL) 	
> 					based solutions, it does not require periodic re-publishing
> 					of the data by the nodes" does actually not follow from
> 					the previous sentence in that paragraph.
>
> 				-	I actually do not think that the introduction describes
> 					what DNCP does, and so the comparison to TTL-based
> 					solutions is rather hard to get here.
Fixed.	

> 					
> 				-	Continuing:
> 				
> 						"On the other hand, it does require the topology
> 						to be visible to every node that wants to be able to
> 						identify unreachable nodes and therefore remove old,
> 						stale data."
> 						
> 					This reads a lot more like an applicability statement than
> 					an introduction; the take-away when reading this is:
> 					
> 						"Each node must have something that maintains
> 						 a topology map of the entire network, such as
> 						 a (LS) routing protocol, for DNCP to function"
> 						
> 					Is that actually the intent here?
> 					
Clarified, it was intended to be read as DNCP itself providing that
topology.


> 				-	"DNCP is most suitable for data that changes only gradually"
> 					How is the reader to interpret "gradually"? Do you mean
> 					"infrequently", or do you really mean "gradualy"?
Clarified.


> 					
> 		o Last paragraph:
> 				"DNCP has relatively few requirements for the underlying
> 				 transport; it requires some way of transmitting either unicast
> 				 datagram or stream data to a peer"
> 			
> 			This is a bit of a forward comment, but we now have "nodes
> 			that are accounted for" and "peers". I see neither defined in
> 			the terminology section.
> 				
> 				"and, if used in multicast mode, a way of
> 				 sending multicast datagrams."
> 			
> 			This is the first mention of two "modes" of this protocol. This
> 			loops back to an earlier comment, that the introduction actually
> 			does not introduce the protocol, but rather is an incomplete
> 			applicability statement.
Fixed and moved to more appropriate sections.


> 				
> 				"If security is desired and one of the
>  	 			 built-in security methods is to be used, support for some
> 				TLS-derived transport scheme - such as TLS [RFC5246] on top of
> 				TCP or DTLS [RFC6347] on top of UDP - is also required."
>
>    			I am not pretending to be a security expert, but "some
>    			TLS-derived...such as ... on top of TCP or DTLS..." (i) does not
>    			sound like it could lead to interoperable implementations, and (ii)
>    			does not sound sufficiently tight as a MTI security mechanism to
>    			pass security reviews. Again, I am no security expert, but perhaps
>    			getting one looped in early would be advicable?
Clarified that profile MUST define details.

> 			
> 	Terminology:
> 		o	Suggest adding "In this document ..." somewhere to this text:
>
> 				"For readability, any DNCP profile specific
> 				 parameters with a profile-specific fixed value are
> 				 prefixed with DNCP_."
Fixed.

> 				
> 		o	DNCP network: I read this twice, and came away with two different
> 			understandings, perhaps you can clarify which it is:
>
> 				o	A set of nodes running DNCP, within the same domain, and
> 					for which a path betwen any two DNCP nodes includes only
> 					other DNCP nodes; i.e., a DNCP network forms a connected
> 					component with only other DNCP nodes.
> 					
> 				o	A set of nodes running DNCP. They may be anywhere on the
> 					Internet, they are part of the same DNCP network as long
> 					as they (through other means) have learned of each others
> 					addresses.
> 					
> 			In the former, that'd be (for example) a deployment within my
> 			home -- in the latter, it could be a node in my home and a node in
> 			your home forming a DNCP network.
> 			
> 			The text is not quite clear on this point.
Both are valid use cases; hopefully clarified.

> 	
> 		o	Link: a point of clarification here. In "DNCP network", there was
> 			talk about "unidirectional links" and "bidirectional links"; in
> 			"Link" the definition is somewhat vague "directly connected" and
> 			"can communicate". Could something like "without decrementing TTL/
> 			hop-count" be added, and could a statement on bidirectionality
> 			(IOW, that this is just an IP link) be added?
This isn’t IP specific as such; however, some better definition is
welcome. some types of IP links are not strictly bidirectional either
(hello, mesh).	

> 			
> 			
> 		o	"Interface" is overloading the term "port" (IP port) which can be
> 			confusing
Done (stole definition from some RFC that is ‘port free’)


> 			
> 		o	"Endpoint" - The definition "locally configured use of DNCP" is not
> 			clear -- are you really not talking about a DNCP process?
> 			
> 			I am not sure that it is clear how a DNCP process can be "attached
> 			to  ... a specific remote unicast address, or to a range of unicast
> 			addresses that are allowed to contact"
>
> 			I can see how a DNCP process can be configured to allow connections
> 			from a specific range of addresses, or can be configured to connect
> 			to a specific remote unicast address. Is that what you mean instead?
> 			
Clarified, endpoint most likely resembles network socket, i.e. bound to
interface or connected to certain remote address etc.


> 			
> 		o	"Peer" - states that two peers "communicate directly". For link,
> 			the definition is "directly connected nodes can communicate".
> 			Would it then not be easier to say "a DNCP node on the same link
> 			as ..." ?
> 		
It is not. Removed directly if it helps.

> 		o	"Node state"
> 				"The hash function and the number of bits used are defined
> 				 in the DNCP profile."
> 				
> 			Suggest:
> 				"The hash function and the length of the hash value are defined
> 				 in the DNCP profile."
> 			
Done.
> 			
> 		o	"Network state hash" - same comment as for node state (above)

Done.
> 		
> 	Data model:
> 		o	"Latest update sequence number"
> 			This may just be my personal taste, but does it hurt to mandate
> 			a specific way of doing the looping comparison? The reason I
> 			suggest this is, that it's one of those things where creativity
> 			in an implementation seems to simply be an invitation for bugs,
> 			and for little gain
> 			
Done.

> 		o	"Relative time delta"
> 			Document talks about "a 32 bit number on the wire" -- does that
> 			mean that wireless links are excluded?
I thought this was an expression, but guess not, replaced with
‘transmitted as’ (both here + fragment stuff)


> 			
> 		o	Related to terminology, there seems to be some fuzzyness around
> 			node and endpoint. For example, in data model one of the things that
> 			a DNCP node may have is:
>
> 				"Unicast address: the DNCP node it should connect with"
> 			
> 			Does that mean *any* DNCP process (i.e., *any* endpoint) at that
> 			address, or a *specific* DNCP process at that address?
> 			
> 			The same, but inverse, for "Range of addresses: the DNCP nodes that
> 			are allowed to connect" - is this "any DHCP process (i.e., *any*
> 			endpoint) on any of these addresses?
> 			
> 			Following, the same section reads:
>
> 				"For each remote (peer, endpoint) pair detected on a local
> 				endpoint, a DNCP node has..."
> 		
> 			the following text indicating that there's some sort of distinction
> 			between which endpoint.
> 			
> 			This whole thing needs some clarification.
I think there was a general misconception about the term endpoint, which
is hopefully cleared up in the latest revision.

			
> 		
> 	Operation
> 		
> 		o	First a generic comment that Trickle itself has some operating
> 			conditions which scopes its applicability, and it would behove
> 			this document to, in its own applicability statement, call out
> 			those.
Added some comments regarding applicability.

> 			
> 		o	On the same token, while the use of Trickle in an unicast fashion
> 			is possible, I wonder if (in general) unicast use is advicable. I
> 			appreciate that some links are point-to-point and so a broadcast
> 			across it becomes an unicast -- but, does that necessitate being
> 			called out?
> 			
> 			IF the reason for this "because we can use TCP", then be explicit
> 			about this - but, also, that you're then not exactly using Trickle
> 			where and how it was intended. I wonder if you could be explicit
> 			as to what consequences this "alternate use of Trickle" have? It
> 			seems that the use of unicast is directly contradicting the main
> 			operating consideration of Trickle?

In general DNCP is transport agnostic, therefore calling out a specific
transport such as TCP is a bit debatable. RFC 6206 seems to be all about
picking right values at least; they DO NOT say it is multicast or
broadcast only, only that it communicates with 1 address. that's what we
do, it's just the other endpoint.

> 			
> 		o	2nd paragraph states:
> 		
> 				"the multicast transport does not have to be particularly
> 				 secure"
> 		
> 			What is the definition of "not have to be particularly secure"?
> 			Is cleartext OK? Authentication? Encryption?
> 			Should I do something more?
> 			
Clarified: ‘.. does not have to be secured.’

> 	5.1 Trickle-driven status updates
> 		o 	First paragraph:
> 		
> 				"Multicast MUST be employed on a multicast-capable interface;
> 				 otherwise, unicast can be used as well"
> 			
> 			If the interface is not multicast-capable, then unicast can be
> 			used as well as what? Certainly not multicast, since the interface
> 			is not multicast capable...?
> 			
All fixed.

> 		o	Continuing:
> 		
> 				"If possible, most recent,"
> 			
> 			What would make it "not possible"?
> 				
>    				"recently changed, or best of all, all known Node State TLVs"
>    			
>    			OK, so assuming that for some reason (MTU limitation) it is not
>    			possible, does the above represent an order that I MUST respect,
>    			or is it "take a pick from among these, according to your whim of
>    			the day"?
>
>  				"(Section 7.2.3) SHOULD be also included,"
>  				
>  			SHOULD is a strong statement, especially when prefixed by
>  			"if possible". That, essentially, renders it a MAY.
>  			
>  				"unless it is defined as undesirable for some reason
>  				 by the DNCP profile
> 			
> 			Now it DEFINITELY is a MAY since apparently a profile can state
> 			that these TLVs MUST NOT be included -- and, I assume, since the
> 			document permits it to do so, it is possible without breaking the
> 			algorithm.
Degraded to MAY; while it improves convergence speed, it is not worth
being too specific about it.

> 			
> 		o	And, continuing again:
> 		
> 				"If the
>    				 DNCP profile supports dense broadcast link optimization
> 				 (Section 6.2), and if a node does not have the highest node
> 				 identifier on a link, the endpoint may be in a unicast mode in
> 				 which multicast traffic is only listened to.  In that mode,
> 				 multicast updates MUST NOT be sent."
>
> 			Really hard to parse. Is that not equivalent to saying:
> 			
> 				"If a DNCP endpoint is not configured to be in multicast
> 				  mode, then it MUST NOT send multicast updates"
> 				
> 			?
> 			
> 			If it is, then say that -- if it is not, then a rewrite is needed,
> 			as that's what I manage to extract from the text.
Hopefully clarified now, about when multicast/unicast is used.



>
> 	
> 	5.2.  Processing of Received TLVs
> 		o	First paragraph reads:
> 		
> 				"The DNCP profile may specify criteria based on which particular
> 				 TLVs are ignored."
> 			
> 			Criteria for what? Do you perhaps mean:
> 			
> 				"The DNCP profile may specify which TLVs to process, and
> 				 which to ignore"?
> 			
> 			Auxiliary question, then, and related to my penultimate comment
> 			to 5.1, are there any constraints on that, any risks from ignoring
> 			(or not) specific TLVs to the operation of the network?
Added some text to the profile section and reference.


> 			
> 		o	I am also confused by the 3rd sentence in the first paragraph:
> 		
> 				"Any ’reply’ mentioned in the steps below denotes sending of
> 			 	 the specified TLV(s) via unicast to the originator of the TLV
> 			 	 being processed."
> 			 	
> 			 This confusion is likely due to the lack of a "protocol overview
> 			 and functioning" description [either as its own section, or as part
> 			 of the introduction].
> 			
> 			 I know how trickle works. Trickle is a distributed consistency
> 			 algorithm. When an inconsistency is detected, then an action is
> 			 triggered that rectifies that inconsistency.  DNCP claims to be trickle based, but apparently also a sort of request/reply
> 			 mechanism. Combined with trickle-over-unicast-links, I am not sure
> 			 what the protocol logic actually is. Reading through to the end of
> 			 Section 5, I think that I understand the idea, but I am not sure.
> 			
> 			 And the old "when in doubt, look at the state machines" didn't help
> 			 either, there aren't any.
> 			
> 			 The point to this comment is, that the document immediately jumps
> 			 into the details -- but forgets to give the "10000ft view" of the
> 			 protocol functioning.
Added protocol overview and made connection between trickle, merkle tree
and requests more clear.


> 			
> 		o	First paragraph states two SHOULD. Would those not be MUST? What
> 			breaks if not respecting those criteria?
Done.

> 			
> 		o	2nd paragraph, a "valid address", that definition is rather unclear.
> 			I understand that that's something specified in "the profile", but
> 			what is the relationship to the different addresses discussed in
> 			the data model section?
> 			
> 			It is not clear what the parenthesis to this paragraph means,
> 			but that is probably again a case of the "use case" and "protocol
> 			overview" not being documented - the document so far has nowhere
> 			described interaction with outside processes.
Text changed.

> 		
> 		o	First bullet, but generally through these, and other, bullets:
> 		
> 			I had a really hard time deciphering this. First:
> 			
> 				"The receiver MUST reply
> 		         with a Network State TLV (Section 7.2.2) and a Node State TLV
> 		         (Section 7.2.3) for each node data used to calculate the
> 		         network state hash"
> 		
> 		    Alright, off to find "network state hash".
> 		
> 		    The terminology tells me that it is:
> 		
> 		    	"a hash value which represents the current state of
>   				 the network.  The hash function and the number of
>                  bits used are defined in the DNCP profile.
>                  Whenever a node is added, removed or updates its
>                  published node data this hash value changes as
>                  well. It is calculated over each reachable nodes'
>                  update number concatenated with the hash value of
>                  its node data. For calculation these tuples are
>                  sorted in ascending order of the respective node's
>                  node identifier.
>
> 		    Searching further, I find Section 5.1, but that simply states:
> 		
> 		    	"The Trickle state for all endpoints is
> 			     considered inconsistent and reset if and only if the locally
> 			     calculated network state hash changes."
>
> 			Next occurence is in these bullets, and then just before Section 6,
> 			
> 				"During
> 			     the grace period, the nodes that were not marked reachable
> 			     in the most recent graph traversal MUST NOT be used for
> 			     calculation of the network state hash, be provided to any
> 			     applications that need to use the whole TLV graph, or be
> 			     provided to remote nodes."
> 			
> 			Alright, now I know what I can't use for calculating it.
> 			
> 			A few occurences later, in section 7.2.2, in what looks like a
> 			section laying out the packet -- sorry, TLV -- format, I see for
> 			"Network State TLV":
> 			
> 				"This TLV contains the current locally calculated network state
> 				hash. It is calculated over each reachable nodes' update number
>    				concatenated with the hash value of its node data in ascending
>    				order of the respective node identifiers"
>    				
> 			Phew. Now, it does seem a little at odds with the terminology. The
> 			terminology states something about tuples that are ordered. While
> 			those tuples are not defined (they should be), at least what is
> 			described is clear and possibly can be implemented. What is in 7.2.2
> 			is not ant cannot.
Unified and deduplicated the definitions and added appropriate references.

> 			
> 			This is an instance of a general issue that I have with this
> 			document: that it doesn't take a step back, and properly define
> 			things in a proper order, but dives into (and repeats) details.
> 			
> 			
> 		o	Also to section 5.2, for each of the cases that are described, could
> 			a conceptual description of "what this corresponds to" be added? For
> 			example:
> 		
> 				Upon reciept of a Node State TLV:
> 					If the node identifier matches the local node identifier and
> 					the TLV has a higher update sequence number than its current
>     	     		local value, or the same update sequence number and a
>     	     		different hash, the node SHOULD re-publish its own node data
>     	     		with an update sequence number 1000 higher than the received
>     	     		one.
> 			
> 		 	It's not clear why it is a "SHOULD re-publish" (not MUST, nor what
> 		 	happens if SHOULD is not followed). And it is not clear why 1000 ...
> 			
> 			[I just pick this example, but it applies to all processing bullets]
Hopefully all fixed.

> 			
> 	o	In the same cases, it is a lot more readable (IMO) to do nested bullets:
> 	
> 		o	If FOO; and either of:		
> 	 			- BAR
> 	 			- GNYF
> 	 			- BLAB
> 	 		Then do all of the following:
> 	 			- ...
> 	 			- ...
> 	 			- ...
> 	 	o 	Otherwise, if not-FOO, ...
> 	 	
> 	 	That's a personal preference, though, so feel free to disregard this
> 	 	comment.
> 	 		
> 	 o	Section 5.3 and elsewhere, suggest replacing:
> 	
> 	 		"If it comes via..."
> 	 	
> 	 	by:
> 	 	
> 	 		"If received over ..."
> 	 	
Done.

> 		
> 	o	Last paragraph in 5.3:
> 			Same comment as 3rd comment to 5.1 made above.
Some rewriting done.

> 		
> 	o 	Section 5.4, first sentence:
> 			"DNCP validates the set of data within it ..."
> 			
> 		Should that not be:
> 			"A DNCP instance validates the data within its data sets ..."
> 		
> 		?
>
> 		Also, "nodes that are currently accounted for; what's the definition
> 		of "accounted for"?
Replaced the whole paragraph.

> 		
> 	o	Section 5.4, first paragraph
> 		The statement:
> 		
> 			"therefore,
>    			 unlike Time-To-Live (TTL) based solutions, it does not require
> 		     periodic re-publishing of the data by the nodes.  On the other
> 		     hand, it does require the topology to be visible to every node that
> 		     wants to be able to identify unreachable nodes and therefore remove
> 		     old, stale data."
> 		
> 		which also appeared in the introduction, is copied verbatimly. Once
> 		more, the statement is a claim which is not supported, and that which
> 		follows "therefore" is not a consequence of that which comes before
> 		"therefore".
Got rid of duplicate.

> 	
> 	o	Section 5.4, first paragraph
> 	
> 			"When a Neighbor TLV or a whole node is added or removed, the
> 			neighbor graph SHOULD be traversed, starting from the local node.
> 			The edges to be traversed are identified by looking for Neighbor
> 			TLVs on both nodes, that have the other node’s identifier in the
> 			neighbor node identifier, and local and neighbor endpoint
> 			identifiers swapped. Each node reached should be marked currently
> 			reachable."
> 			
> 		First comment, why SHOULD and not MUST?
Retained this part, there was a ‘lightweight’ node option that can do it
without this; however, I consider it non-interesting so changed to MUST.

> 		
> 		Second comment, and now you made me go look...."neighbor" sounds like
> 		"someone on the same link as me" so  the "neighbor graph" is really just
> 		a set relating "this node" and "another node which is on the same link
> 		as this node".
> 	
> 		Yet, looking in the terminology, I see "Neighbor graph" defined as:
> 				"the undirected graph of DNCP nodes produced by
>                  retaining only bidirectional peer relationships
>                  between nodes.
> 		
> 		Which doesn't sound as much like a "neighbor graph" as it does a
> 		"topology graph" for the whole network.
> 		
> 		So, is the terminology wrong, or is the definition wrong?
Renamed to “Topology Graph” - probably confusion of non-native-speaking
authors.


> 		
> 	o	Section 5.4, 3rd paragraph
> 		
> 		Is it actually important that the content of that graph be "purged"?
> 		That sounds like an implementation detail -- rather, it sounds like
> 		the elements of the graph should "not be used for calculations and
> 		MAY be removed". Or, is there a specific requirement that I am
> 		missing?
Added lots of text; gist of it, basically, is that unreachable nodes
SHOULD be removed and MAY be removed immediately.

> 		
> 	o	Section 6.1, I do not understand the parenthesis in this sentence:
> 	
> 			Trickle-driven status updates (Section 5.1) provide a mechanism for
> 			handling of new peer detection (if applicable) on an endpoint
> 		
> 		Under what conditions is that applicable, and under which is it not?
Actually always now; removed (if applicable).

> 	
> 	o	Section 6.2:
> 	
> 			"An upper bound for the number of neighbors that are allowed for a
>    			 (particular type of) link that an endpoint runs on SHOULD be
>    			 provided by a DNCP profile, user configuration, or some hardcoded
>    			 default in the implementation."
>    			
>    		A couple of things to that:
>    			1)	Can you explain the parenthesis? What type of link?
>    			2)	How does "an endpoint runs on" a link?
>    			3)	Why SHOULD?
>    			4)	Is this specification seriously suggesting "some hardcoded
>    				default in the implementation" as a SHOULD?
>
> 		[I am tempted to upgrade this to a "Major issue" simply because of 4) ]   	
Clarified, the choice to use it is not really visible externally. Now
the text has per multicast-enabled link type constraints, and also
per-profile support for extension at all.

	
> 		
> 		
> 		Also to 6.2, this particular optimization, do you have any
> 		quantification of its actual benefit? What should I look for to
> 		determine if this "optimization" yields a benefit or not? What are
> 		you trying to optimize? Over what link types does this function?
> 		I am dubious that it "optimizes" much, if anything, across an Ethernet, for example ...
Oddly enough, most link-state routing protocols have this optimization.
Added further description on why it is helpful.

> 		
> 	o	Section 7
> 		As indicated previously, having to search through the frame format
> 		diagrams for "how to calculate the value" isn't ideal.
Should be clearly defined earlier now.

> 		
> 	o	Section 7.2.3, I worry when I see something like this:
> 	
> 			"The whole network should have roughly the same idea about the time
> 			 since origination of any particular published state."
> 			
> 		What is the definition of "roughly"?
> 		Is the "should" intentionally in non-caps?
> 		What're the consequences if not?
> 		[Note that trickle almost mechanically makes information propagate
> 		with non-trivial jitter across a network, so how do you ensure this?]
Clarified the paragraph, since the original text could be interpreted
invertedly.

> 		
> 	o	Section 7.2.4, CUSTOM-DATA TLV.
> 	
> 		Given the description:
> 			"This TLV can be used to contain anything; the URI used should be
> 			 under control of the author of that specification."
> 		
> 		It seems that (i) the description is self-contradictory: it cannot
> 		contain *anything* but can contain an URI?
> 		
> 		Secondly, how is this supposed to work, what does it mean [for DNCP]
> 		that "the URI is under control of the author"?
> 		
> 		Thirdly, what does "that specification" refer to?
> 		
> 		Fourthly, why lower-case should? Indeed, why is the "control" of the
> 		URI of any importance to DNCP?
Removed, since it had issues (besides being ambiguously defined). DNCP
profiles can define additional TLVs easily.

>
> 	o	Section 9, the bullet:
> 	
> 			"When receiving messages, what sort of messages are dropped, as
> 			specified in Section 5.2"
> 		
> 		Seems at odds with Section 5.2, which discusses TLV processing.
Unified terms to “ignore”, added explanation mentioning security reasons


> 		
>
> Nits:
>    		
> 	Requirement Language:
> 		o	Please reflect Errata 499 for RFC2119 in the boilerplate
> 		
> 		o	The RFC2119 boilerplate could conveniently be in the terminology
> 			section, given that it is terminology.
> 			
>
Both done.


From nobody Sun Jun 21 07:28:02 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2DDF1A1A55 for <homenet@ietfa.amsl.com>; Sun, 21 Jun 2015 07:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.35
X-Spam-Level: 
X-Spam-Status: No, score=0.35 tagged_above=-999 required=5 tests=[HELO_EQ_FR=0.35] autolearn=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 vSHSvA3Wj4gx for <homenet@ietfa.amsl.com>; Sun, 21 Jun 2015 07:27:59 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1CC21A1A0B for <homenet@ietf.org>; Sun, 21 Jun 2015 07:27:58 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5LERuFN006805 for <homenet@ietf.org>; Sun, 21 Jun 2015 16:27:56 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 481D961FA2 for <homenet@ietf.org>; Sun, 21 Jun 2015 16:27:56 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id QS9djDLGF_Vz for <homenet@ietf.org>; Sun, 21 Jun 2015 16:27:55 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E929661F9A for <homenet@ietf.org>; Sun, 21 Jun 2015 16:27:53 +0200 (CEST)
Date: Sun, 21 Jun 2015 16:27:53 +0200
Message-ID: <877fqx5e6u.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "homenet@ietf.org" <homenet@ietf.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 21 Jun 2015 16:27:56 +0200 (CEST)
X-Miltered: at korolev with ID 5586C9EC.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5586C9EC.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5586C9EC.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/UvVF3H8pgIHoS_OVUJkD_ZcJydI>
Subject: [homenet] Babeld-1.6.1 available, please upgrade
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 21 Jun 2015 14:28:00 -0000

Hi,

Babeld-1.6.1 has now migrated into OpenWRT trunk and Debian unstable 
(thanks to Gabriel and Stéphane).  This version fixes a bug with 
source-specific routing, so you'll likely want to upgrade if you're 
experimenting with the Homenet stack.

The changelog is on https://github.com/jech/babeld/blob/master/CHANGES

-- Juliusz


From nobody Tue Jun 23 02:26:15 2015
Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE6441AC3CE for <homenet@ietfa.amsl.com>; Tue, 23 Jun 2015 02:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 SUhzZ5qvkeaz for <homenet@ietfa.amsl.com>; Tue, 23 Jun 2015 02:26:13 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DFBA1AC3CD for <homenet@ietf.org>; Tue, 23 Jun 2015 02:26:13 -0700 (PDT)
Received: from [46.227.151.81] (port=52801 helo=Rays-MacBook-Pro.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1Z7KT5-0001vW-AG (Exim 4.72) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Tue, 23 Jun 2015 10:26:11 +0100
Message-ID: <55892633.6080205@bellis.me.uk>
Date: Tue, 23 Jun 2015 10:26:11 +0100
From: Ray Bellis <ray@bellis.me.uk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: homenet@ietf.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/f4AsbbIuHLhUY46Eb8BJQG5_h2A>
Subject: [homenet] draft-ietf-homenet-hncp-06 now in WGLC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 23 Jun 2015 09:26:15 -0000

This email marks the commencement of a three-week Working Group Last
Call for draft-ietf-homenet-hncp.

Please get any final comments in to the authors (cc: the WG) as soon as
possible.

thanks,

Ray and Mark


From nobody Thu Jun 25 06:02:00 2015
Return-Path: <barryleiba@computer.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 950471A7D85; Thu, 25 Jun 2015 06:01:58 -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
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 v1LBd5y54j2T; Thu, 25 Jun 2015 06:01:57 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 148D71A1DBD; Thu, 25 Jun 2015 06:01:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Barry Leiba" <barryleiba@computer.org>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150625130147.28512.8432.idtracker@ietfa.amsl.com>
Date: Thu, 25 Jun 2015 06:01:47 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/W0zdadtTHIBvA1wg7pvSbyAVWno>
Cc: homenet@ietf.org
Subject: [homenet] Barry Leiba's No Objection on draft-ietf-homenet-prefix-assignment-07: (with COMMENT)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <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, 25 Jun 2015 13:01:58 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-homenet-prefix-assignment-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-homenet-prefix-assignment/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Well written and clear; thanks.



From nobody Fri Jun 26 08:41:40 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA1A11A87EC for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 08:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 CyVdcXF_QgCm for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 08:41:38 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B4351A8825 for <homenet@ietf.org>; Fri, 26 Jun 2015 08:41:17 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5QFfE3J016213; Fri, 26 Jun 2015 17:41:14 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 0B04361F9D; Fri, 26 Jun 2015 17:41:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 1ZtANczEmUdN; Fri, 26 Jun 2015 17:41:13 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1324E61F9A; Fri, 26 Jun 2015 17:41:12 +0200 (CEST)
Date: Fri, 26 Jun 2015 17:41:11 +0200
Message-ID: <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <5581A2FB.8010108@iki.fi>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 26 Jun 2015 17:41:15 +0200 (CEST)
X-Miltered: at korolev with ID 558D729A.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 558D729A.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 558D729A.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Cnaet8ZQvxl8mXEpBUcNp6sxbaQ>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Fri, 26 Jun 2015 15:41:39 -0000

Markus,

I still don't understand the intent of the "ad hoc" interface type.

If the ad-hoc interface is designed for non-transitive links, then the 
draft should say so (in which case I'll be glad to provide you with 
suitable prose).  However, in this case it should also identify the bits 
of DNCP which are not applicable to non-transitive interfaces (Section 
6.1.5, obviously, but I don't understand DNCP well enough to say if there 
are others).

Section 4 speaks of "ad-hoc mode" -- does that mean 802.11 IBSS?  If it 
is, then you should use the proper terminology, but I think that support 
for non-transitive links should not be restricted to 802.11 (even if the 
implementation is limited to it).

And sorry if I sound like a broken record, but I would like the ability to 
set up a router-router link with less than a full /64 allocated to it, at 
least in the ad-hoc case.

-- Juliusz


From nobody Fri Jun 26 08:48:42 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B561A8856 for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 08:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 cHJlnv-CudKy for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 08:48:40 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 757221A8851 for <homenet@ietf.org>; Fri, 26 Jun 2015 08:48:40 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5QFmcoD019864; Fri, 26 Jun 2015 17:48:38 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E551161FA1; Fri, 26 Jun 2015 17:48:38 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 3Viw7euwvoOp; Fri, 26 Jun 2015 17:48:38 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id F15E861F9D; Fri, 26 Jun 2015 17:48:37 +0200 (CEST)
Date: Fri, 26 Jun 2015 17:48:37 +0200
Message-ID: <87fv5empwq.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <5581A2FB.8010108@iki.fi>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 26 Jun 2015 17:48:38 +0200 (CEST)
X-Miltered: at korolev with ID 558D7456.005 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 558D7456.005 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 558D7456.005 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/RkFThuWzvFXwZmy1mYUeEEzKg3k>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Fri, 26 Jun 2015 15:48:41 -0000

Trying to wrap my head around Section 5, so please bear with me.

If there's an IPv6-only non-Homenet router that doesn't provide PD (either 
because it only does DHCPv6 address assignment, or because it only 
advertises RA), then the link will be considered internal.  Is that correct?

If a router speaks DHCPv4 or DHCPv6-PD with a user-class of "HOMENET" but 
doesn't speak HNCP, nothing will break, right?  (Perhaps a second 
User-Class like "HOMENET-COMPATIBLE" should be defined for this case, as 
this may simplify debugging.)

Thanks,

-- Juliusz





From nobody Fri Jun 26 08:59:33 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37B361A8888 for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 08:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 eAe_ZZOAdZH1 for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 08:59:30 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 683CD1A887D for <homenet@ietf.org>; Fri, 26 Jun 2015 08:59:30 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5QFxTOZ025341; Fri, 26 Jun 2015 17:59:29 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 1777961F9D; Fri, 26 Jun 2015 17:59:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id V2aMu9ddhYYc; Fri, 26 Jun 2015 17:59:28 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0D06D61F9A; Fri, 26 Jun 2015 17:59:28 +0200 (CEST)
Date: Fri, 26 Jun 2015 17:59:27 +0200
Message-ID: <87d20impeo.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87fv5empwq.wl-jch@pps.univ-paris-diderot.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87fv5empwq.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 26 Jun 2015 17:59:29 +0200 (CEST)
X-Miltered: at korolev with ID 558D76E1.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 558D76E1.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 558D76E1.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/qJaF4oZc2IS90hXWmLT0cr_VHWs>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Fri, 26 Jun 2015 15:59:31 -0000

> If a router speaks DHCPv4 or DHCPv6-PD with a user-class of "HOMENET" but 
> doesn't speak HNCP, nothing will break, right?  (Perhaps a second 
> User-Class like "HOMENET-COMPATIBLE" should be defined for this case, as 
> this may simplify debugging.)

I'm an idiot.  Please ignore this paragraph.

-- Juliusz


From nobody Fri Jun 26 09:19:04 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9441A0119 for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 09:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 BX-lgpWhUCHf for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 09:19:02 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (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 3EA541A010E for <homenet@ietf.org>; Fri, 26 Jun 2015 09:19:02 -0700 (PDT)
Received: by obpn3 with SMTP id n3so69885640obp.0 for <homenet@ietf.org>; Fri, 26 Jun 2015 09:19:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=eR0kreEaHPMrGCdz1NT9ArDoCFThbvd6mvfQi+Qjdlw=; b=Xeo2bP2gv2xXjMQjpAvbaugVa9MnTZdzmVXQSQP7C5/aXVebbJ69xP9MwB/qc820bY rD/IdSpmriWHtsaH00PE1rwlDQrbCoLozSrvn2Sy9dkovwujkqUYp/+MWIGeGYwL4AA8 SjEeN7m8KU2c4KkQVU5O3iX3Opcskhs+uI9O3ocEi7pwK+XXXBPPnn/p3R8wgPrxO+u6 a/u5YbCSwoePWwfUkr4UNrBe6xufoTKNsFKiMeNa4sI7udyQkVVE64s71tuEwCzKfJlO gtKgwAlMBAJgsm7fgAJwdTIAybooyGcZO8PoIHwzBOP0RN5DhPW4UwopTylSxr1IR9c3 EixA==
MIME-Version: 1.0
X-Received: by 10.182.246.136 with SMTP id xw8mr16491561obc.29.1435335541772;  Fri, 26 Jun 2015 09:19:01 -0700 (PDT)
Received: by 10.202.105.129 with HTTP; Fri, 26 Jun 2015 09:19:01 -0700 (PDT)
In-Reply-To: <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 26 Jun 2015 09:19:01 -0700
Message-ID: <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/yBe0RZwiUyZWAYxmwvmGeuX-WrE>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Fri, 26 Jun 2015 16:19:03 -0000

On Fri, Jun 26, 2015 at 8:41 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
> Markus,
>
> I still don't understand the intent of the "ad hoc" interface type.
>
> If the ad-hoc interface is designed for non-transitive links, then the dr=
aft
> should say so (in which case I'll be glad to provide you with suitable
> prose).  However, in this case it should also identify the bits of DNCP
> which are not applicable to non-transitive interfaces (Section 6.1.5,
> obviously, but I don't understand DNCP well enough to say if there are
> others).
>
> Section 4 speaks of "ad-hoc mode" -- does that mean 802.11 IBSS?  If it i=
s,
> then you should use the proper terminology, but I think that support for
> non-transitive links should not be restricted to 802.11 (even if the
> implementation is limited to it).
>
> And sorry if I sound like a broken record, but I would like the ability t=
o
> set up a router-router link with less than a full /64 allocated to it, at
> least in the ad-hoc case.

+10 on /128 support.

I have way more p2p links than available 64s.

> -- Juliusz
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast


From nobody Fri Jun 26 13:34:23 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18D7B1A9102 for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 13:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 TQnn0OA8ckgy for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 13:34:20 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (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 ACE631A90EA for <homenet@ietf.org>; Fri, 26 Jun 2015 13:34:20 -0700 (PDT)
Received: by pdbci14 with SMTP id ci14so80878863pdb.2 for <homenet@ietf.org>; Fri, 26 Jun 2015 13:34:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=knfRaNT04NLCBAXYpw+eDhf4qzxHY2UQxBqwrt1jC2o=; b=FAYMMDWV1bBb3cLa57OdmhWec26OnKnn9gKtbsVLZcRIvTRoDyxQ9U59zhFmdKIdpx 9aOwll1XY903EsTF2Cp15DW9WNvGPVyowdoEW2E+dEYtm58XQlWQ1R6O4Ae/mOuhkwZA XanLTMYYcPHKSKwqIwY8JOn8YlczgS1izGtYx8MABDjmPw9DA9MoBYOFwU6rg1X1aeZ9 LmZ6MTlQ1+0kBy4hYCsbTmBGkUn/px2YbJvLpzva0EpDKVsvL32u9SZbNwJ8iE3dvoVM QwiS6XqsZONrl/8UPbTsSK/obLTRlC+Lb/tj1f01KPSBXIbHhJXgFQmxBpTl8s52thkt Y3DQ==
X-Received: by 10.70.102.11 with SMTP id fk11mr6805679pdb.144.1435350860436; Fri, 26 Jun 2015 13:34:20 -0700 (PDT)
Received: from ?IPv6:2406:e007:4e59:1:28cc:dc4c:9703:6781? ([2406:e007:4e59:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id gj9sm34193064pbc.77.2015.06.26.13.34.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Jun 2015 13:34:19 -0700 (PDT)
Message-ID: <558DB74C.8040106@gmail.com>
Date: Sat, 27 Jun 2015 08:34:20 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>,  Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com>
In-Reply-To: <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8DIkr-pEyy2RGJ19DfvcFsibGrY>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Fri, 26 Jun 2015 20:34:22 -0000

On 27/06/2015 04:19, Dave Taht wrote:
> On Fri, Jun 26, 2015 at 8:41 AM, Juliusz Chroboczek
> <jch@pps.univ-paris-diderot.fr> wrote:

...
>> And sorry if I sound like a broken record, but I would like the ability to
>> set up a router-router link with less than a full /64 allocated to it, at
>> least in the ad-hoc case.
> 
> +10 on /128 support.
> 
> I have way more p2p links than available 64s.

If you mean RFC6164, that would be a /127 prefix. But in any case /64 is not
sacred in IPv6. https://tools.ietf.org/html/draft-ietf-v6ops-cidr-prefix-03
was just approved by the IESG and is in the RFC Editor queue.
Any prefix length must be possible, even if /64 is preferred.

Which is actually what the draft says, in slightly strange syntax:

"  If the considered delegated prefix is an IPv6 prefix, and whenever
   there is at least one available prefix of length 64, a prefix of
   length 64 MUST be selected unless configured otherwise by an
   administrator.  In case no prefix of length 64 would be available, a
   longer prefix MAY be selected."

I'm not sure about the words "by an administrator". With my autonomic
networking hat on, I feel that configuration might arise with no human
intervention. But in any case, even given that homenet wants to prefer
/64, any length must be allowed.

    Brian


From nobody Fri Jun 26 16:49:31 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8832D1B2BAA for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 16:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 VtlMa0qkjF9u for <homenet@ietfa.amsl.com>; Fri, 26 Jun 2015 16:49:29 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 974ED1B2BA9 for <homenet@ietf.org>; Fri, 26 Jun 2015 16:49:28 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5QNnQg6030293; Sat, 27 Jun 2015 01:49:26 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 14C5761F9A; Sat, 27 Jun 2015 01:49:26 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id avdFeykYr3qe; Sat, 27 Jun 2015 01:49:25 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 7347561FA2; Sat, 27 Jun 2015 01:49:22 +0200 (CEST)
Date: Sat, 27 Jun 2015 01:49:21 +0200
Message-ID: <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <558DB74C.8040106@gmail.com>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 27 Jun 2015 01:49:26 +0200 (CEST)
X-Miltered: at korolev with ID 558DE506.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 558DE506.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 558DE506.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/3wDj5_zfih-Um06aGTDvjhZYx9E>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Fri, 26 Jun 2015 23:49:30 -0000

>> +10 on /128 support.

> If you mean RFC6164, that would be a /127 prefix.

I think Dave meant no on-link information, which unless I'm mistaken is 
equivalent to putting a /128 on the interface.  With explicitly scoped 
link-local addresses, on-link information becomes a mere optimisation 
(although an important one in the multihomed host case, where redirects 
cannot cause you to switch interfaces).

> "  If the considered delegated prefix is an IPv6 prefix, and whenever
>    there is at least one available prefix of length 64, a prefix of
>    length 64 MUST be selected unless configured otherwise by an
>    administrator.  In case no prefix of length 64 would be available, a
>    longer prefix MAY be selected."

Well spotted, thanks.  Markus, would you be open to relaxing the MUST, and 
adding a guideline about which of the available /64s is suitable for 
carving up?

-- Juliusz


From nobody Sat Jun 27 07:40:13 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD5EA1A89B5 for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 07:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.75
X-Spam-Level: *
X-Spam-Status: No, score=1.75 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6] autolearn=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 VzYSjnPr4pvh for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 07:40:05 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20EB01A89A7 for <homenet@ietf.org>; Sat, 27 Jun 2015 07:40:04 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5REe3pa032399; Sat, 27 Jun 2015 16:40:03 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 0781F61FA2; Sat, 27 Jun 2015 16:40:03 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id nJnLPGn7PRfN; Sat, 27 Jun 2015 16:40:02 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id DC5A861FA1; Sat, 27 Jun 2015 16:40:01 +0200 (CEST)
Date: Sat, 27 Jun 2015 16:40:00 +0200
Message-ID: <87fv5d8bb3.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 27 Jun 2015 16:40:03 +0200 (CEST)
X-Miltered: at korolev with ID 558EB5C3.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 558EB5C3.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 558EB5C3.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/WvntkyqCi4hdONxbh0ArANIbtFc>
Cc: homenet@ietf.org
Subject: [homenet] How to compute DNCP/HNCP node data?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 14:40:07 -0000

Markus,

I haven't gotten any smarter since yesterday, so please be patient.

DNCP uses the value H(node data) in a few places, but unless I'm missing 
something this doesn't seem to be clearly defined anywhre.  I have two 
hypotheses:

1. This value is computed by the originator, and is simply forwarded by 
other nodes in Node State TLVs without interpretation or validation.  
Therefore, the exact means of computing this hash does not need to be 
specified.

2. This value needs to be computed locally by this node, and therefore the 
"node data" has a canonical representation that's described somewhere and 
I'm too stupid to see where.

Could you please clarify?  (I hope it is (1), by the way.)

-- Juliusz


From nobody Sat Jun 27 07:55:21 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6D021B29F5 for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 07:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 evwVt-jlgqDv for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 07:55:18 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44D3B1B29F3 for <homenet@ietf.org>; Sat, 27 Jun 2015 07:55:18 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5REtGvT004777; Sat, 27 Jun 2015 16:55:16 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E6F2961F9D; Sat, 27 Jun 2015 16:55:16 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id l3VlLm0AEHc0; Sat, 27 Jun 2015 16:55:16 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1459C61F9A; Sat, 27 Jun 2015 16:55:16 +0200 (CEST)
Date: Sat, 27 Jun 2015 16:55:16 +0200
Message-ID: <87d20h8aln.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 27 Jun 2015 16:55:16 +0200 (CEST)
X-Miltered: at korolev with ID 558EB954.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 558EB954.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 558EB954.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/betSGIRJ4RdM5TrBHf140ZJIzV4>
Cc: homenet@ietf.org
Subject: [homenet] A few more DNCP -06 nits and questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 14:55:19 -0000

Markus,

Section 4.4 of -06 seems to say that Node Endpoint TLVs MUST be silently 
discarded.

Section 5, "containing data about the most recently sent RNS", should that 
be per interface ("endpoint")?  Since there's a distinct trickle instance 
per interface, this would make sense to me.

Since there's state shared between the Endpoint TLV and the other TLVs in 
a datagram, shouldn't you be requiring that the Endpoint TLV be sent first?

-- Juliusz


From nobody Sat Jun 27 08:53:05 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16F6E1B2E5A for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 08:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.35
X-Spam-Level: 
X-Spam-Status: No, score=0.35 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001] autolearn=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 3wDxS1XvwQud for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 08:53:02 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 774231A0025 for <homenet@ietf.org>; Sat, 27 Jun 2015 08:53:02 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1Z8sPa-0007W9-15 with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-SHA:128) for ; Sat, 27 Jun 2015 17:52:58 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <87fv5d8bb3.wl-jch@pps.univ-paris-diderot.fr>
References: <87fv5d8bb3.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----5IO3HBR821B33J2LLEN7U47NXL5SME"
Content-Transfer-Encoding: 8bit
From: Steven Barth <cyrus@openwrt.org>
Date: Sat, 27 Jun 2015 17:52:57 +0200
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Markus Stenberg <markus.stenberg@iki.fi>
Message-ID: <D0751E47-F461-4097-8995-56D6E4E4A4A6@openwrt.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/qXGiSxoSsIVDSHLC5M0YxZMEOEQ>
Cc: homenet@ietf.org
Subject: Re: [homenet] How to compute DNCP/HNCP node data?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 15:53:04 -0000

------5IO3HBR821B33J2LLEN7U47NXL5SME
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8

Hi Juliusz,

The glossary for node state should iirc say that hash function and size is defined in profile e.g. hncp. Profile recommendations section in dncp recommends sha-256. HNCP itself should also mention something in dncp profile. The hash function is used for both levels of the Merkle tree i.e. also for network state hash. DNCP specifies canonical form of node data as binary sorted so it should be all defined and unambiguous. 

Cheers,

Steven
------5IO3HBR821B33J2LLEN7U47NXL5SME
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

Hi Juliusz,<br>
<br>
The glossary for node state should iirc say that hash function and size is defined in profile e.g. hncp. Profile recommendations section in dncp recommends sha-256. HNCP itself should also mention something in dncp profile. The hash function is used for both levels of the Merkle tree i.e. also for network state hash. DNCP specifies canonical form of node data as binary sorted so it should be all defined and unambiguous. <br>
<br>
Cheers,<br>
<br>
Steven
------5IO3HBR821B33J2LLEN7U47NXL5SME--


From nobody Sat Jun 27 09:44:35 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322391A1B4C for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 09:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 764XO7a1H1gT for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 09:44:33 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52DED1A1B48 for <homenet@ietf.org>; Sat, 27 Jun 2015 09:44:33 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5RGiVqX031361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 27 Jun 2015 18:44:31 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t5RGiVvi023329; Sat, 27 Jun 2015 18:44:31 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5796361F9A; Sat, 27 Jun 2015 18:44:31 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id kSzTL0GR0-CD; Sat, 27 Jun 2015 18:44:30 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 532F461F9D; Sat, 27 Jun 2015 18:44:29 +0200 (CEST)
Date: Sat, 27 Jun 2015 18:44:28 +0200
Message-ID: <87381d85jn.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <D0751E47-F461-4097-8995-56D6E4E4A4A6@openwrt.org>
References: <87fv5d8bb3.wl-jch@pps.univ-paris-diderot.fr> <D0751E47-F461-4097-8995-56D6E4E4A4A6@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Sat, 27 Jun 2015 18:44:31 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sat, 27 Jun 2015 18:44:31 +0200 (CEST)
X-Miltered: at korolev with ID 558ED2EF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 558ED2EF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 558ED2EF.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 558ED2EF.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 558ED2EF.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 558ED2EF.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/-lOcISRU9GG-xSPNATNJtdHPiBs>
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] How to compute DNCP/HNCP node data?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 16:44:34 -0000

> Profile recommendations section in dncp recommends sha-256.

Er... -06 recommends the leading 8 octets of MD-5.  Section 3.

But that's not what I'm asking about.  The question is what it is exactly 
that I'm hashing:

1. simply copy the has received from the originator, no questions asked; 
2. hash the raw data received from the originator; 
3. hash data that I've formatted from my internal data structures.

(1) is the simplest to implement, but it doesn't allow validation 
(detecting buggy or malicious peers).  (2) is pretty simple too, but it 
requires that I keep duplicate data -- one raw copy and one in my data 
structures.  (3) is more involved, since it requires defining a canonical 
form for the data (e.g. how to sort the TLVs and what to do with duplicate 
TLVs).

I'm currently doing (2).

-- Juliusz


From nobody Sat Jun 27 10:23:57 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 429D51A017F for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 10:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_DE=0.35] autolearn=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 hCkIudAVYKqU for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 10:23:54 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 18C521A0178 for <homenet@ietf.org>; Sat, 27 Jun 2015 10:23:53 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1Z8tpX-0001Lf-9l with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-SHA:128) for ; Sat, 27 Jun 2015 19:23:51 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <87381d85jn.wl-jch@pps.univ-paris-diderot.fr>
References: <87fv5d8bb3.wl-jch@pps.univ-paris-diderot.fr> <D0751E47-F461-4097-8995-56D6E4E4A4A6@openwrt.org> <87381d85jn.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
From: Steven Barth <cyrus@openwrt.org>
Date: Sat, 27 Jun 2015 19:23:51 +0200
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <AE09A9C8-4CEE-4EC5-B31D-ACE45599A6B2@openwrt.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/R2SUDNbpDURDsu0aLH19fEgCyzI>
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] How to compute DNCP/HNCP node data?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 17:23:55 -0000

>> Profile recommendations section in dncp recommends sha-256.
>
>Er... -06 recommends the leading 8 octets of MD-5.  Section 3.

DNCP recommends sha256 for profiles. HNCP uses what you mentioned.


>1. simply copy the has received from the originator, no questions
>asked; 
>2. hash the raw data received from the originator; 
>3. hash data that I've formatted from my internal data structures.

Since dncp mandates the canonical order this essentially means 2 and 3 are identical.  I personally don't believe in supporting buggy clients as in clients violating MUST statements since at some point it just breaks.


Cheers,

Steven


From nobody Sat Jun 27 11:25:35 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAB81A6EF1 for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 11:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 js_W8dR4On1V for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 11:25:32 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C47F1A6F0E for <homenet@ietf.org>; Sat, 27 Jun 2015 11:25:32 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9F1F420098 for <homenet@ietf.org>; Sat, 27 Jun 2015 14:40:51 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id F27EA63AE8; Sat, 27 Jun 2015 14:25:30 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D858463AD9 for <homenet@ietf.org>; Sat, 27 Jun 2015 14:25:30 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: HOMENET <homenet@ietf.org>
In-Reply-To: <558DB74C.8040106@gmail.com>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 27 Jun 2015 14:25:30 -0400
Message-ID: <10261.1435429530@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/RNH22IDBj0RNnd7IDMjmFwKh93A>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 18:25:34 -0000

--=-=-=
Content-Type: text/plain


    >>> And sorry if I sound like a broken record, but I would like the ability to
    >>> set up a router-router link with less than a full /64 allocated to it, at
    >>> least in the ad-hoc case.

Not sure who said this part.

My question is: for a router/router link, even if it's really ethernet rather
than PPP, why wouldn't one use *just* link-local addresses?  While I have
encountered a few OSPFv3 implementations that wouldn't run over link-local
addresses, the vendors admitted that it was a bug. (That equipment got
obsoleted due to 512K limit on v4 routing slots before that got fixed though)

If there something in HNCP that would require router/router links to be
numbered?   Or is it a case of, one just doesn't *know* that there will never
be end-hosts on the link.   If one requires manual intervention to allocate
a prefix longer than /64 to a link, then one could also just say it was a
router-only link.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVY7ql4CLcPvd0N1lAQLe5wf+KzZUH8mX0rw7huEeX4N/W28OC38m1J+2
sEOXKWAJ+dAGOK07Q7aK9sTO5YK10P55G+wwIgCbaq2VBYUvuJqC1e6iExlNPHE3
Z8sQ8tHgTRvloC05xOY/8WoyjNEz+t7ikNtwZkZEq3SdLFne1b5QHhtMCvCo1qjn
3FYZdxF5vtsv+OSvombrnnHTCjW0EwHZqWcLXIvwD2igHJ4yT2uL+Qwvj1p8HozH
vrRyc4PiWrSDyjK5NwbJZ76ROeZQi2mnXLk5yQJrA88Z1Uw2K126D+SN3xOdNgiz
6SQ+zvdcKknuxAc6yFeijZ9IZyohD2MaXvZ+ERf+FeYrNsged6R1RQ==
=3H4W
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Jun 27 13:16:03 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD5A1A8943 for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 13:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 WTnVbcp1pJZx for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 13:16:00 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (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 7B5141A8935 for <homenet@ietf.org>; Sat, 27 Jun 2015 13:16:00 -0700 (PDT)
Received: by pactm7 with SMTP id tm7so84835372pac.2 for <homenet@ietf.org>; Sat, 27 Jun 2015 13:16:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5bkJNgH0reEBLgTKaPgpkBOuBAwCYxTib+mnrbQWXG4=; b=QFdh1zz7X0FYA1+B6xlPEz2zjgoXe96gLfqW699IymSKVJ1b7zkEqq9Qflvb6l83Fm SjK7ach30eVKmkn+BeRHmjm11v3l6xNvNoB//8Rn10fWGER3MMGNJfi5QhPMkZHvje2d a04YAEfvqqmgsTs75LnHKSTKfP21vlB8zOaNVGPBfN+8VNZ4b0dlMItq8b7xhPPz4Kxp oK8LvgVbit8KtrbgdYsPx5x+TjWdP6eWh8/PJeYn6ccAZoGEVrcLkiPfhlFl/hwX0pOM a/BbVAWqAqUO18E+UEiyJYSU1nWlbSjgANhkSIbUYez8j4i2KT1Da9So+qQrPQ64a+nK 4Sdg==
X-Received: by 10.68.240.7 with SMTP id vw7mr16284721pbc.135.1435436160167; Sat, 27 Jun 2015 13:16:00 -0700 (PDT)
Received: from ?IPv6:2406:e007:7d57:1:28cc:dc4c:9703:6781? ([2406:e007:7d57:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id ll6sm37259505pbc.28.2015.06.27.13.15.57 for <homenet@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 27 Jun 2015 13:15:58 -0700 (PDT)
Message-ID: <558F0475.8010005@gmail.com>
Date: Sun, 28 Jun 2015 08:15:49 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <10261.1435429530@sandelman.ca>
In-Reply-To: <10261.1435429530@sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/AbS0uavjGApX45E_thl4hDa3OL8>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 20:16:02 -0000

On 28/06/2015 06:25, Michael Richardson wrote:
> 
>     >>> And sorry if I sound like a broken record, but I would like the ability to
>     >>> set up a router-router link with less than a full /64 allocated to it, at
>     >>> least in the ad-hoc case.
> 
> Not sure who said this part.
> 
> My question is: for a router/router link, even if it's really ethernet rather
> than PPP, why wouldn't one use *just* link-local addresses?  

As long as you don't break the rules by using those addresses in ICMP replies.

   Brian

> While I have
> encountered a few OSPFv3 implementations that wouldn't run over link-local
> addresses, the vendors admitted that it was a bug. (That equipment got
> obsoleted due to 512K limit on v4 routing slots before that got fixed though)
> 
> If there something in HNCP that would require router/router links to be
> numbered?   Or is it a case of, one just doesn't *know* that there will never
> be end-hosts on the link.   If one requires manual intervention to allocate
> a prefix longer than /64 to a link, then one could also just say it was a
> router-only link.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 


From SRS0=naiM=HF=darou.fr=pierre.pfister@bounces.m4x.org  Sat Jun 27 14:48:51 2015
Return-Path: <SRS0=naiM=HF=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD141A9042 for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 14:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 cESMbKJZ3Q-W for <homenet@ietfa.amsl.com>; Sat, 27 Jun 2015 14:48:48 -0700 (PDT)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7CE71A1BDD for <homenet@ietf.org>; Sat, 27 Jun 2015 14:48:48 -0700 (PDT)
Received: from ppfister-m-ja6k.home (AStrasbourg-651-1-45-129.w90-6.abo.wanadoo.fr [90.6.240.129]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id C438D1408EFB4; Sat, 27 Jun 2015 23:48:42 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr>
Date: Sat, 27 Jun 2015 23:48:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2098)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Sat Jun 27 23:48:44 2015 +0200 (CEST))
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/NV1uJ1ODB5e4ydZl6otSXVaKCyI>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sat, 27 Jun 2015 21:49:12 -0000

Hello Juliusz and Brian,

I agree with you both. The text is actually how it is because of strong =
opinions I received from others.
IMO, 64 should be preferred as long as it does not harm the network=20
(or in cases where it is obviously not necessary, such as point-to-point =
links).

Relaxing the =C2=AB administrator =C2=BB may be confusing, as Brian =
said.
So I guess the MUST could become a SHOULD, which imply it requires =
implementers to fully understand the drawbacks
of using non-64 prefix lengths. For instance, /127 could be =
automatically used (no need for administrator) if a link
is auto-detected as point-to-point.

- Pierre

>=20
>>> +10 on /128 support.
>=20
>> If you mean RFC6164, that would be a /127 prefix.
>=20
> I think Dave meant no on-link information, which unless I'm mistaken =
is equivalent to putting a /128 on the interface.  With explicitly =
scoped link-local addresses, on-link information becomes a mere =
optimisation (although an important one in the multihomed host case, =
where redirects cannot cause you to switch interfaces).
>=20
>> "  If the considered delegated prefix is an IPv6 prefix, and whenever
>>   there is at least one available prefix of length 64, a prefix of
>>   length 64 MUST be selected unless configured otherwise by an
>>   administrator.  In case no prefix of length 64 would be available, =
a
>>   longer prefix MAY be selected."
>=20
> Well spotted, thanks.  Markus, would you be open to relaxing the MUST, =
and adding a guideline about which of the available /64s is suitable for =
carving up?
>=20
> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Sun Jun 28 01:58:19 2015
Return-Path: <gert@Space.Net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648BD1AD0CF for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 01:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 33R9rbQSXi-G for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 01:58:16 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DB761AD0CE for <homenet@ietf.org>; Sun, 28 Jun 2015 01:58:15 -0700 (PDT)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 7767362D7A for <homenet@ietf.org>; Sun, 28 Jun 2015 10:58:13 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 3CE0660152 for <homenet@ietf.org>; Sun, 28 Jun 2015 10:58:13 +0200 (CEST)
Received: (qmail 65063 invoked by uid 1007); 28 Jun 2015 10:58:13 +0200
Date: Sun, 28 Jun 2015 10:58:13 +0200
From: Gert Doering <gert@space.net>
To: Pierre Pfister <pierre.pfister@darou.fr>
Message-ID: <20150628085813.GY67883@Space.Net>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr> <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8pEd8DHw51NpBRjSYmCP3F54aLE>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 28 Jun 2015 08:58:18 -0000

Hi,

On Sat, Jun 27, 2015 at 11:48:43PM +0200, Pierre Pfister wrote:
> Relaxing the « administrator » may be confusing, as Brian said.
> So I guess the MUST could become a SHOULD, which imply it requires implementers to fully understand the drawbacks
> of using non-64 prefix lengths. For instance, /127 could be automatically used (no need for administrator) if a link
> is auto-detected as point-to-point.

A MUST is perfectly right here.  You can't have implementation A decide
"let's use a /64 here" while implementation B goes for "/127"...

The sentence is also clearly allowing alternatives: if I tell my router
"hey, I want to use /127s on point-to-point links", this is "unless configured 
otherwise by an administrator", so the MUST is not getting in the way then.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From SRS0=QTgy=HG=darou.fr=pierre.pfister@bounces.m4x.org  Sun Jun 28 06:09:33 2015
Return-Path: <SRS0=QTgy=HG=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31FA01B2CCF for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 06:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 TOOxUyMB7ayO for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 06:09:31 -0700 (PDT)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D84911B2CCC for <homenet@ietf.org>; Sun, 28 Jun 2015 06:09:30 -0700 (PDT)
Received: from [10.61.208.161] (unknown [173.38.220.43]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 636CE140912E2; Sun, 28 Jun 2015 15:09:20 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <20150628085813.GY67883@Space.Net>
Date: Sun, 28 Jun 2015 15:09:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr> <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr> <20150628085813.GY67883@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.2098)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Sun Jun 28 15:09:27 2015 +0200 (CEST))
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jYGV4Hffveb6gqsmaODGTZREdVk>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 28 Jun 2015 13:09:59 -0000

Hello,

> Le 28 juin 2015 =E0 10:58, Gert Doering <gert@space.net> a =E9crit :
>=20
> Hi,
>=20
> On Sat, Jun 27, 2015 at 11:48:43PM +0200, Pierre Pfister wrote:
>> Relaxing the =AB administrator =BB may be confusing, as Brian said.
>> So I guess the MUST could become a SHOULD, which imply it requires =
implementers to fully understand the drawbacks
>> of using non-64 prefix lengths. For instance, /127 could be =
automatically used (no need for administrator) if a link
>> is auto-detected as point-to-point.
>=20
> A MUST is perfectly right here.  You can't have implementation A =
decide
> "let's use a /64 here" while implementation B goes for "/127"=85

You actually can have implementations with different prefix length.=20
This is handled by the prefix assignment algorithm.
You may have multiple routers with multiple prefix lengths, but one =
single
prefix is ultimately chosen and used by all routers connected to the =
link.

- Pierre

>=20
> The sentence is also clearly allowing alternatives: if I tell my =
router
> "hey, I want to use /127s on point-to-point links", this is "unless =
configured=20
> otherwise by an administrator", so the MUST is not getting in the way =
then.
>=20
> Gert Doering
>        -- NetMaster
> --=20
> have you enabled IPv6 on something today...?
>=20
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. =
Grundner-Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Sun Jun 28 07:22:47 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 352FA1B2DA6 for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 07:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 TSCy3DnNBXLZ for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 07:22:44 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BA971B2D97 for <homenet@ietf.org>; Sun, 28 Jun 2015 07:22:41 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5SEMdLO014110 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <homenet@ietf.org>; Sun, 28 Jun 2015 16:22:40 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t5SEMd29015070 for <homenet@ietf.org>; Sun, 28 Jun 2015 16:22:39 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 742CB61FA1 for <homenet@ietf.org>; Sun, 28 Jun 2015 16:22:39 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id POu9z-OjIDR3 for <homenet@ietf.org>; Sun, 28 Jun 2015 16:22:38 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 96DDE61F9D for <homenet@ietf.org>; Sun, 28 Jun 2015 16:22:37 +0200 (CEST)
Date: Sun, 28 Jun 2015 16:22:37 +0200
Message-ID: <87wpynnc9e.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: HOMENET <homenet@ietf.org>
In-Reply-To: <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr> <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr> <20150628085813.GY67883@Space.Net> <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Sun, 28 Jun 2015 16:22:40 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sun, 28 Jun 2015 16:22:39 +0200 (CEST)
X-Miltered: at korolev with ID 5590032F.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5590032F.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5590032F.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5590032F.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5590032F.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5590032F.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/q-mmk36lejQLLRsOxslltHoSTdw>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 28 Jun 2015 14:22:46 -0000

Concerning the /128-on-loopback issue...

The HNCP draft is not quite clear about the semantics of the NODE-ADDRESS 
TLV (Section 6.3 of -06).  Is that for on-link addresses only?

In other words, is it legal for a router to grab an address from a prefix 
assigned by some other router (not necessarily a neighbour), advertise it 
over NODE-ADDRESS, assign it to one if its interfaces, and advertise the 
/128 over Babel?

If it's legal and doesn't cause any issues I don't see, then that pretty 
much solves this particular problem.

-- Juliusz


From nobody Sun Jun 28 11:22:42 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF3E1A0130 for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 11:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 oF3xiakXNIdx for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 11:22:40 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A96401A0126 for <homenet@ietf.org>; Sun, 28 Jun 2015 11:22:39 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5SIMbH2019855; Sun, 28 Jun 2015 20:22:37 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 7EC6261FA1; Sun, 28 Jun 2015 20:22:37 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Cd-ZERlTjczm; Sun, 28 Jun 2015 20:22:36 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 4932B61F9D; Sun, 28 Jun 2015 20:22:33 +0200 (CEST)
Date: Sun, 28 Jun 2015 20:22:33 +0200
Message-ID: <87a8vjn15i.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>, Steven Barth <cyrus@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 28 Jun 2015 20:22:37 +0200 (CEST)
X-Miltered: at korolev with ID 55903B6D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 55903B6D.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 55903B6D.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/p6JbR2HEF5Z0MfrEgYfbgzBqEd4>
Cc: homenet@ietf.org
Subject: [homenet] DNCP: issue with network partitions and monitoring nodes
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 28 Jun 2015 18:22:41 -0000

Markus, Steven,

Unless I'm mistaken, there's an issue with DNCP and monitoring nodes.  
Consider the following topology:


   A --- M --- B

A and B are ordinary DNCP nodes, while M is a monitoring node, as 
described in the second paragraph of Section 4.4.  So M doesn't publish 
a NODE-STATE TLV, but other than that it fully participates in the 
protocol.

Due to the silly walk described in Section 4.6, A's network state consists 
of just itself, and similarly B.  Whenever M sends a NODE-STATE TLV, 
either A's or B's Trickle timers are reset, leading to excessive traffic.

I don't see a good solution to that.  If you don't reset trickle when you 
see inconsistency from a node that doesn't publish NODE-STATE, then you 
have a bootstrapping problem (new node whose NODE-STATE is unknown).  If 
you forbid monitoring nodes from sending NODE-STATE, then you break 
Trickle for them.

Perhaps there's no good way to allow a node to participate without 
publishing NODE-STATE.  Grr.

-- Juliusz


From nobody Sun Jun 28 13:00:34 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2E9E1A21B1 for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 13:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 HYzv4mQBR4zX for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 13:00:31 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (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 32BCB1A21AC for <homenet@ietf.org>; Sun, 28 Jun 2015 13:00:31 -0700 (PDT)
Received: by pactm7 with SMTP id tm7so93666888pac.2 for <homenet@ietf.org>; Sun, 28 Jun 2015 13:00:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=c3wuTBfyMn5slKKGJBb2kN30+6HGAzdUWie7P/hRzVc=; b=dJzyh57FakM51pfoygPdVd3LqtchMUToRRMQ7ypEli8PkdRg/fkT1X/PhMc9gJfMGU RS3NXp9QGfw2mavPS+qvlOYv71CQqlhg6TK/pYrLkw88/RsnfX/XTu0mV4bXDx4NUcnZ c5YUfXnCgFx9EvLzp7/lL1BjP6V9nj9keroa6Nl8tUHhQ0Efmo8FxzIG4+nis7t+yPv8 NcBHO7Atz5BNbQPer3XRtRO+QcpkbKAzZ7eZrXYh/P1AyuTTFUlnumqxQftYxgWDm586 wC3A+N3wJk5x/Cx+yP1v/EaMy2iLIg1JIRMS2BAS1FB430feccYhpbAlorIlegmCKZ/O skag==
X-Received: by 10.70.37.144 with SMTP id y16mr24683313pdj.86.1435521630801; Sun, 28 Jun 2015 13:00:30 -0700 (PDT)
Received: from ?IPv6:2406:e007:5d86:1:28cc:dc4c:9703:6781? ([2406:e007:5d86:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id qa10sm2260711pbc.44.2015.06.28.13.00.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Jun 2015 13:00:29 -0700 (PDT)
Message-ID: <55905253.6090900@gmail.com>
Date: Mon, 29 Jun 2015 08:00:19 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Pierre Pfister <pierre.pfister@darou.fr>,  Gert Doering <gert@space.net>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr> <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr> <20150628085813.GY67883@Space.Net> <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr>
In-Reply-To: <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Cvz0GlRiVUJuQ7_wrN97DdwWYf8>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 28 Jun 2015 20:00:33 -0000

On 29/06/2015 01:09, Pierre Pfister wrote:
> Hello,
>=20
>> Le 28 juin 2015 =C3=A0 10:58, Gert Doering <gert@space.net> a =C3=A9cr=
it :
>>
>> Hi,
>>
>> On Sat, Jun 27, 2015 at 11:48:43PM +0200, Pierre Pfister wrote:
>>> Relaxing the =C2=AB administrator =C2=BB may be confusing, as Brian s=
aid.
>>> So I guess the MUST could become a SHOULD, which imply it requires im=
plementers to fully understand the drawbacks
>>> of using non-64 prefix lengths. For instance, /127 could be automatic=
ally used (no need for administrator) if a link
>>> is auto-detected as point-to-point.
>>
>> A MUST is perfectly right here.  You can't have implementation A decid=
e
>> "let's use a /64 here" while implementation B goes for "/127"=E2=80=A6=

>=20
> You actually can have implementations with different prefix length.=20
> This is handled by the prefix assignment algorithm.

Yes, you need that ability in the protocol, but it won't work in practice=

to pick an oddball like /80 unless all the host stacks on the link can
handle a shorter IID like 48 (whether it's a LAN or a pt2pt). RFC 7421.

> You may have multiple routers with multiple prefix lengths, but one sin=
gle
> prefix is ultimately chosen and used by all routers connected to the li=
nk.

So will it work if one router on a pt2pt expects to use a /127 and the ot=
her
one can only support /64?

    Brian

>=20
> - Pierre
>=20
>>
>> The sentence is also clearly allowing alternatives: if I tell my route=
r
>> "hey, I want to use /127s on point-to-point links", this is "unless co=
nfigured=20
>> otherwise by an administrator", so the MUST is not getting in the way =
then.
>>
>> Gert Doering
>>        -- NetMaster
>> --=20
>> have you enabled IPv6 on something today...?
>>
>> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
>> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Cul=
emann
>> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
>> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> .
>=20


From nobody Sun Jun 28 13:49:18 2015
Return-Path: <pierre.pfister@darou.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 553C21A88C6 for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 13:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.356
X-Spam-Level: 
X-Spam-Status: No, score=-1.356 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 nLrC8TVli7NM for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 13:49:15 -0700 (PDT)
Received: from ks395963.kimsufi.com (darou.fr [IPv6:2001:41d0:8:408c::1111]) by ietfa.amsl.com (Postfix) with ESMTP id 101381A88BE for <homenet@ietf.org>; Sun, 28 Jun 2015 13:49:15 -0700 (PDT)
Received: by ks395963.kimsufi.com (Postfix, from userid 112) id 1870E60432; Sun, 28 Jun 2015 22:49:14 +0200 (CEST)
Received: from [192.168.42.11] (ip-61.net-82-216-124.rev.numericable.fr [82.216.124.61]) (Authenticated sender: pierre@darou.fr) by ks395963.kimsufi.com (Postfix) with ESMTPSA id C3A5660227; Sun, 28 Jun 2015 22:49:11 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_595606D0-03E3-4BBD-9AB6-3A5C5FCBFEAB"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <87wpynnc9e.wl-jch@pps.univ-paris-diderot.fr>
Date: Sun, 28 Jun 2015 22:49:13 +0200
Message-Id: <D05C498F-2F5B-4997-9281-5C89EAC6A6FD@darou.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr> <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr> <20150628085813.GY67883@Space.Net> <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr> <87wpynnc9e.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jgSM9xebu1cXKQu519Flb_-EVwI>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 28 Jun 2015 20:49:17 -0000

--Apple-Mail=_595606D0-03E3-4BBD-9AB6-3A5C5FCBFEAB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hello Juliusz,

No, as it is specified for now, a router cannot assign an address on an =
end-point=20
unless that en-point is in a =E2=80=98Common Link=E2=80=99 which =
includes the end-point identifier.
"An assigned address MUST be in the first quarter of an assigned
      prefix currently applied on a Common Link which includes the
      interface specified by the endpoint identifier."

The address assignment process does not require this limitation though. =
I guess we could consider removing that.

But if what you are trying to do is assign sparse /128 to different =
links or loopbacks, there exists a perfectly valid way to do so.
A router can assign a /128 prefix for private use (just like it would do =
a PD, i.e., by advertising an ASSIGNED-PREFIX TLV with an End-Point ID =
equal to 0,=20
or even another End-Point ID that is not used by any real interfaces), =
and use the address (And advertise it through the RP,=20
just like it would do with any other assigned prefix).

- Pierre


> Le 28 juin 2015 =C3=A0 16:22, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> a =C3=A9crit :
>=20
> Concerning the /128-on-loopback issue...
>=20
> The HNCP draft is not quite clear about the semantics of the =
NODE-ADDRESS TLV (Section 6.3 of -06).  Is that for on-link addresses =
only?
>=20
> In other words, is it legal for a router to grab an address from a =
prefix assigned by some other router (not necessarily a neighbour), =
advertise it over NODE-ADDRESS, assign it to one if its interfaces, and =
advertise the /128 over Babel?
>=20
> If it's legal and doesn't cause any issues I don't see, then that =
pretty much solves this particular problem.
>=20
> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_595606D0-03E3-4BBD-9AB6-3A5C5FCBFEAB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Hello Juliusz,</div><div class=3D""><br =
class=3D""></div><div class=3D"">No, as it is specified for now, a =
router cannot assign an address on an end-point&nbsp;</div><div =
class=3D"">unless that en-point is in a =E2=80=98Common Link=E2=80=99 =
which includes the end-point identifier.</div><div class=3D""><font =
face=3D"Courier" class=3D"">"<span style=3D"font-size: 13px;" =
class=3D"">An assigned address MUST be in the first quarter of an =
assigned</span></font></div><pre class=3D"newpage" style=3D"font-size: =
13px; margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><font face=3D"Courier" class=3D"">      prefix currently =
applied on a Common Link which includes the
      interface specified by the endpoint identifier."</font></pre><div =
class=3D""><br class=3D""></div><div class=3D"">The address assignment =
process does not require this limitation though. I guess we could =
consider removing that.</div><div class=3D""><br class=3D""></div><div =
class=3D"">But if what you are trying to do is assign sparse /128 to =
different links or loopbacks, there exists a perfectly valid way to do =
so.</div><div class=3D"">A router can assign a /128 prefix for private =
use (just like it would do a PD, i.e., by advertising an ASSIGNED-PREFIX =
TLV with an End-Point ID equal to 0,&nbsp;</div><div class=3D"">or even =
another End-Point ID that is not used by any real interfaces), and use =
the address (And advertise it through the RP,&nbsp;</div><div =
class=3D"">just like it would do with any other assigned =
prefix).</div><div class=3D""><br class=3D""></div><div class=3D"">- =
Pierre</div><div class=3D""><br class=3D""></div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">Le =
28 juin 2015 =C3=A0 16:22, Juliusz Chroboczek &lt;<a =
href=3D"mailto:jch@pps.univ-paris-diderot.fr" =
class=3D"">jch@pps.univ-paris-diderot.fr</a>&gt; a =C3=A9crit :</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">Concerning the =
/128-on-loopback issue...<br class=3D""><br class=3D"">The HNCP draft is =
not quite clear about the semantics of the NODE-ADDRESS TLV (Section 6.3 =
of -06). &nbsp;Is that for on-link addresses only?<br class=3D""><br =
class=3D"">In other words, is it legal for a router to grab an address =
from a prefix assigned by some other router (not necessarily a =
neighbour), advertise it over NODE-ADDRESS, assign it to one if its =
interfaces, and advertise the /128 over Babel?<br class=3D""><br =
class=3D"">If it's legal and doesn't cause any issues I don't see, then =
that pretty much solves this particular problem.<br class=3D""><br =
class=3D"">-- Juliusz<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">homenet mailing list<br class=3D""><a =
href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/homenet<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_595606D0-03E3-4BBD-9AB6-3A5C5FCBFEAB--


From nobody Sun Jun 28 14:10:03 2015
Return-Path: <pierre.pfister@darou.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EADFE1A8941 for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 14:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.356
X-Spam-Level: 
X-Spam-Status: No, score=-1.356 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 gYh09JdhY1I4 for <homenet@ietfa.amsl.com>; Sun, 28 Jun 2015 14:10:00 -0700 (PDT)
Received: from ks395963.kimsufi.com (darou.fr [176.31.121.140]) by ietfa.amsl.com (Postfix) with ESMTP id 58CAF1A88FD for <homenet@ietf.org>; Sun, 28 Jun 2015 14:10:00 -0700 (PDT)
Received: by ks395963.kimsufi.com (Postfix, from userid 112) id 992AA60432; Sun, 28 Jun 2015 23:09:59 +0200 (CEST)
Received: from [192.168.42.11] (ip-61.net-82-216-124.rev.numericable.fr [82.216.124.61]) (Authenticated sender: pierre@darou.fr) by ks395963.kimsufi.com (Postfix) with ESMTPSA id 3DDA660227; Sun, 28 Jun 2015 23:09:56 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B7201ADD-119C-4BBF-BBDB-A067CE80A094"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <55905253.6090900@gmail.com>
Date: Sun, 28 Jun 2015 23:09:58 +0200
Message-Id: <B56E4B9D-321A-436A-97A8-F5B3355FC549@darou.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr> <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr> <20150628085813.GY67883@Space.Net> <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr> <55905253.6090900@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/-8kfWCo1VH40TL06qx1U1u_uAT8>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Gert Doering <gert@space.net>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Sun, 28 Jun 2015 21:10:03 -0000

--Apple-Mail=_B7201ADD-119C-4BBF-BBDB-A067CE80A094
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 28 juin 2015 =C3=A0 22:00, Brian E Carpenter =
<brian.e.carpenter@gmail.com> a =C3=A9crit :
>=20
> On 29/06/2015 01:09, Pierre Pfister wrote:
>> Hello,
>>=20
>>> Le 28 juin 2015 =C3=A0 10:58, Gert Doering <gert@space.net> a =C3=A9cr=
it :
>>>=20
>>> Hi,
>>>=20
>>> On Sat, Jun 27, 2015 at 11:48:43PM +0200, Pierre Pfister wrote:
>>>> Relaxing the =C2=AB administrator =C2=BB may be confusing, as Brian =
said.
>>>> So I guess the MUST could become a SHOULD, which imply it requires =
implementers to fully understand the drawbacks
>>>> of using non-64 prefix lengths. For instance, /127 could be =
automatically used (no need for administrator) if a link
>>>> is auto-detected as point-to-point.
>>>=20
>>> A MUST is perfectly right here.  You can't have implementation A =
decide
>>> "let's use a /64 here" while implementation B goes for "/127"=E2=80=A6=

>>=20
>> You actually can have implementations with different prefix length.=20=

>> This is handled by the prefix assignment algorithm.
>=20
> Yes, you need that ability in the protocol, but it won't work in =
practice
> to pick an oddball like /80 unless all the host stacks on the link can
> handle a shorter IID like 48 (whether it's a LAN or a pt2pt). RFC =
7421.

Which is why /64 SHOULD be preferred.
We also have this:
"In any case, a router MUST support a mechanism suitable to distribute
   addresses from the considered prefix to clients on the link.
   Otherwise it MUST NOT create or adopt it, i.e. a router assigning an
   IPv4 prefix MUST support the L-capability and a router assigning an
   IPv6 prefix not suitable for Stateless Address Autoconfiguration MUST
   support the H-capability as defined in Section 10 =
<https://tools.ietf.org/html/draft-ietf-homenet-hncp-06#section-10>.
"

So a router will not advertise a /80 on a typical link unless it =
implements stageful DHCPv6.

>=20
>> You may have multiple routers with multiple prefix lengths, but one =
single
>> prefix is ultimately chosen and used by all routers connected to the =
link.
>=20
> So will it work if one router on a pt2pt expects to use a /127 and the =
other
> one can only support /64?

The current document does not specify how to configure a pt2pt link.
This could be specified later really easily, in a backward compatible =
way.
Also, in general, why and how would a router assign a /64 to a pt2pt =
link ?
I mean, considering pt2pt link, we can assume both ends of the link know =
the nature of the link=E2=80=A6
and are therefore able to not do weird things such as assigning a /64 on =
a pt2pt link.

- Pierre

>=20
>    Brian
>=20
>>=20
>> - Pierre
>>=20
>>>=20
>>> The sentence is also clearly allowing alternatives: if I tell my =
router
>>> "hey, I want to use /127s on point-to-point links", this is "unless =
configured=20
>>> otherwise by an administrator", so the MUST is not getting in the =
way then.
>>>=20
>>> Gert Doering
>>>       -- NetMaster
>>> --=20
>>> have you enabled IPv6 on something today...?
>>>=20
>>> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
>>> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. =
Grundner-Culemann
>>> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
>>> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
>>>=20
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homenet
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>> .
>>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_B7201ADD-119C-4BBF-BBDB-A067CE80A094
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><br class=3D""></div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">Le =
28 juin 2015 =C3=A0 22:00, Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com" =
class=3D"">brian.e.carpenter@gmail.com</a>&gt; a =C3=A9crit :</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">On 29/06/2015 01:09, =
Pierre Pfister wrote:<br class=3D""><blockquote type=3D"cite" =
class=3D"">Hello,<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">Le 28 juin 2015 =C3=A0 10:58, Gert Doering &lt;<a =
href=3D"mailto:gert@space.net" class=3D"">gert@space.net</a>&gt; a =
=C3=A9crit :<br class=3D""><br class=3D"">Hi,<br class=3D""><br =
class=3D"">On Sat, Jun 27, 2015 at 11:48:43PM +0200, Pierre Pfister =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">Relaxing the =
=C2=AB administrator =C2=BB may be confusing, as Brian said.<br =
class=3D"">So I guess the MUST could become a SHOULD, which imply it =
requires implementers to fully understand the drawbacks<br class=3D"">of =
using non-64 prefix lengths. For instance, /127 could be automatically =
used (no need for administrator) if a link<br class=3D"">is =
auto-detected as point-to-point.<br class=3D""></blockquote><br =
class=3D"">A MUST is perfectly right here. &nbsp;You can't have =
implementation A decide<br class=3D"">"let's use a /64 here" while =
implementation B goes for "/127"=E2=80=A6<br class=3D""></blockquote><br =
class=3D"">You actually can have implementations with different prefix =
length. <br class=3D"">This is handled by the prefix assignment =
algorithm.<br class=3D""></blockquote><br class=3D"">Yes, you need that =
ability in the protocol, but it won't work in practice<br class=3D"">to =
pick an oddball like /80 unless all the host stacks on the link can<br =
class=3D"">handle a shorter IID like 48 (whether it's a LAN or a pt2pt). =
RFC 7421.<br class=3D""></div></blockquote><div><br =
class=3D""></div><div>Which is why /64 SHOULD be preferred.</div><div>We =
also have this:</div><div><font face=3D"Courier" class=3D"">"<span =
style=3D"font-size: 13px;" class=3D"">In any case, a router MUST support =
a mechanism suitable to distribute</span></font></div><pre =
class=3D"newpage" style=3D"font-size: 13px; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always;"><font face=3D"Courier" =
class=3D"">   addresses from the considered prefix to clients on the =
link.
   Otherwise it MUST NOT create or adopt it, i.e. a router assigning an
   IPv4 prefix MUST support the L-capability and a router assigning an
   IPv6 prefix not suitable for Stateless Address Autoconfiguration MUST
   support the H-capability as defined in <a =
href=3D"https://tools.ietf.org/html/draft-ietf-homenet-hncp-06#section-10"=
 class=3D"">Section 10</a>.</font></pre><div class=3D""><font =
face=3D"Courier" class=3D"">"</font></div><div class=3D""><br =
class=3D""></div><div class=3D"">So a router will not advertise a /80 on =
a typical link unless it implements stageful DHCPv6.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">You may have multiple =
routers with multiple prefix lengths, but one single<br class=3D"">prefix =
is ultimately chosen and used by all routers connected to the link.<br =
class=3D""></blockquote><br class=3D"">So will it work if one router on =
a pt2pt expects to use a /127 and the other<br class=3D"">one can only =
support /64?<br class=3D""></div></blockquote><div><br =
class=3D""></div><div>The current document does not specify how to =
configure a pt2pt link.</div><div>This could be specified later really =
easily, in a backward compatible way.</div><div>Also, in general, why =
and how would a router assign a /64 to a pt2pt link ?</div><div>I mean, =
considering pt2pt link, we can assume both ends of the link know the =
nature of the link=E2=80=A6</div><div>and are therefore able to not do =
weird things such as assigning a /64 on a pt2pt link.</div><div><br =
class=3D""></div><div>- Pierre</div><div><br class=3D""></div><blockquote =
type=3D"cite" class=3D""><div class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;Brian<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"">- Pierre<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">The =
sentence is also clearly allowing alternatives: if I tell my router<br =
class=3D"">"hey, I want to use /127s on point-to-point links", this is =
"unless configured <br class=3D"">otherwise by an administrator", so the =
MUST is not getting in the way then.<br class=3D""><br class=3D"">Gert =
Doering<br class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- =
NetMaster<br class=3D"">-- <br class=3D"">have you enabled IPv6 on =
something today...?<br class=3D""><br class=3D"">SpaceNet AG =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Vorstand: =
Sebastian v. Bomhard<br class=3D"">Joseph-Dollinger-Bogen 14 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Aufsichtsratsvors.: =
A. Grundner-Culemann<br class=3D"">D-80807 Muenchen =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;HRB: 136055 (AG Muenchen)<br =
class=3D"">Tel: +49 (0)89/32356-444 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;USt-IdNr.: =
DE813185279<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">homenet mailing list<br class=3D""><a =
href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/homenet<br =
class=3D""></blockquote><br =
class=3D"">_______________________________________________<br =
class=3D"">homenet mailing list<br class=3D""><a =
href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/homenet<br =
class=3D"">.<br class=3D""><br class=3D""></blockquote><br =
class=3D"">_______________________________________________<br =
class=3D"">homenet mailing list<br class=3D""><a =
href=3D"mailto:homenet@ietf.org" class=3D"">homenet@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/homenet<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_B7201ADD-119C-4BBF-BBDB-A067CE80A094--


From nobody Mon Jun 29 02:40:25 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 129211A8924 for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 02:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.279
X-Spam-Level: 
X-Spam-Status: No, score=0.279 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_NEUTRAL=0.779] autolearn=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 RgblRN5yzKKE for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 02:40:20 -0700 (PDT)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.229]) by ietfa.amsl.com (Postfix) with ESMTP id E7B3C1A891C for <homenet@ietf.org>; Mon, 29 Jun 2015 02:40:19 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 5511FF64074087C6; Mon, 29 Jun 2015 12:40:18 +0300
Message-ID: <55911299.7060205@iki.fi>
Date: Mon, 29 Jun 2015 12:40:41 +0300
From: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com>	<5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nR8kaznNZaBx9IG_QjR_3aSjLRg>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Mon, 29 Jun 2015 09:40:22 -0000

On 26.6.2015 18.41, Juliusz Chroboczek wrote:
> Markus,
>
> I still don't understand the intent of the "ad hoc" interface type.
>
> If the ad-hoc interface is designed for non-transitive links, then the
> draft should say so (in which case I'll be glad to provide you with
> suitable prose).  However, in this case it should also identify the bits
> of DNCP which are not applicable to non-transitive interfaces (Section
> 6.1.5, obviously, but I don't understand DNCP well enough to say if
> there are others).

Clarifications on the text are obviously welcome and even needed :)

Due to renumbering of sections, this is bit awkward, but _as far as I 
know_, the only part that requires transitive interfaces _in DNCP_ is 
the support for dense broadcast links.

6.1.5 in dncp-06 is 'neighbor removal', and it makes no transitivity 
assumption. For each individual node, an endpoint is a local construct 
(e.g. 'this meshy eth0 interface I want to multicast+unicast on') and 
the peers that are present on it (nodes N_1.. N_n that happen to have 
been recently reachable / we have received keep-alives from / we know to 
be there by other means).

> Section 4 speaks of "ad-hoc mode" -- does that mean 802.11 IBSS?  If it
> is, then you should use the proper terminology, but I think that support
> for non-transitive links should not be restricted to 802.11 (even if the
> implementation is limited to it).

Even implementation isn't limited to it.

> And sorry if I sound like a broken record, but I would like the ability
> to set up a router-router link with less than a full /64 allocated to
> it, at least in the ad-hoc case.

I am not sure about the draft text about what it should say, as non-/64 
seems to be a political hot potato (there are drafts on this too), but 
at least the implementation isn't limited to this (given configuration) 
and the draft allows for it as well (given configuration). The default 
of /64 seems still sane to me though, given no configuration.

Cheers,

-Markus


From nobody Mon Jun 29 02:58:01 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B831A8977 for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 02:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 xAnTZQVXY2J2 for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 02:57:57 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FBE51A8974 for <homenet@ietf.org>; Mon, 29 Jun 2015 02:57:56 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5T9vsVl029556; Mon, 29 Jun 2015 11:57:54 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id AF3F961F9D; Mon, 29 Jun 2015 11:57:54 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id IL71QiOniP1j; Mon, 29 Jun 2015 11:57:53 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B291361F9A; Mon, 29 Jun 2015 11:57:53 +0200 (CEST)
Date: Mon, 29 Jun 2015 11:57:53 +0200
Message-ID: <871tgualb2.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <55911299.7060205@iki.fi>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <55911299.7060205@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 29 Jun 2015 11:57:54 +0200 (CEST)
X-Miltered: at korolev with ID 559116A2.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 559116A2.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 559116A2.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/0VRy03na2lnm3tgd2bTzzDMGV3U>
Cc: homenet@ietf.org
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Mon, 29 Jun 2015 09:57:59 -0000

> _as far as I know_, the only part that requires transitive interfaces 
> _in DNCP_ is the support for dense broadcast links.

After staring at the draft for two days, I agree.

-- Juliusz


From nobody Mon Jun 29 03:31:19 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5D41A8A72 for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 03:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_NEUTRAL=0.779] autolearn=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 wNO1PZaOi80g for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 03:31:17 -0700 (PDT)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.230]) by ietfa.amsl.com (Postfix) with ESMTP id 136DE1A8A71 for <homenet@ietf.org>; Mon, 29 Jun 2015 03:31:17 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 5511FF6407409F67; Mon, 29 Jun 2015 13:31:16 +0300
Message-ID: <55911E8A.7090408@iki.fi>
Date: Mon, 29 Jun 2015 13:31:38 +0300
From: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,  Steven Barth <cyrus@openwrt.org>
References: <87a8vjn15i.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87a8vjn15i.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/64DwKMaPEMacDF1T4sneutL-k-o>
Cc: homenet@ietf.org
Subject: Re: [homenet] DNCP: issue with network partitions and monitoring nodes
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Mon, 29 Jun 2015 10:31:18 -0000

On 28.6.2015 21.22, Juliusz Chroboczek wrote:
> Markus, Steven,
>
> Unless I'm mistaken, there's an issue with DNCP and monitoring nodes.
> Consider the following topology:
>
>
>    A --- M --- B

I would not call that node 'monitor'; instead e.g. 'forwarding' or 
'bridge' node. To me, 'monitor' implies passive observation. This does 
not seem to be that.

> A and B are ordinary DNCP nodes, while M is a monitoring node, as
> described in the second paragraph of Section 4.4.  So M doesn't publish
> a NODE-STATE TLV, but other than that it fully participates in the
> protocol.
>
> Due to the silly walk described in Section 4.6, A's network state
> consists of just itself, and similarly B.  Whenever M sends a NODE-STATE
> TLV, either A's or B's Trickle timers are reset, leading to excessive
> traffic.

I wonder if it is too late to change it to 'silly walk', it is much 
better than the boring 'topology graph traversal' that Thomas Clausen 
wanted.

> I don't see a good solution to that.  If you don't reset trickle when
> you see inconsistency from a node that doesn't publish NODE-STATE, then
> you have a bootstrapping problem (new node whose NODE-STATE is
> unknown).  If you forbid monitoring nodes from sending NODE-STATE, then
> you break Trickle for them.
>
> Perhaps there's no good way to allow a node to participate without
> publishing NODE-STATE.  Grr.

That, essentially.

However, if you want to _bridge_ stuff, you can just forward 'things 
from A to B, and things from B to A' on the M node, and it should work. 
You can even rate limit them to some degree and do some other things I 
rather not commit in writing though :)

Cheers,

-Markus


From nobody Mon Jun 29 03:34:00 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0861A8A83 for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 03:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_NEUTRAL=0.779] autolearn=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 Q8Grr-98NTGH for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 03:33:58 -0700 (PDT)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.229]) by ietfa.amsl.com (Postfix) with ESMTP id 744C51A8A82 for <homenet@ietf.org>; Mon, 29 Jun 2015 03:33:58 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 552B87C904EBBBD2; Mon, 29 Jun 2015 13:33:57 +0300
Message-ID: <55911F2C.9060700@iki.fi>
Date: Mon, 29 Jun 2015 13:34:20 +0300
From: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Steven Barth <cyrus@openwrt.org>,  Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87fv5d8bb3.wl-jch@pps.univ-paris-diderot.fr> <D0751E47-F461-4097-8995-56D6E4E4A4A6@openwrt.org> <87381d85jn.wl-jch@pps.univ-paris-diderot.fr> <AE09A9C8-4CEE-4EC5-B31D-ACE45599A6B2@openwrt.org>
In-Reply-To: <AE09A9C8-4CEE-4EC5-B31D-ACE45599A6B2@openwrt.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/uAuFOYp3oHEjusI58CdVaAmTDZM>
Cc: homenet@ietf.org
Subject: Re: [homenet] How to compute DNCP/HNCP node data?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Mon, 29 Jun 2015 10:33:59 -0000

On 27.6.2015 20.23, Steven Barth wrote:
>>> Profile recommendations section in dncp recommends sha-256.
>>
>> Er... -06 recommends the leading 8 octets of MD-5.  Section 3.
>
> DNCP recommends sha256 for profiles. HNCP uses what you mentioned.
>
>
>> 1. simply copy the has received from the originator, no questions
>> asked;
>> 2. hash the raw data received from the originator;
>> 3. hash data that I've formatted from my internal data structures.
>
> Since dncp mandates the canonical order this essentially means 2 and 3 are identical.  I personally don't believe in supporting buggy clients as in clients violating MUST statements since at some point it just breaks.

Actually, I do not think it does anymore mandate _internal 
implementation_ in dncp-06 (it used to earlier). However, on the wire, 
there is canonical ordering of TLVs etc.

Anyway, [2] is correct, [3] is obviously impossible to interoperate 
with, and [1] a bad idea.

Cheers,

-Markus


From nobody Mon Jun 29 08:15:22 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E378F1A19EC for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 08:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=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 BJTo7Vt4PCAZ for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 08:15:20 -0700 (PDT)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.229]) by ietfa.amsl.com (Postfix) with ESMTP id B3BAD1A0AF1 for <homenet@ietf.org>; Mon, 29 Jun 2015 08:15:19 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 552B87C904EC459B; Mon, 29 Jun 2015 18:15:18 +0300
Message-ID: <5591611B.7010001@iki.fi>
Date: Mon, 29 Jun 2015 18:15:39 +0300
From: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87d20h8aln.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87d20h8aln.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/H_xEJnv6hF5nM9RLwxXvvB79NaY>
Cc: homenet@ietf.org
Subject: Re: [homenet] A few more DNCP -06 nits and questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Mon, 29 Jun 2015 15:15:22 -0000

On 27.6.2015 17.55, Juliusz Chroboczek wrote:
> Markus,
>
> Section 4.4 of -06 seems to say that Node Endpoint TLVs MUST be silently
> discarded.

Not really, it is not unknown TLV as supporting it is required. However, 
wording deltas accepted if it makes it clearer.

> Section 5, "containing data about the most recently sent RNS", should
> that be per interface ("endpoint")?  Since there's a distinct trickle
> instance per interface, this would make sense to me.

It describes a minimal implementation (and that global counter covers 
the minimum needed RNS sending rate limiting). A possibly more 'correct' 
one would be e.g. tied to Trickle instances, which may be either per 
endpoint, or per (peer, local endpoint) in unicast case.

> Since there's state shared between the Endpoint TLV and the other TLVs
> in a datagram, shouldn't you be requiring that the Endpoint TLV be sent
> first?

We used to have a rather strict ordering of message contents (e.g. same 
as inside node data). It was not found desirable by reviewers. As a 
result of that, currently we do not force _any_ ordering.

I think you have a valid point here though; as the (datagram-case) 
packet processing can be made single pass given ordering constraint, it 
does make sense.

What do you think would be best here? Just specify that it MUST be 
before a Network State TLV within datagram? Or something more broad, 
like first TLV? (possibly too broad for future?)
Cheers,

-Markus


From nobody Mon Jun 29 09:06:33 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48F761ACE85 for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 09:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Wwn65UE96ooO for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 09:06:30 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 C7F9A1ACE87 for <homenet@ietf.org>; Mon, 29 Jun 2015 09:06:30 -0700 (PDT)
Received: by oigx81 with SMTP id x81so121259571oig.1 for <homenet@ietf.org>; Mon, 29 Jun 2015 09:06:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/nsq/sVwU3z+BaNAeiSqEmK2HmhjW8Cf6BkaPLMBJm4=; b=jaLGZZWCfM9PGkf/XGas/MRcfn0kt2eUwl7YqCC4VXXxNeIYKNyrQ2YMhIjuydgLi7 eYWxX/6UCqgndlWhyvYJ7hPSB8AVjJ3Xd146GoVdaxd1n92pAoMhaiegWtxEA/iwdSVF pNDNYIwlPKS3EQJaMcQVXwgdOG+4mIJ6gaWSwaYrhgggSarZCBldY2cIdmzKfd+avKeh qjhnC67dikDSmh4ezvS20s+Xgaj3YIOgdlraryuOZ1GeKhwhYwPYeLi1fhbRZDAXW+/N lUTit6+pIIomPJGi+jmRP7xwkVFC+wCQsZYR6L5z7kmAfJ5DkNb+m7jd5GsMIZ34nC6T K11A==
MIME-Version: 1.0
X-Received: by 10.202.92.68 with SMTP id q65mr14012914oib.11.1435593990337; Mon, 29 Jun 2015 09:06:30 -0700 (PDT)
Received: by 10.202.107.9 with HTTP; Mon, 29 Jun 2015 09:06:30 -0700 (PDT)
In-Reply-To: <55911299.7060205@iki.fi>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <55911299.7060205@iki.fi>
Date: Mon, 29 Jun 2015 09:06:30 -0700
Message-ID: <CAA93jw6ggsii=oOtRz9xeiHQmXd7R4KeNYQj7PVzwq2_qLMavQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/b77EAH1LBCD_FISVdTJAvwyOqRU>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Mon, 29 Jun 2015 16:06:32 -0000

On Mon, Jun 29, 2015 at 2:40 AM, Markus Stenberg <markus.stenberg@iki.fi> w=
rote:
> On 26.6.2015 18.41, Juliusz Chroboczek wrote:

> Even implementation isn't limited to it.
>
>> And sorry if I sound like a broken record, but I would like the ability
>> to set up a router-router link with less than a full /64 allocated to
>> it, at least in the ad-hoc case.
>
>
> I am not sure about the draft text about what it should say, as non-/64
> seems to be a political hot potato (there are drafts on this too), but at
> least the implementation isn't limited to this (given configuration) and =
the
> draft allows for it as well (given configuration). The default of /64 see=
ms
> still sane to me though, given no configuration.

Regardless of whatever politics of artificial scarcity aligned to
wasting 64 bits,
128s are inevitable.

> Cheers,
>
> -Markus
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast


From nobody Mon Jun 29 13:46:11 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B76901B3419 for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 13:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 r42f9vy0EI4L for <homenet@ietfa.amsl.com>; Mon, 29 Jun 2015 13:46:08 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (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 6E1A11B3412 for <homenet@ietf.org>; Mon, 29 Jun 2015 13:46:08 -0700 (PDT)
Received: by pdbci14 with SMTP id ci14so122552097pdb.2 for <homenet@ietf.org>; Mon, 29 Jun 2015 13:46:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=QTHgav8srCHk/V8e9BYmTEkKUpemhZEn9ceswv9cOEY=; b=K4DSNugef0gAONckqKod3jo2TkoJ0PL4XJyjNNaZsxVCuR/HC5M9HPnPc6w5XVqKEu 55Dg/x9yEe+7vXvUVUOLqfV622hyiz/OuLB3qOQAI9qerGZFfNS1tqAooBp61p6qBNXE TymACg6eJFICrA/LBmYWxXMsdVsPOaD9ciBrs2+oskB3Q8tosYoPv2laOQtSXcopBq/v EJfCbMyH4gHNilR2ZA3DCTYn/l+w67o3/7eQmellXxgbJKDZlbt6EUhFhOHBM9vPDO8+ Kc1bg6cQEE1cFuNX8z54U5OYLLgxKHIraTE2xvvEMUPBYDBrTG0+FHOUFf/o226kHAGR MHBA==
X-Received: by 10.66.132.81 with SMTP id os17mr35695196pab.153.1435610768084;  Mon, 29 Jun 2015 13:46:08 -0700 (PDT)
Received: from ?IPv6:2406:e007:6ec9:1:28cc:dc4c:9703:6781? ([2406:e007:6ec9:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id ez4sm9002817pbb.13.2015.06.29.13.46.05 for <homenet@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jun 2015 13:46:07 -0700 (PDT)
Message-ID: <5591AE8C.1070006@gmail.com>
Date: Tue, 30 Jun 2015 08:46:04 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <55911299.7060205@iki.fi> <CAA93jw6ggsii=oOtRz9xeiHQmXd7R4KeNYQj7PVzwq2_qLMavQ@mail.gmail.com>
In-Reply-To: <CAA93jw6ggsii=oOtRz9xeiHQmXd7R4KeNYQj7PVzwq2_qLMavQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JNrGr_ZzUnMHMrWIXA7lW2hLP4Y>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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: Mon, 29 Jun 2015 20:46:09 -0000

On 30/06/2015 04:06, Dave Taht wrote:
> On Mon, Jun 29, 2015 at 2:40 AM, Markus Stenberg <markus.stenberg@iki.fi> wrote:
>> On 26.6.2015 18.41, Juliusz Chroboczek wrote:
> 
>> Even implementation isn't limited to it.
>>
>>> And sorry if I sound like a broken record, but I would like the ability
>>> to set up a router-router link with less than a full /64 allocated to
>>> it, at least in the ad-hoc case.
>>
>>
>> I am not sure about the draft text about what it should say, as non-/64
>> seems to be a political hot potato (there are drafts on this too), but at
>> least the implementation isn't limited to this (given configuration) and the
>> draft allows for it as well (given configuration). The default of /64 seems
>> still sane to me though, given no configuration.
> 
> Regardless of whatever politics of artificial scarcity aligned to
> wasting 64 bits,
> 128s are inevitable.

Yes. My point is only that the *protocol* should allow any length, in accordance
with the IPv6 architecture. The default settings should correspond to reality.

    Brian


From nobody Tue Jun 30 05:01:59 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5359F1A8A48 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 05:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 OnUs0gEc49p8 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 05:01:56 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAC781A8A47 for <homenet@ietf.org>; Tue, 30 Jun 2015 05:01:55 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5UC1roJ025338; Tue, 30 Jun 2015 14:01:53 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C08C761FA3; Tue, 30 Jun 2015 14:01:53 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 5AU1cL01Kv1i; Tue, 30 Jun 2015 14:01:52 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 6536E61FA2; Tue, 30 Jun 2015 14:01:50 +0200 (CEST)
Date: Tue, 30 Jun 2015 14:01:51 +0200
Message-ID: <87fv59wgk0.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 30 Jun 2015 14:01:54 +0200 (CEST)
X-Miltered: at korolev with ID 55928531.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 55928531.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 55928531.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JgBZAzeEF51gadyfOq-e6vkh6zg>
Cc: homenet@ietf.org
Subject: [homenet] Inconsistencies between hnetd and the DNCP/HNCP drafts
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 12:01:57 -0000

I've had two surprises trying to interoperate with hnetd.

1. nncp-06 Section 10 says that the Version is 0.  hnetd sends and expects 
a version field of 1.

2. The same section says the following about versioning:

    Each node [...] MUST ignore (except for DNCP synchronization purposes)
    any TLVs with a type greater than 32 published by nodes not also
    publishing an HNCP-Version TLV or publishing such a TLV with
    a different Version number.

However, this is not what hnetd does -- if there is no Version TLV or the 
Version is 0, it drops the node, which causes persistent desynchronisation 
of DNCP state, which causes repeated Trickle timer resets, which sucks.

(By the way, if you've read up to here, you're invited to help me choose 
the name of the second implementation of HNCP.  homenetd?  homed?  hncpd? 
uhncpd?  markus-s-folly-d?)

-- Juliusz


From nobody Tue Jun 30 05:12:08 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7325A1A8A75 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 05:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 34COu-rBd8OI for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 05:12:06 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D65F1A8A66 for <homenet@ietf.org>; Tue, 30 Jun 2015 05:12:06 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5UCC5Qn001176; Tue, 30 Jun 2015 14:12:05 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 2364A61FA2; Tue, 30 Jun 2015 14:12:05 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id KWpMuWYJtIfU; Tue, 30 Jun 2015 14:12:04 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1BE3A61F9D; Tue, 30 Jun 2015 14:12:04 +0200 (CEST)
Date: Tue, 30 Jun 2015 14:12:04 +0200
Message-ID: <87egktwg2z.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <55911E8A.7090408@iki.fi>
References: <87a8vjn15i.wl-jch@pps.univ-paris-diderot.fr> <55911E8A.7090408@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 30 Jun 2015 14:12:05 +0200 (CEST)
X-Miltered: at korolev with ID 55928795.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 55928795.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 55928795.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/D5VuvNCA__6nx-YkkpoHs3sCRyA>
Cc: Steven Barth <cyrus@openwrt.org>, homenet@ietf.org
Subject: Re: [homenet] DNCP: issue with network partitions and monitoring	nodes
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 12:12:07 -0000

>>    A --- M --- B

[...]

>> M doesn't publish a NODE-STATE TLV, but other than that it fully 
>> participates in the protocol.

> However, if you want to _bridge_ stuff, you can just forward 'things from 
> A to B, and things from B to A' on the M node, and it should work.

I'm probably missing something, then.

For a given node N, let N's Silly Walk Set, written SWS(N), be the set of 
nodes that N includes in the computation of its network hash.

If M is just forwarding beween A and B, and is not publishing a node 
state, then SWS(A) = {A} and SWS(B) = {B}.  Therefore, the network states 
published by A and B will be different, and everytime N forwards A's 
network state to B, B will reset its trickle timer, and similarly in the 
other direction.

What am I missing?

-- Juliusz


From nobody Tue Jun 30 05:42:01 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A141A8BBE for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 05:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.261
X-Spam-Level: 
X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 tyVwK3l2WTpA for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 05:41:58 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDD6C1A8AE6 for <homenet@ietf.org>; Tue, 30 Jun 2015 05:41:57 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id DCE10A1; Tue, 30 Jun 2015 14:41:55 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435668115; bh=3ExDQWlH4Vkibx5GBkEnP7mtwCZRMqL7qOq5ZjTcTHA=; h=Date:From:To:Subject:In-Reply-To:References:From; b=Iik85rQXEuLGJhrQJYfM8sxyhl1x3PC1U+p9iPT0KDDDug+P0MLVDsdlX0qzymXhd Rb96MCH9pmEeoiWoI01YtwiiwLg1MpRsnCtewmtja+8nqlhVrsVK1Br+K4YF28a1Ty vc1O8ZmNDfmGS7LopJQjiXUZW7cyoOGqTflQyc8s=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D5D3B9F for <homenet@ietf.org>; Tue, 30 Jun 2015 14:41:55 +0200 (CEST)
Date: Tue, 30 Jun 2015 14:41:55 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: homenet@ietf.org
In-Reply-To: <55892633.6080205@bellis.me.uk>
Message-ID: <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se>
References: <55892633.6080205@bellis.me.uk>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JsxPd2VGVtHj6f4OthncsPdn5YA>
Subject: Re: [homenet] draft-ietf-homenet-hncp-06 now in WGLC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 12:42:00 -0000

On Tue, 23 Jun 2015, Ray Bellis wrote:

> This email marks the commencement of a three-week Working Group Last
> Call for draft-ietf-homenet-hncp.
>
> Please get any final comments in to the authors (cc: the WG) as soon as
> possible.

If I understand correctly, work is now ongoing to create a separate 
implementation of HNCP? This would be a good step to address my concern I 
have voiced privately to the authors that not enough people have gone 
through the document. I also find them hard to read (some parts have been 
changed after I gave this feedback) and it uses terminology that might 
benefit from further explanation and/or making examples what they mean. 
For instance, the section about "common link" (section 4). Upon reading 
this, I think I understand that this applies to for instance a shared 
ethernet segment where both can see each others HNCP packets. Having an 
example here about why things are done, what problems are solved etc, 
would probably make it easier to understand rationale for the choices.

6.2.4 "create an on-link route"? What's an on-link route? Also, why is it 
a "MAY" that it doesn't create an address for itself to this prefix? An 
explanation and rationale here would be good.

6.2.6 The list of things to do there isn't clear to me. "wait for them to 
be applied"? Applied where? How? Using the HCNP Prefix Assignment 
Algorithm? In the RIB? It implies HNCP Prefix Assignment Algo afterwards, 
but this isn't clear to me.

Section 11 about the MUST for RFC7084 compliance. What parts of RFC7084 
must be implemented? MUSTs? SHOULDs?

I personally think this WGLC is premature. I will not oppose it going 
forward, but I have concerns that the document(s) isn't ready for shipping 
off as RFCs yet due to not enough people having read them.

So I think I am basically saying that the documents are probably correct, 
but there is still very valuable information still only in the heads of 
the implementors that has not been written down in the document, that 
would be valuable to have in there and that would also help future 
implementors who might be reading the document trying to understand what's 
going on, why things are done the way they are, etc.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Jun 30 06:38:18 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55DD01AD0A9 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 06:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=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 yiI-Z728MBlT for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 06:38:16 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 C22871AD05D for <homenet@ietf.org>; Tue, 30 Jun 2015 06:38:15 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1Z9vjo-00085w-Vi with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for ; Tue, 30 Jun 2015 15:38:13 +0200
Message-ID: <55929BC1.5070004@openwrt.org>
Date: Tue, 30 Jun 2015 15:38:09 +0200
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,  Markus Stenberg <markus.stenberg@iki.fi>
References: <87fv59wgk0.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87fv59wgk0.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/yAPfQea-ntY38N9oPlgwqG5x1fI>
Cc: homenet@ietf.org
Subject: Re: [homenet] Inconsistencies between hnetd and the DNCP/HNCP drafts
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 13:38:17 -0000

> I've had two surprises trying to interoperate with hnetd.
> 
> 1. nncp-06 Section 10 says that the Version is 0.  hnetd sends and expects a version field of 1.
> 
> 2. The same section says the following about versioning:
> 
>    Each node [...] MUST ignore (except for DNCP synchronization purposes)
>    any TLVs with a type greater than 32 published by nodes not also
>    publishing an HNCP-Version TLV or publishing such a TLV with
>    a different Version number.
> 
> However, this is not what hnetd does -- if there is no Version TLV or the Version is 0, it drops the node, which causes persistent desynchronisation of DNCP state, which causes repeated Trickle timer resets, which sucks.

Good catch, I think we missed updating the software for these parts.
The behavior you've seen sounds like what historic version of the draft said.

I'll put it on our TODO.


Cheers,

Steven


From nobody Tue Jun 30 07:09:01 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D881A8A8E for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 07:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 3RvumTYs30Kx for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 07:09:00 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 574FE1A8A3E for <homenet@ietf.org>; Tue, 30 Jun 2015 07:08:55 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5UE8rma027769; Tue, 30 Jun 2015 16:08:53 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id A708E61FA2; Tue, 30 Jun 2015 16:08:53 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id baVe55o5Y7L8; Tue, 30 Jun 2015 16:08:47 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 06FC461F9D; Tue, 30 Jun 2015 16:08:46 +0200 (CEST)
Date: Tue, 30 Jun 2015 16:08:47 +0200
Message-ID: <877fqlwaog.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se>
References: <55892633.6080205@bellis.me.uk> <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 30 Jun 2015 16:08:53 +0200 (CEST)
X-Miltered: at korolev with ID 5592A2F5.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5592A2F5.004 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5592A2F5.004 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xCSlkzM-btQMyYDSepW0VY59GsU>
Cc: homenet@ietf.org
Subject: Re: [homenet] draft-ietf-homenet-hncp-06 now in WGLC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 14:09:00 -0000

> If I understand correctly, work is now ongoing to create a separate
> implementation of HNCP?

It's just a private hack, but might end up being useful.  The initial plan
was to spend a week-end explaining DNCP to myself, but the week-end has
now become four days.

I'm doing full DNCP right now (with keepalives, without unicast endpoints,
and omitting one micro-optimisation that I happen to disagree with), and
just enough HNCP to get hnetd to speak to me.  1500 LOC, not counting MD5.

> This would be a good step to address my concern I have voiced privately
> to the authors that not enough people have gone through the document.

Yes, it would have been a good thing if some large private-sector actor
with an interest in home networking had sponsored an independent
reimplementation before the DNCP WGLC.

> I personally think this WGLC is premature.

I'm actually more concerned by DNCP.  HNCP is extensible -- if we get it
wrong, we can deprecate some TLVs and add new ones without breaking
compatibility.

Not so DNCP -- DNCP requires precise state synchronisation, so any trivial
change is likely to require a whole new protocol.  Plus there's no version
number in DNCP, so the only way to evolve it is to pick a new port
(picking a new multicast group will not be enough in case clients want to
participate in both variants).

I've got a large list of DNCP issues, which I'll probably be able to write
up today or tomorrow.

-- Juliusz


From nobody Tue Jun 30 08:13:07 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C123E1B2DC6 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=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 mOLipox7dQSQ for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:13:04 -0700 (PDT)
Received: from kirsi2.inet.fi (mta-out1.inet.fi [62.71.2.229]) by ietfa.amsl.com (Postfix) with ESMTP id B1B361B2DC5 for <homenet@ietf.org>; Tue, 30 Jun 2015 08:13:02 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by kirsi2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 5511FF6A00C5D954; Tue, 30 Jun 2015 18:13:01 +0300
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <87a8vjn15i.wl-jch@pps.univ-paris-diderot.fr> <55911E8A.7090408@iki.fi> <87egktwg2z.wl-jch@pps.univ-paris-diderot.fr>
From: Markus Stenberg <markus.stenberg@iki.fi>
Message-ID: <5592B212.1050309@iki.fi>
Date: Tue, 30 Jun 2015 18:13:22 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <87egktwg2z.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/iq9luubGZ8gP_Lt2mZwROZNi0rY>
Cc: Steven Barth <cyrus@openwrt.org>, homenet@ietf.org
Subject: Re: [homenet] DNCP: issue with network partitions and monitoring nodes
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 15:13:06 -0000

On 30.6.2015 15.12, Juliusz Chroboczek wrote:
>>>    A --- M --- B
>
> [...]
>
>>> M doesn't publish a NODE-STATE TLV, but other than that it fully
>>> participates in the protocol.
>
>> However, if you want to _bridge_ stuff, you can just forward 'things
>> from A to B, and things from B to A' on the M node, and it should work.
>
> I'm probably missing something, then.
>
> For a given node N, let N's Silly Walk Set, written SWS(N), be the set
> of nodes that N includes in the computation of its network hash.
>
> If M is just forwarding beween A and B, and is not publishing a node
> state, then SWS(A) = {A} and SWS(B) = {B}.  Therefore, the network
> states published by A and B will be different, and everytime N forwards
> A's network state to B, B will reset its trickle timer, and similarly in
> the other direction.
>
> What am I missing?

If node M forwards the packets verbatim between nodes A and node B, they 
think they're adjacent. ('bridging')

However, if node M wants to actually participate in the protocol instead 
of being light-weight packet forwarder (which requires keeping track of 
e.g. one node on each of two links, and just communicate with that one, 
and relay multicasts or convert them to unicasts to that particular 
tracked node on other side of the fence), it gets more complicated.

That forwarding scheme does not preclude M from also keeping it's own 
read-only dataset.

Cheers,

-Markus


From nobody Tue Jun 30 08:16:00 2015
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC0D1A907A for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_NEUTRAL=0.779] autolearn=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 MWd-Nzgo-8jw for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:15:58 -0700 (PDT)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.230]) by ietfa.amsl.com (Postfix) with ESMTP id 87CB11A9234 for <homenet@ietf.org>; Tue, 30 Jun 2015 08:15:57 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by jenni1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 5511FF5807744EAA for homenet@ietf.org; Tue, 30 Jun 2015 18:15:56 +0300
To: homenet@ietf.org
References: <55892633.6080205@bellis.me.uk> <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se>
From: Markus Stenberg <markus.stenberg@iki.fi>
Message-ID: <5592B2C1.8080508@iki.fi>
Date: Tue, 30 Jun 2015 18:16:17 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/C0Z4leld7oa1nDy2RSc_0E8mtsA>
Subject: Re: [homenet] draft-ietf-homenet-hncp-06 now in WGLC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 15:15:59 -0000

On 30.6.2015 15.41, Mikael Abrahamsson wrote:
> On Tue, 23 Jun 2015, Ray Bellis wrote:
> If I understand correctly, work is now ongoing to create a separate
> implementation of HNCP? This would be a good step to address my concern
> I have voiced privately to the authors that not enough people have gone
> through the document. I also find them hard to read (some parts have
> been changed after I gave this feedback) and it uses terminology that
> might benefit from further explanation and/or making examples what they
> mean. For instance, the section about "common link" (section 4). Upon
> reading this, I think I understand that this applies to for instance a
> shared ethernet segment where both can see each others HNCP packets.
> Having an example here about why things are done, what problems are
> solved etc, would probably make it easier to understand rationale for
> the choices.
>
> 6.2.4 "create an on-link route"? What's an on-link route? Also, why is
> it a "MAY" that it doesn't create an address for itself to this prefix?
> An explanation and rationale here would be good.
>
> 6.2.6 The list of things to do there isn't clear to me. "wait for them
> to be applied"? Applied where? How? Using the HCNP Prefix Assignment
> Algorithm? In the RIB? It implies HNCP Prefix Assignment Algo
> afterwards, but this isn't clear to me.
>
> Section 11 about the MUST for RFC7084 compliance. What parts of RFC7084
> must be implemented? MUSTs? SHOULDs?

First of all, thanks for the feedback on the content (again).

> I personally think this WGLC is premature. I will not oppose it going
> forward, but I have concerns that the document(s) isn't ready for
> shipping off as RFCs yet due to not enough people having read them.
>
> So I think I am basically saying that the documents are probably
> correct, but there is still very valuable information still only in the
> heads of the implementors that has not been written down in the
> document, that would be valuable to have in there and that would also
> help future implementors who might be reading the document trying to
> understand what's going on, why things are done the way they are, etc.

IETF tradition is that without WGLC or other implemenation efforts, 
there is not much action either. HNCP document is already soon 1.5 years 
old and the number of reviews is not _that_ great outside the main 
implementation crew.

Hopefully Juliusz will give us feedback on his results ASAP, and 
obviously any other reviews are welcome.

Cheers,

-Markus


From nobody Tue Jun 30 08:22:22 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55CEB1ACCE7 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 c9h4TpmFQ01y for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:22:16 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 6C4F81A9046 for <homenet@ietf.org>; Tue, 30 Jun 2015 08:22:16 -0700 (PDT)
Received: by oiax193 with SMTP id x193so9904980oia.2 for <homenet@ietf.org>; Tue, 30 Jun 2015 08:22:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=aoUC4ltSP9k4iaOxHWybZto5UGPB3Dlw0bnnHQbTPos=; b=KuvAlP2+NcleqIDVIt65gz7y2Gnmlk+rj136MwmMk9YJeOtuPGZcor825eVUelFVA4 Xp9ToGtILT8pjpkhg1uBRum1LTtNHYjxOx4CfnzK/dIGR/6TW+OioxllwItAIiCoooGx UYqz3chxcyymNpaZDAdI9sbEQUBFRdwcaiI/J8zV3UvfyDgHf9xPK4b+BPEnB8/UQ0hL Lg9MHMAnyXHaqV9BtWwsMxKVjx0jZr8rbkstpn0oJ+1u1pVsFaRXfb4CIjpqTq3t4ozD upKVtKvU4YFl21fIB+hffk2ygLX/6rKFngS36gV7fc6Iqepu2cE44yxqdgst7Txu9/H2 g+Cg==
MIME-Version: 1.0
X-Received: by 10.60.78.230 with SMTP id e6mr20996602oex.24.1435677735832; Tue, 30 Jun 2015 08:22:15 -0700 (PDT)
Received: by 10.202.107.9 with HTTP; Tue, 30 Jun 2015 08:22:15 -0700 (PDT)
In-Reply-To: <5592B2C1.8080508@iki.fi>
References: <55892633.6080205@bellis.me.uk> <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se> <5592B2C1.8080508@iki.fi>
Date: Tue, 30 Jun 2015 08:22:15 -0700
Message-ID: <CAA93jw7Y7fH7omPdUBAN9d6tr7xbYG70CMwSJsd0hrvp9PM8ew@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/D1UGGDZyjtGha6MkkWXYgS2jJHo>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] draft-ietf-homenet-hncp-06 now in WGLC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 15:22:18 -0000

My request was more dogfooding. a *lot* more dogfooding.

On Tue, Jun 30, 2015 at 8:16 AM, Markus Stenberg <markus.stenberg@iki.fi> w=
rote:
> On 30.6.2015 15.41, Mikael Abrahamsson wrote:
>>
>> On Tue, 23 Jun 2015, Ray Bellis wrote:
>> If I understand correctly, work is now ongoing to create a separate
>> implementation of HNCP? This would be a good step to address my concern
>> I have voiced privately to the authors that not enough people have gone
>> through the document. I also find them hard to read (some parts have
>> been changed after I gave this feedback) and it uses terminology that
>> might benefit from further explanation and/or making examples what they
>> mean. For instance, the section about "common link" (section 4). Upon
>> reading this, I think I understand that this applies to for instance a
>> shared ethernet segment where both can see each others HNCP packets.
>> Having an example here about why things are done, what problems are
>> solved etc, would probably make it easier to understand rationale for
>> the choices.
>>
>> 6.2.4 "create an on-link route"? What's an on-link route? Also, why is
>> it a "MAY" that it doesn't create an address for itself to this prefix?
>> An explanation and rationale here would be good.
>>
>> 6.2.6 The list of things to do there isn't clear to me. "wait for them
>> to be applied"? Applied where? How? Using the HCNP Prefix Assignment
>> Algorithm? In the RIB? It implies HNCP Prefix Assignment Algo
>> afterwards, but this isn't clear to me.
>>
>> Section 11 about the MUST for RFC7084 compliance. What parts of RFC7084
>> must be implemented? MUSTs? SHOULDs?
>
>
> First of all, thanks for the feedback on the content (again).
>
>> I personally think this WGLC is premature. I will not oppose it going
>> forward, but I have concerns that the document(s) isn't ready for
>> shipping off as RFCs yet due to not enough people having read them.
>>
>> So I think I am basically saying that the documents are probably
>> correct, but there is still very valuable information still only in the
>> heads of the implementors that has not been written down in the
>> document, that would be valuable to have in there and that would also
>> help future implementors who might be reading the document trying to
>> understand what's going on, why things are done the way they are, etc.
>
>
> IETF tradition is that without WGLC or other implemenation efforts, there=
 is
> not much action either. HNCP document is already soon 1.5 years old and t=
he
> number of reviews is not _that_ great outside the main implementation cre=
w.
>
> Hopefully Juliusz will give us feedback on his results ASAP, and obviousl=
y
> any other reviews are welcome.
>
> Cheers,
>
> -Markus
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast


From nobody Tue Jun 30 08:55:12 2015
Return-Path: <cyrus@openwrt.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A12351AC42B for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=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 1Pio09x2LNr4 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 08:55:09 -0700 (PDT)
Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 80A231ACD35 for <homenet@ietf.org>; Tue, 30 Jun 2015 08:55:07 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1Z9xsH-0004C8-5L with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for ; Tue, 30 Jun 2015 17:55:05 +0200
Message-ID: <5592BBD7.4030306@openwrt.org>
Date: Tue, 30 Jun 2015 17:55:03 +0200
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, homenet@ietf.org
References: <55892633.6080205@bellis.me.uk> <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CP713812G3FAanMeqmgjgpZz39M>
Subject: Re: [homenet] draft-ietf-homenet-hncp-06 now in WGLC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 15:55:10 -0000

Hello Mikael,

thanks for your continuous feedback.


Am 30.06.2015 um 14:41 schrieb Mikael Abrahamsson:
> 6.2.4 "create an on-link route"? What's an on-link route? Also, why is it a "MAY" that it doesn't create an address for itself to this prefix? An explanation and rationale here would be good.
> 
> 6.2.6 The list of things to do there isn't clear to me. "wait for them to be applied"? Applied where? How? Using the HCNP Prefix Assignment Algorithm? In the RIB? It implies HNCP Prefix Assignment Algo afterwards, but this isn't clear to me.
> 
> Section 11 about the MUST for RFC7084 compliance. What parts of RFC7084 must be implemented? MUSTs? SHOULDs?

I just pushed an update to our drafts repository which should hopefully address your comments.
Please see https://github.com/fingon/ietf-drafts/compare/c82f52d...c9f5b57 and let us know if you have any further issues.


Thanks,

Steven


From nobody Tue Jun 30 09:19:57 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2111ACDBC for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 09:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 Hk33xAYQO6P9 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 09:19:54 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 560F21ACDBA for <homenet@ietf.org>; Tue, 30 Jun 2015 09:19:54 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5UGJoOY015355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Jun 2015 18:19:50 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t5UGJnp1017354; Tue, 30 Jun 2015 18:19:49 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5512E61F9A; Tue, 30 Jun 2015 18:19:49 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id u8N_qWI5qMIU; Tue, 30 Jun 2015 18:19:48 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 5027C61FA2; Tue, 30 Jun 2015 18:19:48 +0200 (CEST)
Date: Tue, 30 Jun 2015 18:19:47 +0200
Message-ID: <87wpyluq1o.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <5592B212.1050309@iki.fi>
References: <87a8vjn15i.wl-jch@pps.univ-paris-diderot.fr> <55911E8A.7090408@iki.fi> <87egktwg2z.wl-jch@pps.univ-paris-diderot.fr> <5592B212.1050309@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 30 Jun 2015 18:19:52 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 30 Jun 2015 18:19:50 +0200 (CEST)
X-Miltered: at korolev with ID 5592C1A6.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5592C1A5.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5592C1A6.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5592C1A5.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5592C1A6.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5592C1A5.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bolHxOdGNMJAiF42IMVRW_Po9bc>
Cc: Steven Barth <cyrus@openwrt.org>, homenet@ietf.org
Subject: Re: [homenet] DNCP: issue with network partitions and monitoring nodes
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 16:19:56 -0000

> If node M forwards the packets verbatim between nodes A and node B, they
> think they're adjacent. ('bridging')

Ah!

-- Juliusz


From nobody Tue Jun 30 10:11:05 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917A91AD0A8 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 10:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 JDz3usAnyNld for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 10:11:03 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF4DF1ACD92 for <homenet@ietf.org>; Tue, 30 Jun 2015 10:11:02 -0700 (PDT)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t5UHB1vx008206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Jun 2015 19:11:01 +0200
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t5UHB18A006612; Tue, 30 Jun 2015 19:11:01 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id EDD2661F9D; Tue, 30 Jun 2015 19:11:00 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id A39pc0mO28OL; Tue, 30 Jun 2015 19:10:59 +0200 (CEST)
Received: from pirx.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 9761161FA2; Tue, 30 Jun 2015 19:10:59 +0200 (CEST)
Date: Tue, 30 Jun 2015 19:10:59 +0200
Message-ID: <87si99unoc.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>, Steven Barth <cyrus@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 30 Jun 2015 19:11:01 +0200 (CEST)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 30 Jun 2015 19:11:01 +0200 (CEST)
X-Miltered: at korolev with ID 5592CDA5.015 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5592CDA5.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5592CDA5.015 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5592CDA5.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5592CDA5.015 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5592CDA5.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/BO2Z51X0Mh9NELTXUwayMugiaHg>
Cc: homenet@ietf.org
Subject: [homenet] Concerns about DNCP
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 17:11:04 -0000

Concerns about DNCP
===================

DNCP is an elegant and small protocol that distributes HNCP data across
the Homenet.  DNCP works by flooding a hash of the full network state over
link-local multicast, and synchronising the actual state piecewise by
using link-local unicast request/response pairs.  This document outlines
a number of concerns with DNCP as described in draft-ietf-homenet-dncp-06.

I very strongly support the work that is being done on DNCP and HNCP.
I will be glad to see something very similar to the current drafts adopted
by the Homenet WG.


Packet format
-------------

### There is no header

A DNCP packet consists of just a sequence of TLVs.  This means that there
is no way to version the DNCP protocol.  Should a change in the TLV format
be required, a new UDP port will need to be allocated.  (A new multicast
group is not sufficient, since DNCP also uses unicast).

I recommend adding a fixed-size header with a version number.

### NODE-ENDPOINT is stateful

The DNCP/HNCP protocol suite uses the elegant technique of using
recursively embedded TLVs: hop-to-hop data is in the packet toplevel,
end-to-end data is in the NODE-STATE TLV, which may in turn contain TLVs
that themselves contain embedded TLVs.  The TLVs are mostly stateless, in
the sense that they can be sent in any order or even in independent
packets.  NODE-ENDPOINT is an exception.

NODE-ENDPOINT identifies the sender of this packet, and applies to all
TLVs in this packet.  The current specification implies that the
NODE-ENDPOINT may appear anywhere in the packet, which would force the
receiver to make two passes over the packet.

Conceptually, NODE-ENDPOINT is a packet header, and it is best treated
that way.  Ideally, the information it contains would be part of the
fixed-size packet header suggested above (but after the version number,
which should be parsable even when the NODE-ENDPOINT format changes).
Alternatively, specify that NODE-ENDPOINT MUST be the very first TLV in
a packet, or at least appear before all currently-defined TLVs, which
merely formalises what existing implementations already do.

### NODE-ENDPOINT is underspecified

It is not clear whether NODE-ENDPOINT is required in all packets, and if
not which TLVs are allowed in a packet without a NODE-ENDPOINT.  Existing
implementations appear to differ in that respect.

### Node data is underspecified

The NODE-STATE TLV carries the end-to-end hash of the "node data".
However, the exact "node data" is never specified exactly.  For example,
there is padding applied between TLVs (look, Ma, I've saved 4ns parsing my
packet), and it is nowhere specified whether this padding participates in
the hashing (it does).

It turns out that in the absence of fragmentation the "node data" is just
the raw binary data in the NODE-STATE TLV.  This is the reasonable thing
to do, and must be specified in this manner.  It must also be made clear
that this binary data MUST NOT be modified in transit (parsing/reformatting
is not likely to work reliably), and that its hash SHOULD (or is that MAY?)
be validated on reception.

### Normalisation is apparently useless

DNCP specifies that the TLVs within a node state be sorted.  Since both
the raw binary data and the hash are end-to-end, it is not clear why this
partial normalisation is useful.

At the very least, the draft should make it clear that this normalisation
should not be relied upon, and that peers MUST forward the binary data
unchanged.  I recommend simply dropping the normalisation, although this
will require changes to the fragmentation scheme.

### FRAGMENT-COUNT is stateful in the reverse direction

FRAGMENT-COUNT is stateful, but in the reverse direction: it changes the
interpretation of the enclosing NODE-STATE TLV.  Usually, the NODE-STATE
hash carries exactly data being hashed; with a FRAGMENT-COUNT, it carries
part of that data, and FRAGMENT-COUNT is not being hashed.

FRAGMENT-COUNT is not end-to-end data, and it doesn't belong within the
NODE-STATE TLV.  It should either be a field in the NODE-STATE TLV itself
(not in an embedded TLV), or put in a TLV that contains the NODE-STATE
TLV.

### Fragmentation is specified at the TLV level

The section about fragmentation is not quite clear to me.  It appears to
specify fragmentation in terms of TLVs (every fragment must consist of
a valid series of TLVs), and appears to assume that the receiver is doing
something smart in order to avoid reassembly timeouts.

Unfortunately, this encoding makes it very difficult to implement
a simpler scheme, where fragmentation and reassembly are TLV-agnostic and
act entirely at the byte-stream level.  In particular, a fragment TLV does
not specify an initial byte offset, and the total length of the
reassembled packet is not known beforehand, which makes buffer management
in the receiver challenging.

I recommend a TLV-agnostic fragmentation scheme, with fragment offsets
counted in octets and a total reassembled size explicitly encoded.

### The fragment timeout is not specified

It is not clear when the receiver can discard an incomplete defragmentation
buffer.  This might not be an issue if a TLV-based fragmentation scheme is
used.

### Keep-alive intervals are flooded

The KEEP-ALIVE-INTERVAL is within the node state, and hence flooded across
the network.  This information is of no interest to remote nodes, this TLV
should be within at the top level of the packet in order to reduce the
amount of information being flooded.


Protocol dynamics
-----------------

### Need to check sender

Most of the packets in DNCP have exactly the same meaning whether they are
sent to a unicast or a multicast address.  There is one exception: the
keepalive timer is only reset for inconsistent network state when they
are sent over unicast.  This requires that the receiver check the
destination address of packets, which is non-portable and might be
impossible on some systems.

I recommend removing the requirement to distinguish between unicast and
multicast.  If such distinction is needed, make it explicit in the TLV
contents.

### Not clear when multicasts and unsolicited packets can be sent

As it is written, the draft requires that all TLVs other than
NETWORK-STATE be sent over unicast and does not allow unsolicited packets
other than NETWORK-STATE.  However, the draft authors indicate that
unsolicited multicast packets are allowed.

The draft should specify clearly when multicast and unsolicited packets
are allowed.  In particular, it should mention whether it is legal to
reply to a request over multicast (which may make sense, at least on some
link layers), and which packets can be sent unsolicited over multicast.

### Non standard port

The draft specifies that it is required to answer a request from a node
that does not publish a node state.  What should happen when this request
comes from a non-standard port?  Monitoring software may need to run on
the same node as a normal DNCP implementation.

### Non-publishing nodes

A node may want to participate in the full protocol without publishing
a node state in order to reduce the amount of data being flooded.  Doing
this naively might cause persistent state desynchronisation, leading to
repeated resetting of the Trickle timers.

Ideally, the draft would specify exactly which behaviours are allowed for
non-publishing nodes.  At any rate, a warning about the dangers of
non-publishing nodes should be included in the draft.


From nobody Tue Jun 30 16:32:56 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26301AD364 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 16:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 HkYksF8Z8iFN for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 16:32:52 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (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 BD4461AD352 for <homenet@ietf.org>; Tue, 30 Jun 2015 16:32:52 -0700 (PDT)
Received: by pdjd13 with SMTP id d13so14168592pdj.0 for <homenet@ietf.org>; Tue, 30 Jun 2015 16:32:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5jR++N7YfTuvd7eBv4WuRQ0R9eEq7EAfVy0DVZct9hs=; b=irLBaGjU/8bwXZhdOWgoZS0UpVbUeqATeN90pnj9+h1jO4AlttSjCOf70nWLJYJH6u W0JHFv3gTPhjnO9f/yRVshnOZgUHOUadWphF2xaWMPFPVfktfpLV1/YOkk7nCbRdwGbN /1CHdwYuMJUn4m87nXJy2GXH/V5pIxtf9SkmbY46I7JuOt9CjtF6NHoYnDfjYtJS2sq/ y0X3GcZ7iq6NMP/xH5rlYOtwtVj1PgsMsxlrg+bz1O3qzoIbm5+4WQVsx/AReO04M5UJ zrXqbm4kQxdR0C7nxJNdYZYX3uZT5kiq+TiRrtrH2HAmpypikxctN55G7HNjOHnDlEN1 CRPQ==
X-Received: by 10.70.103.145 with SMTP id fw17mr17418864pdb.1.1435707171698; Tue, 30 Jun 2015 16:32:51 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by mx.google.com with ESMTPSA id qs8sm26030pbc.38.2015.06.30.16.32.46 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jun 2015 16:32:50 -0700 (PDT)
Message-ID: <55932721.5060906@gmail.com>
Date: Wed, 01 Jul 2015 11:32:49 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Pierre Pfister <pierre.pfister@darou.fr>
References: <20150617163747.22885.8743.idtracker@ietfa.amsl.com> <5581A2FB.8010108@iki.fi> <87h9pumq94.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw56j9fYVxe-Ut3qTb4vOXyG-SgnW6EpCE0yinmYxoyRiA@mail.gmail.com> <558DB74C.8040106@gmail.com> <87r3oyvxmm.wl-jch@pps.univ-paris-diderot.fr> <8C4A5BF8-B803-49C6-8FE8-1C30103F07DC@darou.fr> <20150628085813.GY67883@Space.Net> <321044EB-A36F-4E5A-BB9C-C1580519CCD3@darou.fr> <55905253.6090900@gmail.com> <B56E4B9D-321A-436A-97A8-F5B3355FC549@darou.fr>
In-Reply-To: <B56E4B9D-321A-436A-97A8-F5B3355FC549@darou.fr>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/EwNh3CApyieones2YPEd4xIPerQ>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Gert Doering <gert@space.net>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-06.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 30 Jun 2015 23:32:55 -0000

See below...

On 29/06/2015 09:09, Pierre Pfister wrote:
>=20
>=20
>> Le 28 juin 2015 =C3=A0 22:00, Brian E Carpenter <brian.e.carpenter@gma=
il.com> a =C3=A9crit :
>>
>> On 29/06/2015 01:09, Pierre Pfister wrote:
>>> Hello,
>>>
>>>> Le 28 juin 2015 =C3=A0 10:58, Gert Doering <gert@space.net> a =C3=A9=
crit :
>>>>
>>>> Hi,
>>>>
>>>> On Sat, Jun 27, 2015 at 11:48:43PM +0200, Pierre Pfister wrote:
>>>>> Relaxing the =C2=AB administrator =C2=BB may be confusing, as Brian=
 said.
>>>>> So I guess the MUST could become a SHOULD, which imply it requires =
implementers to fully understand the drawbacks
>>>>> of using non-64 prefix lengths. For instance, /127 could be automat=
ically used (no need for administrator) if a link
>>>>> is auto-detected as point-to-point.
>>>>
>>>> A MUST is perfectly right here.  You can't have implementation A dec=
ide
>>>> "let's use a /64 here" while implementation B goes for "/127"=E2=80=A6=

>>>
>>> You actually can have implementations with different prefix length.=20
>>> This is handled by the prefix assignment algorithm.
>>
>> Yes, you need that ability in the protocol, but it won't work in pract=
ice
>> to pick an oddball like /80 unless all the host stacks on the link can=

>> handle a shorter IID like 48 (whether it's a LAN or a pt2pt). RFC 7421=
=2E
>=20
> Which is why /64 SHOULD be preferred.
> We also have this:
> "In any case, a router MUST support a mechanism suitable to distribute
>    addresses from the considered prefix to clients on the link.
>    Otherwise it MUST NOT create or adopt it, i.e. a router assigning an=

>    IPv4 prefix MUST support the L-capability and a router assigning an
>    IPv6 prefix not suitable for Stateless Address Autoconfiguration MUS=
T
>    support the H-capability as defined in Section 10 <https://tools.iet=
f.org/html/draft-ietf-homenet-hncp-06#section-10>.
> "
>=20
> So a router will not advertise a /80 on a typical link unless it implem=
ents stageful DHCPv6.
>=20
>>
>>> You may have multiple routers with multiple prefix lengths, but one s=
ingle
>>> prefix is ultimately chosen and used by all routers connected to the =
link.
>>
>> So will it work if one router on a pt2pt expects to use a /127 and the=
 other
>> one can only support /64?
>=20
> The current document does not specify how to configure a pt2pt link.
> This could be specified later really easily, in a backward compatible w=
ay.
> Also, in general, why and how would a router assign a /64 to a pt2pt li=
nk ?

I believe that RFC 7421 was needed because, in ISP land, people were
often assigning a /64 because they thought they had to, since all
the IID mechanisms assumed /64. So there was no reason for it, it was
just human behaviour.

> I mean, considering pt2pt link, we can assume both ends of the link kno=
w the nature of the link=E2=80=A6
> and are therefore able to not do weird things such as assigning a /64 o=
n a pt2pt link.

I hope you are right. "Don't be weird" is a good motto, but "SHOULD confo=
rm
to RFC 7421" might be better in an RFC ;-).
(But then: do you want the SOHO network to automatically reserve a /64
out of which you take all the /127s for pt2pt links?)

   Brian


    Brian

>=20
> - Pierre
>=20
>>
>>    Brian
>>
>>>
>>> - Pierre
>>>
>>>>
>>>> The sentence is also clearly allowing alternatives: if I tell my rou=
ter
>>>> "hey, I want to use /127s on point-to-point links", this is "unless =
configured=20
>>>> otherwise by an administrator", so the MUST is not getting in the wa=
y then.
>>>>
>>>> Gert Doering
>>>>       -- NetMaster
>>>> --=20
>>>> have you enabled IPv6 on something today...?
>>>>
>>>> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
>>>> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-C=
ulemann
>>>> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
>>>> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
>>>>
>>>> _______________________________________________
>>>> homenet mailing list
>>>> homenet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/homenet
>>>
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homenet
>>> .
>>>
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>=20
>=20


From nobody Tue Jun 30 23:56:24 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2FB1AD259 for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 23:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level: 
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 DpDbh_3wO_QV for <homenet@ietfa.amsl.com>; Tue, 30 Jun 2015 23:56:20 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 251621AD1EC for <homenet@ietf.org>; Tue, 30 Jun 2015 23:56:20 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id EF6ABA1; Wed,  1 Jul 2015 08:56:17 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435733777; bh=c7OVXpmvBatxWjWwGjRZgXmUqvTlOGng4L9HmkgI0C0=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=UjufGXdCiBP5ICuJ9ZTCP46jtxs+WeDGHIWsGcOKv3qLj1YSrWUP6f/OUQ2kUGwbN +furhNnacu80VhE+6ZT561BxUP4z+Ea6QbNs+TIb9kMYlTE3B/aLUV+rmiw6eCbFYM L3Ga9r6cBIhan3tyoJ1NagjadHHCfPMMZIlRQWBA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E85AE9F; Wed,  1 Jul 2015 08:56:17 +0200 (CEST)
Date: Wed, 1 Jul 2015 08:56:17 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <5592BBD7.4030306@openwrt.org>
Message-ID: <alpine.DEB.2.02.1507010851360.9487@uplift.swm.pp.se>
References: <55892633.6080205@bellis.me.uk> <alpine.DEB.2.02.1506301404350.9487@uplift.swm.pp.se> <5592BBD7.4030306@openwrt.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ZTHKHz6DVGM6I363cDnV7iyVYKw>
Cc: homenet@ietf.org
Subject: Re: [homenet] draft-ietf-homenet-hncp-06 now in WGLC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <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, 01 Jul 2015 06:56:22 -0000

On Tue, 30 Jun 2015, Steven Barth wrote:

> Hello Mikael,
>
> thanks for your continuous feedback.
>
>
> Am 30.06.2015 um 14:41 schrieb Mikael Abrahamsson:
>> 6.2.4 "create an on-link route"? What's an on-link route? Also, why is it a "MAY" that it doesn't create an address for itself to this prefix? An explanation and rationale here would be good.
>>
>> 6.2.6 The list of things to do there isn't clear to me. "wait for them to be applied"? Applied where? How? Using the HCNP Prefix Assignment Algorithm? In the RIB? It implies HNCP Prefix Assignment Algo afterwards, but this isn't clear to me.
>>
>> Section 11 about the MUST for RFC7084 compliance. What parts of RFC7084 must be implemented? MUSTs? SHOULDs?
>
> I just pushed an update to our drafts repository which should hopefully address your comments.
> Please see https://github.com/fingon/ietf-drafts/compare/c82f52d...c9f5b57 and let us know if you have any further issues.

Thanks, yes, that's better.

Hm, regarding section 11, requirements for HNCP routers. How is that size 
hint calculated? Also, other kinds of behaviours like null-routing the 
delegated PD to avoid ping-pong routing when you receive packets for 
subnets currently not in use in the delegated prefix, where is that 
specified?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

