IETF Logo Mail Archive

Re: [core] Confirmable message

peter van der Stok <stokcons@xs4all.nl> Tue, 24 January 2017 09:08 UTC

Return-Path: <stokcons@xs4all.nl>
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 EC8131294AC for <core@ietfa.amsl.com>; Tue, 24 Jan 2017 01:08:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham 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 y4ps9ofXasSL for <core@ietfa.amsl.com>; Tue, 24 Jan 2017 01:08:54 -0800 (PST)
Received: from lb2-smtp-cloud6.xs4all.net (lb2-smtp-cloud6.xs4all.net [194.109.24.28]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BE6F12949D for <core@ietf.org>; Tue, 24 Jan 2017 01:08:53 -0800 (PST)
Received: from webmail.xs4all.nl ([194.109.20.211]) by smtp-cloud6.xs4all.net with ESMTP id c98r1u00X4ZF39u0198rxs; Tue, 24 Jan 2017 10:08:52 +0100
Received: from AMontpellier-654-1-133-202.w90-0.abo.wanadoo.fr ([90.0.92.202]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Tue, 24 Jan 2017 10:08:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Tue, 24 Jan 2017 10:08:51 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: Ana Minaburo <ana@minaburo.com>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <CAOPRf-f9mxjArhB0FLto32xXxKxrLnR=dKET+H+BtBrFRi+dEQ@mail.gmail.com>
References: <CAOPRf-f9mxjArhB0FLto32xXxKxrLnR=dKET+H+BtBrFRi+dEQ@mail.gmail.com>
Message-ID: <177d3ea5b2b029e1df8aed315e56ff04@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Sjt_clugo_j3-nagGiXoQvwHevk>
Cc: Core <core@ietf.org>
Subject: Re: [core] Confirmable message
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: consultancy@vanderstok.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: Tue, 24 Jan 2017 09:08:57 -0000

Hi Ana,

thanks for the motivated suggestion.
We can change the text such that every implementation MUST support the 
confirmable requests, and MAY support non-confirmable requests.

would that do the trick? It is then possible that a client that accesses 
unknowingly a LPWAN server uses confirmable requests and cannot use 
non-confirmable requests.

Other variations are possible. But I like to restrict the number of 
request possibilities.

Peter

Ana Minaburo schreef op 2017-01-24 09:42:
> Hi Peter
> 
> In the draft, draft-vanderstok-core-comi-11.txt,  you mention that a
> confirmable message is mandatory for carry CoMi requests. We
> understand that for setting a value it is necessary to be sure that
> the information has been correctly received. In LPWAN WG we are
> studying the way to compress header and reduce traffic on very
> constraint links. Do you think, it could be possible to suppress this
> constraint and allow the use of NON confirmable messages ?
> 
> Thanks
> 
> Ana
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email