Note how T-Frames and I-Frames selected.

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

diff --git a/doc/txt/tep125.txt b/doc/txt/tep125.txt
index dc7cc0af0e355fb9f5d65b7798efbfcc8cc663f6..f7b1955ff34bfcda26e6b6dc740db85223b5b026 100644 (file)
--- a/doc/txt/tep125.txt
+++ b/doc/txt/tep125.txt
@@ -36,13 +36,13 @@ The TinyOS 2.0 active message layer adds a packet field for higher-level
 protocol dispatch. This document describes the two TinyOS 2.0 frame format
 for 802.15.4 networks. The first format is for isolated TinyOS networks;
 the second format is for networks that share the spectrum with 6lowpan
-networks[1_].
+networks[1]_.
 
 2. 802.15.4
 ====================================================================
 
 802.15.4 supports several different source and destination addressing
-modes, and so has a variable sized packet header.[2_] A TinyOS device MUST
+modes, and so has a variable sized packet header.[2]_ A TinyOS device MUST
 support packet frames with 16-bit short source and destination addresses.
 A TinyOS device MAY support additional 802.15.4 frame formats. 
 
@@ -51,7 +51,7 @@ A TinyOS device MAY support additional 802.15.4 frame formats.
 
 TinyOS has two 802.15.4 frame formats. The first format, the T-Frame, is
 for TinyOS networks which do not share their channel with other wireless
-networking archtiectures. This frame format assumes that TinyOS can use
+networking architectures. This frame format assumes that TinyOS can use
 every bit of the packet and does not need to state that it is a TinyOS packet.
 T-Frame stands for "TinyOS Frame."
 
@@ -76,25 +76,30 @@ The TinyOS 802.15.4 I-frame format is as follows::
   | 802.15.4 Header   | 6lowpan | AM type |        data        | 802.15.4 CRC |
   +-------------------+---------+------------------------------+--------------+
 
-AM type is the same as in a T-frame. 6lowpan is the IANA-assigned code
-to identify this as a TinyOS packet. At this time, the exact value of
-this code has not been determined. To inform 6lowpan that this is not
-a 6lowpan packet, the code used MUST be in the range of 192-55.
+AM type is the same as in a T-frame. 6lowpan is the NALP code to identify 
+this as a TinyOS packet. NALP codes must be in the range of 0-63.
+TinyOS uses code 63.
 
+The AM type 63 is reserved for both T-Frames and I-Frames. A TinyOS 
+program MUST NOT use it.
 
 4. Implementation
 ====================================================================
 
-An implementation of the T-Frame can be found in tinyos-2.x/tos/chips/cc2420.
+An implementation of T-Frames and I-Frames can be found in
+tinyos-2.x/tos/chips/cc2420/.  The components in
+tos/chips/cc2420/lowpan/ control which is used. By default, TinyOS
+802.15.4 stacks use I-Frames, and the 'tframe' make option configures
+them to use T-Frames. This make option defines a symbol named
+``TFRAMES_ENABLED``. In the case of the CC2420 stack, this causes
+``CC2420.h`` to define ``CC2420_IFRAME_TYPE``, which adds the extra
+byte to the message_t header structure.
+
 
-An implementation of the I-Frame will soon be found in 
-tinyos-2.x/tos/chips/cc2420.
 
 5. Author Addresses
 ====================================================================
 
-
-|
 | Jonathan Hui
 | 657 Mission St. Ste. 600
 | Arched Rock Corporation
@@ -112,7 +117,10 @@ tinyos-2.x/tos/chips/cc2420.
 | email - pal@cs.stanford.edu
 |
 | David Moss
-| Rincon Research
-|
-|
+| Rincon Research Corporation
+| 101 N. Wilmot, Suite 101
+| Tucson, AZ  85750
 |
+| phone - +1 520 519 3138
+| email - dmm@rincon.com
+