IETF Logo Mail Archive

Re: [apps-discuss] [Technical Errata Reported] RFC6839 (4367)

Dave Cridland <dave@cridland.net> Sat, 16 May 2015 18:57 UTC

Return-Path: <dave@cridland.net>
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 A60401A07BC for <apps-discuss@ietfa.amsl.com>; Sat, 16 May 2015 11:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 NqSF7axX9Qph for <apps-discuss@ietfa.amsl.com>; Sat, 16 May 2015 11:56:59 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 561A71A004D for <apps-discuss@ietf.org>; Sat, 16 May 2015 11:56:59 -0700 (PDT)
Received: by oift201 with SMTP id t201so104387813oif.3 for <apps-discuss@ietf.org>; Sat, 16 May 2015 11:56:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PTulL6DLQph9oOYBCitkAvkFOt4bUY5ODh/vUKX0pFQ=; b=HpuF9incDkJUZxZazai07PW1Q01YxZpY8RK+d73fwaJs2QBC/6AnfOI6oa9Zwl6Vwx txHzy9vALtgRt0lx0hQoKMUJveEjunoJ1+pIGGtuiryXkW3Yp9Dk0b1jQSw/4h0EjEBZ p6wdU2ZC9L55FbdG4L/PXAfkzPu+OjjZBMcQs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PTulL6DLQph9oOYBCitkAvkFOt4bUY5ODh/vUKX0pFQ=; b=bGNWg43ZcmIT1A3M74sBDZeAo8IMVR/tv/244+QUjs+6DPgcUMOb7h3IwEDdfCosc0 rLqgL2j/nsgt6C6UvEqZb/sHvVJC2ufczIcS42U/0p3A5VmvaQUypezLAR5zHM8UrH7t O1KjcqoaricHhPblZKNFXdjzVDfMbxTLV4Gj5YE4T5Q2Lw1ZyoAy0svjtCgq1WECk6bL oFHKhf5t6zoAYAGtXvyCIxLUxjR0eWzytdgABHxeF0dcw62+XlnTFAkw+DuD7NvD1fqN yep3dFciYrJPtQ0MI+KMs2HTJzCH48/KIA/TzkJy9N6H39i8rozFpt4X/PPAhPaShmbi 5AKA==
X-Gm-Message-State: ALoCoQm2l5evPrP6wvlumqopswsjd96AOh1XrH8NB4FGmwKDJM4WrqCxiQDoMff3DuBxpYtM3HA1
MIME-Version: 1.0
X-Received: by 10.60.145.228 with SMTP id sx4mr13349788oeb.79.1431802618821; Sat, 16 May 2015 11:56:58 -0700 (PDT)
Received: by 10.60.119.4 with HTTP; Sat, 16 May 2015 11:56:58 -0700 (PDT)
Received: by 10.60.119.4 with HTTP; Sat, 16 May 2015 11:56:58 -0700 (PDT)
In-Reply-To: <55578A38.2010609@ninebynine.org>
References: <20150515131052.8E76D180092@rfc-editor.org> <CALaySJ++ptrFqjjC=mRC9zH8ns18bermy2YAfYYLx5OtX0Zdqw@mail.gmail.com> <CAPQd5oTZZKimSWcQaLBeHmq7o-npxvL8KM3HRQPW9JQPHs_ONw@mail.gmail.com> <55562081.6070504@att.com> <CAPQd5oRws8pQo7qR6xG2E0_=4vka-ymQO8sb_gAOup5_56F11g@mail.gmail.com> <555624A6.5050505@att.com> <55578A38.2010609@ninebynine.org>
Date: Sat, 16 May 2015 19:56:58 +0100
Message-ID: <CAKHUCzyVqBpYeWmPxz+z1JU1aHuY0npc08x_2SMHdBFQVCaYaw@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Graham Klyne <gk@ninebynine.org>
Content-Type: multipart/alternative; boundary="047d7b5d30da7bd445051637860e"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/t7p85LtXTxgqvURGlPFgfax0wlU>
Cc: "tony+sss@maillennium.att.com" <tony+sss@maillennium.att.com>, apps-discuss@ietf.org, Barry Leiba <barryleiba@computer.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [apps-discuss] [Technical Errata Reported] RFC6839 (4367)
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: Sat, 16 May 2015 18:57:01 -0000

On 16 May 2015 19:19, "Graham Klyne" <gk@ninebynine.org> wrote:
>
> On 15/05/2015 17:53, Tony Hansen wrote:
>>
>> There is one more constraint for a file written with utf-8 to use the
>> encoding of 8bit: the lines are limited to 998 bytes in length (not
>> counting the CRLF line terminators). See RFC 2045 for details.
>
>
> I think that would be a problem for JSON - there's no way (I know of) to
break long text strings over multiple lines, so that restriction would rule
out very long string values.  So maybe "binary" is the right choice.
>

Plenty of languages don't use line termination in the same way, and in
principle therefore plenty of things might not work as 8-bit.

All that means is that once serialized, the application needs to test for
long lines and use something different if needs be, like binary or base 64.

But that's no different to HTML, or plain text.

> #g
> --
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

v2.23.0 | Report a Bug | By Email