< draft-wilde-json-seq-suffix-02.txt		draft-wilde-json-seq-suffix-03.txt >
	Network Working Group E. Wilde		Network Working Group E. Wilde
	Internet-Draft CA Technologies		Internet-Draft CA Technologies
	Intended status: Informational December 9, 2016		Intended status: Informational December 31, 2016
	Expires: June 12, 2017		Expires: July 4, 2017
	A Media Type Structured Syntax Suffix for JSON Text Sequences		A Media Type Structured Syntax Suffix for JSON Text Sequences
	draft-wilde-json-seq-suffix-02		draft-wilde-json-seq-suffix-03
	Abstract		Abstract
	Structured Syntax Suffixes for media types allow other media types to		Structured Syntax Suffixes for media types allow other media types to
	build on them and make it explicit that they are built on an existing		build on them and make it explicit that they are built on an existing
	media type as their foundation. This specification defines and		media type as their foundation. This specification defines and
	registers "+json-seq" as a structured syntax suffix for JSON Text		registers "+json-seq" as a structured syntax suffix for JSON Text
	Sequences.		Sequences.
	Note to Readers		Note to Readers
	skipping to change at page 1, line 45 ¶		skipping to change at page 1, line 45 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on June 12, 2017.		This Internet-Draft will expire on July 4, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 22 ¶		skipping to change at page 3, line 22 ¶
	Applications encountering such a media type can then either simply		Applications encountering such a media type can then either simply
	use generic processing if all they need is a generic view of the JSON		use generic processing if all they need is a generic view of the JSON
	Text Sequence, or they can use generic JSON Text Sequence tools for		Text Sequence, or they can use generic JSON Text Sequence tools for
	initial parsing, and then can implement their own specific processing		initial parsing, and then can implement their own specific processing
	on top of that generic parsing tool.		on top of that generic parsing tool.
	4. IANA Considerations		4. IANA Considerations
	Structured Syntax Suffixes are registered within the "Structured		Structured Syntax Suffixes are registered within the "Structured
	Syntax Suffix Registry" maintained at		Syntax Suffix Registry" maintained at
	<https://www.iana.org/assignments/media-type-structured-suffix/media-		<https://www.iana.org/assignments/media-type-structured-suffix>.
	type-structured-suffix.xhtml>.
	IANA is requested to register the "+json-seq" structured syntax		IANA is requested to register the "+json-seq" structured syntax
	suffix in accordance with [RFC6838].		suffix in accordance with [RFC6838].
	Name: JSON Text Sequence		Name: JSON Text Sequence
	+suffix: +json-seq		+suffix: +json-seq
	References: [RFC7464]		References: [RFC7464], RFC [[ RFC Editor, please insert assigned
			RFC number. ]]
	Encoding considerations: See [RFC7464] Section 2.2		Encoding considerations: See [RFC7464] Section 2.2
	Fragment identifier considerations: The syntax and semantics of		Fragment identifier considerations: The syntax and semantics of
	fragment identifiers specified for +json-seq SHOULD be as		fragment identifiers specified for +json-seq SHOULD be as
	specified for "application/json-seq". (At publication of this		specified for "application/json-seq". (At publication of this
	document, there is no fragment identification syntax defined for		document, there is no fragment identification syntax defined for
	"application/json-seq".)		"application/json-seq".)
	The syntax and semantics for fragment identifiers for a		The syntax and semantics for fragment identifiers for a
	skipping to change at page 4, line 12 ¶		skipping to change at page 4, line 12 ¶
	identifier does not resolve per the +json-seq rules, then		identifier does not resolve per the +json-seq rules, then
	process as specified in "xxx/yyy+json-seq".		process as specified in "xxx/yyy+json-seq".
	For cases not defined in +json-seq, then process as		For cases not defined in +json-seq, then process as
	specified in "xxx/yyy+json-seq".		specified in "xxx/yyy+json-seq".
	Interoperability considerations: n/a		Interoperability considerations: n/a
	Security considerations: See [RFC7464] Section 3		Security considerations: See [RFC7464] Section 3
	Contact: Applications and Real-Time Area Working Group		Contact: Applications and Real-Time Area Discussion
	(art@ietf.org)		(art@ietf.org), or any IESG designated successor.
	Author/Change controller: The Applications and Real-Time Area		Author/Change controller: The Applications and Real-Time Area
	Working Group. IESG has change control over this registration.		Working Group. IESG has change control over this registration.
	5. Security Considerations		5. Security Considerations
	All the security considerations of JSON Text Sequences [RFC7464]		All the security considerations of JSON Text Sequences [RFC7464]
	apply. They are as follows:		apply. They are as follows:
	All the security considerations of JSON [RFC7159] apply. This format		All the security considerations of JSON [RFC7159] apply. This format
	skipping to change at page 5, line 27 ¶		skipping to change at page 5, line 27 ¶
	Structured Syntax Suffixes", RFC 6839,		Structured Syntax Suffixes", RFC 6839,
	DOI 10.17487/RFC6839, January 2013,		DOI 10.17487/RFC6839, January 2013,
	<http://www.rfc-editor.org/info/rfc6839>.		<http://www.rfc-editor.org/info/rfc6839>.
	[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data		[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
	Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March		Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
	2014, <http://www.rfc-editor.org/info/rfc7159>.		2014, <http://www.rfc-editor.org/info/rfc7159>.
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
	Thanks for comments and suggestions provided by Allan Doyle, Warren		Thanks for comments and suggestions provided by Ben Campbell, Allan
	Kumari, Sean Leonard, Alexey Melnikov, and Brian Raymor.		Doyle, Warren Kumari, Sean Leonard, Alexey Melnikov, Brian Raymor,
			and Peter Yee.
	Author's Address		Author's Address
	Erik Wilde		Erik Wilde
	CA Technologies		CA Technologies
	Email: erik.wilde@dret.net		Email: erik.wilde@dret.net
	URI: http://dret.net/netdret/		URI: http://dret.net/netdret/
End of changes. 7 change blocks.
	11 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/