[Secdispatch] addressing Content-Type-Encoding errata on EST / RFC7030

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 19 June 2019 13:38 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9C5D41204AD for <secdispatch@ietfa.amsl.com>; Wed, 19 Jun 2019 06:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id hqBsyI1ZNeK8 for <secdispatch@ietfa.amsl.com>; Wed, 19 Jun 2019 06:38:37 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C4751204AA for <secdispatch@ietf.org>; Wed, 19 Jun 2019 06:38:36 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca []) by tuna.sandelman.ca (Postfix) with ESMTP id 3892F380BE for <secdispatch@ietf.org>; Wed, 19 Jun 2019 09:37:01 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 9D7E4E9E; Wed, 19 Jun 2019 09:38:34 -0400 (EDT)
Received: from sandelman.ca (localhost []) by sandelman.ca (Postfix) with ESMTP id 9AFC0E47 for <secdispatch@ietf.org>; Wed, 19 Jun 2019 09:38:34 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: secdispatch@ietf.org
In-Reply-To: <040a01d5263c$6c51efa0$44f5cee0$@augustcellars.com>
References: <6535.1560786935@dooku.sandelman.ca> <10505.1560789112@dooku.sandelman.ca> <12718.1560790704@dooku.sandelman.ca> <040a01d5263c$6c51efa0$44f5cee0$@augustcellars.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 19 Jun 2019 09:38:34 -0400
Message-ID: <16160.1560951514@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/plIOeAt8FKl0Csd33THkuMh4-zY>
Subject: [Secdispatch] addressing Content-Type-Encoding errata on EST / RFC7030
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 13:38:39 -0000

Dear secdispatch Chairs,

I have written draft-richardson-lamps-rfc7030est-clarify-02 to deal with
the errata:

it turns out that deployed code prevents us from having a signal that
would let us remove the needless base64 encoding, but at least we can
remove the deprecated CTE header which was not being used anyway.

I believe that we can deal with:

in this document as well, although I haven't yet done that.  The result would
be a standards track document that Updates RFC7030.

As an aside, I think that the errata needs to move from reported to accepted.

Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-