IETF Logo Mail Archive

Re: [Json] Obsoletes RFC 4627

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Fri, 27 September 2013 04:03 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 156B621F9DC7 for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 21:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.569
X-Spam-Level:
X-Spam-Status: No, score=-101.569 tagged_above=-999 required=5 tests=[AWL=-1.779, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfS577tTUIVL for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 21:03:51 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9B15921F9A65 for <json@ietf.org>; Thu, 26 Sep 2013 21:03:48 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id r8R43epi015462; Fri, 27 Sep 2013 13:03:43 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 24c4_efd3_cb07bb3c_2729_11e3_b910_001e6722eec2; Fri, 27 Sep 2013 13:03:39 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id DC29CBFB14; Fri, 27 Sep 2013 13:03:39 +0900 (JST)
Message-ID: <5245038F.4060206@it.aoyama.ac.jp>
Date: Fri, 27 Sep 2013 13:03:27 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <BF7E36B9C495A6468E8EC573603ED9411EF1BB0B@xmb-aln-x11.cisco.com> <B2706F01-E791-40AE-AC54-6DC7C3E2A0E3@mnot.net> <95AA0989-6473-4E83-861B-E84140EC083F@vpnc.org>
In-Reply-To: <95AA0989-6473-4E83-861B-E84140EC083F@vpnc.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] Obsoletes RFC 4627
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 04:03:57 -0000

On 2013/09/27 9:30, Paul Hoffman wrote:
> <no hat>
>
> On Sep 26, 2013, at 4:24 PM, Mark Nottingham<mnot@mnot.net>  wrote:
>
>> * Shouldn't this document obsolete 4627?
>
> Er, yes, it probably should. Does anyone have any objection to this?

None at all here. If it doesn't obsolete RFC 4627, why would we have 
done all the work?

Regards,   Martin.

> --Paul Hoffman
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

v2.23.0 | Report a Bug | By Email