[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep123.txt,1.14,1.15

[Omprakash Gnawali]

Update of /cvsroot/tinyos/tinyos-2.x/doc/txt
In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv2162

Modified Files:
	tep123.txt 
Log Message:
finalize

Index: tep123.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep123.txt,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** tep123.txt	7 Jan 2009 22:08:22 -0000	1.14
--- tep123.txt	16 Jan 2009 19:50:47 -0000	1.15
***************
*** 6,11 ****
  :Group: Network Working Group 
  :Type: Documentary
! :Status: Draft
! :TinyOS-Version: 2.x
  :Author: Rodrigo Fonseca, Omprakash Gnawali, Kyle Jamieson, Sukun Kim, Philip Levis, and Alec Woo
  
--- 6,11 ----
  :Group: Network Working Group 
  :Type: Documentary
! :Status: Final
! :TinyOS-Version: > 2.1
  :Author: Rodrigo Fonseca, Omprakash Gnawali, Kyle Jamieson, Sukun Kim, Philip Levis, and Alec Woo
  
***************
*** 45,48 ****
--- 45,50 ----
  inconsistencies.
  
+ All fields in this specification are in network byte order.
+ 
  2. Assumptions and Limitations
  ==============================================================================
***************
*** 153,157 ****
  Field definitions are as follows:
  
!   * P: Routing pull. The P bit allows nodes to request routing information from other nodes. If a node with a valid route hears a packet with the P bit set, it SHOULD transmit a routing frame in the near future. Data frames are unicast so only the destination of the unicast transmission responds to the P bit in the data frame.
    * C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next data frame it transmits.
    * THL: Time Has Lived. When a node generates a CTP data frame, it MUST set THL to 0. When a node receives a CTP data frame, it MUST increment the THL. If a node receives a THL of 255, it increments it to 0.
--- 155,159 ----
  Field definitions are as follows:
  
!   * P: Routing pull. The P bit allows nodes to request routing information from other nodes. If the unicast destination of the data frame with a valid route hears a packet with the P bit set, it SHOULD transmit a routing frame in the near future. Nodes other than the link-layer destination of the data frame MAY respond to the P bit in the data frame.
    * C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next data frame it transmits.
    * THL: Time Has Lived. When a node generates a CTP data frame, it MUST set THL to 0. When a node receives a CTP data frame, it MUST increment the THL. If a node receives a THL of 255, it increments it to 0.
***************
*** 162,168 ****
    * data: the data payload, of zero or more bytes. A node forwarding a data frame MUST NOT modify the data payload. The length of the data field is computed by subtracting the size of the CTP header from the size of the link layer payload provided by the link layer.
  
- Note that the two 16-bit fields, ETX and origin, appear in network
- byte-order in the data frame.
- 
  Together, the origin, seqno and collect_id fields denote a unique 
  ***origin packet.*** Together, the origin, seqno, collect_id, and
--- 164,167 ----
***************
*** 195,206 ****
  The fields are as follows:
    
!   * P: Same as data frame with one difference: Routing frames are broadcast so multiple nodes respond to the P bit in the routing frame. Thus, the P bit in the routing frame can be used for quick bootstrapping of the routes: when a node boots up and sends a frame with the P bit set, the neighboring nodes can quickly transmit routing frames advertising their routes enabling the new node to quickly compute the route to the sink.
    * C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next routing frame it transmits.
    * parent: The node's current parent.
    * metric: The node's current routing metric value.
  
- Note that the two 16-bit fields, parent and ETX, appear in network
- byte-order in the routing frame.
- 
  When a node hears a routing frame, it MUST update its routing table to
  reflect the address' new metric. If a node's ETX value changes
--- 194,202 ----
  The fields are as follows:
    
!   * P: Same as data frame with one difference: Routing frames are broadcast so multiple nodes respond to the P bit in the routing frame.
    * C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next routing frame it transmits.
    * parent: The node's current parent.
    * metric: The node's current routing metric value.
  
  When a node hears a routing frame, it MUST update its routing table to
  reflect the address' new metric. If a node's ETX value changes
***************
*** 371,375 ****
  |
  | email - awoo at archrock.com
! 
  
  8. Citations
--- 367,380 ----
  |
  | email - awoo at archrock.com
! |
! |
! | Sukun Kim
! | Samsung Electronics
! | 416 Maetan-3-dong, Yeongtong-Gu
! | Suwon, Gyeonggi 443-742
! | Korea, Republic of
! |
! | phone - +82 10 3065 6836
! | email - sukun.kim at samsung.com
  
  8. Citations