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

Roman Shpount <roman@telurix.com> Mon, 19 April 2021 22:06 UTC

Return-Path: <roman@telurix.com>
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 D73A93A463A for <stir@ietfa.amsl.com>; Mon, 19 Apr 2021 15:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=telurix-com.20150623.gappssmtp.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 SHu0ow7cURKG for <stir@ietfa.amsl.com>; Mon, 19 Apr 2021 15:06:34 -0700 (PDT)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 18C4B3A4639 for <stir@ietf.org>; Mon, 19 Apr 2021 15:06:33 -0700 (PDT)
Received: by mail-qv1-xf2a.google.com with SMTP id h15so7875965qvu.4 for <stir@ietf.org>; Mon, 19 Apr 2021 15:06:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3MBfcoFTPDrEN4scE3yskJ9UQh2/jeWGKw0cCGb5wxU=; b=XjeSn0wqPhbtyLjpj2UnFaggqz1NSAau2FvUmF5VlYNaHK8tIXeboAbSgxZ/Z0xj3K 4VcdUkT2oPE/VbSAu1AmLeVcy5iVeRvdmDxKmuDwJKmhSfGMZasnVK2bc6+axqJp+XyJ R05obTdyHXYcf/+yDxex5QGEYy91Q4OPYM6vq/HACfpJX+zmYiMTmupUQvUs6oq4es7W tMuTFb2KOJ+KnbgJL2Ein9WEDO+iAm4FVxCqjqsnjeflJ3uJX278/TDXBna8e+TQzoXJ nQMIOGfyUBw2qHGoEO9cEpToR6kJXx6WY5BzVlpEMx1TUb/3vcWU+4EOEuu/ea+0eW4w CB9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3MBfcoFTPDrEN4scE3yskJ9UQh2/jeWGKw0cCGb5wxU=; b=N+0jhd1Wio13xJjhBTEnGJXrdYhUY6euVMp7PtjutEzXl6j+IAEiaJ8zfOw01QVmIc vYLJT4u4VeLwsAVToxF8jkymHy7dAawovJUnLqi+a2E9diteE5B8tOEmT/FcH1Bx95tv wPzXMAzDRkvlOATWcK+KsuH/VhBZ7xK+mcAcp1+0LfTNLVDgKhse445TLM+sTUlnP4mi v8+P6bgUZydCvnQctWzcp3NceceXUCWnEZUJeviTWPFzHyeUNUn5C4wQC2mD0EwiaF30 m9i6Vk40kHM9JKJjl5QN2FC6AVR1hx6kVIM9yRb3yZ0av5nRmpU2qoDVseh9IzvdM5b8 J3UQ==
X-Gm-Message-State: AOAM532hHgw3tci2TY47ZfkW585FD13KzgfXJogJdn8IyIJme9+K0ULf aURXfd6jwhmffWa19Uer5RfSpanMDQ52/w==
X-Google-Smtp-Source: ABdhPJxQ7CCbr2FPwv+CCelLq8FrmjxOeriue3WOw5tIXjA9oGaOSxs/9hDL+rUWNgpL3+00fdAzmg==
X-Received: by 2002:ad4:49ac:: with SMTP id u12mr23965281qvx.22.1618869992116; Mon, 19 Apr 2021 15:06:32 -0700 (PDT)
Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com. [209.85.219.176]) by smtp.gmail.com with ESMTPSA id u9sm10541108qtf.76.2021.04.19.15.06.30 for <stir@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 19 Apr 2021 15:06:31 -0700 (PDT)
Received: by mail-yb1-f176.google.com with SMTP id g38so40606294ybi.12 for <stir@ietf.org>; Mon, 19 Apr 2021 15:06:30 -0700 (PDT)
X-Received: by 2002:a25:6c8a:: with SMTP id h132mr20410787ybc.454.1618869990483; Mon, 19 Apr 2021 15:06:30 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <167dde10-f242-2b6f-a7ce-96991158589a@petit-huguenin.org>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 19 Apr 2021 18:06:18 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvkN+BSY0XuBmfApDDWOLhqCLLFuQgVQryE+yHUftWs4w@mail.gmail.com>
Message-ID: <CAD5OKxvkN+BSY0XuBmfApDDWOLhqCLLFuQgVQryE+yHUftWs4w@mail.gmail.com>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
Cc: Russ Housley <housley@vigilsec.com>, IETF STIR Mail List <stir@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="000000000000b86caa05c05a8a6a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/jOKJN1NBATsTx3MIunQ6kp65LkA>
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: Mon, 19 Apr 2021 22:06:39 -0000

On Mon, Apr 19, 2021 at 3:26 PM Marc Petit-Huguenin <marc@petit-huguenin.org>
wrote:

>
> > SWS allows CRLF.  Is that allowed in a claim?
>
> No, but that's why I said 'a quoted value whose unquoted part is
> equivalent to the token in the "ppt" parameter'.  All these are the same
> claim ('\' used to wrap)
>
> ppt=test
> ppt=TeST
> ppt="test"
> ppt="TeST"
> ppt = test
> ppt = "test"
> ppt \
>    = \
>      "teSt"
>
> These are different claims than above:
>
> ppt=" test"
> ppt="test "
> ppt="test
> ppt=test"
> ppt = "\
>    test"
> ppt = "test\
>   "
>
> > If so, I thought that LDQUOT is defined as SWS DQUOTE, and RDQUOT is
> defined as DQUOTE SWS.
> >
> > If we are going to take this approach, we need to allow white space
> before EQUAL, and we also need it for the unquoted token.
>
> EQUAL is SWS "=" SWS, so no need.
>

If we define ident-type = "ppt" EQUAL ( token / ( LDQUOT token RDQUOT ) )
then
ppt=" test"
ppt="test "
ppt="test
ppt=test"
ppt = "\
   test"
ppt = "test\
  "
are all invalid. A token cannot contain a space. Both quotes are required
if either is present.

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.

Best Regards,
_____________
Roman Shpount