Re: [Dots] Role reversal in RFC7252
Carsten Bormann <cabo@tzi.org> Fri, 08 November 2019 17:10 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AED2A1208AB for <dots@ietfa.amsl.com>; Fri, 8 Nov 2019 09:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 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] 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 MK7oA8lRdmad for <dots@ietfa.amsl.com>; Fri, 8 Nov 2019 09:10:07 -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 672D512083C for <dots@ietf.org>; Fri, 8 Nov 2019 09:10:07 -0800 (PST)
Received: from [192.168.217.102] (p548DC893.dip0.t-ipconnect.de [84.141.200.147]) (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 478mws50mSz108H; Fri, 8 Nov 2019 18:10:05 +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: <787AE7BB302AE849A7480A190F8B93303135F7FE@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Fri, 08 Nov 2019 18:10:05 +0100
Cc: "dots@ietf.org" <dots@ietf.org>
X-Mao-Original-Outgoing-Id: 594925803.439213-958efc301215338605ec97b091768141
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A790E73-62A3-46CE-B821-25B315CBC269@tzi.org>
References: <787AE7BB302AE849A7480A190F8B93303135F7FE@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/NWXqTR54BKvgUM3RjTbDA8bUlKo>
Subject: Re: [Dots] Role reversal in RFC7252
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2019 17:10:10 -0000
On Nov 8, 2019, at 13:29, <mohamed.boucadair@orange.com> <mohamed.boucadair@orange.com> wrote: > > Hi Carsten, > > Can you please help indicate whether (and thus which part of) RFC7252 discusses client/server role reversal so that a CoAP server can send (non-Empty) requests to a CoAP client? 2. Constrained Application Protocol The interaction model of CoAP is similar to the client/server model of HTTP. However, machine-to-machine interactions typically result in a CoAP implementation acting in both client and server roles. Obviously, the one sending a request is always a client. But it might have been a server in the last interaction. Because we don’t need a connection (or, with RFC 8323, the connection does not dictate the direction), this is easy to do. Grüße, Carsten
- [Dots] Role reversal in RFC7252 mohamed.boucadair
- Re: [Dots] Role reversal in RFC7252 Carsten Bormann
- Re: [Dots] Role reversal in RFC7252 mohamed.boucadair
- Re: [Dots] Role reversal in RFC7252 Carsten Bormann
- Re: [Dots] Role reversal in RFC7252 mohamed.boucadair