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

"Benoit Claise" <bclaise@cisco.com> Tue, 20 October 2015 20:41 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: homenet@ietf.org
Delivered-To: homenet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F451B2C88; Tue, 20 Oct 2015 13:41:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.6.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151020204159.17294.93467.idtracker@ietfa.amsl.com>
Date: Tue, 20 Oct 2015 13:41:59 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/fLi7e_MvQUyI8Iv4TR-gwdoYrsI>
Cc: homenet-chairs@ietf.org, draft-ietf-homenet-dncp@ietf.org, homenet@ietf.org, mark@townsley.net, victor@jvknet.com
Subject: [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
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 20:42:00 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-homenet-dncp-11: Discuss

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-dncp/



----------------------------------------------------------------------
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.