From 8e7e5ce90ba23fbc26416d8e95ad1169af0b84d2 Mon Sep 17 00:00:00 2001 From: Othmar Gsenger Date: Fri, 27 Apr 2007 16:08:01 +0000 Subject: toc --- internet-draft-satp.xml | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'internet-draft-satp.xml') diff --git a/internet-draft-satp.xml b/internet-draft-satp.xml index 19aec12..52bb4a1 100644 --- a/internet-draft-satp.xml +++ b/internet-draft-satp.xml @@ -9,6 +9,7 @@ ]> + secure anycast tunneling protocol (satp) @@ -266,6 +267,9 @@ HEX Replay protection is done by a replay list. Every anycast receiver has it's own replay list, which SOULDN'T be syncronised, because of massive overhead. This leads to an additional possible attack. A attacker is able to replay a captured packet once to every anycast reciever. This attack is considered of be very unlikely, because multiple attack hosts in different loactions are needed to reach the seperate anycast receivers and the number of replays is limited to the count of receivers - 1. Such replays might also happen because of routing problems, so a payload protocol HAS TO be robust against a small number of duplicated packages. The window size and position HAS TO be syncronised between multible anycast receivers to limit this attack. +
+ To use the protocol on top of IP, UDP and TCP protocol numberes have to be +
-- cgit v1.2.3