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

Corey Bonnell <CBonnell@trustwave.com> Tue, 05 June 2018 15:38 UTC

Return-Path: <CBonnell@trustwave.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 751F21310F2 for <trans@ietfa.amsl.com>; Tue, 5 Jun 2018 08:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=trustwave.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 ZWCTuQuyKk_G for <trans@ietfa.amsl.com>; Tue, 5 Jun 2018 08:38:54 -0700 (PDT)
Received: from seg-node-chi-01.trustwave.com (seg-node-chi-01.trustwave.com [204.13.200.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55ECD1310DD for <trans@ietf.org>; Tue, 5 Jun 2018 08:38:54 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (Not Verified[216.32.180.52]) by seg-node-chi-01.trustwave.com with Trustwave SEG (v8, 0, 6, 10791) (using TLS: TLSv1.2, AES256-GCM-SHA384) id <B5b16ae8a0001>; Tue, 05 Jun 2018 10:38:50 -0500
Received: from SN6PR07MB4575.namprd07.prod.outlook.com (52.135.95.19) by SN6PR07MB4813.namprd07.prod.outlook.com (52.135.69.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.15; Tue, 5 Jun 2018 15:38:48 +0000
Received: from SN6PR07MB4575.namprd07.prod.outlook.com ([fe80::7c6f:3d51:c4c3:7295]) by SN6PR07MB4575.namprd07.prod.outlook.com ([fe80::7c6f:3d51:c4c3:7295%4]) with mapi id 15.20.0820.015; Tue, 5 Jun 2018 15:38:48 +0000
From: Corey Bonnell <CBonnell@trustwave.com>
To: "trans@ietf.org" <trans@ietf.org>
Thread-Topic: Error reporting format in draft-ietf-trans-rfc6962-bis
Thread-Index: AQHT/ONMwAiUQSQIGESOwwTrewD1Ng==
Date: Tue, 5 Jun 2018 15:38:48 +0000
Message-ID: <15D07DC0-B9E1-4D76-9F7D-B89856226B9A@trustwave.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=CBonnell@trustwave.com;
x-originating-ip: [71.112.197.127]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN6PR07MB4813; 7:7a5mW9mnGTYqI3qpDOjHqjGLfM7Arvc6Lj8NwIc7W/rhMidoMcUmPFci+h8zptK4XcXltyhWXBcevtlSJcFZEFcKFFlLhWcix8JJjHJWOc0TvqPATG7XDZVV/5qpyW/JYqgdwBdPbUWDOUI/qPSGtBRIamnCQDxaPnfiUkVwCyBwIOV6s6CYnOQp6DeT1z2z2FOUX8049GQuEZqfM96/EkqAmamZvhfITs9cy+aPbxmBuYhUt8VWaR1VozJ0i/2P
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:SN6PR07MB4813;
x-ms-traffictypediagnostic: SN6PR07MB4813:
x-microsoft-antispam-prvs: <SN6PR07MB48138336EAFEED67F4AC6AE0CF660@SN6PR07MB4813.namprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(192374486261705)(171964332516350)(21748063052155)(211171220733660);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(3231254)(944501410)(52105095)(10201501046)(93006095)(93001095)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:SN6PR07MB4813; BCL:0; PCL:0; RULEID:; SRVR:SN6PR07MB4813;
x-forefront-prvs: 0694C54398
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(396003)(346002)(366004)(39380400002)(39860400002)(199004)(189003)(8936002)(6116002)(68736007)(2616005)(5660300001)(36756003)(2351001)(25786009)(3846002)(236005)(478600001)(316002)(53936002)(2906002)(476003)(82746002)(54896002)(6512007)(3280700002)(9326002)(99286004)(3660700001)(6506007)(86362001)(2900100001)(186003)(26005)(102836004)(72206003)(486006)(1730700003)(5250100002)(83716003)(606006)(105586002)(33656002)(6486002)(6306002)(81166006)(8676002)(81156014)(59450400001)(7736002)(106356001)(80792005)(97736004)(6436002)(2501003)(14454004)(6916009)(66066001)(5640700003); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR07MB4813; H:SN6PR07MB4575.namprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: trustwave.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: SnfYhxgprNdfLABR4QrCH2skA6QCqoF6Kvt0C/RgbGWRWCxqlXisAp/YJMVocwbqykjwlklHjjyul9g7tH366+jJS4iePZ+CMjCTPBHKA6sKfKKU9Fp5viG5ASMnKPs3S+Db/8S6xQdw/YZod9srlQWqZXrpUxXabYUwEnr0zIIx02lax4DA3BwchEfLfM0L
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_15D07DC0B9E14D769F7DB89856226B9Atrustwavecom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 6f604fbd-8ff6-4bf0-45df-08d5cafa6ea4
X-OriginatorOrg: trustwave.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6f604fbd-8ff6-4bf0-45df-08d5cafa6ea4
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2018 15:38:48.9375 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cb1dab68-a067-4b6b-ae7e-c012e8c33f6a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR07MB4813
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=trustwave.com; s=080318_segcloud; t=1528213131; bh=JjTeVzetJvRaMwbptIZdd2CpTDTugppuBBvXkVNKXoI=; h=From:To:Subject:Thread-Topic:Thread-Index:Date:Message-ID: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:authentication-results:x-originating-ip: x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-microsoft-antispam: x-ms-traffictypediagnostic:x-microsoft-antispam-prvs: x-exchange-antispam-report-test:x-ms-exchange-senderadcheck: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf: x-microsoft-antispam-message-info:spamdiagnosticoutput: spamdiagnosticmetadata:Content-Type:MIME-Version: X-MS-Office365-Filtering-Correlation-Id:X-OriginatorOrg: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id: X-MS-Exchange-Transport-CrossTenantHeadersStamped; b=pvR/vqXHAOu21AxbNyXExf4Dqt1BmVEBCrX0H1yNXJLMkSYQhJkOZ/89Cy+lc/miZ uhwP2XDKC0qGPUGWWVD2jy3BgSAqmaijpfte+SdVOSBpQVeaIwDWwqlPl72KLiy/xy cWGBTkmfy2WJ7xvMCEFxvVzLWzaCr7xkoOOiWmJyJkPLFPciF0WOiRNWcjypO58rv8 IOxipgGo6vSvHqif0jprjJhdC/LKlxsLOzhxzjFvge3bXns6nzMlLYHFJf/bW+Zozu ZNuDq/qROlq3Wrq7ng1K3P9w9fRxG8V/flnRjZsBomgF32k5gtOcxNbN8vW6NssDg3 PQ98Jwt7VaOfQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/WGxqqYsfiYVt22m0stoQXOl5h3g>
Subject: [Trans] Error reporting format in draft-ietf-trans-rfc6962-bis
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 05 Jun 2018 15:38:58 -0000

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<http://www.trustwave.com/>