[Id-event] URN name space for secevent profiles
Marius Scurtescu <mscurtescu@google.com> Tue, 11 April 2017 22:43 UTC
Return-Path: <mscurtescu@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 07862126C83 for <id-event@ietfa.amsl.com>; Tue, 11 Apr 2017 15:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 a-iE5tNLnKWu for <id-event@ietfa.amsl.com>; Tue, 11 Apr 2017 15:42:59 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 9AEBA126C26 for <id-event@ietf.org>; Tue, 11 Apr 2017 15:42:59 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id k87so6167991ioi.0 for <id-event@ietf.org>; Tue, 11 Apr 2017 15:42:59 -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=Sz/HZ+/eXTKy47iLh0oafn7bha1SVhcQ6jVld46ALm0=; b=BvVsNANlh1r9VUm7UiadHsXecIeDuAT2qftfCq/G0zvrjFQ/RkpME2ZGEz1ux1qKj+ xkvNnbsUVVhm6Z7tIWUxoERcuM9gS5iK4NsIUWjt91TZzrO7hqtLVG3WYprc0MSUNH1C f1c19Thw5ZjF/iCiaJT2JL1g2OC1I3miPC3/UQ8Ew0P7r5ZzVif8gpI3Yaak3WR9zeoZ QfxY49biTImFpUKWar4QZKh5T1iCVsP92ak5OSTzrqi/iEiE09Qn8l+tfzjrVJth4fhG leQkZpdmuYmI7OXqvPUAByMNSIbwoSqqjJ+dwx/0Kpa0J9cLtNxfTOy8dym8H8w1Yz8u sIjw==
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=Sz/HZ+/eXTKy47iLh0oafn7bha1SVhcQ6jVld46ALm0=; b=bg2sevgYsqokRK07nOPL4fs/WMUJW1vELRn0X6oNkaiGKAep3RCrm1WzGEsYIIVx5K U/w+th6eGE7P/L7wsviRA1mcDTh6I+89aJrpM1Qn1UwgcmmKeCPvjpLwczIn/HH3l78h 8LQNzm8d15DQPpgqNOsf9ziLreywjO+e6FYSTW9Rs4gLx3P2NGajkADzo6xVQjymutaC w4bQtOADr4/LYkBfCpvgFwOUMqzSDwMFUccW5/a39LlTc1Qdm0CzC6Jv22BmwxV2EWrv AdpjiAYhzN9Nd6BTp4gGwap07qWTS61jsiKKoIvFV07fozH42ZSF3rNxJM7fAUXFzVRU AzLg==
X-Gm-Message-State: AN3rC/6eCWIbO+ke88OqYbybSsXkbRQBjpKSBB1uEzs/76pgYAeOH3X4KjjvUHVqh5tuui5vor3qYWakQaC6P+S8
X-Received: by 10.107.11.159 with SMTP id 31mr13117011iol.41.1491950578448; Tue, 11 Apr 2017 15:42:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.87.3 with HTTP; Tue, 11 Apr 2017 15:42:38 -0700 (PDT)
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 11 Apr 2017 15:42:38 -0700
Message-ID: <CAGdjJp+j1Rrx5oSRQcCUocF7JNSEZb6iLh-5AC-2pTfsq-pRTQ@mail.gmail.com>
To: ID Events Mailing List <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="001a113edcd4407cfb054cebd0c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/XiwMlWg8-wueh_9om494Ci_to3I>
Subject: [Id-event] URN name space for secevent profiles
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 11 Apr 2017 22:43:01 -0000
Different secevent profiles will have to define URIs for event types and most likely if standardized most of these URIs will be defined as URNs. secevent could define the URN name space under which profiles can define their own URNs. The proposal is to use URN sub-delegation for "ietf" namespace (RFC 3553), something like: urn:ietf:params:secevent:event-type:<profile-id>:<event-id> As an example, RISC could define the following event types: urn:ietf:params:secevent:event-type:risc:sessions-revoked urn:ietf:params:secevent:event-type:risc:tokens-revoked urn:ietf:params:secevent:event-type:risc:account-deleted urn:ietf:params:secevent:event-type:risc:all Similarly, secevent could define a URN prefix for the aud claim (to avoid access token and id token collisions): urn:ietf:params:secevent:aud-client-id:<client-id> Thoughts? Marius
- [Id-event] URN name space for secevent profiles Marius Scurtescu
- Re: [Id-event] URN name space for secevent profil… Phil Hunt (IDM)
- Re: [Id-event] URN name space for secevent profil… Justin Richer
- Re: [Id-event] URN name space for secevent profil… Phil Hunt (IDM)
- Re: [Id-event] URN name space for secevent profil… Mike Jones
- Re: [Id-event] URN name space for secevent profil… Mike Jones
- Re: [Id-event] URN name space for secevent profil… Marius Scurtescu
- Re: [Id-event] URN name space for secevent profil… Mike Jones
- Re: [Id-event] URN name space for secevent profil… Marius Scurtescu
- Re: [Id-event] URN name space for secevent profil… Mike Jones
- Re: [Id-event] URN name space for secevent profil… Marius Scurtescu
- Re: [Id-event] URN name space for secevent profil… Mike Jones
- Re: [Id-event] URN name space for secevent profil… William Denniss