IETF Logo Mail Archive

Re: [apps-discuss] Encoding considerations (was Technical Errata for RFC 6839

Nico Williams <nico@cryptonector.com> Tue, 19 May 2015 00:34 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0406D1B2C03 for <apps-discuss@ietfa.amsl.com>; Mon, 18 May 2015 17:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.233
X-Spam-Level:
X-Spam-Status: No, score=0.233 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 NawyIquwrJ48 for <apps-discuss@ietfa.amsl.com>; Mon, 18 May 2015 17:34:00 -0700 (PDT)
Received: from homiemail-a104.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 40FBD1B2C02 for <apps-discuss@ietf.org>; Mon, 18 May 2015 17:34:00 -0700 (PDT)
Received: from homiemail-a104.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a104.g.dreamhost.com (Postfix) with ESMTP id 228502004F31E; Mon, 18 May 2015 17:34:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=qEZL0DQMqZ+NZo sJL6d1QlBfkZQ=; b=QUpoXV8N2gutxKbbs7Y7U3wxVA5TiMCYGbdKgUStqFIRWL iuXumviDLSsBnPIvDCw3KKUgC+zG5LTeCDimKQIbyv23szvFRjDJTvShQP3yNudO q6VdH7n2/9p4zMFXEc7qmgtK+iK4Q0W+gCwMZSKZ9VytEcQfESIf9LZlR6aOQ=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a104.g.dreamhost.com (Postfix) with ESMTPA id B40582004F31D; Mon, 18 May 2015 17:33:59 -0700 (PDT)
Date: Mon, 18 May 2015 19:33:59 -0500
From: Nico Williams <nico@cryptonector.com>
To: Larry Masinter <masinter@adobe.com>
Message-ID: <20150519003358.GC9922@localhost>
References: <FFF8E611-07F5-4793-A5E7-E72E518A44A5@adobe.com> <20150519002405.GB9922@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20150519002405.GB9922@localhost>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/vd4MMVz1wBxbUlMmmvIulmJX-lo>
Cc: Barry Leiba <barryleiba@computer.org>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Encoding considerations (was Technical Errata for RFC 6839
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2015 00:34:01 -0000

On Mon, May 18, 2015 at 07:24:06PM -0500, Nico Williams wrote:
> On Mon, May 18, 2015 at 11:58:06PM +0000, Larry Masinter wrote:
> > >> In fact a lot of formats based on XML or JSON are by their nature
> > >> _always_ 8bit or 7bit compatible. And I see some value in pointing that out
> > >> where it's appropriate to do so
> 
> Encoded JSON texts can contain non-ASCII without escaping, so JSON is not
> 7-bit compatible, but JSON texts can be re-encoded such that all
> non-ASCII Unicode codepoints are escaped, so in a sense JSON is 7-bit
> compatible.  But so what?
> 
> What's the context anyways?

Never mind, I found the context.

Nico
--

v2.23.0 | Report a Bug | By Email