Home Networking (homenet) L. Ruminski
Internet-Draft M. Kutzner
Intended status: Informational A. Dymek
Expires: January 15, 2014 S. Kwiatkowski
July 15, 2013
Grazed and Lightweight Open Protocol (GaLOP), v. 1.0
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance
with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working
documents as Internet-Drafts. The list of current
Internet-Drafts is at
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."
The list of current Internet-Drafts can be accessed at
The list of Internet-Draft Shadow Directories can be accessed at
This Internet-Draft will expire on January 15, 2014.
This informational memo specifies a Grazed and Lightweight Open
Protocol (GaLOP), designed to exchange information within the
Hackney project [HACKNEY]. The document describes messages'
structures, defined message types used in the communication and
standard connection scenarios.
Ruminski Expires January 15, 2014 [Page 1]Internet-Draft GaLOP July 2013
Copyright (c) 2012 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.
The main goal for the protocol is to provide fast and reliable
communication between mobile devices (client software) and
Personal Computer (server software) via Bluetooth with minimal
data size needed to realize full functionality of the project.
The protocol was designed to be easy to extend - adding new
features and developing clients for other mobile platforms
should be as easy as possible.
Conventions used in this document
In examples, "CL:" and "SR:" indicate lines sent by the client
and server respectively.
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 RFC-2119.
The following acronyms are used in this document:
SID - Session Identifier
GID - Gamepad functionality Identifier
DID - Device Identifier
UUID - Universally Unique Identifier
RFCOMM - Radio frequency communication protocol
J2ME - Java Platform, Micro Edition
MT - Message Data Type
PL - Payload
GaLOP in Bluetooth architecture model
By default, protocol uses the communication provided by RFCOMM.
It is assigned to the same middleware layer, as RFCOMM and to
Message data definition
Ruminski Expires January 15, 2014 [Page 2]