separate bcp from doc

[tinyos-2.x.git] / doc / txt / tep4.txt

diff --git a/doc/txt/tep4.txt b/doc/txt/tep4.txt
index fb60916bb0531bf5f84166d9f17d85da5f591d84..6aa4c458c9056944bd9e9e38e67e5765de19c4af 100644 (file)
--- a/doc/txt/tep4.txt
+++ b/doc/txt/tep4.txt
@@ -32,24 +32,25 @@ 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.
+unreserved pool. This TEP describes the process of AM ID allocations
+and deallocations and how the allocations are documented.
 
-2. Current Allocations
+2. AM ID pools
 ====================================================================
 
-The unreserved pool is in the range 0-127 (0x00-0x7F). The reserved
-pool is in the range 128-255 (0x80-0xFF).
+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 (0x00 - 0x7F)
+2.1 Unreserved pool (0x80 - 0xFF)
 ---------------------------------
 
-When an application uses the AM ID in the range 0-127, it is
+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 (0x80 - 0xFF)
+2.2 Reserved pool (0x00 - 0x7F)
 -------------------------------
 
 When a protocol uses an allocated AM ID in the reserved pool, it is
@@ -57,29 +58,6 @@ 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.
 
-Here is a list of current allocations::
-
-  * 0xF0 - 0XFF are reserved for collection protocols maintained by
-    the Network Protocol Working Group.
-
-    0xF0 - CTP routing beacon and LEEP (''tos/lib/net/ctp'', TEP 119, 123, and 124)
-    0xF1 - CTP data packets (''tos/lib/net/ctp'', TEP 119, 123)
-    0xF2 - CTP debug messages (''tos/lib/net/ctp'')
-    0xF3 - MultiHopLQI routing beacon (''tos/lib/net/lqi'')
-    0xF4 - MultiHopLQI data packets (''tos/lib/net/lqi'')
-    0xF5 - MultiHopLQI debug messages (''tos/lib/net/lqi'')
-
-  * 0xE0 - 0xEF are reserved for dissemination protocols maintained by
-    the Network Protocol Working Group.
-
-    0xE0 - Drip (''tos/lib/net/drip'', TEP 118)
-    0xE1 - DIP (''tos/lib/net/dip'', TEP 118)
-
-  * 0xD0 - DYMO (''tos/lib/net/dymo'') maintained by the Network
-    Protocol Working Group.
-
-
-
 3. Requesting AM ID Allocation
 ====================================================================
 
@@ -93,12 +71,12 @@ 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
+* 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 update this TEP.
+Working Group will allocate an AM ID and document the allocation.
 
 4. Reclaiming the AM ID Allocation
 ====================================================================
@@ -107,16 +85,22 @@ 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 update this TEP by deleting the entry for the obsolete
-protocol.
+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.
 
-5. Acknowledgments
+6. Acknowledgments
 ====================================================================
 
 Thanks to the TinyOS community at large for helping to formulate this
 ID allocation policy.
 
-6. Author's Address
+7. Author's Address
 ====================================================================
 
 | Omprakash Gnawali
@@ -127,7 +111,9 @@ ID allocation policy.
 | phone - +1 213 821-5627
 | email - gnawali@usc.edu
 
-7. Citations
+8. Citations
 ====================================================================
 
+.. [TEP_1] TEP 1: TEP Structure and Keywords 
+
 .. [1] TEP 116: Packet Protocols