IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Thu, 13 June 2019 06:28 UTC

Return-Path: <cabo@tzi.org>
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 56CDD120088 for <anima@ietfa.amsl.com>; Wed, 12 Jun 2019 23:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 cuGkWA3Nx_Wr for <anima@ietfa.amsl.com>; Wed, 12 Jun 2019 23:28:01 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88EC2120199 for <anima@ietf.org>; Wed, 12 Jun 2019 23:27:58 -0700 (PDT)
Received: from client-0045.vpn.uni-bremen.de (client-0045.vpn.uni-bremen.de [134.102.107.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 45PYhD1SrszyYc; Thu, 13 Jun 2019 08:27:56 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8a538f76-787d-de13-97f1-16195daae8ce@gmx.de>
Date: Thu, 13 Jun 2019 08:27:55 +0200
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, anima@ietf.org, ietf-http-wg@w3.org, draft-ietf-pkix-est@ietf.org
X-Mao-Original-Outgoing-Id: 582100073.5914871-5bce2e092151ac0bd5a2ea4fb65730f6
Content-Transfer-Encoding: quoted-printable
Message-Id: <F896BCBC-6C32-4107-B4B5-C12617F81326@tzi.org>
References: <32410.1560275231@localhost> <15839.1560351718@localhost> <8a538f76-787d-de13-97f1-16195daae8ce@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/sfev_MdLg-cgZTVFxE8jl3SQCIo>
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: Thu, 13 Jun 2019 06:28:03 -0000

On Jun 12, 2019, at 19:26, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
>> 2) Assuming the answer to (1) is no, what should we make of RFC7030
>>    that says to use it, and to base64 binary objects?
> 
> Raise an erratum :-).

Not sure about the smiley here.  This is an erratum.
Now how to resolve this depends on what option causes the smallest damage.

RFC 7030 is supposed to be a widely deployed protocol, so it should not be hard to find out what people out there are actually doing.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email