IETF Logo Mail Archive

Re: [Acme] Specify which JWS serialization is used

Logan Widick <logan.widick@gmail.com> Wed, 03 January 2018 23:30 UTC

Return-Path: <logan.widick@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 F264F12D7E6 for <acme@ietfa.amsl.com>; Wed, 3 Jan 2018 15:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 hRsThLyDIqkQ for <acme@ietfa.amsl.com>; Wed, 3 Jan 2018 15:30:41 -0800 (PST)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 EF0D812D7E4 for <acme@ietf.org>; Wed, 3 Jan 2018 15:30:40 -0800 (PST)
Received: by mail-it0-x22f.google.com with SMTP id z6so375095iti.4 for <acme@ietf.org>; Wed, 03 Jan 2018 15:30:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v6Irzv/YQr43J0OWyA/U5aa4O4+zveGcQ+JwPQh+JgA=; b=GIz6xXhySa72u2BBIxeqX+Lblw+CwdBsOcn94zzjhc632zALwHUmwCiuUBZMqY8N47 8mPc0P4avPplHqHlCVDNx8533sf1e974TZYNkbhzy2Ea2dgEbrW/Z1kqYZrkagazJPQW 9hWQ/r9XzZeJE1dt3mMlWj4kCAhn1/tt+9nXl9jvw44uiHnPiT4EBGVV92WVPdvKAou0 XZT2+EVk7h1BO8xkznDilfqWZEmSuUsBU1CGfYI/Eyp/J6r/q+EyMeNDwQ0sKPwPIRq6 Zb2OeIVx8VU8kPl4nWlC3DpTWTZZnEk2pfRvEckkrVHnF7LiOAyOWgF3YWzNyWqgsS1z 7ehA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=v6Irzv/YQr43J0OWyA/U5aa4O4+zveGcQ+JwPQh+JgA=; b=aWR3HKVaa5yUMRr4XGmvK9jkNl0aCIQOi/Wj/kk5MRbbWBmb9XnUoaRad3VJuPvigY m2TOuMPzuH5JmPOf7TLaZ8CGukSp8nSzblkxixoYfTbezP0regdBDXBHjDNO6zrQ3uPc 7vQw/qJqg61AJQ063JVXuWN1kiC1x5oSSQi7WqoA2MZqph58dvFc9uddT+hwAtflaMp0 N+QSGUK5mldKw5thAH7U6l7g7SMdYROYH9SIK+0x/d4vB2/jbBbfqKKpDclatB9FGgHb ks3dycEfyIwDy++F/HoKrdnDq5Dhbqnqz7WR9c5MG2b6XyOmYmghJ/jtAYzWclvWljl4 kmbg==
X-Gm-Message-State: AKGB3mLi02GFX2hKg2xnW8nH0Zk132KRo5SdiRf2tJL3NsZ4qUlbmy0s uqKXKr6irEZPQIiOS7cWmqgNiEQAwqCAyqsuEbH05w==
X-Google-Smtp-Source: ACJfBovTjrRcXxFG2JgS5IwDgn8LNxZHCYf7fBMoPmNrKqwMCRnb9NgNp/3/k6yD49bOPo5kt96lRCEvD1+U45J6qaA=
X-Received: by 10.36.172.14 with SMTP id s14mr3737348ite.142.1515022240203; Wed, 03 Jan 2018 15:30:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.152.59 with HTTP; Wed, 3 Jan 2018 15:30:39 -0800 (PST)
In-Reply-To: <20180103230734.GM21695@carrot.tutnicht.de>
References: <20180103230734.GM21695@carrot.tutnicht.de>
From: Logan Widick <logan.widick@gmail.com>
Date: Wed, 03 Jan 2018 17:30:39 -0600
Message-ID: <CAMmAzEKGUcyJRuZHmbMWpODwAhaMX8vVH8S_dJrXP_sEjaoXJg@mail.gmail.com>
To: Jörn Heissler <acme-specs@joern.heissler.de>
Cc: ACME WG <acme@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1fc9787448980561e79ac8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/FjKhGrwN_NhZ2Qv-BhGapj8yB5c>
Subject: Re: [Acme] Specify which JWS serialization is used
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 03 Jan 2018 23:30:43 -0000

I agree that a serialization format (or set of formats) would need to be
standardized. Related thread:
https://www.ietf.org/mail-archive/web/acme/current/msg01690.html

Sincerely,

Logan Widick

On Wed, Jan 3, 2018 at 5:07 PM, Jörn Heissler <acme-specs@joern.heissler.de>
wrote:

> Hello and happy new Year!
>
> I've found an inaccuracy in the ACME specs.
>
> https://tools.ietf.org/html/rfc7515#section-7 states:
>
>     Applications using this specification need to specify what
> serialization
>     and serialization features are used for that application.
>
> Although this is neither a "SHOULD" nor a "MUST", I think ACME should
> specify
> which serialization formats need to be supported by server implementations.
>
> RFC7515 defines four serialization formats:
>
> * JWS Compact Serialization
> * General JWS JSON Serialization Syntax
>   * One signature only
>   * Multiple signatures
> * Flattened JWS JSON Serialization Syntax
>
> https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.
> html#rfc.section.6.2
> states:
>
>     In the examples below, JWS objects are shown in the JSON or
>     flattened JSON serialization
>
> All examples in the ACME specification use only the flattened
> serialization.
> Depending on the clarification above, this might need to be amended too.
>
> Best regards
> Jörn Heissler
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>
>

v2.23.0 | Report a Bug | By Email