IETF Logo Mail Archive

Re: [Json] [Technical Errata Reported] RFC7158 (3907)

Bjoern Hoehrmann <derhoermi@gmx.net> Sun, 02 March 2014 22:30 UTC

Return-Path: <derhoermi@gmx.net>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942851A0B17 for <json@ietfa.amsl.com>; Sun, 2 Mar 2014 14:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jcqC4ixlK6at for <json@ietfa.amsl.com>; Sun, 2 Mar 2014 14:30:25 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 530BE1A096D for <json@ietf.org>; Sun, 2 Mar 2014 14:30:25 -0800 (PST)
Received: from netb ([89.204.139.118]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0Lu3J4-1XKHti1ynW-011RN9; Sun, 02 Mar 2014 23:30:14 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Marc Lehmann <schmorp@schmorp.de>
Date: Sun, 02 Mar 2014 23:29:49 +0100
Message-ID: <82b7h9l5djqeali7cr36uadlicg1183bsv@hive.bjoern.hoehrmann.de>
References: <20140302203413.A7DEB7FC2CB@rfc-editor.org> <v687h9pv3q3tpodgrq01c9ogt1oe9cilbs@hive.bjoern.hoehrmann.de> <20140302220629.GA4246@schmorp.de>
In-Reply-To: <20140302220629.GA4246@schmorp.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:d1iwhwudri8FvpHMqJbxJCx3QzyjSjjd/X1bCL+2AGHtuhWqqKB cZ/k5FtWT+WxiI0n2qRaWF9GoQAV2HL65Xa8M4fh5ZU69rOqG1v25mhelgw8KHkTdw6okUV DswzQarLph0gH1gaxZATCUdwmdO1/QEPHLREQKa2wi/c0CvrJiSry5M+h7JJEYOrQYGLUTe GttQpdgHScfBiB42Vh7KA==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/z-VXSY3PDKFZcxqeeeXShuO4Fm8
Cc: presnick@qti.qualcomm.com, paul.hoffman@vpnc.org, json@ietf.org, tbray@textuality.com, mamille2@cisco.com, barryleiba@computer.org, rfc7158@schmorp.de, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Json] [Technical Errata Reported] RFC7158 (3907)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Mar 2014 22:30:27 -0000

* Marc Lehmann wrote:
>Just for additional info, I followed the instructions given in the
>RFC to give feedback (the page linked to by the rfc for feedback,
>http://www.rfc-editor.org/info/rfc7158, didn't seem to list any other
>options to give feedback than the errata system).
>
>It was merely my intent to give feedback on this issue (which is a big
>issue for me as an implementerm not necessarily an errata).

The document has gone through a series of drafts with various calls for
review and many comments and has now been published as RFC, meaning it's
impossible to change it; it can only be replaced through the heavyweight
process of going through the IETF consensus process again. RFC Errata
https://www.ietf.org/iesg/statement/errata-processing.html allow us to
track some information about errors in the document, but people who miss
this change from RFC 4627 in their use of the document are not likely to
consult the errata pages.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

v2.23.0 | Report a Bug | By Email