IETF Logo Mail Archive

Re: [sacm] [sacmwg/draft-ietf-sacm-arch] Define the method to describe capabilities (#20)

bmunyan <notifications@github.com> Thu, 04 November 2021 15:53 UTC

Return-Path: <noreply@github.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90DE93A0DC3 for <sacm@ietfa.amsl.com>; Thu, 4 Nov 2021 08:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 y2WTEiBiguXH for <sacm@ietfa.amsl.com>; Thu, 4 Nov 2021 08:53:44 -0700 (PDT)
Received: from smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 702E83A0D19 for <sacm@ietf.org>; Thu, 4 Nov 2021 08:53:36 -0700 (PDT)
Received: from github-lowworker-28f8021.ac4-iad.github.net (github-lowworker-28f8021.ac4-iad.github.net [10.52.25.98]) by smtp.github.com (Postfix) with ESMTP id 8A0935607DD for <sacm@ietf.org>; Thu, 4 Nov 2021 08:53:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1636041215; bh=8j5NPJ0en4V0OE3YK+kit+TMmcaJ2C09BE8/8xsaXtw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bU7CQw05RzW7x+Nh6Wjl+d4MKjWDlhxmSrgXYs3ZYqeXsrxd6L4w+ZRAMOVEaWH/5 Ji3wb+3Yz4pqi2PwIkyha5wL/9epkpOgx77bPkgqN5Qs/1wSoohN7Cliuhlm0CJrG9 y2FD/WdJj98mk0c2tWeGviJ2KDiELnXe7oBz9FZ8=
Date: Thu, 04 Nov 2021 08:53:35 -0700
From: bmunyan <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-arch <reply+ACTMJUOKWKJWF4HZXXX3RBF7R7YQ7EVBNHHDDNNYAA@reply.github.com>
To: sacmwg/draft-ietf-sacm-arch <draft-ietf-sacm-arch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-arch/issues/20/961177919@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-arch/issues/20@github.com>
References: <sacmwg/draft-ietf-sacm-arch/issues/20@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_618401ff7b7af_c72c7246589"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: bmunyan
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/XVX5nfU1rwVsija8eoSOafqe8vQ>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-arch] Define the method to describe capabilities (#20)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2021 15:53:46 -0000

apart from the example above, not much.  i think the idea was to associate "capability urn's" to topic(s), but i feel like, during the "pre-the-previous-ietf" timeframe, i may have thought it was overkill to try and abstract specific topic names to the capability urn crap.

I feel like this was part of the component onboarding bits - some component registers with the manager and says "i can do 'foo'", and the manager replies with "because you can do 'foo', subscribe to these topics" -- it was a way to let components advertise what they do.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-arch/issues/20#issuecomment-961177919

v2.23.0 | Report a Bug | By Email