IETF Logo Mail Archive

Re: [Acme] Barry Leiba's Discuss on draft-ietf-acme-email-smime-10: (with DISCUSS and COMMENT)

Barry Leiba <barryleiba@computer.org> Thu, 12 November 2020 17:51 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3BC3A1458; Thu, 12 Nov 2020 09:51:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 buGVWuYTlrGG; Thu, 12 Nov 2020 09:51:37 -0800 (PST)
Received: from mail-vs1-f53.google.com (mail-vs1-f53.google.com [209.85.217.53]) (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 135A33A1520; Thu, 12 Nov 2020 09:51:30 -0800 (PST)
Received: by mail-vs1-f53.google.com with SMTP id u7so3715101vsq.11; Thu, 12 Nov 2020 09:51:30 -0800 (PST)
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:content-transfer-encoding; bh=4pigvMjkcACeJYdXxwjVZrMmRneOoVSEiNRKDI218A8=; b=Q2kc58gnc5DboGNqpXLFM/0wnUrhTuwEDB/OCRXvke7MwOvb+jHhjkXF7os41Nr4V2 vU4mxRhBrhnUeL6Id6KqTXeXh4wzR2IJVfQEFBKr9z423+BpLJXGZJe9lmMziO28sD3U m4UNWjEBZpOu5cmW3ZU2w152zUCJX5X1tPGbLIsJMiyyLbSA2RjuZySXN79RZIkhCL/a 4t7M94QAPiOtip0uL2cSKmEWEFfwfdkzvSCwo0c9BHm3pDSzBk+SojkplfXYtBeqQ3ux gExUKAZaR0ePvB+WBetsn4lhPCZE2Is/eNk0l/nfsQd1BOwQz5AS/wChJYvefjF26oer B+KQ==
X-Gm-Message-State: AOAM530hk6dHDUQj3vGLTlCZkzDg/wUvVRcdIH+KHVKjrsCpEldR+UkY 7ExvF7s+78dbortdev+1JiaZdnDukPeb++T83xA=
X-Google-Smtp-Source: ABdhPJyprv6PKK/6ENeyZhapdlB26tMu7tJ9RBGDM4U1ru7QuyhCyH4OTMZoWye2NO7vBerHnloV2TEuSAfDR0sMRvk=
X-Received: by 2002:a05:6102:10d0:: with SMTP id t16mr539459vsr.9.1605203488817; Thu, 12 Nov 2020 09:51:28 -0800 (PST)
MIME-Version: 1.0
References: <160390414669.4316.7078245483813646358@ietfa.amsl.com> <9d1f51f3-838c-cf5b-c05b-5a1e53ace5d7@isode.com> <CALaySJL_rB_-ZktZtUHn+9k_czkrhrXh7AXoBuL7h+FwAiV4OQ@mail.gmail.com> <565e6077-ece3-0726-8858-4ee10cf01bd0@isode.com> <7853353c-f50e-7e02-953e-9e2b4dd3b334@isode.com>
In-Reply-To: <7853353c-f50e-7e02-953e-9e2b4dd3b334@isode.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 12 Nov 2020 12:51:17 -0500
Message-ID: <CALaySJ+0_g5gsjJQFWA4MDAKhbe6otvGe1sSpXNixd=CTc9fhA@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: The IESG <iesg@ietf.org>, "Salz, Rich" <rsalz@akamai.com>, acme@ietf.org, acme-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/3XlfDp4qRJNc4L1McCmJbl-uXp4>
Subject: Re: [Acme] Barry Leiba's Discuss on draft-ietf-acme-email-smime-10: (with DISCUSS and COMMENT)
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2020 17:51:39 -0000

Thanks, Alexey.  I'll wait to see the text changes about DMARC & SPF,
and then update my ballot.  Thanks again for addressing things!

Barry

On Thu, Nov 12, 2020 at 11:30 AM Alexey Melnikov
<alexey.melnikov@isode.com> wrote:
>
> Hi Barry,
>
> On 05/11/2020 11:03, Alexey Melnikov wrote:
> > Hi Barry,
> >
> > On 29/10/2020 21:33, Barry Leiba wrote:
>    [snip]
> >>>> The example body contains a “.”, which is not a valid base64url
> >>>> character.
> >>> It is JWS, which contains a dot.
> >> I'm confused, then.  The text says that it's "one or more line
> >> containing the base64url-encoded SHA-256 digest [FIPS180-4] of the key
> >> authorization".
> >>
> >> How can that contain a dot?  The key authorization might, but then you
> >> make a digest of it and encode the digest, and that encoded blob can't
> >> contain a dot, right?  What am I missing (just hit me over the head;
> >> it's OK).
> > I will come back to you on this.
>
> Yes, you are right and I am wrong. I will fix.
>
> Best Regards,
>
> Alexey
>
>

v2.23.0 | Report a Bug | By Email