Re: [stir] Proposal for update of erratum #6519

Marc Petit-Huguenin <marc@petit-huguenin.org> Tue, 20 April 2021 21:25 UTC

Return-Path: <marc@petit-huguenin.org>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20CC03A1C62 for <stir@ietfa.amsl.com>; Tue, 20 Apr 2021 14:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 1NjeRjFU1aRU for <stir@ietfa.amsl.com>; Tue, 20 Apr 2021 14:25:15 -0700 (PDT)
Received: from implementers.org (implementers.org [92.243.22.217]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 744213A1C5B for <stir@ietf.org>; Tue, 20 Apr 2021 14:25:15 -0700 (PDT)
Received: from [IPv6:2601:648:8400:8e7d:d250:99ff:fedf:93cd] (unknown [IPv6:2601:648:8400:8e7d:d250:99ff:fedf:93cd]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 40BD5AE255; Tue, 20 Apr 2021 23:25:11 +0200 (CEST)
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: Roman Shpount <roman@telurix.com>
Cc: Russ Housley <housley@vigilsec.com>, IETF STIR Mail List <stir@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <42e964d3-2a16-660b-f8b4-fd9daedad115@petit-huguenin.org> <AM0PR07MB38604255784FF9E621257B2D93499@AM0PR07MB3860.eurprd07.prod.outlook.com> <3d8e2fce-d124-99b9-e295-734a36ad564a@petit-huguenin.org> <7558AA11-A7F9-4091-BFD3-F42C742AABAE@vigilsec.com> <167dde10-f242-2b6f-a7ce-96991158589a@petit-huguenin.org> <CAD5OKxvkN+BSY0XuBmfApDDWOLhqCLLFuQgVQryE+yHUftWs4w@mail.gmail.com> <15fc4a20-b5c8-cd27-b30e-76e1f479b4ff@petit-huguenin.org> <CAD5OKxvmvmotpxB8BGJfqRrVTjEGKQkQRow37gmwRMFaBGjEoA@mail.gmail.com>
Message-ID: <57c1d751-795b-8ab2-9c00-7bcdcc90f3b9@petit-huguenin.org>
Date: Tue, 20 Apr 2021 14:25:09 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxvmvmotpxB8BGJfqRrVTjEGKQkQRow37gmwRMFaBGjEoA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/MUGMBYw1e9tT6sjntATbVmKmmM0>
Subject: Re: [stir] Proposal for update of erratum #6519
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2021 21:25:20 -0000

On 4/19/21 6:57 PM, Roman Shpount wrote:
> On Mon, Apr 19, 2021 at 7:56 PM Marc Petit-Huguenin <marc@petit-huguenin.org>
> wrote:
> 
>> A literalist.  Fantastic.
>>
> 
> I did not know we are supposed to judge this errata on artistic merits.
> 
> Now, can we go back to fix that text ?
>>
> 
> This is exactly what I am doing.
> 
> My understanding was that grammar was defined as ident-type = "ppt" EQUAL (
> token / ( LDQUOT token RDQUOT ) ) explicitly to avoid these sorts of
> issues. I agree with your note that the new syntax does not allow for
> spaces immediately before or immediately after the token when quoted and I
> think it should be present in the errata. I also think that we should add a
> note that even though the ppt value is case insensitive, a normalized
> version as defined in
> https://www.iana.org/assignments/passport/passport.xhtml (or all lower case
> version) should be used when constructing a JWT header.

Good point.

> 
> 
>>>
>>> Also, I thought the group decision was endpoints MUST accept ppt value
>> as a
>>> token with or without quotes. Endpoints MUST send a token in quotes. I
>> have
>>> explicitly asked if the group wanted SHOULD in either place, and the
>>> preference was for the MUST level requirements. I think the errata should
>>> say this unless there is a good reason to change it.
>>
>> That was not my understanding.
>>
> 
> We can go back to the recording to check on the decision.
> 
> More importantly, what is the normative strength of "be tolerant to the
> absence of quotes when receiving"? Is this MUST accept quotes? SHOULD
> accept quotes?
> 
> In the sentence "Implementations SHOULD use quotes around the token when
> sending", what would be the valid use cases when implementations are
> allowed not to use quotes?
> 
> My understanding is that SHOULD implies well know exceptions.
> 
> Best Regards,
> _____________
> Roman Shpount
> 


-- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug