From: scipio Date: Fri, 20 Jun 2008 19:12:21 +0000 (+0000) Subject: AM ID TEPs. X-Git-Tag: release_tinyos_2_1_0_0~220 X-Git-Url: https://oss.titaniummirror.com/gitweb/?p=tinyos-2.x.git;a=commitdiff_plain;h=2985cd60836a567923285e2903a11c0225101df1 AM ID TEPs. --- diff --git a/doc/html/tep135.html b/doc/html/tep135.html new file mode 100644 index 00000000..41f1192a --- /dev/null +++ b/doc/html/tep135.html @@ -0,0 +1,399 @@ + + + + + + +Active Message ID Allocation in TinyOS 2.1 + + + + +
+

Active Message ID Allocation in TinyOS 2.1

+ +++ + + + + + + + + + + + + + + + + + + + + + +
TEP:135
Group:Network Protocol Working Group
Type:Documentary
Status:Draft
TinyOS-Version:2.1
Author:Omprakash Gnawali
Draft-Created:19-June-2008
Draft-Version:1.1
Draft-Modified:2008-06-20
Draft-Discuss:TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu>
+
+

Note

+

This memo documents a part of TinyOS 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] and [TEP_4].

+
+
+

1. Introduction

+

In this TEP, we document the Active Message Type [1] allocations +in TinyOS 2.1.

+
+

2. Unreserved pool (0x80 - 0xFF)

+

The unreserved pool is in the range 128-255 (0x80-0xFF). Applications +distributed with TinyOS use AM IDs in this range. Protocols and +applications in contrib as well as those developed by the community +but not included in the distribution or contrib SHOULD use AM IDs in +this range.

+
+
+

3. Reserved pool (0x00 - 0x7F)

+

The reserved pool is in the range 0-127 (0x00-0x7F). The AM IDs in +this range are used by protocols distributed with TinyOS.

+

Here is a list of allocations for TinyOS 2.1:

+
+* 0x70 - 0x7F are reserved for collection protocols maintained by
+  the Network Protocol Working Group.
+
+  0x70 - CTP routing beacon and LEEP (''tos/lib/net/ctp'', TEP 119, 123, and 124)
+  0x71 - CTP data packets (''tos/lib/net/ctp'', TEP 119, 123)
+  0x72 - CTP debug messages (''tos/lib/net/ctp'')
+  0x73 - MultiHopLQI routing beacon (''tos/lib/net/lqi'')
+  0x74 - MultiHopLQI data packets (''tos/lib/net/lqi'')
+  0x75 - MultiHopLQI debug messages (''tos/lib/net/lqi'')
+
+* 0x60 - 0x6F are reserved for dissemination protocols maintained by
+  the Network Protocol Working Group.
+
+  0x60 - Drip (''tos/lib/net/drip'', TEP 118)
+  0x61 - DIP (''tos/lib/net/dip'', TEP 118)
+
+* 0x50 - 0x5F are reserved for Deluge (''tos/lib/net/Deluge'')
+  maintained by the Network Protocol Working Group.
+
+  0x50 - AM_DELUGEADVMSG (advertisements)
+  0x51 - AM_DELUGEREQMSG (requests)
+  0x52 - AM_DELUGEDATAMSG (data)
+  0x53 - DELUGE_AM_FLASH_VOL_MANAGER (flash volume manager)
+  0x54 - DELUGE_AM_DELUGE_MANAGER (deluge manger)
+
+* 0x3F - TinyOS NALP code (TEP 125) reserved by the Core Working
+  Group.
+
+
+
+
+

4. Author's Address

+
+
Omprakash Gnawali
+
Ronald Tutor Hall (RTH) 418
+
3710 S. McClintock Avenue
+
Los Angeles, CA 90089
+

+
phone - +1 213 821-5627
+
email - gnawali@usc.edu
+
+
+
+

5. Citations

+ + + + + +
[TEP_1]TEP 1: TEP Structure and Keywords
+ + + + + +
[TEP_4]TEP 4: Active Message ID Allocation for Network Protocols and Applications
+ + + + + +
[1]TEP 116: Packet Protocols
+
+
+ + diff --git a/doc/html/tep4.html b/doc/html/tep4.html new file mode 100644 index 00000000..dcb02c7f --- /dev/null +++ b/doc/html/tep4.html @@ -0,0 +1,412 @@ + + + + + + +Active Message ID Allocation for Network Protocols and Applications + + + + +
+

Active Message ID Allocation for Network Protocols and Applications

+ +++ + + + + + + + + + + + + + + + + + + + + + +
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].

+
+
+

1. Introduction

+

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.

+
+
+

2. AM ID pools

+

The unreserved pool is in the range 128-255 (0x80-0xFF). The reserved +pool is in the range 0-127 (0x00-0x7F).

+
+

2.1 Unreserved pool (0x80 - 0xFF)

+

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.

+
+
+

2.2 Reserved pool (0x00 - 0x7F)

+

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.

+
+
+
+

3. Requesting AM ID Allocation

+

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.

+
+
+

4. Reclaiming the AM ID 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.

+
+
+

5. Documenting allocations and deallocations

+

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.

+
+
+

6. Acknowledgments

+

Thanks to the TinyOS community at large for helping to formulate this +ID allocation policy.

+
+
+

7. Author's Address

+
+
Omprakash Gnawali
+
Ronald Tutor Hall (RTH) 418
+
3710 S. McClintock Avenue
+
Los Angeles, CA 90089
+

+
phone - +1 213 821-5627
+
email - gnawali@usc.edu
+
+
+
+

8. Citations

+ + + + + +
[TEP_1]TEP 1: TEP Structure and Keywords
+ + + + + +
[1]TEP 116: Packet Protocols
+
+
+ +