IETF Logo Mail Archive

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

Markus Stenberg <markus.stenberg@iki.fi> Thu, 17 September 2015 17: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 9A7751ACE1A; Thu, 17 Sep 2015 10:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.226
X-Spam-Level:
X-Spam-Status: No, score=0.226 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, 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 nj9KQ_L1ZKMV; Thu, 17 Sep 2015 10:22:52 -0700 (PDT)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id 7E5C21B2A12; Thu, 17 Sep 2015 10:22:52 -0700 (PDT)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 55F66DA6002D608A; Thu, 17 Sep 2015 20:22:48 +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: <55FAE8DF.9020308@cisco.com>
Date: Thu, 17 Sep 2015 20:22:47 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <971958B0-D0E9-4E5A-8068-D86D848FFF47@iki.fi>
References: <20150917091111.14753.45178.idtracker@ietfa.amsl.com> <A5116A52-2B60-4C99-8B9F-F02A22E8F42A@iki.fi> <55FAE8DF.9020308@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Gf-XCpor5oQsU6hlAYEo7__rBQw>
Cc: homenet-chairs@ietf.org, Mark Townsley <mark@townsley.net>, victor@jvknet.com, draft-ietf-homenet-dncp.shepherd@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-homenet-dncp@ietf.org, homenet@ietf.org, draft-ietf-homenet-dncp.ad@ietf.org
Subject: Re: [homenet] Benoit Claise's Discuss on draft-ietf-homenet-dncp-09: (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: Thu, 17 Sep 2015 17:22:54 -0000

> On 17.9.2015, at 19.22, Benoit Claise <bclaise@cisco.com> wrote:
> Instead of focusing on the specific questions/answers, the key message is.
> The applicability section doesn’t answer my questions: when to (re-)use this protocol?

I still rephrase my previous answer - the one sentence that summarizes (what intro + applicability statement detain more detail) is: do you want to synchronize a small set of TLV tuples that changes relatively infrequently across a set of nodes, or not.

To expand it somewhat, most ‘application’ protocols can be more or less modeled as client-server (potentially hierarchical - hello DHCP), or distributed state sharing (e.g. link-state routing protocols, Pierre’s recent prefix assignment RFC). DNCP-profile defined TLV _transport_ can be used for either (it would be trivial to e.g. encapsulate DHCPv6 if you felt like it, not like it were a good idea). DNCP _state synchronization_ is just for the latter, and optimized for the case noted above.

I still do not know what to do about the text though.

Cheers,

-Markus

v2.23.0 | Report a Bug | By Email