Re: Status of RFC 20 (was: Re: Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09)

Julian Reschke <julian.reschke@gmx.de> Thu, 18 December 2014 14:16 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7264A1A8A05 for <ietf@ietfa.amsl.com>; Thu, 18 Dec 2014 06:16:46 -0800 (PST)
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 Hr7c39dQnEAx for <ietf@ietfa.amsl.com>; Thu, 18 Dec 2014 06:16:44 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D9AA1A89F1 for <ietf@ietf.org>; Thu, 18 Dec 2014 06:16:44 -0800 (PST)
Received: from [192.168.1.26] ([217.91.35.233]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MNYxW-1Xyt7E1URW-007Fjn; Thu, 18 Dec 2014 15:16:22 +0100
Message-ID: <5492E1B1.2040600@gmx.de>
Date: Thu, 18 Dec 2014 15:16:17 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Status of RFC 20 (was: Re: Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09)
References: <20141206170611.39377.qmail@ary.lan> <54833B14.7010104@cs.tcd.ie> <CAC4RtVC=yJs1p8Ei2AFSfSiqo9OwXkWhioXPWYU_JKRCSo0VKw@mail.gmail.com>
In-Reply-To: <CAC4RtVC=yJs1p8Ei2AFSfSiqo9OwXkWhioXPWYU_JKRCSo0VKw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:DDmhWyBRZy7vXRB2VcylEjSuJ1+TLrnhgSC/wm2mAqANTZwsyC+ 6U1Pb/lbHAS6WO9wMc5K2Y7LGcSy9wjFPRrxlt89mtJhMTy4VHYXJuSw/7EvWB2u19lpcjL jNFtYNnPSY6+OEXf59kPjcz+T5IqgvQ7/61X36mTtUrTn0VHWrrmQiL5SXpjE9gimeWc/0C Okd+98hytdtIjftth803Q==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/em9zGyFKHQMfVIMev2uoV3qj_0M
Cc: John Levine <johnl@taugh.com>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 14:16:46 -0000

On 2014-12-07 01:19, Barry Leiba wrote:
>> PS: If Barry or anyone else wants to do this instead that's
>> fine by me.
>
> I already have; the status-change document is in Last Call Requested state.
>
> Barry

So RFC 20 says it defines a "coded character set". However, in current 
specs (at least in APPS) we frequently talk about "character encoding 
schemes" (<http://tools.ietf.org/html/rfc6365#section-2>), in general 
mapping Unicode code points to octet sequences.

So does RFC 20 define a CES as well? If it does not, should we have an 
additional document taking care of this?

Best regards, Julian