Re: [Jose-reg-review] [IANA #1231970] expert review for draft-santesson-svt (jose)

Joe Hildebrand <hildjj@cursive.net> Thu, 09 June 2022 17:37 UTC

Return-Path: <hildjj@cursive.net>
X-Original-To: jose-reg-review@ietfa.amsl.com
Delivered-To: jose-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE2CC157B53 for <jose-reg-review@ietfa.amsl.com>; Thu, 9 Jun 2022 10:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level:
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=cursive.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dG0AkxndXwiG for <jose-reg-review@ietfa.amsl.com>; Thu, 9 Jun 2022 10:37:45 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D6C2C157B3B for <jose-reg-review@ietf.org>; Thu, 9 Jun 2022 10:37:45 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id y12so22881252ior.7 for <jose-reg-review@ietf.org>; Thu, 09 Jun 2022 10:37:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FqrwkflkeVE9uzTccPK1TpxhKOdsc0voKxWIf5J769U=; b=CNlrCcNwQUnheB/wx3NVwoEByYbJA5nCFGUMO6PW19wwl2fjYVAHrQw0bgSk2ostjE 3N7ANMuI4fZOv9/vXO84zz/VDh+kHMRs4ev5QkNrJbQjbu11DOTdMaNj2ShQPfs3zql2 BuYXl/QhQdk3tlwrCgsFoLPnuluCnnEcBCaqk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FqrwkflkeVE9uzTccPK1TpxhKOdsc0voKxWIf5J769U=; b=mNWixxvCIi5oujb8hdXbpdgGJMQeFqs3aAfJC04M5NFGPeH5DWAjHzEWu5DNLHFPgV d4zIA6ce80fegIQzNN50zNSUWoVTJN8g/YLVirfF6C/KBUeAnBljL09S9N+B9TaucPCH hIzUAcRxR2ej7GNtFOYkzsdM5s5tv51uDLN3vaxE/6Hov07Ej5zp+Gr/kexr1xk4ejWM P955FjOb+bqDBC5g/LBijyvxzV9yKvV5D8pmnl9q7F3CnG76cUKi/iiIFyXjL43SHpXH YSPICEcER8QXWlqjRbk83qaTuIuY/n6uBrKQegg9Gv9vD93TlCV4khSgRsoFiQ9MRFi2 AieA==
X-Gm-Message-State: AOAM53332zLn+2hhp1UVcz1lS717fV0NI0GYPJ5KDpfYTCnCeb28FYcT Qc1DewXhDfBmEnBFSAapi5kK2A==
X-Google-Smtp-Source: ABdhPJzcMvcdBiI2YWbkvm3zw6PDNjWdIv3wk4BoHAjsB/YVJTNpIDmicdA842LITKRnL3u60p5ALQ==
X-Received: by 2002:a05:6638:210e:b0:32e:b8e5:6a95 with SMTP id n14-20020a056638210e00b0032eb8e56a95mr22190057jaj.81.1654796264571; Thu, 09 Jun 2022 10:37:44 -0700 (PDT)
Received: from smtpclient.apple ([2601:282:177e:142d:cf6:bc4c:5261:2ac3]) by smtp.gmail.com with ESMTPSA id i12-20020a926d0c000000b002d39ae9918asm10482899ilc.54.2022.06.09.10.37.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Jun 2022 10:37:43 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Joe Hildebrand <hildjj@cursive.net>
In-Reply-To: <rt-4.4.3-16037-1654548831-520.1231970-9-0@icann.org>
Date: Thu, 09 Jun 2022 11:37:42 -0600
Cc: jose-reg-review@ietf.org, joe-ietf@cursive.net, Sean Turner <sean@sn3rd.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AA96B6F-0197-4301-89CB-E07EDFFAE453@cursive.net>
References: <RT-Ticket-1231970@icann.org> <rt-4.4.3-24468-1654548506-292.1231970-9-0@icann.org> <rt-4.4.3-16037-1654548831-520.1231970-9-0@icann.org>
To: drafts-expert-review-comment@iana.org
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose-reg-review/k5VO8J72yjrXZf7juVOxRlywtKc>
Subject: Re: [Jose-reg-review] [IANA #1231970] expert review for draft-santesson-svt (jose)
X-BeenThere: jose-reg-review@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "The JSON Web Algorithm standard \(RFC 7518\) establishes this email list for designated experts to discuss proposed changes, additions, and removals to the set of algorithms in the JSON Object Signing and Encryption \(JOSE\) registry, http://www.iana.org/assignments/jose." <jose-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose-reg-review>, <mailto:jose-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose-reg-review/>
List-Post: <mailto:jose-reg-review@ietf.org>
List-Help: <mailto:jose-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose-reg-review>, <mailto:jose-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2022 17:37:49 -0000

I believe this can go forward without waiting for Sean, this registry isn't as critical to security as some of the other ones in JOSE.

This value does not conflict with any already in the registry.
The Registration Template from https://www.rfc-editor.org/rfc/rfc7515.html#section-9.1.1 is filled out completely and correctly.
The specification in section C.1.1 of the RFC-to-be seems clear in the context of the document.
Header fields are not mandatory-to-implement, so I don't see any intro concerns for existing implementations.

Approved.

— 
Joe Hildebrand

> On Jun 6, 2022, at 2:53 PM, Amanda Baber via RT <drafts-expert-review-comment@iana.org> wrote:
> 
> Hi Joe, Sean,
> 
> Can you review the JSON Web Signature and Encryption Header Parameter registration proposal in this document for us? It's currently on version -08:
> 
> https://datatracker.ietf.org/doc/html/draft-santesson-svt
> 
> If you're the first to respond, and you believe we can notify the authors/ISE that this review is complete without waiting for the other expert, just let us know. If we don't hear otherwise, we'll wait for replies from both of you.
> 
> If you approve, we'll make this assignment when the ISE asks us and the RFC Editor to process the document.
> 
> Although RFC 7515 calls for a three-week mailing list review, this document is on the IESG telechat agenda for 6/16. Can you respond by Wednesday the 15th?
> 
> The registry is here: https://www.iana.org/assignments/jose
> 
> thanks,
> 
> Amanda Baber
> IANA Operations Manager