IETF Logo Mail Archive

Re: [core] Comments and questions on draft-jarvinen-core-fasor-02

Carsten Bormann <cabo@tzi.org> Wed, 20 November 2019 05:33 UTC

Return-Path: <cabo@tzi.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 42EF9120271 for <core@ietfa.amsl.com>; Tue, 19 Nov 2019 21:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 3wPqgEH20rjN for <core@ietfa.amsl.com>; Tue, 19 Nov 2019 21:33:24 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3033120800 for <core@ietf.org>; Tue, 19 Nov 2019 21:33:23 -0800 (PST)
Received: from dhcp-9c88.meeting.ietf.org (dhcp-9c88.meeting.ietf.org [31.133.156.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 47HrvP30dFzyZs; Wed, 20 Nov 2019 06:33:21 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <9917155C-DBA2-43F7-B14C-3B778B27E96F@ericsson.com>
Date: Wed, 20 Nov 2019 13:33:17 +0800
Cc: "core@ietf.org" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 595920795.747981-4c4a9c8451e4851bbe5926189179fb25
Content-Transfer-Encoding: quoted-printable
Message-Id: <976DBC2F-20DE-4E4F-BB45-BB1C24027AE0@tzi.org>
References: <9917155C-DBA2-43F7-B14C-3B778B27E96F@ericsson.com>
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/PatnTYuj_yicSjMRd874wZZJBm8>
Subject: Re: [core] Comments and questions on draft-jarvinen-core-fasor-02
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 20 Nov 2019 05:33:27 -0000

On Nov 20, 2019, at 13:06, Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org> wrote:
> 
> - Does CoAP allow changing option values in retransmissions? 

Yes, it actually encourages that, e.g.:

   The value is intended to be current at the time of transmission.
   Servers that provide resources with strict tolerances on the value of
   Max-Age SHOULD update the value before each retransmission.[…]

https://tools.ietf.org/html/rfc7252#section-5.10.5

(The interesting part here is eventual consistency — you can’t be sure that the acknowledgement you get is actually for the most recent retransmission.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email