Re: [Id-event] Subject Identifiers - Working Group Last Call

Yaron Sheffer <yaronf.ietf@gmail.com> Thu, 27 May 2021 12:46 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 23DCE3A0781 for <id-event@ietfa.amsl.com>; Thu, 27 May 2021 05:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 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_MESSAGE=0.001, MIME_HTML_ONLY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 v8We7hWyUOqs for <id-event@ietfa.amsl.com>; Thu, 27 May 2021 05:46:10 -0700 (PDT)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 A580F3A0776 for <id-event@ietf.org>; Thu, 27 May 2021 05:46:09 -0700 (PDT)
Received: by mail-wm1-x32c.google.com with SMTP id o127so121705wmo.4 for <id-event@ietf.org>; Thu, 27 May 2021 05:46:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:date:from:subject:thread-topic:in-reply-to:message-id :references:to:cc:content-transfer-encoding; bh=/QiCghJMpO4vsfwx3UwB/BWmuQbbSBB2MFrgANgu3SU=; b=Y37NaXUp0Lyquj0jowd3OxkEZfklamMlm07IjTYyhiPRXzrArnrbR9OU07eh17Dv6b hHlLqzwnFIJF0FR84RaUzxcPUESbCyxPl3CURhqi3myBLe27B7Qa1HLh86+OnhyjiVbr SD2WErpU2NgXPURTHTDQGwMWgBpCJFEjFFqbcGoXlx4paRhBO8JX0ci9ikS1hmd5h2+q 5GrnzCka27b8pkbti1HatM+ETTdnK37bdoEm7FHJi8RO4oozn4JHeCicelDQEmSS+thq h8Y04wVMkx2YqtxjrGV/Dzbykf4VTSe2P6l5DfChe9I2pQnRvcPSE+Ad5+Rkv0sWLEPM 5z+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:from:subject:thread-topic :in-reply-to:message-id:references:to:cc:content-transfer-encoding; bh=/QiCghJMpO4vsfwx3UwB/BWmuQbbSBB2MFrgANgu3SU=; b=k5Mht78ccKrwb/63cXkXbAQSdam7MaCIytnwLJsyy2J6GvrEWfsA7NRUPTDv10g7DV f0yI0mJ8jnjo8pvTGDAmC8reCdlT6RkiiOj24IDpsiZKGZxG5AOA/VjK6SgDwdOpF2+i RJtB/FMyX9mlA4CrGT72Ud3RjoQMxJ54VbETqW58peNTcZp0i++4QJhe3mLCbS+lxZIT 9e8V3iYbjHtWPj5w26qu/UkV6K+/1R1aRvkG9SZOjtnYb5iJXteeh0Zqoh/XTBqSMjmF 49BEhzaJ+zlzdK0/taeIvwWwVSfkJ9RNgd5TGw9goOmH3j4FeEsolcNrh3ZFGm1eoaix UKQw==
X-Gm-Message-State: AOAM531JFQtvukPzT4LZMgwDeHU2I5BErGPy4SWDdkAXt3na+SH8TBZu m0rjlyeRumP7WiOKnRVC+NE=
X-Google-Smtp-Source: ABdhPJwt1H5lglAYaH3y2UMQPjsXh4MwqWtQJeQHsboPFjFuVYz3QKYSA/cFuJZO1RoErHPihP0W4w==
X-Received: by 2002:a05:600c:218c:: with SMTP id e12mr8402737wme.16.1622119567143; Thu, 27 May 2021 05:46:07 -0700 (PDT)
Received: from INTUL183d7d6fa (pub-corp-42-8.intuit.com. [91.102.42.8]) by smtp.gmail.com with ESMTPSA id z188sm2921736wme.38.2021.05.27.05.46.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 May 2021 05:46:06 -0700 (PDT)
MIME-Version: 1.0
Date: Thu, 27 May 2021 15:46:02 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Thread-Topic: Re: Subject Identifiers - Working Group Last Call
In-Reply-To: <CAD9ie-uSbNHq=Mt3ohA=URf5rv2hz7YUdUMhOf80C_f=XBrGLA@mail.gmail.com>
Message-ID: <36D66A89-D178-6047-B270-73AD540E7FAD@hxcore.ol>
References: <CAD9ie-uSbNHq=Mt3ohA=URf5rv2hz7YUdUMhOf80C_f=XBrGLA@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>, SecEvent <id-event@ietf.org>
Cc: "Richard Backman, Annabelle" <richanna=40amazon.com@dmarc.ietf.org>, Roman Danyliw <rdd@cert.org>, Marius Scurtescu <marius.scurtescu@coinbase.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/9foYm71m-wPau9C-O9swce4NCN4>
Subject: Re: [Id-event] Subject Identifiers - Working Group Last Call
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: Thu, 27 May 2021 12:46:15 -0000

Thank you Dick and the authors.

 

With my co-chair hat off, I support progressing this document. I also have a couple comments:

 

3.2.2: The text refers twice to "alias" subject IDs, but the format is now named "aliases".

 

Fig. 14 seems to be in conflict with the requirement to have a single subject for the JWT ("a JWT has one and only one JWT Subject"). Yes, maybe Elizabeth has a second email address, but we cannot assume that applications have this kind of logic. Similarly, the subject-related discussion in Sec. 4.2 (which is arguably a bit vague) as well as Fig. 18 seems to allow two different subjects within the JWT.

 

Thanks,

                Yaron

 

From: Dick Hardt <dick.hardt@gmail.com>
Date: Wednesday, May 26, 2021 at 23:22
To: SecEvent <id-event@ietf.org>
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, Richard Backman, Annabelle <richanna=40amazon.com@dmarc.ietf.org>, Roman Danyliw <rdd@cert.org>, Marius Scurtescu <marius.scurtescu@coinbase.com>
Subject: Subject Identifiers - Working Group Last Call

Hello WG

 

Thanks to Annabelle (and Marius) for the latest update:

 

 

Yaron and I would like to make another working group last call on this draft. We are hopeful there will be enough feedback on this draft from people that have reviewed it for us to recommend the draft progressing to the next step. 

 

Please review and respond if you are supportive of this draft, and if you are not supportive, please clarify your concerns.

 

Dick and Yaron

 

Image removed by sender.