[core] #410 (block): Initial MID on restart after blockwise transfer
"core issue tracker" <trac+core@zinfandel.tools.ietf.org> Fri, 06 May 2016 13:01 UTC
Return-Path: <trac+core@trac.tools.ietf.org>
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 B52DB12D987 for <core@ietfa.amsl.com>; Fri, 6 May 2016 06:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level:
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] autolearn=unavailable autolearn_force=no
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 dilq2r5zWJ5X for <core@ietfa.amsl.com>; Fri, 6 May 2016 06:01:37 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 2836C12D978 for <core@ietf.org>; Fri, 6 May 2016 06:01:32 -0700 (PDT)
Received: from localhost ([::1]:33237 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+core@trac.tools.ietf.org>) id 1ayfNq-0004aR-UX; Fri, 06 May 2016 06:01:30 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: core issue tracker <trac+core@zinfandel.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: draft-ietf-core-block@tools.ietf.org, achim.kraus@bosch-si.com
X-Trac-Project: core
Date: Fri, 06 May 2016 13:01:30 -0000
X-URL: https://tools.ietf.org/core/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/wg/core/trac/ticket/410
Message-ID: <064.4cbf8d09348a03ec25afdd8a19df82d0@trac.tools.ietf.org>
X-Trac-Ticket-ID: 410
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-core-block@tools.ietf.org, achim.kraus@bosch-si.com, core@ietf.org
X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: draft-ietf-core-block@ietf.org
Resent-Message-Id: <20160506130132.2836C12D978@ietfa.amsl.com>
Resent-Date: Fri, 06 May 2016 06:01:32 -0700
Resent-From: trac+core@trac.tools.ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/F2UbKrkRyb_4W9s-iEUUZkDjmSU>
Cc: core@ietf.org
Subject: [core] #410 (block): Initial MID on restart after blockwise transfer
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: trac+core@zinfandel.tools.ietf.org
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, 06 May 2016 13:01:41 -0000
#410: Initial MID on restart after blockwise transfer Doing tests on firmware updates using - a blockwise transfer (draft-ietf-core-block-20), - a random initial value of the MID (as recommended in RFC7252, 4.4. last part of implementation note), - I found on restarts short after such a transfer, a rather high probability of MID collision. (This is obvious caused by having rather more MIDs in use, than in normal communication situations). Therefore I would propose to add an implementation note in "draft-ietf- core-block" or/and "draft-ietf-lwig-coap" for proper handling of that situation. On my experience there are two possibilities: a: on graceful shutdown (after blockwise) store the last MID and load it on restart. b: if on restart (after blockwise) communication errors occur, wait for at least EXCHANGE_LIFETIME to escape the “probable” MID collision. This may also be the strategy, when a fails to load the MID for any reason. -- -------------------------------------+------------------------------------- Reporter: achim.kraus@bosch- | Owner: draft-ietf-core- si.com | block@tools.ietf.org Type: editorial | Status: new Priority: minor | Milestone: Component: block | Version: Severity: - | Keywords: -------------------------------------+------------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/core/trac/ticket/410> core <https://tools.ietf.org/core/>
- [core] #410 (block): Initial MID on restart after… core issue tracker
- Re: [core] #410 (block): Initial MID on restart a… core issue tracker
- Re: [core] #410 (block): Initial MID on restart a… Carsten Bormann
- Re: [core] #410 (block): Initial MID on restart a… Kraus Achim (INST/ESY1)