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

Ted Lemon <> Wed, 18 November 2015 22:13 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 1A0141B305E for <>; Wed, 18 Nov 2015 14:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7rQJ99p00Rj4 for <>; Wed, 18 Nov 2015 14:13:46 -0800 (PST)
Received: from ( [IPv6:2a01:7e01::f03c:91ff:fee4:ad68]) by (Postfix) with ESMTP id 1F9C71B3091 for <>; Wed, 18 Nov 2015 14:13:36 -0800 (PST)
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----sinikael-?=_1-14478848143130.7932846830226481"
From: Ted Lemon <>
In-Reply-To: <>
References: <> <> <> <> <> <>
Date: Wed, 18 Nov 2015 22:13:34 +0000
Message-Id: <>
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [homenet] Kathleen Moriarty's Discuss on draft-ietf-homenet-hncp-09: (with DISCUSS)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 18 Nov 2015 22:13:49 -0000

Wednesday, Nov 18, 2015 12:23 PM Brian E Carpenter wrote:
>> 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.

That's why I said MTI, not MTU!   But MTI means not #ifdef.

Sent from Whiteout Mail -

My PGP key: