[Id-event] A few Subject ID comments
Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 23 July 2019 18:12 UTC
Return-Path: <yaronf.ietf@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 8FE8F120426 for <id-event@ietfa.amsl.com>; Tue, 23 Jul 2019 11:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=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 xIBFQYlgNKmy for <id-event@ietfa.amsl.com>; Tue, 23 Jul 2019 11:12:07 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 86801120408 for <id-event@ietf.org>; Tue, 23 Jul 2019 11:12:07 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id n4so44247813wrs.3 for <id-event@ietf.org>; Tue, 23 Jul 2019 11:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=Y/9PEa8bkEhGGnDnZHMYvZfMqwP6fT3Fgduq1LMON3o=; b=TIRDdok7z9n8u7R4Kn0yFvT11vHEKcA7LyuQwRGtK79tHh+tM6DD5hfXRUOjNY4yn/ xVBqvLpEQTxz6mp0wNh2+KnnuiBNQ/JiKfqiqVrc/c6USgvqNh7hql/eSbXM/C8fRyI2 HmBW4RXolKYtxYBktxpcL3wR4XKNPh+hF2q7eeNkVSTwOCOr67K88KTlWwDlqzptmwdw 63cntOogmdBQROlqEcOYJmSbS3iupvaBOOTjjOpO2+XgRL0PV1s2wwgiTQyt8YFBjd+r mlLdQkeg1jRibIZW47nko1kEimDx6K074fSIUhfmWV/b897JO1Fz4yWTgU9Jz2afRz1W UVrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=Y/9PEa8bkEhGGnDnZHMYvZfMqwP6fT3Fgduq1LMON3o=; b=mQuEhPuTvAehXunUlBte59rsA4YTRGxfYcZGTdZLhd3e+Jl3MVKptIWFGq87NwcmRi N81YlLCfMipqZ1qY160HVr4P0j6MQnRs7h++PZvNVYsur9RYrUCKLfduuEfrSswmwYDj VSMC0BQIFCnsqLaJ+gm0XecN3uXXF4qA5xmczhSbDHkZuvHwUFM109vY7XB5er2/1MJ/ P43wthJNoOkm+5H+xqxIc/khLArDsDbA1AixJPZsQM3QYg8JZ1u7FJZh3z3ejEcKIpxm dEoKp/oc6bZ6Chqz/+nJhh0FdtlejOhV3yWosyUIlecqVp/iX9NGfcYk7PhwKWKl5eBD j8YQ==
X-Gm-Message-State: APjAAAX7ytgOESO+kSUUeQPF8LqEDxh9e1SOMtUoN721UwE14m6KlVBi TLV8FgdBqOqybIS+NPVUN2iuN7jj
X-Google-Smtp-Source: APXvYqw/HXLtuAH0faVeVRUOwpwG+QNcoKbcs1zsL4UOf7VFpjTvZaB1t5C3mF1hzOJ/Tqo0T7dKzQ==
X-Received: by 2002:a5d:6a84:: with SMTP id s4mr5922345wru.125.1563905525806; Tue, 23 Jul 2019 11:12:05 -0700 (PDT)
Received: from [192.168.43.74] ([2.53.182.142]) by smtp.gmail.com with ESMTPSA id u6sm46477929wml.9.2019.07.23.11.12.04 for <id-event@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Jul 2019 11:12:05 -0700 (PDT)
To: SecEvent <id-event@ietf.org>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <2ba33497-27f5-9ced-c47b-4d301f5870e6@gmail.com>
Date: Tue, 23 Jul 2019 21:12:02 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/t0GT6_yodGqlbMVkRX4pqy94mNk>
Subject: [Id-event] A few Subject ID comments
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: Tue, 23 Jul 2019 18:12:10 -0000
Sorry I couldn't be there in person, so here's a couple comments before I forget:
- Shouldn't this draft officially "update" the SET RFC, because we are changing the semantics of what the subject is? In particular if we're allowing JWTs (SETs?) with no "sub" claim.
- There are a few dangling commas in the examples in Sec. 4.1 which IIRC is not legal JSON.
- If the semantics of having both "sub" and "sub_id" in a JWT is that both are aliases to the same principal, wouldn't it simplify everything (including the code) is we disallowed this case and instead, required the use of "sub_id" with an "aliases" construct?
Thanks,
Yaron
- [Id-event] A few Subject ID comments Yaron Sheffer