Re: [Webpush] [media-types] Media type review for application/webpush-options+json

Martin J. Dürst <duerst@it.aoyama.ac.jp> Mon, 19 June 2017 04:01 UTC

To: Martin Thomson <martin.thomson@gmail.com>, media-types@iana.org
CC: "webpush@ietf.org" <webpush@ietf.org>
References: <CABkgnnVYhFq7pvHn+_HDW3ufCQtnYbmO98jh0=iOxbghu-M8ww@mail.gmail.com>
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <ea2e334f-26ea-a567-558f-7d4a0288fe26@it.aoyama.ac.jp>
Date: Mon, 19 Jun 2017 13:01:06 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnVYhFq7pvHn+_HDW3ufCQtnYbmO98jh0=iOxbghu-M8ww@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Jun 2017 04:01:09.1106 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0650
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/-_MKV4GyWREtV3YKK1DBRaDCJEI>
Subject: Re: [Webpush] [media-types] Media type review for application/webpush-options+json
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol <webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>, <mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>, <mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jun 2017 04:01:15 -0000

Hello Martin,

For those fields where you have "n/a", I think in most cases, "none" 
would be more precise. Also, "Published specification:  This document." 
doesn't work when the template is extracted. Also, "Encoding 
considerations:  binary" looks wrong (but maybe it was choosen because 
8bit has a line length limitation?). Anyway, it would be good to add a 
comment there that the format is essentially text-based, and the 
character encoding is UTF-8.

Regards,   Martin.

On 2017/06/19 12:41, Martin Thomson wrote:
> Copying the template from
> https://datatracker.ietf.org/doc/html/draft-ietf-webpush-vapid#section-6.3
> 
>     Type name:  application
> 
>     Subtype name:  webpush-options+json
> 
>     Required parameters:  n/a
> 
>     Optional parameters:  n/a
> 
>     Encoding considerations:  binary
> 
>     Security considerations:  See [RFC7159] for security considerations
>        specific to JSON.
> 
>     Interoperability considerations:  See [RFC7159] for interoperability
>        considerations specific to JSON.
> 
>     Published specification:  This document.
> 
>     Applications that use this media type:  Web browsers, via the Web
>        Push Protocol [RFC8030].
> 
>     Fragment identifier considerations:  None, see [RFC7159].
> 
>     Additional information:
> 
>        Deprecated alias names for this type:  n/a
> 
>        Magic number(s):  n/a
> 
>        File extension(s):  .json
> 
>        Macintosh file type code(s):  TEXT
> 
>     Person & email address to contact for further information:  Martin
>        Thomson (martin.thomson@gmail.com)
> 
>     Intended usage:  LIMITED USE
> 
>     Restrictions on usage:  For use with the Web Push Protocol [RFC8030].
> 
>     Author:  See "Authors' Addresses" section of this document.
> 
>     Change controller:  Internet Engineering Task Force

Re: [Webpush] [media-types] Media type review for… Martin Thomson
[Webpush] Media type review for application/webpu… Martin Thomson
Re: [Webpush] [media-types] Media type review for… Martin J. Dürst