Re: [Anima] addressing Content-Type-Encoding errata on EST / RFC7030 --- relationship to BRSKI

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 22 July 2019 02:51 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105DB120096 for <anima@ietfa.amsl.com>; Sun, 21 Jul 2019 19:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 3UBkQRS2WXbE for <anima@ietfa.amsl.com>; Sun, 21 Jul 2019 19:51:37 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D60F1120033 for <anima@ietf.org>; Sun, 21 Jul 2019 19:51:36 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:1232:144:6e88:14ff:fe34:93bc]) by relay.sandelman.ca (Postfix) with ESMTPS id BDDEA1F44B; Mon, 22 Jul 2019 02:51:34 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id D9C332025; Sun, 21 Jul 2019 22:51:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: anima@ietf.org
In-reply-to: <37592AA0-87AB-4036-93A9-B60F56539F53@tzi.org>
References: <6535.1560786935@dooku.sandelman.ca> <20190710145907.ypo57aacomi73bdx@faui48f.informatik.uni-erlangen.de> <17732.1563383448@localhost> <37592AA0-87AB-4036-93A9-B60F56539F53@tzi.org>
Comments: In-reply-to Carsten Bormann <cabo@tzi.org> message dated "Wed, 17 Jul 2019 23:55:16 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 21 Jul 2019 22:51:54 -0400
Message-ID: <12491.1563763914@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/HuA5i8JlK2GftNqRxOVuVY138zY>
Subject: Re: [Anima] addressing Content-Type-Encoding errata on EST / RFC7030 --- relationship to BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2019 02:51:39 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > On Jul 17, 2019, at 19:10, Michael Richardson <mcr+ietf@sandelman.ca>
    > wrote:
    >> 
    >> always base64 the payloads

    > Which means that the content-type headers lie.  Backwards
    > combyativbility [actual autocorrect result :-)] can be nasty.  But
    > sniffing this out should be easy.

You are saying that the Content-Type: application/pkcs* claims are
incorrect, because the payloads have been base64 encoded.
This would be quite normal had these payloads been carried in email
(which does happen) but then there would have been a useful CTE header to
clarify the encoding.

I agree that it's definitely inconsistent, and this is why I think it's not
enough for it to just remain as errata.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [