X-Git-Url: https://www.tinc-vpn.org/git/browse?p=tinc;a=blobdiff_plain;f=doc%2FCONNECTIVITY;h=11123ee3e4f20ae02545c30fa14d4da8dded3808;hp=0d11b5cc701d911c60cd46b1275bb10a2afcdab1;hb=d964d84662b73e351b71905a3c743b666a42aa1d;hpb=7926a156e5b118d06295228e57de0cc9de0433b4 diff --git a/doc/CONNECTIVITY b/doc/CONNECTIVITY index 0d11b5cc..11123ee3 100644 --- a/doc/CONNECTIVITY +++ b/doc/CONNECTIVITY @@ -1,7 +1,7 @@ This document describes how nodes in a VPN find and connect to eachother and maintain a stable network. - Copyright 2001-2004 Guus Sliepen + Copyright 2001-2006 Guus Sliepen Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this @@ -12,8 +12,6 @@ maintain a stable network. provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. - $Id$ - 1. Synchronisation ================== @@ -28,7 +26,7 @@ share the same information. It will also almost completely prevent information from looping, because "new" information that is already known is ignored and not forwarded any further. However, since information can also be deleted there's the possibility of a looping sequence of add/delete messages. This is -resolved by additionaly adding a unique identifier to each broadcasted message. +resolved by additionally adding a unique identifier to each broadcasted message. Messages are dropped if the same message with that identifier has already been seen.