From fa5a8c4e6d639cc10f2354479ac369df7907d662 Mon Sep 17 00:00:00 2001 From: scipio Date: Tue, 16 Jan 2007 01:08:26 +0000 Subject: [PATCH] Tweak in text based on CTP workshop 2. --- doc/txt/tep123.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/txt/tep123.txt b/doc/txt/tep123.txt index 7cbf5aa7..60d6cbfa 100644 --- a/doc/txt/tep123.txt +++ b/doc/txt/tep123.txt @@ -130,7 +130,7 @@ The CTP data frame format is as follows:: Field definitions are as follows: - * C: Congestion notification. If a node is receiving packets faster than it can forward them, it MAY set the C field to notify other nodes. If a node hears a packet from node *N* with the C bit set, it MUST NOT transmit CTP data frames to *N* until it hears a packet from N with the C bit cleared. + * C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next data frame it transmits. * 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. * 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. * ETX: The ETX routing metric of the single-hop sender. When a node transmits a CTP data frame, it MUST put the ETX value of its route through the single-hop destination in the ETX field. If a node receives a packet with a lower gradient than its own, then it MUST schedule a routing frame in the near future. @@ -169,7 +169,7 @@ The CTP routing frame format is as follows:: The fields are as follows: - * C: Same as data 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. * P: Same as data frame. * parent: The node's current parent. * metric: The node's current routing metric value. -- 2.39.2