IETF Logo Mail Archive

Re: [Acme] Specify which JWS serialization is used

Logan Widick <logan.widick@gmail.com> Sun, 04 March 2018 13:45 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 F251D12711A for <acme@ietfa.amsl.com>; Sun, 4 Mar 2018 05:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 LlCoEUme5tlr for <acme@ietfa.amsl.com>; Sun, 4 Mar 2018 05:45:38 -0800 (PST)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 15B471270AC for <acme@ietf.org>; Sun, 4 Mar 2018 05:45:38 -0800 (PST)
Received: by mail-it0-x230.google.com with SMTP id k79so6932353ita.2 for <acme@ietf.org>; Sun, 04 Mar 2018 05:45:38 -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=twjU3kvyl+KtRD8MtwVNID7YjI/9BTMOQTPPThc3reY=; b=V852IIlVbI+FrURkqMcDVIKH2svarCOlXH8XVrM0exnmPAKS6x90w1y0893WnE9/KL QPxGAL5It0vWMxghcdHsNHFMa+KKl2/38/wtFkzPfAeV6zcPNy2DEBeC6vHWuZmUlh/n T6iX7jch2iXAUoQCNup25lH6xUVR+IkY3+LBGNBrLLsblafUr8MiNPXZF9H+24GVYUgN iWI4qIIyfzRNiCAWkE0SazP0/44EjvgmXzdzsw4JEKFTSG2JSxwo4jqSA1BjZ8WYDTVC t/rurICDRqRAQbfPmyMcItWg32X6nZ9qvkJaXsu3P7LBr+tjGUL4bTZOgLfVgcDGcAWN DE6w==
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=twjU3kvyl+KtRD8MtwVNID7YjI/9BTMOQTPPThc3reY=; b=aiFScGispi7vslohABOu+I141GCm7NLL0BIMwat7SMPtxb7Ng/rVziA4JFInOnLGk/ Tb6ss6X5+02QvpLcuCMp0vZtXL368vF39oLQLymH78vDS5MU/Q0JSev9OjYkT3yW8IyN UVu2bUrqjxjbtd51eX0w11omOoD81VHppq6s00679S0Tm/QS7QZN1UUfQnVd24ZRko9C y8FStpFkJDE+9BZoXkvt7kEyIUQss74KVVSJT4X6sX3BPzP83yF5jcNkL4EYi9WF+qt1 AGuNb2Qtew0xs6P4jIqWp7+X/bRbx/eBRmBo0I79BSjXTt3fi7HzzmHcVmTbP9AT9ZZt iVow==
X-Gm-Message-State: AElRT7E+W/7N/d0TA1Vg7BanlSKPb/7gce+vPo61B+Jmvrw+xP0vnLV4 8QFOVoCMCK3sL+wOs/lMFt3mw37EAr3oamEwG7o=
X-Google-Smtp-Source: AG47ELuAjrsR9EHtMAjeX1H/+dY6hkBiFxTzhqsZr2d4f/eDyXu4bNwogbyiHi1Dhp2bRxVHyyPfqzETlbakFJORL/U=
X-Received: by 10.36.123.65 with SMTP id q62mr10070976itc.120.1520171137207; Sun, 04 Mar 2018 05:45:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.27.77 with HTTP; Sun, 4 Mar 2018 05:45:36 -0800 (PST)
In-Reply-To: <20180304125854.GH2161@carrot.tutnicht.de>
References: <CAMmAzEKSv1pbKC80JLpRQxTrGApc7KVu6A7cqDp-Tmrcq4vvLg@mail.gmail.com> <20180104110204.GP21695@carrot.tutnicht.de> <CAMmAzEKJhMaUBtCWSNZyGv-f+-edZ-WTq3=WFD_b1bXfvua89A@mail.gmail.com> <20180106001126.GB3076@carrot.tutnicht.de> <CAMmAzELgjpAmVCX6YB0VMvNQV3NH3NDdM_pdcz6d+h=ZO2rJww@mail.gmail.com> <CAMmAzEKMffffrxAihotVWPpqy=LaRkpSJuW9CpSVoQfLQ-nBwQ@mail.gmail.com> <CAL02cgRLXkkQECF5ssGh39uFL0xJp-3EODxGSQVzfPuEnE7FgA@mail.gmail.com> <63F4F466-8398-41E6-BD25-5414ADA9D1B3@felipegasper.com> <CAMmAzEKksnuBi0LPHsAsd2qs1brbMqrJBdtsbArTr6HhGrkN+A@mail.gmail.com> <CAL02cgRrH9fG-E9_oc4naSNvE4igaUcs9wXDfTtCTUCx+c4wbg@mail.gmail.com> <20180304125854.GH2161@carrot.tutnicht.de>
From: Logan Widick <logan.widick@gmail.com>
Date: Sun, 04 Mar 2018 07:45:36 -0600
Message-ID: <CAMmAzEJ0A2iOd2ASSHGJRfuB6Ss-BaOCXWsxUKUZx9UUzbT1ng@mail.gmail.com>
To: Jörn Heissler <acme-specs@joern.heissler.de>
Cc: Richard Barnes <rlb@ipv.sx>, Felipe Gasper <felipe@felipegasper.com>, ACME WG <acme@ietf.org>, Fraser Tweedale <frase@frase.id.au>
Content-Type: multipart/alternative; boundary="001a114749d2a192c60566966cb7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/kgefXErLX4SYPSqAgm5stGMdvLE>
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: Sun, 04 Mar 2018 13:45:40 -0000

Good catch. Should it be 415 (Unsupported Media Type) plus which of the
following (or which combination of the following):

   - A new problem document field (tentatively named
   "supportedSerializations": an array of media type strings)?
   - A new directory field (tentatively named "supportedSerializations": an
   array of media type strings)?
      - Should this go in the directory's "meta" object, or in the
      directory object itself?
   - A HTTP header?
   - Something else?

Logan


On Sun, Mar 4, 2018 at 6:58 AM, Jörn Heissler <acme-specs@joern.heissler.de>
wrote:

> On Fri, Mar 02, 2018 at 17:29:04 -0500, Richard Barnes wrote:
> > > On Mar 2, 2018 9:47 AM, "Felipe Gasper" <felipe@felipegasper.com>
> wrote:
> > >
> > > Could there be some way of using a header like “Accept” for a server to
> > > indicate whether it supports jose, jose+json, or both?
> > On Fri, Mar 2, 2018 at 2:29 PM, Logan Widick <logan.widick@gmail.com>
> wrote:
> >
> > > I think the follow-on (#398) includes the Accept header in error
> responses
> > > (to requests with unacceptable serializations).
> > >
> >
> > Indeed it does!
>
> The way I understand https://tools.ietf.org/html/rfc7231#section-6.5.6
> the 406 status and the Accept header are only valid to negotiate
> server-to-client
> content types.
>
> Is it really okay to use them for client-to-server?
> I think code 415 "Unsupported Media Type" is more appropriate:
> https://tools.ietf.org/html/rfc7231#section-6.5.13
> Together with an error document specifying the supported JWS
> serializations.
>
> Cheers
> Joern Heissler
>

v2.23.0 | Report a Bug | By Email