[core] DTLS and Epochs

Jim Schaad <ietf@augustcellars.com> Mon, 15 May 2017 04:37 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 32C91120721 for <core@ietfa.amsl.com>; Sun, 14 May 2017 21:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.698
X-Spam-Level:
X-Spam-Status: No, score=0.698 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 Jpgtv0n2X0_T for <core@ietfa.amsl.com>; Sun, 14 May 2017 21:36:59 -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 2E5BC1200F3 for <core@ietf.org>; Sun, 14 May 2017 21:33:02 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; d=augustcellars.com; s=winery; c=simple/simple; t=1494822778; h=from:subject:to:date:message-id; bh=1MS65/e4T08al4cJ3WOVQSHWT6CcOdZYnYgUMrpiAtM=; b=ilL07bNNCSBJ/b+vOJj80Qq4U1mDhLZZOvXeHVw/vNEYTB6V6ejf5Uw8ERSXHowjn1Irz9B/88w Mx+Z9+LdNMPzoSuTDRi9oISgPDIP/tdXOweXL7xvhgEjcLagtlWPL/PJgFbV86xzuucZP+EnmxBoH 3dUDe2uNXYHypoZLGTeIZQ9KDW+Mhi6NpWBBg/W7wmm8FmwR5fpeED5kFLI1URhsveXQRUPJc0TCu qHdy2edg8TGRfstzFBxgkS39c8D9T80pBvbhxC3ist3qTTU3LeZGGWtgvr8y8qCTZ7nwebh5LHkg4 KN9L6fU36nOSrXQpYiqdFGZuo4H6D6NH9EFw==
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; Sun, 14 May 2017 21:32:58 -0700
Received: from Hebrews (24.21.96.37) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Sun, 14 May 2017 21:32:30 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: core@ietf.org
Date: Sun, 14 May 2017 21:21:44 -0700
Message-ID: <003501d2cd32$c4417a10$4cc46e30$@augustcellars.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdLNMilfa5ceDMFXSzWGbktOvFqaPw==
X-Originating-IP: [24.21.96.37]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/biDJ8n4w0kBQATzyh9xHlKnGy1o>
Subject: [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: Mon, 15 May 2017 04:37:00 -0000

I am working on getting my DTLS code to work correctly and I have come
across something that I do not understand.  I did not see any messages in
the mailing list that dealt with this so I would like to get an explanation
if possible.

RFC 7252 states that a response is not to be correlated with a request
unless the message id, the DTLS session and the DTLS epoch are the same.  I
can understand the reasoning behind the id and session being the same,
however I am unsure of the reason that the epoch would need to be the same
as well.  I cannot see of a reason why the epoch should matter.  The
security session is still the same.  I could understand that there would be
a reason to kill an association if additional client or server
authentication information had been passed along, but while that would
change the epoch, an epoch can change just because enough messages have been
sent over the pipe.

Can somebody please explain the reasoning to me.

Jim