Re: [dispatch] Murray Kucherawy's No Objection on draft-ietf-dispatch-javascript-mjs-13: (with COMMENT)

[Mathias Bynens <[e-mail]>]

On Tue, Jan 11, 2022 at 4:35 AM Murray S. Kucherawy <[e-mail]>
wrote:

> On Mon, Jan 10, 2022 at 5:20 AM Mathias Bynens <[e-mail]> wrote:
>
>> Thank you. Please take a look at this patch:
>> https://github.com/linuxwolf/bmeck-ids/pull/65/files
>>
>> For context, these are historical legacy types that are supported in
>> practice: https://mathiasbynens.be/demo/javascript-mime-type Although
>> they are OBSOLETED, it’s important that the document specifies them because
>> they are required for Web compatibility.
>>
>
> I think that's an improvement.  I'd be curious to hear what John thinks.
>
> If as you commented in github you don't like the word "grandfathered", you
> could instead work the word "legacy" into the prose and still say the same
> thing.
>
> Any further comment on the MUST issue I raised?
>

This refers to the following paragraph:

```
This document may be updated to take other content into account. Updates of
this document may introduce new optional parameters; implementations MUST
consider the impact of such an update.
```

This MUST is not new; this text is inherited from RFC4329 (section 3). For
our draft, we’ve been hesitant to make changes other than the ones that
were needed to match implementation reality & ensure compat.


>
> -MSK
>