RFC 7464 on JavaScript Object Notation (JSON) Text Sequences

rfc-editor@rfc-editor.org Wed, 25 February 2015 22:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D346E1A8949; Wed, 25 Feb 2015 14:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 BUP-5yl8qcJi; Wed, 25 Feb 2015 14:18:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id D16311A8947; Wed, 25 Feb 2015 14:18:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 390BD187E04; Wed, 25 Feb 2015 14:18:10 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7464 on JavaScript Object Notation (JSON) Text Sequences
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150225221810.390BD187E04@rfc-editor.org>
Date: Wed, 25 Feb 2015 14:18:10 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/ivQxipYSsuZ23qQDhjCglChWiC0>
Cc: drafts-update-ref@iana.org, json@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 22:18:52 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7464

        Title:      JavaScript Object Notation (JSON) Text 
                    Sequences 
        Author:     N. Williams
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2015
        Mailbox:    nico@cryptonector.com
        Pages:      8
        Characters: 16132
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-json-text-sequence-13.txt

        URL:        https://www.rfc-editor.org/info/rfc7464

This document describes the JavaScript Object Notation (JSON) text
sequence format and associated media type "application/json-seq".  A
JSON text sequence consists of any number of JSON texts, all encoded
in UTF-8, each prefixed by an ASCII Record Separator (0x1E), and each
ending with an ASCII Line Feed character (0x0A).

This document is a product of the JavaScript Object Notation Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC