Network Working Group A. Cullen
Internet-Draft December 29, 2015
Intended status: Experimental
Expires: July 1, 2016
Semantic Data Interface Service -- SDIS/1.0
draft-cullen-sdis-00
Abstract
The Semantic Data Interface Service (SDIS) is a protocol defining a
unified method for Internet services to exchange machine-readable and
human-readable data either publicly or privately to other services or
user agents. SDIS uses an input/output model of data translation
between predefined formats in order to allow consistent communication
between services or user agents without requiring each service or
user agent to interpret the specialized APIs of others. For example,
this protocol could be employed by services or user agents to create
"chains" of interfaces, allowing complex operations to be performed
by connecting an output of a service to an input of another, an
output of the second service to an input of a third, and so on. The
protocol could also be used in conjunction with, for example, a
Bluetooth Low Energy-based protocol to refer mobile devices to SDIS
interfaces depending on location in order to provide content for
augmented reality systems.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 1, 2016.
Cullen Expires July 1, 2016 [Page 1]
Internet-Draft SDIS/1.0 December 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Ideology and Terms . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Interaction over TCP . . . . . . . . . . . . . . . . 3
3.1. Message Format . . . . . . . . . . . . . . . . . . . . . 3
3.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2.1. Handshake . . . . . . . . . . . . . . . . . . . . . . 3
3.2.2. Operation Details . . . . . . . . . . . . . . . . . . 3
3.2.3. Format Details . . . . . . . . . . . . . . . . . . . 3
4. Server Tables . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Operation Table . . . . . . . . . . . . . . . . . . . . . 3
4.2. Format Table . . . . . . . . . . . . . . . . . . . . . . 3
5. Usage Best Practices . . . . . . . . . . . . . . . . . . . . 3
5.1. Data Format Allocation . . . . . . . . . . . . . . . . . 3
5.2. Operation Allocation . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
8. Security Considerations . . . . . . . . . . . . . . . . . . . 3
9. Normative References . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
This document is being discussed on the xyz@example.org mailing list.
Introduction here
Cullen Expires July 1, 2016 [Page 2]
Internet-Draft SDIS/1.0 December 2015
2. Ideology and Terms
3. Protocol Interaction over TCP
3.1. Message Format
3.2. Messages
3.2.1. Handshake
3.2.2. Operation Details
3.2.3. Format Details
4. Server Tables
4.1. Operation Table
4.2. Format Table
5. Usage Best Practices
5.1. Data Format Allocation
5.2. Operation Allocation
6. Acknowledgements
7. IANA Considerations
8. Security Considerations
9. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
Author's Address
Aedan Cullen
Email: asc.cn04@gmail.com
Cullen Expires July 1, 2016 [Page 3]
Html markup produced by rfcmarkup 1.115, available from
https://tools.ietf.org/tools/rfcmarkup/