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

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 04 March 2014 10:29 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 9A61E1A042E for <json@ietfa.amsl.com>; Tue, 4 Mar 2014 02:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
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 tE6FIJnedlGv for <json@ietfa.amsl.com>; Tue, 4 Mar 2014 02:29:41 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 990D21A03AC for <json@ietf.org>; Tue, 4 Mar 2014 02:29:41 -0800 (PST)
Received: from dhcp-bc61.meeting.ietf.org (dhcp-bc61.meeting.ietf.org [31.133.188.97]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s24ATU34026076 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 4 Mar 2014 03:29:35 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <53159651.10601@it.aoyama.ac.jp>
Date: Tue, 4 Mar 2014 10:29:28 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3838285-52FF-4DAE-8C7F-1FFD715C8172@vpnc.org>
References: <20140302203413.A7DEB7FC2CB@rfc-editor.org> <v687h9pv3q3tpodgrq01c9ogt1oe9cilbs@hive.bjoern.hoehrmann.de> <20140302220629.GA4246@schmorp.de> <82b7h9l5djqeali7cr36uadlicg1183bsv@hive.bjoern.hoehrmann.de> <D18494CF-5CBC-4DDC-A1B6-01CB8B78AE8E@nic.cz> <53146287.1030505@qti.qualcomm.com> <53159651.10601@it.aoyama.ac.jp>
To: Martin Duerst <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/qev54re_O-97zGoQY-PeIDxZIIo
Cc: json@ietf.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: Tue, 04 Mar 2014 10:29:42 -0000

On Mar 4, 2014, at 9:01 AM, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:

> I saw the announcement for the new RFC (7159). For the record, although I understand the basic idea behind the policy that RFCs are never changed, I think it would have been much wiser to just make the change in place.

This comment is relevant to rfc-interest@rfc-editor.org, not here. This WG doesn't make rules for how RFCs are published.

--Paul Hoffman