Re: [core] Responses to PUB/SUB messages

Michael Koster <michaeljohnkoster@gmail.com> Mon, 11 March 2019 19:51 UTC

Return-Path: <michaeljohnkoster@gmail.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 59412131122 for <core@ietfa.amsl.com>; Mon, 11 Mar 2019 12:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BqSiJ76zkriD for <core@ietfa.amsl.com>; Mon, 11 Mar 2019 12:50:58 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 8FDA71310F8 for <core@ietf.org>; Mon, 11 Mar 2019 12:50:58 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id r124so4844419pgr.3 for <core@ietf.org>; Mon, 11 Mar 2019 12:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=RT7HKhDQYcQuTOGi/PST68TTHFtDtqfctSvvdCLbgFU=; b=AAKR/cRKv6BvS9q8UlpuMl1nDUNlcD4j/bxe4eC5BXnTPT9fBQEdkGFNwai+keKHZe AKtO7SLNSkScPvXnp83uIfHc79dgNEDq5/FeOOLXM2RpvnB3nYYnN7MiXo2FsxNIlkRs ZluNCya/TmwHVeWj5I6Gl+QBzzVPUVVe31zVZ6qJZMlb5307rFsxD+SVQEKTNnkxReyU SbSD/tMzxMSb3iSTsByCgHzclPbT0XqsP1qJR36hft1l10RTaZGFTi5U/bjzG0xGgTHc go5zWfffCoTrPCYW9Ry76zPyfkcI+n7AKc+Pp8S/eaC4cPHiP7FGhNO2IfENknLhUb0e 7tDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=RT7HKhDQYcQuTOGi/PST68TTHFtDtqfctSvvdCLbgFU=; b=dMWBU+O7MNGQkqYiKXxAaLNuRrfWh2StofBOcV0507tnSg/n34pdv2BrSry21lZDqB J5gNZilLWED6hYRxi8NMk87b6CiRC53G/x5/Yr8eIp2Tq8WdhQQDuxwlJpK+6lBDfsFV rHyKvqyF4ce1W4dHiaXQmyOq/WpMZF6YHpQBGFOkQlm+dXcJc1tjYY99mhXxiGdCjd30 2QUKqPSVhK/+GZOojKROnvvd/496LnmLXjSuteJFyjNW4SQy/fOOaOu3MnSQaOqh7TPY CWxxpNxyTOs1SNUSWK2RRPnGi3IUi/iasYaD7DvBkDLmfwi+WGcPfcHEG54QYkwkxLhd vhuA==
X-Gm-Message-State: APjAAAWRE7UGQ/d+NLn0zpKmnvLQbcTiVSmZldc3H/XvlsxLpWbvkQbt ieGaGSktOABnotYVIirFNIk=
X-Google-Smtp-Source: APXvYqyihj/qUdW6jjqMbPhLv4wU0+FoD21LTe1QEV8ErVGZTWBS3y+uyBRjL0ph+kriDWeNf+J7Fg==
X-Received: by 2002:a63:ed45:: with SMTP id m5mr9859548pgk.265.1552333857958; Mon, 11 Mar 2019 12:50:57 -0700 (PDT)
Received: from [172.16.0.3] (c-71-202-145-92.hsd1.ca.comcast.net. [71.202.145.92]) by smtp.gmail.com with ESMTPSA id e26sm9392695pfd.124.2019.03.11.12.50.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Mar 2019 12:50:57 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Michael Koster <michaeljohnkoster@gmail.com>
In-Reply-To: <036f01d4cfd9$99b054f0$cd10fed0$@augustcellars.com>
Date: Mon, 11 Mar 2019 12:50:56 -0700
Cc: core <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <08A40B3A-12C9-494C-8374-9D44D5C8D234@gmail.com>
References: <036f01d4cfd9$99b054f0$cd10fed0$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/qGSBFCX5ubaC77ev-UvU1H0aG94>
Subject: Re: [core] Responses to PUB/SUB messages
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: Mon, 11 Mar 2019 19:51:00 -0000

What if one combines Dynlink with a pub/sub Broker and creates observe bindings to topics? Likewise with Dynlinks one could create push bindings for outgoing notifications. In this case the node that hosts the pub/sub broker will also be a client due to the Dynlinks. Multicast would also be possible with a push Dynlink.

Best regards,

Michael

> On Feb 28, 2019, at 6:50 PM, Jim Schaad <ietf@augustcellars.com> wrote:
> 
> I have ended up with an odd ball question about the Pub/Sub system.  For the
> purpose of security, a message that goes to the pub/sub server is marked
> with a group identifier and a key identifier.  This makes complete sense.
> The question that I have is there any concept of doing a response in some
> manner to something that is on a Pub/Sub server or does that just become a
> new publish?  The concept exists for a multicast and the question exists can
> one simulate doing a multicast operation via a Pub/Sub server.
> 
> Jim
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core