IETF Logo Mail Archive

Re: [Trans] Error reporting format in draft-ietf-trans-rfc6962-bis

Eran Messeri <eranm@google.com> Fri, 24 August 2018 12:12 UTC

Return-Path: <eranm@google.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 556A6130E8C for <trans@ietfa.amsl.com>; Fri, 24 Aug 2018 05:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level:
X-Spam-Status: No, score=-17.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 PnjB5GG92rS1 for <trans@ietfa.amsl.com>; Fri, 24 Aug 2018 05:12:26 -0700 (PDT)
Received: from mail-yw1-xc32.google.com (mail-yw1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (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 D41D1130E6C for <trans@ietf.org>; Fri, 24 Aug 2018 05:12:25 -0700 (PDT)
Received: by mail-yw1-xc32.google.com with SMTP id m62-v6so1494057ywd.6 for <trans@ietf.org>; Fri, 24 Aug 2018 05:12:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tISN9H6sfARwctCWoov/nSYtzJEhfSYu+K6hB/pQj9s=; b=sLboOKR83j3GY3xi/OZ/RoO0F0Zrt1ZhtSiiIwxsotA68eweiHD6uNCw6Vi84nPgHe vL9GHUSW8x3ln8DF+1KjlglN/B+cf/Ko8VU+apD5ugqVhL29iNR1hKdk+W0H/0/ELU/3 kejg5+JvaBREkXE0zXkJwojR2Q3SQ4Qu6yvTis76wWe2sAsdUw6G4wPmPAWAYTGNDMFF Kl/7+Ec0L3623089BjHuqw2v+a28L8dbfP+kJN+RjxTTSfjOEck121qpU2uF3xrQODfb Ynxa3PcYTgSXKoHsjGGBFgqpagkuObAalCACPZ6y39mdk4cvmtkknVTsYniVEmKgqEqs T1YA==
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=tISN9H6sfARwctCWoov/nSYtzJEhfSYu+K6hB/pQj9s=; b=TUzrx/0IvkihM+wq0dnENWS/xrU5CVLXPcEd5aGHXQiHyeWAW28Zg30GcKCHC1R1/R 0UQooo/x5jGk6uAKlg5meIHliYOuJJdOd3qf9yYGhpP5RzlN4/Q4vlRKzaDQX6NaFrmX u5sLcVMmK6T8w2s0gsVYqs4IsI6fTwLmKQQH9X8pAhxOzaAgu50/7K9Dw9eJ0m6jzEwk GzcyrUlTOjCwmIMjd4udvcQznKFfrkmy+f16ClKKKWFC9T1Bao3OUfRbB57cKxjuN8GU aqggK8FT2DsF1bEAgtQ5PKrwj/GON613YpchBm+kLpNmL9PM2H+YQkPnYSMYi2+9HSJV DzrQ==
X-Gm-Message-State: APzg51BGqQ1ymK79fyCYKrJJHtrQZwh8r/+uk+zPGDUe3BcMm2TL9bR5 XVG0j1PHRmEHNsXuYaqq3Yzb2yZE0T/xHtsajJxbFw==
X-Google-Smtp-Source: ANB0VdYYNNZZdkne8kS7piTvx6YEKZ36RZIL0fZaUncxe7cqAf/KP9xv+tlkEVipQeSFT63JABKKlj0DONwkcb6wSRU=
X-Received: by 2002:a0d:cd43:: with SMTP id p64-v6mr791673ywd.12.1535112744527; Fri, 24 Aug 2018 05:12:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:4981:0:0:0:0:0 with HTTP; Fri, 24 Aug 2018 05:11:53 -0700 (PDT)
In-Reply-To: <15D07DC0-B9E1-4D76-9F7D-B89856226B9A@trustwave.com>
References: <15D07DC0-B9E1-4D76-9F7D-B89856226B9A@trustwave.com>
From: Eran Messeri <eranm@google.com>
Date: Fri, 24 Aug 2018 13:11:53 +0100
Message-ID: <CALzYgEcBufV87cp6AP0CUhqm5mg4a0KmBFZvTcjn7nRfPvnzuA@mail.gmail.com>
To: Corey Bonnell <CBonnell@trustwave.com>
Cc: "trans@ietf.org" <trans@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d4802205742d492c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/8arURu-oOnYkAWVxAEFyzfeeWsg>
Subject: Re: [Trans] Error reporting format in draft-ietf-trans-rfc6962-bis
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2018 12:12:28 -0000

I've proposed text to that effect in:
https://github.com/google/certificate-transparency-rfcs/pull/300

Eran

On Tue, Jun 5, 2018 at 4:38 PM, Corey Bonnell <CBonnell@trustwave.com>
wrote:

> Hello,
>
> Apologies if this was previously discussed (I searched the TRANS mail
> archives and didn’t find anything relevant), but section 5 of
> draft-ietf-trans-rfc6962-bis-28 (https://tools.ietf.org/html/
> draft-ietf-trans-rfc6962-bis-28#section-5) describes the preferred error
> reporting format as a JSON object with “error_code” and “error_message”
> fields. Instead of using this bespoke error reporting format, I was
> thinking that using the JSON Problem Details format (
> https://tools.ietf.org/html/rfc7807) would be appropriate here.
>
>
>
> Using the RFC 7807 format provides (at least) two advantages over the
> currently specified format, namely:
>
>    - The use of a standard format, which is already being used in other
>    standards (such as ACME)
>    - The possibility to include additional metadata for error conditions,
>    which may transmit sufficient machine-readable information to allow for CT
>    clients to automatically recover from errors
>
>
>
> Thanks,
>
>
>
> *Corey Bonnell*
>
> Senior Software Engineer
>
>
>
> *Trustwave* | SMART SECURITY ON DEMAND
> www.trustwave.com
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>
>

v2.23.0 | Report a Bug | By Email