Re: [homenet] Benoit Claise's Discuss on draft-ietf-homenet-dncp-11: (with DISCUSS and COMMENT)

Steven Barth <cyrus@openwrt.org> Wed, 21 October 2015 13:31 UTC

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 5AC7F1A8735; Wed, 21 Oct 2015 06:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_FAIL=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 h_ykF5j5-uP2; Wed, 21 Oct 2015 06:31:03 -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 3B3A51A8724; Wed, 21 Oct 2015 06:31:03 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1ZotTm-0003OJ-L5 with ESMTPSA (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) for ; Wed, 21 Oct 2015 15:30:58 +0200
To: Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
References: <20151020204159.17294.93467.idtracker@ietfa.amsl.com>
From: Steven Barth <cyrus@openwrt.org>
Message-ID: <56279391.5050207@openwrt.org>
Date: Wed, 21 Oct 2015 15:30:57 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Icedove/40.0
MIME-Version: 1.0
In-Reply-To: <20151020204159.17294.93467.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CoxvhjA9XEFHk49fbUPm_GiES6w>
Cc: homenet-chairs@ietf.org, draft-ietf-homenet-dncp@ietf.org, homenet@ietf.org, mark@townsley.net, victor@jvknet.com
Subject: Re: [homenet] Benoit Claise's Discuss on draft-ietf-homenet-dncp-11: (with DISCUSS and 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: Wed, 21 Oct 2015 13:31:05 -0000

Hello Benoit,

thanks for your feedback.

I've staged the following additions for -12 in our Git:
https://github.com/fingon/ietf-drafts/commit/859a37237

Would that address your DISCUSS? If not, please let us know what you
would like us to add or change in addition.


Thanks,

Steven


On 20.10.2015 22:41, Benoit Claise wrote:
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Other ADs focused on the protocol specific points. So let me focus on
> something else.
> The applicability section doesn't answer my questions: when to (re-)use
> this protocol?
> Note that the write-up mentioned ANIMA.
> 
> I see the protocol description:
> 
>    DNCP is designed to provide a way for each participating node to
>    publish a set of TLV (Type-Length-Value) tuples, and to provide a
>    shared and common view about the data published by every currently or
>    recently bidirectionally reachable DNCP node in a network.
> 
> However, this applicability section doesn't tell me when to re-use DNCP
> (or define a profile for it).
> I see an effort to address my discuss in the appendix B of draft version
> 11. Thanks 
> 
> What would solve my DISCUSS is an applicability section that would
> contain 
> a high level set of criteria that would briefly explain whether DNCP is
> applicable for 
> the specifications I have in mind. The first 2 paragraphs of section 1.1
> is a good start, 
> then it goes considerations about Trickle, the interval A_NC_I, etc ...
> and you lose the 
> readers.  
> 
> Something like:
> 
>    DNCP is designed to provide a way for each participating node to
>    publish a set of TLV (Type-Length-Value) tuples, and to provide a
>    shared and common view about the data published by every currently or
>    recently bidirectionally reachable DNCP node in a network.
> 
>    [As an example of what I'm expected, see below. 
>     Btw, I have no idea if this text is correct or complete, but that's
> besides the point] 
> 
>    DNCP works with profiles in which you have the flexibility to
> specify:
>    - the appropriate transport: the available options are TCP and UDP
> (see 
>    section appendix B for the tradeoffs)
>    - the transport security: TLS or DTLS, see appendix B). 
>    - If service discovery is required, an optional multicast service can
> be defined.   
>    - TO BE COMPLETED
> 
>    DNCP is applicable to LAN, WAN, or even the Internet. 
>    DNCP can exchange enterprise specific TLV or an IANA registry could be
> specified
>    DNCP specific extensions are possible.
>    TO BE COMPLETED
>  
>    DNCP limitations:	
> 	- Data published limited to 64kB
> 	- Doesn't work for SCTP, DCCP 
>         - All devices in the network must be DNCP node?
>         - TO BE COMPLETED 
> 
> To summarize, I need the 2 min elevator pitch of when (not) to use DNCP.
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> - I would agree with Alvaro, when he wrote: "In general, I found the text
> not straight forward or easy to understand." Potentially due to the
> structure.
> 
> - I hope that a document about manageability considerations (see
> https://tools.ietf.org/html/rfc5706#appendix-A) will follow.
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>