[Json] Coordinating publication of 4627bis with ECMA

Barry Leiba <barryleiba@computer.org> Sun, 12 May 2013 18:48 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7147721F89D5 for <json@ietfa.amsl.com>; Sun, 12 May 2013 11:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.988
X-Spam-Status: No, score=-101.988 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EBpJ44CbSYNc for <json@ietfa.amsl.com>; Sun, 12 May 2013 11:48:52 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id B7AA721F8916 for <json@ietf.org>; Sun, 12 May 2013 11:48:51 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id fm20so5420815lab.39 for <json@ietf.org>; Sun, 12 May 2013 11:48:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=ynRwXQkl2/EFfd43jNaS4c1YkUfZUkKNAkkjS/v1Lmg=; b=lB2Iqi4zIvXBJd3aW9qQTFdOtRVVX7xv/340pPSzDBmwM1h9BpecBE9OeREnpuvT09 WFXCifyu3lEJ5G3G07ffdBTbmY7wAn+eZJuDeVKNozmh8F8Z3JrTasfU/FIXqGKH4w/C xcae1zUoaAWDEkhu68ZvMhv1Q/p/Yzd+6mSjR9rJHTTdAggZgWXA7pGA4gdhKwqiBAel 76N+IftAlZJa0CWLISEBD57JO7fJE7RBNbZxFKt+02B8OVlsCTFzFzSODahuVdCNiPPo xn8QrzlZyFuxl94z8S9E/h3aGdFRoxqiw4XYQYPF89imJQz+BBhSoDEsvoOD1j3StDGb kuhw==
MIME-Version: 1.0
X-Received: by with SMTP id z4mr11509719lae.37.1368384530617; Sun, 12 May 2013 11:48:50 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by with HTTP; Sun, 12 May 2013 11:48:50 -0700 (PDT)
Date: Sun, 12 May 2013 19:48:50 +0100
X-Google-Sender-Auth: 5s7ANQX-JRkAa2YUC8SlahgDbBU
Message-ID: <CALaySJJrd=5RM-VhOp3j_7MMJ-aRvNak-Y1bMeJfgOUq0YdDgQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "json@ietf.org" <json@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [Json] Coordinating publication of 4627bis with ECMA
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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, 12 May 2013 18:48:52 -0000

Because ECMA is dependent upon the results of the 4627bis work that
will be this group's charter, we have discussion the situation with
them in a liaison call.  They are willing to have the work happen in
the IETF, with their participation.  They would like to jointly
publish the resulting document.

This is allowed by our rules: the chairs will manage the discussion
and consensus as normal, and RFC 5378 allows republication of the
resulting RFC.  The difference will come in the IESG approval process,
where we will coordinate with ECMA's approval process to ensure that
the two approved versions match.

I have added the following paragraph to the proposed charter:

The resulting document will be jointly published as an RFC and by ECMA.
ECMA participants will be participating in the working group editing
through the normal process of working group participation.  The responsible
AD will coordinate the approval process with ECMA so that the versions
of the document that are approved by each body are the same.

See https://datatracker.ietf.org/doc/charter-ietf-json/