IETF Logo Mail Archive

Re: [media-types] Review of message/bhttp

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 20 June 2022 11:03 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC318C157B5E for <media-types@ietfa.amsl.com>; Mon, 20 Jun 2022 04:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.319
X-Spam-Level:
X-Spam-Status: No, score=-3.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cD94jb9z5D-b for <media-types@ietfa.amsl.com>; Mon, 20 Jun 2022 04:02:59 -0700 (PDT)
Received: from pechora3.dc.icann.org (pechora3.icann.org [192.0.46.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E61DC157B4D for <media-types@ietf.org>; Mon, 20 Jun 2022 04:02:59 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by pechora3.dc.icann.org (Postfix) with ESMTP id ECC28700060C for <media-types@iana.org>; Mon, 20 Jun 2022 11:02:57 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1655722957; d=isode.com; s=june2016; i=@isode.com; bh=/m0RoQqKURG9xWfoUHpwFIRWpgICJ1OrCBcXd+pp978=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=pGs9S4VxFJytP61eSH/YlWnfYgIUFMDeNVc/lBllfugWo/Mzvt5fcbeGfzf4xxQ6XtOeJ2 2a62YNt2o9BbXGTjvnChJF5YBG9H0vNkwJ0JIA+RTLSFCnZPNdIuNbYRZxBXrDs6VCa3yz cVF1cwq9M0PJk8jpE2g1ug5LCmwuGIA=;
Received: from [172.27.248.207] (connect.isode.net [172.20.0.43]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <YrBTzABhWDtr@statler.isode.com>; Mon, 20 Jun 2022 12:02:36 +0100
Message-ID: <43c1e728-c9d8-0732-4d7d-a22e8b975839@isode.com>
Date: Mon, 20 Jun 2022 12:02:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
To: Martin Thomson <mt@lowentropy.net>, media-types@iana.org
References: <377c006a-8ac0-4904-8e78-bbe580ac738f@beta.fastmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <377c006a-8ac0-4904-8e78-bbe580ac738f@beta.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (pechora3.dc.icann.org [0.0.0.0]); Mon, 20 Jun 2022 11:02:58 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/W5z88u-fLEjzsKSzGR3XxijCS8E>
Subject: Re: [media-types] Review of message/bhttp
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2022 11:03:02 -0000

Hi Martin,

On 23/05/2022 00:48, Martin Thomson wrote:
> Section 7 of draft-ietf-httpbis-binary-message-03 proposes a new message/bhttp media type under the message/ category.  This is semantically equivalent to message/http, but it uses a binary encoding.
>
> https://www.ietf.org/archive/id/draft-ietf-httpbis-binary-message-03.html#name-message-bhttp-media-type
>
> The input of the experts on this list would be appreciated.

My apologies for a late response, but I have a small request on the 
media type registration form.

The following field:

"Applications that use this media type:" currently contains N/A. This 
doesn't look right, as this field can be used by implementors to decide 
whether they need to bother implementing a particular media type.

So please treat this field as if it says "Applications that could use 
this media type" and add some example application that would benefit 
from using it. You have some text in the Introduction section of the 
draft that can be expanded and adapted here.

Thank you,

Alexey

v2.23.0 | Report a Bug | By Email