[Dtls-iot] Reference to mathewson-no-gmtunixtime

Hannes Tschofenig <hannes.tschofenig@gmx.net> Wed, 15 July 2015 11:20 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5731A883A for <dtls-iot@ietfa.amsl.com>; Wed, 15 Jul 2015 04:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yCbGdNGUlak6 for <dtls-iot@ietfa.amsl.com>; Wed, 15 Jul 2015 04:20:55 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB9931A882E for <dtls-iot@ietf.org>; Wed, 15 Jul 2015 04:20:54 -0700 (PDT)
Received: from [192.168.131.133] ([195.149.223.246]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LoEwL-1YnAvV3ZsH-00gILf; Wed, 15 Jul 2015 13:20:53 +0200
Message-ID: <55A6420E.7040703@gmx.net>
Date: Wed, 15 Jul 2015 13:20:46 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="5nlE9iIOmR0BXLaG27mFu3vH7Kp2pwTb4"
X-Provags-ID: V03:K0:8cjDwvJnny0tChLAy/K9/sgG8GsXuolmi9nOFOdHKjSF40ZaKoV BqiLn3i4hKfXCFwmea/aAVqZ3QRmsWR5INkAigOhZWOJOTdrAI1GGKVhF/6ez+vm1unDw2z hHEUjbExm73CjgZrXFbLxWjIRRoMZJep156CCJC2miSpXTZDVTFRo9vIF67hvZLkfajNveH bOzBwPB7WI4FDWmvX4byQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:ZX0aSL7QiSQ=:Q+ubnpta4K5SflCco1p7Zb MVuGETA4GzRXYCSY1kpfKWu9w/cZu8eabxWThZ1+HvWt1euby0e3SpajEaUQKdfhLRgM0SIOS N4XEs+ve1h8kdFi4yYD7Y+p0HsV6B9NHRUHPNLkcFZwaBlpUmOPTwMtFPXD2BVH+AF/CUZH6q D+v54BcXUJjgK0pcwyuc0F0J10f2boAzTfJW6MCNRd+32VjPNQI86T/e6sM3xmnLEKasLvHxV 8yWAzgT/mi2D45mvhphmWWKYCyb/5TiGzp0ApMGmTEnOu2gEooqLDTGvNshCixcZXJidgLjQ7 dEIDn5PvN3HJsRMjv/qe04GcULr+WZPf+uDrO9W7ksA1WqOL6LM5a/yZ+JigsEqPsxcfFiivr MVuOLyQvT51g2LvBfuZxf+9rXPhemQp+1M+tE5i+7Y7qEV+qOt/GqJgk47gnnj/IJ6zDKRPDK CZr2SxSqoDfvIOOsNcl163kz5aN6v8OUwAUpqlCr1jtWHiEbmKTIoKKkO0QXoVTQgcLi+SEuo /RB9/6O10OyA+GkXlZaCJW0z4+whdLzmfV6SHTQlcfbfX7QofaXT1r907Y4ZHTYLmiMrimMui ZcHijzER5GpKIwkMUVbyDJaPi1Y5nGih9BRfkPmH6Z96kpflZmqHfdsygPXHbfkjjTvioyunt qIV9s9LRcdCXlMyOjOrnjbZ6CL9Kle+OzOS8VvQLZbXuttA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/aMmQyG7spQHwfTeXpnS2vQ4X094>
Subject: [Dtls-iot] Reference to mathewson-no-gmtunixtime
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2015 11:20:56 -0000

Stephen wrote:

(8) 14: You are RECOMMENDING to follow
mathewson-no-gmtunixtime which is fine. That however
means that that's a normative reference on which you
need to wait. I'm fine with that, but the WG may or may
not be.


I was worried about this issue myself as well. I was hoping that
mathewson-no-gmtunixtime would have moved along at the time when we get
the profile draft to the IESG. Obviously, this has not happened.

I see the following possible next steps:

a) Remove the reference to mathewson-no-gmtunixtime and point out that
somewhere a secure time source needs to be made available.

b) Copy the relevant text from mathewson-no-gmtunixtime  into this
document (with appropriate attribution). mathewson-no-gmtunixtime  cites
a different motivation for doing what he suggests, which I believe is
less applicable to our scenario.

c) Work with Mathewson on mathewson-no-gmtunixtime  to get it finished.
The profile document would be blocked till that time.


If you ask me for a preference then I would probably go for (b). I am
not sure it is, however, in the mandate of the working group to define
TLS-specific functionality.

Hence, I fear that we have to shoot for (a).

Ciao
Hannes