[Json] On the errata (Was: [Technical Errata Reported] RFC7158 (3907) (3908))

Pete Resnick <presnick@qti.qualcomm.com> Tue, 04 March 2014 15:18 UTC

Return-Path: <presnick@qti.qualcomm.com>
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 0720C1A01DA for <json@ietfa.amsl.com>; Tue, 4 Mar 2014 07:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.848
X-Spam-Level:
X-Spam-Status: No, score=-4.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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 LK6RZIsGoANq for <json@ietfa.amsl.com>; Tue, 4 Mar 2014 07:18:42 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 79F5F1A0179 for <json@ietf.org>; Tue, 4 Mar 2014 07:18:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1393946319; x=1425482319; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mZPJZEYvs6G7K9a0U+btLW6DkO8MFn9C8qmB1UXc70Q=; b=UDiiiR7yllN65IVFaySUHuMDbrvTfesml9CqL9G5GSEEiOp7YhA72rkH 1q67Yh3ptP7z/5QPcxM3V3/Czj/oy8YBAwpNdVU8lR7pObyOGW++J4H2+ ypYaLRwviCPjJ8Vo5E7lgm52Ey2y40YyroSeBHQxjNq4LKofR+Xj8D5u9 g=;
X-IronPort-AV: E=McAfee;i="5400,1158,7366"; a="109260070"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by wolverine02.qualcomm.com with ESMTP; 04 Mar 2014 07:18:39 -0800
X-IronPort-AV: E=Sophos;i="4.97,585,1389772800"; d="scan'208";a="28003020"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 04 Mar 2014 07:18:39 -0800
Received: from dhcp-ac59.meeting.ietf.org (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 4 Mar 2014 07:18:37 -0800
Message-ID: <5315EEC9.3070509@qti.qualcomm.com>
Date: Tue, 4 Mar 2014 15:18:33 +0000
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <rfc7158@schmorp.de>
References: <20140302203413.A7DEB7FC2CB@rfc-editor.org>
In-Reply-To: <20140302203413.A7DEB7FC2CB@rfc-editor.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/json/JEUk1A5hgCijTOTHUStQxdt211E
Cc: json@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Json] On the errata (Was: [Technical Errata Reported] RFC7158 (3907) (3908))
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 15:18:45 -0000

Hi Marc,

As you may have surmised from some of the discussion, the note on the 
RFC Editor page is misleading regarding where to report things, and we 
(the IETF leadership) are working with the RFC Editor to update their 
page to make that clearer. What you have reported is actually input to 
the JSON Working Group, which the working group should be discussing on 
the WG mailing list, not errata, which are really for simple textual 
corrections to published RFCs. Certainly your input is appreciated, and 
it doesn't matter that it landed in the wrong place through no fault of 
your own.

So here's what I would suggest: Your comments have been Cc'ed to the 
JSON WG list from the errata system. I'll leave it to the chairs (Paul 
and Matt) to say whether they want you to resend them directly to the WG 
mailing list with a new Subject so they can track it, or whether the Cc 
of the errata messages will suffice. Either way, please remove the RFC 
Editor and the Area Directors (Barry and I) from the Cc list if you 
continue the discussion of the issue. Meanwhile, I'll have the RFC 
Editor remove these entries from the Errata system; there's no need to 
keep the RFC Editor in the loop on these topics.

Again, I appreciate your input, and I hope we can get the RFC Editor 
pages updated so it's clear where to send different kinds of comments.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478