Re: [homenet] Alia Atlas' Yes on draft-ietf-homenet-dncp-11: (with COMMENT)

Markus Stenberg <markus.stenberg@iki.fi> Fri, 23 October 2015 04:22 UTC

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 05B2B1B2BCB; Thu, 22 Oct 2015 21:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.521
X-Spam-Level:
X-Spam-Status: No, score=-0.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, 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 YRuBR1b4WixI; Thu, 22 Oct 2015 21:22:40 -0700 (PDT)
Received: from julia1.inet.fi (mta-out1.inet.fi [62.71.2.232]) by ietfa.amsl.com (Postfix) with ESMTP id 81B271B2BB7; Thu, 22 Oct 2015 21:22:39 -0700 (PDT)
Received: from poro.lan (80.220.86.47) by julia1.inet.fi (9.0.002.03-2-gbe5d057) (authenticated as stenma-47) id 5613C7B100461BAF; Fri, 23 Oct 2015 07:22:02 +0300
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <20151021161845.17637.14184.idtracker@ietfa.amsl.com>
Date: Fri, 23 Oct 2015 07:22:37 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <04F516FC-2AF4-4087-AA4F-ED79E24CD08E@iki.fi>
References: <20151021161845.17637.14184.idtracker@ietfa.amsl.com>
To: Alia Atlas <akatlas@gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8W2CGAT128bLYskrVMIYmAjGYUI>
Cc: homenet-chairs@ietf.org, draft-ietf-homenet-dncp@ietf.org, homenet@ietf.org, Mark Townsley <mark@townsley.net>, The IESG <iesg@ietf.org>
Subject: Re: [homenet] Alia Atlas' Yes on draft-ietf-homenet-dncp-11: (with COMMENT)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2015 04:22:43 -0000

On 21.10.2015, at 19.18, Alia Atlas <akatlas@gmail.com> wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thank you very much for addressing my previous Discuss points and
> comments.  
> I understand that version -11 will handle the most recent concerns, as
> shown in 
> the github diff.

Well, it will be actually -12 (we change the version # last thing), but we hope so too.  We will post a new version once we come up with good answer to Benoit’s DISCUSS.

> I've also read this draft too many times at this point to be certain that
> I've picked up all the points of
> unclarity. 
> 
> a) As pointed out by Lizhong, it would be very useful to have some text
> discussing
> the issues around a network hash collision.  I suspect that this is
> related to guidance
> for a DNCP profile on how to make a decision about what hash function to
> use and
> how many bits to include

I staged this earlier to address this:

https://github.com/fingon/ietf-drafts/commit/0372f47bbc1866ecb3020bc31fb9cb4014ae8790

> 6) Please define H(...) in terminology, since Sec 4 uses it before it is
> defined in 
> Section 7.

It refers to an explicit field name there, as it is “H(Node Data) field” in the two references there. So for now leaving the meaning of that H() to where it is described (which is section 7). If this notation is distracting, we can rename the field to e.g. Node Data Hash field and describe it’s contents as H(Node Data) instead within it’s own subsection.

I think having the encoding-related definitions in terminology seems excessive because then reading the TLV section would require fairly long jumps between terminology and TLV section.

Cheers,

-Markus