Re: [homenet] Kathleen Moriarty's Discuss on draft-ietf-homenet-hncp-09: (with DISCUSS)

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 18 November 2015 17:23 UTC

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 517631A8AC3; Wed, 18 Nov 2015 09:23:09 -0800 (PST)
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 jweimCrTGRii; Wed, 18 Nov 2015 09:23:08 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 0C8021A8AD4; Wed, 18 Nov 2015 09:23:08 -0800 (PST)
Received: by igl9 with SMTP id 9so106657405igl.0; Wed, 18 Nov 2015 09:23:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=4s17UsQkq/jrZkeaadotIG/6RswhswS9lQL5T8q0WnQ=; b=D2jggdFG+CKbcN2NYEIKaiHqoYfITnPt9EmCaLKh64F7zp40YUw06TjQpE+wGJaepD ZP4r368PLXC5YRnCcgxnyWjXnB0KAEB8JbzlAT4pkAiuFIr5/VxYpG/WvsTyK8IADIHG VTgqsNV89iGyCOX/QiYuCuZ/G4GfGx6R91gh3W2NCQq2z0p/GIbkboXu9NTqIoL7ckq+ s58WMRFUN/gWWpMqlwT1njiasO0LDbcWU4GZTdIB+sXF1OGqpxWieHGHnFnv+iZ4p7E3 +H1Ws6OwvOcilKlYuQXVFcTeL6JDk6Yq3VlRmOXq7nXRp0hDQ0qRy1wbIdH6p4lekAGM ek/Q==
X-Received: by 10.50.126.7 with SMTP id mu7mr6284116igb.2.1447867387478; Wed, 18 Nov 2015 09:23:07 -0800 (PST)
Received: from [10.0.3.190] ([97.65.203.35]) by smtp.gmail.com with ESMTPSA id 126sm1591006ion.32.2015.11.18.09.23.04 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Nov 2015 09:23:05 -0800 (PST)
To: Ted Lemon <mellon@fugue.com>, homenet@ietf.org
References: <20151117235034.24927.22561.idtracker@ietfa.amsl.com> <87poz7qw2k.wl-jch@pps.univ-paris-diderot.fr> <1447858576159-79d51c78-b96c8c38-55ec1307@fugue.com> <8737w3qozs.wl-jch@pps.univ-paris-diderot.fr> <1447863094928-7e8a26f0-271186df-921ed76e@fugue.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <564CB3FE.20503@gmail.com>
Date: Thu, 19 Nov 2015 06:23:10 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <1447863094928-7e8a26f0-271186df-921ed76e@fugue.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/gsDKTkf0IYs22TjzqiBaTM44QFM>
Cc: iesg@ietf.org
Subject: Re: [homenet] Kathleen Moriarty's Discuss on draft-ietf-homenet-hncp-09: (with DISCUSS)
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, 18 Nov 2015 17:23:09 -0000

Ted,

> The bottom line is that I think the reason you have given for not making DTLS MTI is a really bad one.   There is a perfectly good DTLS implementation out there, which is quite easy to use as far as I can tell,

So I am puzzled. If that is the case, it is not the HNCP implementer who has to
write any DTLS code (in my book, the word "implement" in a protocol spec means
"write code"). At most there would need to be a few extra instructions to wrap
a socket in DTLS, and that code would likely be ifdeffed because it would
only be used when needed. Which sounds exactly like a SHOULD to me.
Or maybe "mandatory to be able to switch on." In any case, not part of the
HNCP protocol itself.

Regards
   Brian