[pkix] [Errata Held for Document Update] RFC7030 (5107)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 19 August 2020 20:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB8A3A0A65; Wed, 19 Aug 2020 13:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level:
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, 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 bMBdZndcH3yI; Wed, 19 Aug 2020 13:00:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D1EA3A0A64; Wed, 19 Aug 2020 13:00:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 31E7AF4078B; Wed, 19 Aug 2020 12:59:42 -0700 (PDT)
To: sean@sn3rd.com, pritikin@cisco.com, peter@akayla.com, dharkins@arubanetworks.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rdd@cert.org, iesg@ietf.org, pkix@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200819195942.31E7AF4078B@rfc-editor.org>
Date: Wed, 19 Aug 2020 12:59:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/Tw6K6OJdZKqt_2tF89Y3BIukV40>
Subject: [pkix] [Errata Held for Document Update] RFC7030 (5107)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2020 20:00:01 -0000

The following errata report has been held for document update 
for RFC7030, "Enrollment over Secure Transport". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5107

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Sean Turner <sean@sn3rd.com>
Date Reported: 2017-09-07
Held by: Roman Danyliw (IESG)

Section: 3.2.1

Original Text
-------------


Corrected Text
--------------
Add the following is as the last paragraph of Section 3.2.1:

  [RFC2616] indicates "HTTP does not use the
  Content-Transfer-Encoding (CTE) field of RFC 2045”; nevertheless, this
  document was published specifying the use of the
  Content-Transfer-Encoding header with a value of ‘base64' in Sections
  4.1.3, 4.3.1, 4.3.2, 4.4.2, 4.5.2, as well as in the examples in
  Appendices A.1-A.4.   As HTTP is binary-clean transport, there is no
  need to indicate this for HTTP-based protocols like EST.  EST server
  implementations SHOULD omit the Content-Transfer-Encoding header if
  they know a priori that EST clients do not rely this field.  EST
  Clients SHOULD expect that the Content-Transfer-Encoding header will
  be absent unless they have an a priori agreement with the EST server.
  The mechanism to establish this client dependency is out-of-scope.

Notes
-----
EST, which is an HTTP-based protocol, erroneous used CTE.  This errata addresses this error.

Note that the text was reviewed by a RAI AD as well as multiple EST implementors.

--------------------------------------
RFC7030 (draft-ietf-pkix-est-09)
--------------------------------------
Title               : Enrollment over Secure Transport
Publication Date    : October 2013
Author(s)           : M. Pritikin, Ed., P. Yee, Ed., D. Harkins, Ed.
Category            : PROPOSED STANDARD
Source              : Public-Key Infrastructure (X.509)
Area                : Security
Stream              : IETF
Verifying Party     : IESG