[core] RFC 7967 (No-Response) together with block-wise transfers in CoAP

Fredrik Wegelid <fredrik.wegelid@wittra.se> Wed, 26 June 2019 11:30 UTC

Return-Path: <fredrik.wegelid@wittra.se>
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 3764A1200DB for <core@ietfa.amsl.com>; Wed, 26 Jun 2019 04:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=wittra.se
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 UFsTg74bqiRY for <core@ietfa.amsl.com>; Wed, 26 Jun 2019 04:30:44 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 18FFD120146 for <core@ietf.org>; Wed, 26 Jun 2019 04:30:44 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id t28so1793188lje.9 for <core@ietf.org>; Wed, 26 Jun 2019 04:30:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wittra.se; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=yx9XHqdHPrB1PNJPkh0J+HMDmqCl3Vr2yWHSjCPNQeQ=; b=gStbWECitsdRANNaJPYp9/429kzwjzbB20eB98kREkqYRLFA4kSZ+T9DM/qAWRQ5yG 8566fppYc4LhuxYJxc56VaFICK4CRDNpFU2kwC1oavbV16zTm4jkXJ0w46hxa4n7HjtM aCS0+vqqou+9sIN3jIcmMdymJtbaRXLnF+RfVIx5AQjXlaKI3EoFxYhHcgFA+CL+hSVf /s+uVEd8RZaoHMhpvePaup43CwvmcYDgIEEqmp4Pb33p+6ag4j6S8ernPfeckBzjaqOv IFK5wbi4dr/RVuvQfcYUr8ZDAPbBP5RXswPFLD8gMAo2jTM/RWBhzbe1q2Wr/SnJ6qT8 HbZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=yx9XHqdHPrB1PNJPkh0J+HMDmqCl3Vr2yWHSjCPNQeQ=; b=gTgY1VRLto+I6/X6jUBRnsu6U1s2ksuStAJ44hdLzQbXNE4q8x4mbtV4hnjvF9HO7B hNSNvY05wsQO7VTsq/6jA8rcQQqwpzoHUKAGBeFp1DAWKyNHeKPCPQnjfEjfyR5AY1cH TIDdfcGm8pN+p8T+Y3Pax4cLlnkFxQh2zHsyyKLt8BQ6tzmB93jtEpeq7quUyrDf2AB0 UuthBA/MOUN/UNVoAaGiWTW2ynb4I/ABWAI9r4j3XE4mbE1i7hfPUPa1UM8zTJbOv57H fDMf50kAuAmyQ8N4FXARY9f5AB/gEOxJE6CO7NM6FZ8+QeGm1SffwR/31Y/5B3naUT84 V5RA==
X-Gm-Message-State: APjAAAVJPHGMWBeaEpgKf0UCJhbytcc+s3vxGCoowDIHapDRWSOfc6sQ lgTjEksivKt+tvuktgidFJFahwvhMvg=
X-Google-Smtp-Source: APXvYqyevyIKkvGtdurL99vWlrOZ8bq1zPA1wGS2suhIQzBK+MVPXruxsYLJS7XUZgT/47iwYC++KA==
X-Received: by 2002:a2e:9ec9:: with SMTP id h9mr2490538ljk.90.1561548641860; Wed, 26 Jun 2019 04:30:41 -0700 (PDT)
Received: from sannas-ipad.localdomain (h-206-4.A137.corp.bahnhof.se. [176.10.206.4]) by smtp.gmail.com with ESMTPSA id x194sm2371723lfa.64.2019.06.26.04.30.40 for <core@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jun 2019 04:30:41 -0700 (PDT)
From: Fredrik Wegelid <fredrik.wegelid@wittra.se>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <95486C6F-A08A-487E-974B-5692D474C06B@wittra.se>
Date: Wed, 26 Jun 2019 13:30:40 +0200
To: core@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/x7m70O0_bnQifB_4lK9mECQ1Ov8>
Subject: [core] RFC 7967 (No-Response) together with block-wise transfers in CoAP
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, 26 Jun 2019 11:31:37 -0000

Hi,

I hope that I am using this email list in the correct way. I apologise if that is not the case.
I have some questions/thoughts about using the No-Response option (RFC 7967) together with block-wise transfers in COAP.

In my team we are using CoAP to send messages from devices to a server. The messages are of such a size that we need to make block-wise transfers. In an attempt to reduce the amount of traffic in the network we have looked at using the No-Response option. We are however not clear on how this would work if used together with block-wise transfers. We would like to use the No-Response option to make the server omit the 2.31 Continue responses from the server on each block. We would however still like to be able to get a response on the last block to indicate the status of the entire block sequence. 

Does this make sense? In RFC 7967 block-wise transfers are not mentioned. Are they meant to be used together?

Best regards,
Fredrik Wegelid