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

Martin Thomson <martin.thomson@gmail.com> Mon, 19 June 2017 04:17 UTC

MIME-Version: 1.0
In-Reply-To: <ea2e334f-26ea-a567-558f-7d4a0288fe26@it.aoyama.ac.jp>
References: <CABkgnnVYhFq7pvHn+_HDW3ufCQtnYbmO98jh0=iOxbghu-M8ww@mail.gmail.com> <ea2e334f-26ea-a567-558f-7d4a0288fe26@it.aoyama.ac.jp>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 19 Jun 2017 14:17:01 +1000
Message-ID: <CABkgnnUinps6+ucBnq7QXewE7C32_8EGPNCtY7tfZ-_X-Goe_Q@mail.gmail.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Cc: media-types@iana.org, "webpush@ietf.org" <webpush@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/yLfbvGkLOfj0g5k6guB4d3Uxhy0>
Subject: Re: [media-types] Media type review for application/webpush-options+json
Precedence: list

Thanks Martin,

Corrected in https://github.com/webpush-wg/webpush-vapid/commit/c9e2d0259d2bc6fd3b6

On 19 June 2017 at 14:01, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
> 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: [media-types] Media type review for applicati… Martin Thomson
[media-types] Media type review for application/w… Martin Thomson
Re: [media-types] Media type review for applicati… Martin J. Dürst