IETF Logo Mail Archive

[Id-event] Subject Categories in Subject Identifiers

Atul Tulshibagwale <atultulshi@google.com> Mon, 13 July 2020 16:09 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 974943A1518 for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 09:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.6
X-Spam-Level:
X-Spam-Status: No, score=-17.6 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_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham 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 NKofBcRSW8bP for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 09:09:44 -0700 (PDT)
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 E7F403A1529 for <id-event@ietf.org>; Mon, 13 Jul 2020 09:09:16 -0700 (PDT)
Received: by mail-yb1-xb2f.google.com with SMTP id y13so6639850ybj.10 for <id-event@ietf.org>; Mon, 13 Jul 2020 09:09:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=La1zombYHISo0U3IQJXMoXleNAFe+DTpKOkEDEozkjU=; b=cibRt53EsUGeObB+5bwUz0Uo6aB6ummgac97ojMX1CiSkffKb5P7ao4xxDKKyVNcJN peNYsuNyC/JoOTZpKQupqEu7ZRTJy/+yxlF+zyRr4O+RdM4C64KYxScwMoH4HVCUEQMP 87iNyS9E1Q3kPVtXNP4xyRlxEugJjjx2XeBrGNJwdJt8k7a3i70fR2ChSKN5/gQzlx5g 1UTn5JLAovnA0ayyWa9bLyfKeIQ5MkQwRs/kn2+WiRXVkXW/DDVjbl2yGg1Du6EeUm3B XlXur808aiObyg0tt1Hg2qlhm5Pzz0l7/EgBIMIumsiNZL2dyjEyoRVTTc6ZBYl2yk2M I6Ww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=La1zombYHISo0U3IQJXMoXleNAFe+DTpKOkEDEozkjU=; b=NHtV+zeo8+umdbbSQLE6T6pHyBvPzRLwwuUVUh8jzWFU7ox1UguvNDpaPr42NNgQe8 C8RhGhW11wIMgmCdl/PmocB+IcQRfOuD/8eeoeZWTvW+rO61DFE4c51GGhWVIolwPNgg D2bjpVCezsZLER+pZdW29uDG3vmJuQhEHgfpk2LI90Lq64bGZcU7WH694pnph//INKjG 0bZJanadrbUGalismB+7J5bVeL11H5JhXi9xPp65socc+RCoZ9ztqUMDeDJus+I/5huS 6NWPrB8Su5/haB+7pAO6yx8iO1YHe3V1UJxgj0TdMTgybnarzDtUdDluA0aAGfHjL7sC TVLQ==
X-Gm-Message-State: AOAM5317q8ZFCC/c183J9p0cIbNHjdSoHLqdjKQJvhL3Sg+RVVhKfHxS 6Re3TgBn0oAFy+TearqGPJIjKCldbsQ8xPhWM0zyP03A
X-Google-Smtp-Source: ABdhPJyktsO2TY26DWKrq+atv5lQtil7kAtWWGfhaKalUIvwa1AdvvjB13W4ihC2NaJGh6LTfr8546My1M3iXyS1UoQ=
X-Received: by 2002:a25:5ac5:: with SMTP id o188mr1158496ybb.322.1594656555461; Mon, 13 Jul 2020 09:09:15 -0700 (PDT)
MIME-Version: 1.0
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Mon, 13 Jul 2020 09:09:04 -0700
Message-ID: <CAMCkG5uxCRUPKgbM-XsWmykpvSbjpXybWew=brs4GTNwmQQyQQ@mail.gmail.com>
To: id-event@ietf.org
Content-Type: multipart/alternative; boundary="00000000000087654e05aa54e9d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/_EHa6rBwyBX7MNSYUnzX850uQHI>
Subject: [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 16:09:47 -0000

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

v2.23.0 | Report a Bug | By Email