IETF Logo Mail Archive

Re: [core] Request for clarification of NSTART and concurrent requests

Bryan Green <bryan@aetheros.com> Mon, 15 August 2022 20:40 UTC

Return-Path: <bryan@aetheros.com>
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 998A4C14CF08 for <core@ietfa.amsl.com>; Mon, 15 Aug 2022 13:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aetheros.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0cGoJdoO5NK for <core@ietfa.amsl.com>; Mon, 15 Aug 2022 13:40:29 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A89F9C14F693 for <core@ietf.org>; Mon, 15 Aug 2022 13:40:29 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id mz1so1327659qvb.4 for <core@ietf.org>; Mon, 15 Aug 2022 13:40:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetheros.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=w+XRso8LvOUV1OhwHxJS+ETREAUR6dv2j1/sqDtYOPg=; b=iLAjslFE0s9BgxtB59DV6KOreKOvlAfYIWhvgrOMyAw9sM4KrJ55vQLgddoyKtq8gu SU+XJ31AsEZwf/whyl/B4blhToFSA8pWeZlQ/5IDXTYAfrpscG8O1Sg5POky6iZcb1/T iLBSANNfayaQnUKC8sOUPCo9omkcyMgJXsYv6q8DnqbW5HRqNQ/QP7xtgxf0rgh+bcDb WVhNzQry0pWRaXm/W933PREOmSOusSc8SCiWFkPywEdn4uuAwMsHdNp3sZF3CXMJmJOn gpN+28WUchQG+2l+IFvZh9/FJN361PiPMqVDL7+Oynxp7v4J/D4LVIdibxwq30EpnZhw 1LCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=w+XRso8LvOUV1OhwHxJS+ETREAUR6dv2j1/sqDtYOPg=; b=p/CfR8UcIWvBQLpkeL89YttpWACnaMVGiHvKo1KWAYVmTQyD66ri5GKGzXL5p7aQbW Br/5HwcN2PwSZL5fiAClwWg+6hV1J1lPwhDE5qTX2rIZoN50yKIAhUgN+YsJWK5omRXI dgFUXniT5o91Su65FlW/Emd4wUm9HKnQ1fFJ0vrCpn6O/RJMPcLrJXmXjyPR9fhmP58z 9GJTHYrlyqY4vF/p++7EgZO7jCG5N5ROrdfhNgoabboKKKm1OkJLBPrzsXjDUGC0lGte xZphvu7XMTJiZcxA+tHgCEOf+ebxBz9h95SyJ0RDhC1KKBHLjotKAfsrsxx0jxzA5FAF 5dJA==
X-Gm-Message-State: ACgBeo33xHxYuBx521zw2XKqkfuDiLI7o39MtSrxUVoWChS6THbcJn/q Ch3URA0o+U2A2gdKrK3RodTewcxg5IfQ2er5ZdYeTPecCKU=
X-Google-Smtp-Source: AA6agR6mBz+rVzSaImieYbbUuf1F5rUT+XA5ttUm2GCOgItB8TNF5erXumuCgzvTLr0rkcG4dtQrRzurxFGchzRgKmo=
X-Received: by 2002:ad4:5f0b:0:b0:478:4658:35f7 with SMTP id fo11-20020ad45f0b000000b00478465835f7mr15292971qvb.96.1660596028500; Mon, 15 Aug 2022 13:40:28 -0700 (PDT)
MIME-Version: 1.0
References: <CAOxiEDYnxj5qtavNQ-vPKC_eo4NPJD8sEPZLjmYS5WCAsY1Tbw@mail.gmail.com> <8B08FFA2-7EB7-49EE-BEEA-7678DCAC9995@tzi.org> <C7D01F99-8710-44F8-8048-B6FC3D25EA3E@tzi.org> <CAOxiEDY0T6CgXPZwmwWazXYhNBXk+HFhoy+VBHZMdxkddj3mPA@mail.gmail.com>
In-Reply-To: <CAOxiEDY0T6CgXPZwmwWazXYhNBXk+HFhoy+VBHZMdxkddj3mPA@mail.gmail.com>
From: Bryan Green <bryan@aetheros.com>
Date: Mon, 15 Aug 2022 13:40:17 -0700
Message-ID: <CAOxiEDYZoR18Qm5=2G-f3q+9DZsPuFLFyhhwi7ijSZSFsUJD2g@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: core@ietf.org
Content-Type: multipart/alternative; boundary="00000000000065026205e64da436"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/xFbTN9cqSGkuhLdrt06W1FBRMO8>
Subject: Re: [core] Request for clarification of NSTART and concurrent requests
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 15 Aug 2022 20:40:33 -0000

What would be the appropriate response to a CON request from a constrained
coap server that had reached its limit of concurrent requests from a single
client?
For example if a server was only capable of handling one CON request per
client at a time, and a CON request was received while the prior request
was still being processed, should the server silently ignore the packet, or
is there an appropriate response code to inform the client of the need to
wait?


On Mon, Aug 15, 2022 at 1:13 PM Bryan Green <bryan@aetheros.com> wrote:

> Thank you very much for the response.  That answers my question.
>
> -Bryan
>
>
> On Mon, Aug 15, 2022 at 12:22 PM Carsten Bormann <cabo@tzi.org> wrote:
>
>> On 15. Aug 2022, at 21:19, Carsten Bormann <cabo@tzi.org> wrote:
>> >
>> > heavily suggested
>>
>> heavily CONgested
>>
>> Sorry about that surprising auto-correct.
>>
>> Grüße, Carsten
>>
>>

v2.23.0 | Report a Bug | By Email