Re: [Anima] Content-Transfer-Encoding and HTTP 1.x in ANIMA BRSKI

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 12 June 2019 22:14 UTC

Return-Path: <mcr+ietf@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 2D99512018C for <anima@ietfa.amsl.com>; Wed, 12 Jun 2019 15:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 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] 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 FR3gSaRQbQKT for <anima@ietfa.amsl.com>; Wed, 12 Jun 2019 15:14:18 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87D84120219 for <anima@ietf.org>; Wed, 12 Jun 2019 15:14:18 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 69ED738183; Wed, 12 Jun 2019 18:12:53 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 6AE601301; Wed, 12 Jun 2019 18:14:17 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 696DA91F; Wed, 12 Jun 2019 18:14:17 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: Julian Reschke <julian.reschke@gmx.de>, anima@ietf.org, ietf-http-wg@w3.org, draft-ietf-pkix-est@ietf.org, Carsten Bormann <cabo@tzi.org>
In-Reply-To: <9fcce3cd-c3cb-bd60-a55c-af21da621b88@gmail.com>
References: <32410.1560275231@localhost> <15839.1560351718@localhost> <8a538f76-787d-de13-97f1-16195daae8ce@gmx.de> <9fcce3cd-c3cb-bd60-a55c-af21da621b88@gmail.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, 12 Jun 2019 18:14:17 -0400
Message-ID: <4930.1560377657@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/XKXvJ3DpkPRn8rL1afsKnZLpur4>
Subject: Re: [Anima] Content-Transfer-Encoding and HTTP 1.x in ANIMA 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: Wed, 12 Jun 2019 22:14:22 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> There is no Content-Transfer-Encoding header field in HTTP. It is simply
    >> not needed.

    > Just as a matter of curiosity, what happened in HTTP1.1 to the fragment in
    > RFC2616 that says (under Content-MD5):

    > "The entity-body for composite
    > types MAY contain many body-parts, each with its own MIME and HTTP
    > headers (including Content-MD5, Content-Transfer-Encoding, and
    > Content-Encoding headers)."

yes, I was going to bring this up next :-)

    > This seems to be a source of confusion, e.g.
    > https://stackoverflow.com/questions/5169434/content-transfer-encoding-in-file-uploading-request
    > . RFC7030 uses a content type of application/pkcs7-mime. So is it
    > allowed to specify a MIME header?

I also found that while googling.

I went through the effort of doing a multipart *reply* in HTTP for
draft-ietf-anima-constrained-voucher, and I really found it hard to determine
what the MIME rules for *HTTP* were...

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