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

Atul Tulshibagwale <atultulshi@google.com> Mon, 13 July 2020 20:48 UTC

Return-Path: <atultulshi@google.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 36A933A09D5 for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 13:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.588
X-Spam-Level:
X-Spam-Status: No, score=-17.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 bY-2Zg_2Tr4l for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 13:48:03 -0700 (PDT)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 E912A3A0B90 for <id-event@ietf.org>; Mon, 13 Jul 2020 13:47:49 -0700 (PDT)
Received: by mail-yb1-xb30.google.com with SMTP id v9so7095147ybe.3 for <id-event@ietf.org>; Mon, 13 Jul 2020 13:47:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nBgzMVOsgRtJZ3kicBtORAB4zLmvq0Ryb1pE7dB7kTs=; b=RnrHdiM6BVjusHBce4cM94nTTPiCf9uRYhRZq8sJLIR8NYEnjSp8v3hlLqN97NJ/t8 wFl+yLSz5kwEN46052a7ntzBxCtcHc5NwUApuKgtlEZd5L0vg4e7XXJetNS2ZTyoOlR8 TrHVtapNakIeFTcO7fMKKw6hUsKFMKpedohO3KMc0m5insjQwNr0JzxnVXZPgJLwsB0A fULY1IPggqWMoUrSLTa2pd53msWTqxCXJKpHyzAqlZcN0Q4D91JPx8XDtcZx/+ivdzkX zqfuIjRyFnR35EcIWN10l3MgWIFaFTeWYG0/GwMxX7qjH3p7/aTmS89JbCCTKfVD/N0D S0GQ==
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=nBgzMVOsgRtJZ3kicBtORAB4zLmvq0Ryb1pE7dB7kTs=; b=K4LdJw5nr29+OevEqY5MFC7qZaAt6ai/KQZGSyyVAoRVbjOrnauHa2v/sDl0P2tjUx SXfdYY9WP2JsuOD+bMNrptYPmd98W1LjlORebBQFkirB43AdgPdB4e9g0IpLG8LckLKL qMGOJWnIVLqSkCKV4zAPWBvWdYRn3hmWprWMNo43dBg7xFtS+7ZT0cNM1J8YOMy3f2PG mA4VaulNjQONavZ22mk9igwK0sb+cLGSWwAOdDEdtqeXjH4DZE0GzrrdUufLHTyIr+A7 HYCQ+krfS1nC6XiGjOUEdnlQCwijKGj2k8XrnODgNZbLOiRBn9e81TWCuPeWgNDRXJXi 51Fg==
X-Gm-Message-State: AOAM533FJJycD9WRDSdi0swYVuNf+PdwO1YOg9APiT/d7LOj+9IqyC2c FZRy9N7iXSRn2hfQm06ZuYYt7EAxy9BNsIiRgKw6MQ8iTGA=
X-Google-Smtp-Source: ABdhPJyfuQ6Q7q2uxi3oxvBW1JXITFQHmVpZouLfSpcEK0D7E4TKzRROgGqnlh6Q96fijtGlEBe6bdGpqoXKERTPh9w=
X-Received: by 2002:a25:2805:: with SMTP id o5mr2893457ybo.97.1594673268725; Mon, 13 Jul 2020 13:47:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAMCkG5uxCRUPKgbM-XsWmykpvSbjpXybWew=brs4GTNwmQQyQQ@mail.gmail.com> <CAD9ie-tXCtxQK9XPX6JBMnY2Byi=STGh7gzwMho88KqH6zG_vw@mail.gmail.com>
In-Reply-To: <CAD9ie-tXCtxQK9XPX6JBMnY2Byi=STGh7gzwMho88KqH6zG_vw@mail.gmail.com>
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Mon, 13 Jul 2020 13:47:37 -0700
Message-ID: <CAMCkG5s3zgR=cMdXQ=Ct+KTcUFpLVNL2+DxUpMzx66NAG6o+bQ@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Cc: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>, SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b7c20205aa58cdec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/4EBeXPWL9nbBgFFCxi9DGcqXMzs>
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 20:48:05 -0000

To address Mike's point I'm clarifying the proposal syntax here.

I'm proposing that we add a "categories" claim to subject identifiers,
regardless of the subject-identifier type (i.e. a common claim), with the
following text:

Subject Categories

   Subjects may be categorized as users, devices or sessions.  To

   specify the category of a subject, a "category" claim MAY be

   included.  If present, the claim MUST have a value that is one of:

   user  Specifies that the subject category is a user.

   device  Specifies that the subject category is a device.

   session  Specifies that the subject category is a session.

To address Dick's question:
I suppose one could think of it either way. I am neutral to adding it
within subject identifiers or at a higher-level in the event that includes
the subject identifier claim. This was also a point of discussion in the
SSE working group, so I'll let others comment on this. This may be dropped
if no one has strong reasons to include it in the subject identifiers claim.

Thanks,
Atul

On Mon, Jul 13, 2020 at 11:25 AM Dick Hardt <dick.hardt@gmail.com> wrote:

> 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
>>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>