| TEP: | 4 | +
|---|---|
| Group: | Network Protocol Working Group | +
| Type: | Best Current Practice | +
| Status: | +Draft |
| TinyOS-Version: | 2.x | +
| Author: | +Omprakash Gnawali |
| Draft-Created: | 07-May-2008 | +
| Draft-Version: | 1.6 | +
| Draft-Modified: | 2008-06-20 | +
| Draft-Discuss: | TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu> | +
Note
+This document specifies a Best Current Practices for the +TinyOS Community, and requests discussion and suggestions for +improvements. Distribution of this memo is unlimited. This memo +is in full compliance with [TEP_1].
+In order to document the Active Message Type [1], also known as +Active Message Identifier (AM ID), used by the protocols and to +prevent AM ID conflicts between applications and protocols distributed +with TinyOS 2.x, the application and protocol developers MUST use AM +IDs in the appropriate range. The network protocol implementors MUST +use AM ID allocated by the Network Protocol Working Group for the +specific protocol. The application developers MUST use AM IDs from the +unreserved pool. This TEP describes the process of AM ID allocations +and deallocations and how the allocations are documented.
+The unreserved pool is in the range 128-255 (0x80-0xFF). The reserved +pool is in the range 0-127 (0x00-0x7F).
+When an application uses the AM ID in the range 128-255, it is +guaranteed to not conflict with AM IDs used by the protocols +distributed with TinyOS 2.x. These IDs may conflict with the protocols +in the contrib tree or other applications. No allocation request is +necessary to use AM IDs in this range.
+When a protocol uses an allocated AM ID in the reserved pool, it is +guaranteed to not conflict with AM IDs used by applications or other +protocols that also use an allocated AM ID. The AM ID may conflict +with the protocols and applications in the contrib tree.
+The Network Protocol Working Group will maintain a list of all the +allocations in the reserved range.
+Developers whose protocols will be included within the ''tos'' +directory MUST receive AM ID allocation from the Network Protocol +Working Group. This allocation policy applies to software and +protocols maintained by any working group.
+To receive an AM ID allocation, please send an email to the chair of +Network Protocol Working Group with the following information: +* Working Group responsible for the protocol +* Name of the protocol and relevant TEPs +* Location of the protocol in TinyOS source tree
+Upon receiving this information, the chair of the Network Protocol +Working Group will allocate an AM ID and document the allocation.
+When the working group responsible for maintaining the protocol with +an allocated AM ID obsoletes the protocol, the chair of the working +group should send a deallocation request to the chair of the Network +Protocol Working Group. The chair of the Network Protocol Working +Group will document the deallocation.
+For each TinyOS 2.x release that introduces a new protocol or use of a +new AM ID, the chair of the Network Protocol Working Group creates a +new TEP that lists all the AM ID allocations for that release.
+Thanks to the TinyOS community at large for helping to formulate this +ID allocation policy.
+| [TEP_1] | TEP 1: TEP Structure and Keywords |
| [1] | TEP 116: Packet Protocols |