In order to document the Active Message Type [1], also known as +
In order to document the Active Message Type [TEP_116], 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 @@ -357,9 +357,13 @@ protocols maintained by any working group.
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.
+* Location of the protocol in TinyOS source tree +* Number of AM IDs requested and description of each ID +* Specific AM ID request (only if necessary) +Upon receiving this request, the chair of the Network Protocol Working +Group will allocate the AM ID(s) and document the allocation. If the +request is made for a specific AM ID, the chair of the Network +Protocol Work Group will try to accommodate that request.
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.
+new Informational TEP that lists all the AM ID allocations for that +release. The TEP is finalized at the time of the release. [TEP_135] +documents the AM IDs allocated for TinyOS 2.1.| [1] | TEP 116: Packet Protocols |
| [TEP_116] | TEP 116: Packet Protocols |
| [TEP_135] | TEP 135: Active Message ID Allocation in TinyOS 2.1 |