[Tinyos-2-commits] CVS: tinyos-2.x/doc/html tep125.html,1.4,1.5

[Phil Levis]

Update of /cvsroot/tinyos/tinyos-2.x/doc/html
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv22750/html

Modified Files:
	tep125.html 
Log Message:
TEP 125.


Index: tep125.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep125.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** tep125.html	14 Aug 2007 18:58:00 -0000	1.4
--- tep125.html	13 May 2008 18:38:55 -0000	1.5
***************
*** 299,305 ****
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">2-Feb-2007</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.2</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-04-09</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
--- 299,305 ----
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">2-Feb-2007</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.4</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2008-05-13</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
***************
*** 340,344 ****
  <p>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
  every bit of the packet and does not need to state that it is a TinyOS packet.
  T-Frame stands for &quot;TinyOS Frame.&quot;</p>
--- 340,344 ----
  <p>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 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 &quot;TinyOS Frame.&quot;</p>
***************
*** 362,376 ****
  +-------------------+---------+------------------------------+--------------+
  </pre>
! <p>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.</p>
! <p>The AM type 6lowpan is reserved. A TinyOS program MUST NOT use it.</p>
  </div>
  <div class="section">
  <h1><a id="implementation" name="implementation">4. Implementation</a></h1>
  <p>An implementation of the T-Frame can be found in tinyos-2.x/tos/chips/cc2420.</p>
! <p>An implementation of the I-Frame will soon be found in
! tinyos-2.x/tos/chips/cc2420.</p>
  </div>
  <div class="section">
--- 362,375 ----
  +-------------------+---------+------------------------------+--------------+
  </pre>
! <p>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.</p>
! <p>The AM type 63 is reserved for both T-Frames and I-Frames. A TinyOS
! program MUST NOT use it.</p>
  </div>
  <div class="section">
  <h1><a id="implementation" name="implementation">4. Implementation</a></h1>
  <p>An implementation of the T-Frame can be found in tinyos-2.x/tos/chips/cc2420.</p>
! <p>An implementation of the I-Frame can be found in tinyos-2.x/tos/chips/cc2420.</p>
  </div>
  <div class="section">