[Json] ECMA-262 normative?

[Carsten Bormann <[e-mail]>]

On Sep 26, 2013, at 20:52, Eliot Lear <[e-mail]> wrote:

> there is the question on whether or not the
> document should simply normatively reference ECMA.

I'm not sure this aspect was picked up yet.

The current draft lists ECMA-262 (1999) as a normative reference.

A quick reading of
http://www.ietf.org/iesg/statement/normative-informative.html
"IESG Statement: Normative and Informative References"
shows that this is an erratum that needs to be corrected.*)
The reference must be informative.

Grüße, Carsten

PS.:  As people sometimes don't have the ability to use links in a message, the juicy sentence is:

> Normative references specify documents that must be read to understand or implement the technology in the new RFC, or whose technology must be present for the technology in the new RFC to work. 

If we make that true for ECMA-262, we have seriously broken the document.