IETF Logo Mail Archive

Re: [core] CoAP for high throughput applications

Carsten Bormann <cabo@tzi.org> Tue, 05 April 2016 16:57 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 5828A12D7C4 for <core@ietfa.amsl.com>; Tue, 5 Apr 2016 09:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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 6s604MFTLCrz for <core@ietfa.amsl.com>; Tue, 5 Apr 2016 09:57:57 -0700 (PDT)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A494E12D7D7 for <core@ietf.org>; Tue, 5 Apr 2016 09:57:55 -0700 (PDT)
Received: from mfilter17-d.gandi.net (mfilter17-d.gandi.net [217.70.178.145]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id D8B3541C099; Tue, 5 Apr 2016 18:57:53 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter17-d.gandi.net
Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter17-d.gandi.net (mfilter17-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id qzZge6m02Wt0; Tue, 5 Apr 2016 18:57:52 +0200 (CEST)
X-Originating-IP: 31.133.160.124
Received: from dhcp-a07c.meeting.ietf.org (dhcp-a07c.meeting.ietf.org [31.133.160.124]) (Authenticated sender: cabo@cabo.im) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id DD0AD41C07F; Tue, 5 Apr 2016 18:57:50 +0200 (CEST)
Message-ID: <5703EE8B.5050509@tzi.org>
Date: Tue, 05 Apr 2016 13:57:47 -0300
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Kovatsch Matthias <kovatsch@inf.ethz.ch>
References: <D32866D3.62C58%thomas.fossati@alcatel-lucent.com> <5702E93E.3030005@tzi.org> <D328743C.62C97%thomas.fossati@alcatel-lucent.com> <55877B3AFB359744BA0F2140E36F52B54F186325@MBX110.d.ethz.ch>
In-Reply-To: <55877B3AFB359744BA0F2140E36F52B54F186325@MBX110.d.ethz.ch>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/aPyIhHH3SvGp-AQwSy3cH909v0g>
Cc: "core@ietf.org" <core@ietf.org>
Subject: Re: [core] CoAP for high throughput applications
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 05 Apr 2016 16:57:59 -0000

Kovatsch Matthias wrote:
> In case you really need to send a higher rate of requests from a client, it could use multiple ports.

... and it is worth noting that distributing requests over a large
number of outgoing ports is something that DNS servers and resolvers
know to do well.  It seems to me the need to change anything about the
message-ID here is very low even for high-rate applications.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email