IETF Logo Mail Archive

Re: [Id-event] Subject Categories in Subject Identifiers

Dick Hardt <dick.hardt@gmail.com> Mon, 13 July 2020 18:25 UTC

Return-Path: <dick.hardt@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D473A166E for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 11:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.682
X-Spam-Level:
X-Spam-Status: No, score=-0.682 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, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 QBvydy1ahymO for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 11:25:12 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 0E5C73A1666 for <id-event@ietf.org>; Mon, 13 Jul 2020 11:25:11 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id d17so19139857ljl.3 for <id-event@ietf.org>; Mon, 13 Jul 2020 11:25:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=K3iiBQ6NYqgcJRSzcQ0DZdVNin6t8aohSv+Kjq7quYQ=; b=nfoqpdP2SlCk4svsrr31lQ1MjM8tE65obuL3PZdSsmod1zq9z6e2K2fY0F7TFnSgsy tlZHPGUY5w+Kw0uFfqw4xu+pdx9LiugpfKaj69CbTFD9RqNuqC2iVgB/9rAkDYsKRPdR jHLfQyF75lL2yz8EJKwTygWHbCFO5o0geUhHbtEUUypPYEnRTtmG2NmURRTotq1YzdCg f6aStCJKeKaU1WAprMhevPMMmbHuOV2/wNRINonm+aa5a11gY3eHRIF14WlZGfKNSvi4 qVBz/zMK/TRMuB/xLICvVQocnI0dDwc5dwAwtm4NeOr8cRl+N0hr9uRelS+7kv2rzfBc 1qOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=K3iiBQ6NYqgcJRSzcQ0DZdVNin6t8aohSv+Kjq7quYQ=; b=pqlM1q+xYvM8LmLj2hOs2fHxDn9pHqVNsFdMPAQgYdh2/ePzlIQaYA+4dvBlzY4BCU LA/WhCtOHDkz/pqTofHKQn8xubTPY+VQjuxMUjxhjCwcp5jCHwRxiUd+n2EHNSpBu+Nu ipfhtO+9xb+bYGNfpwfMgz61DhZA4UkuznXTjQb0nXao3xNgN2FO3QUoNH47yjKoN503 GmQNg/EAkR7PbR9jkE+/Xv7fwn4U50A8z6gsHpEwoKI4nhvBxJOKaEj8cbVe8kbvusCm RUqO35wWvM7EPYntCbcyjPv3qU0cKyClRs7rOqQAx5sYzhbD1JS3pEII5rcFhV/MSSe9 bKaA==
X-Gm-Message-State: AOAM530/P/c0Vsws30nhGn4z7Fm0iwE9uHizgIPDhE6oNhH4NOq7o8gX 3ga2UCoSIZtjQUa+eqDFvzDIDkIhldU0V1LPOCGuuQOdl6s=
X-Google-Smtp-Source: ABdhPJzkczjNo+sQ77gVNcXQDOAMLCZ/Ljpa6rVil3FnPNpmmbl7liXUT6ObwFXUk1tsRFSb8jkopAJTCJst77Lp38E=
X-Received: by 2002:a2e:8316:: with SMTP id a22mr436416ljh.246.1594664710000; Mon, 13 Jul 2020 11:25:10 -0700 (PDT)
MIME-Version: 1.0
References: <CAMCkG5uxCRUPKgbM-XsWmykpvSbjpXybWew=brs4GTNwmQQyQQ@mail.gmail.com>
In-Reply-To: <CAMCkG5uxCRUPKgbM-XsWmykpvSbjpXybWew=brs4GTNwmQQyQQ@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 13 Jul 2020 11:24:33 -0700
Message-ID: <CAD9ie-tXCtxQK9XPX6JBMnY2Byi=STGh7gzwMho88KqH6zG_vw@mail.gmail.com>
To: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>
Cc: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000093546505aa56cff2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/XVX_onORmDvulf3ibwxZXHfotZs>
Subject: Re: [Id-event] Subject Categories in Subject Identifiers
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2020 18:25:14 -0000

Hi Atul

I don't follow why this statement is true:

"Since this is a property of the subject rather than the event"

I would come to the opposite conclusion.

ᐧ

On Mon, Jul 13, 2020 at 9:10 AM Atul Tulshibagwale <atultulshi=
40google.com@dmarc.ietf.org> wrote:

> Hi all,
> Subject Identifiers will be used in various specifications about events
> pertaining to those subject identifiers. In order to determine the scope of
> the event, it is important to know what the transmitter of the event that
> includes the subject identifier refers to.
>
> For example, when a subject identifier specifies a phone number as the
> identifier, is the transmitter of the event that includes such a subject
> identifier specifying the user or the device represented by the subject
> identifier.
>
> Since this is a property of the subject rather than the event, it should
> be logically included in the subject identifier spec. Therefore, I'm
> proposing that we include a "subject category" claim within the subject
> identifier. The subject category could have one of the following values:
>
>    - *User*
>    - *Device*
>    - *Session*
>
> The above values are sufficient for the SSE profile, but other values may
> be possible (although such a possibility is not a part of my proposal
> <https://github.com/richanna/secevent/pull/1>).
>
> Thanks,
> Atul
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>

v2.23.0 | Report a Bug | By Email