Re: [core] DTLS and Epochs

Jim Schaad <ietf@augustcellars.com> Fri, 02 June 2017 03:38 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94003131453 for <core@ietfa.amsl.com>; Thu, 1 Jun 2017 20:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=augustcellars.com
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 tT9rZ97sYGQo for <core@ietfa.amsl.com>; Thu, 1 Jun 2017 20:38:16 -0700 (PDT)
Received: from mail4.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22B1D1294C7 for <core@ietf.org>; Thu, 1 Jun 2017 20:38:16 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; d=augustcellars.com; s=winery; c=simple/simple; t=1496374691; h=from:subject:to:date:message-id; bh=OG5mfOJ2itFTTL62GxS4gv6tHOHgufGyBvkKOYs5sP0=; b=hCZxwz12DJuHZCWykaQkdnCtBppZn/asfcDAl4MhckZQ4nvAYhqTZs4iOscpCVd4fxVk2/gCPqd 6oWxjBt7T1dyQ0tyHWVLED6YlyHTe+VKTNAcJt6Lyq3OUO+F5KKJ+YulRoKvcoUpvUBogPMeuP1gB RwIMSt9rufJLaxH0eaUjNXM72sSLBlEzSVu3IQYpbKghOEuFxD+mYA+532CXDTFeHX0iRaR+5Jj3j bHbsard4mfe9B10HilXRSvMgLJ7Pbbly1ZcLxWeM+rip0aCecnYiintYdxY93wcBooJ7z93PbCcXM 6dA3QCgbT0n8/UoQLwve/zl1437FwZtstLeg==
Received: from mail2.augustcellars.com (192.168.1.201) by mail4.augustcellars.com (192.168.1.153) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 1 Jun 2017 20:38:11 -0700
Received: from Hebrews (50.39.83.102) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 1 Jun 2017 20:38:08 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'weigengyu' <weigengyu@bupt.edu.cn>, 'Carsten Bormann' <cabo@tzi.org>
CC: 'Klaus Hartke' <hartke@tzi.org>, core@ietf.org
References: <003501d2cd32$c4417a10$4cc46e30$@augustcellars.com> <CAAzbHvYb39cPMmw_S0eZ4RSwzzmcE7636tjyu=kyCbUtBOwb0g@mail.gmail.com> <005e01d2cd8f$ae548dc0$0afda940$@augustcellars.com> <BC45A96C78AE43AF896A65A184D287B5@WeiGengyuPC> <014601d2daf1$8f1865c0$ad493140$@augustcellars.com> <849AEC05-87E3-48A7-B5C6-E6B6C8DC98D5@tzi.org> <015501d2dafe$dc53e640$94fbb2c0$@augustcellars.com> <0EE7D28C4BD94A4BB8ACA70FF0182BFC@WeiGengyuPC>
In-Reply-To: <0EE7D28C4BD94A4BB8ACA70FF0182BFC@WeiGengyuPC>
Date: Thu, 01 Jun 2017 20:38:06 -0700
Message-ID: <000001d2db51$a7d31c30$f7795490$@augustcellars.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDNpaiTKhTjOCugYu4GMFgItWlKOAHYofZfATwV17wCXqj8+gECJzwEAn/HMtwCQrMlzAJeyvcCo66gRIA=
X-Originating-IP: [50.39.83.102]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/7wu2wgJE6bxbronJTfzd3IjSp8U>
Subject: Re: [core] DTLS and Epochs
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jun 2017 03:38:17 -0000

Section 9.1.1 of RFC 7252 in paragraph 2 has the unfortunate requirement that all messages MUST be responded to using the epoch value.  Without the knowledge that the epoch value has changed this is not enforceable on either end.

-----Original Message-----
From: weigengyu [mailto:weigengyu@bupt.edu.cn] 
Sent: Thursday, June 1, 2017 5:27 PM
To: Jim Schaad <ietf@augustcellars.com>; 'Carsten Bormann' <cabo@tzi.org>
Cc: 'Klaus Hartke' <hartke@tzi.org>; core@ietf.org
Subject: Re: [core] DTLS and Epochs

Hi,

> Please note - I did not say that the epoch was not changed, I said 
> that it does not tell me that the epoch has changed.
> From a strictly security point of view there is no reason to do so if, 
> for example, the epoch changed just because the key was rolled over.

Why the epoch changed event must tell "me", i.e. the upper layer entity?

Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件-----
From: Jim Schaad
Sent: Friday, June 02, 2017 1:45 AM
To: 'Carsten Bormann'
Cc: 'weigengyu' ; 'Klaus Hartke' ; core@ietf.org
Subject: RE: [core] DTLS and Epochs



-----Original Message-----
From: Carsten Bormann [mailto:cabo@tzi.org]
Sent: Thursday, June 1, 2017 9:36 AM
To: Jim Schaad <ietf@augustcellars.com>
Cc: weigengyu <weigengyu@bupt.edu.cn>; Klaus Hartke <hartke@tzi.org>; 
core@ietf.org
Subject: Re: [core] DTLS and Epochs

On Jun 1, 2017, at 18:10, Jim Schaad <ietf@augustcellars.com> wrote:
>
> Please note - I did not say that the epoch was not changed, I said that it 
> does not tell me that the epoch has changed.  From a strictly security 
> point of view there is no reason to do so if, for example, the epoch 
> changed just because the key was rolled over.

Right, and the question for me is:  How do we get from the overly 
restrictive spec in 7252 to something that is still secure and can be 
supported by TLS libraries that are out there.

[JLS] I believe that the only way is to do an update to 7252.  I originally 
thought that I would file an errata, but I do not believe that is a correct 
use of the errata system.  It is used for things which are unclear or 
technically wrong.  This is not wrong, just misguided. It might be easiest 
to just do a delta RFC unless there is a good number of errata that need to 
be rolled into an updated document.

Jim


Grüße, Carsten