Re: [Json] Proposed Wording for New WG Charter

Julian Reschke <julian.reschke@gmx.de> Tue, 18 March 2014 15:38 UTC

Return-Path: <julian.reschke@gmx.de>
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 0CACB1A042E for <json@ietfa.amsl.com>; Tue, 18 Mar 2014 08:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 rRbS6Eiu0ABY for <json@ietfa.amsl.com>; Tue, 18 Mar 2014 08:38:50 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 4D19A1A03BC for <json@ietf.org>; Tue, 18 Mar 2014 08:38:50 -0700 (PDT)
Received: from [192.168.1.103] ([217.91.35.233]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0Lpxdr-1X5cZF3xNn-00ffe7; Tue, 18 Mar 2014 16:38:39 +0100
Message-ID: <5328687D.9050509@gmx.de>
Date: Tue, 18 Mar 2014 16:38:37 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <53277484.70305@cisco.com> <5327F05E.7060905@gmx.de> <EC3168FE-EA36-4036-8B36-974FDA7BD88E@vpnc.org> <532864FC.8040700@gmx.de> <CE6D04D1-C063-41E6-A635-3AD8127B6F28@vpnc.org>
In-Reply-To: <CE6D04D1-C063-41E6-A635-3AD8127B6F28@vpnc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:RPAIoz6+tOu1GBXM6JSc/gYOahxk1gPrzWelX/i9yE9R0jyMDh0 8B6WcL51IS/lZQIjrQIWW8t6d90Oo25wIPef4qqsGUspNG7wQV4oMD7lQyrDdJsKcE11Gfr 2pQyDhWz+Ze5xq/h0AqxbP45bhjAy4AOkJDuKnJuIsHriTpS7BT7qvuCHGtiAZHi8g9KOGb fjPQeZmvKcvxDVz6ne9KA==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/NAPV6agPcdUo_R8-4ixQOuqJfjI
Cc: IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Proposed Wording for New WG Charter
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, 18 Mar 2014 15:38:52 -0000

On 2014-03-18 16:30, Paul Hoffman wrote:
> On Mar 18, 2014, at 8:23 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
>
>> On 2014-03-18 16:14, Paul Hoffman wrote:
>>>
>>> On Mar 18, 2014, at 12:06 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
>>>
>>>> On 2014-03-17 23:17, Matt Miller wrote:
>>>>> Greetings again.  We earlier asked a couple of questions to gauge what
>>>>> the new proposed WG charter ought to contain.  That feedback has been
>>>>> valuable, but has drilled into implementation specifics before a new
>>>>> charter was actually agreed on!  We have been chastised by our AD about
>>>>> this, and for good reason.  We think we already have enough input from
>>>>> the London meeting and the list over the past few days to make the
>>>>> following proposal for a new charter:
>>>>> ...
>>>>
>>>> What happened to the proposal to add James Snell's json-merge draft to the list of WG items?
>>>
>>> I don't remember that discussion. draft-ietf-appsawg-json-merge-patch should still be part of AppsAWG; it just needs someone to take over the work.
>>>
>>> --Paul Hoffman
>>
>> We talked about that after the WG meeting, didn't we?
>
> Errrr, maybe? Your recollection may be better than mine.
>
> Having said that, I'm not sure if this draft needs to move from AppsAWG: it just needs an author to finish the draft.

...and it needs review from people using JSON in protocols -- I *think* 
this is more likely to happen if if moves over to the JSON WG...