From 2d4feeaca714c14673a13453367277d306869f05 Mon Sep 17 00:00:00 2001 From: Othmar Gsenger Date: Thu, 21 Jun 2007 17:52:06 +0000 Subject: 64bit sauber gemacht rfc intro --- internet-draft-satp.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'internet-draft-satp.xml') diff --git a/internet-draft-satp.xml b/internet-draft-satp.xml index 83886c2..cf1f91b 100644 --- a/internet-draft-satp.xml +++ b/internet-draft-satp.xml @@ -50,7 +50,9 @@
- SATP is somehow a mixture of a generic encapsulation protocol like GRE and a secure tunneling protocol as IPsec in tunnel mode. To save some header overhead it uses the encryption techniques of SRTP. It supports peer to peer tunnels, where tunnel endpoints can be any combination of unicast, multicast or anycast hosts, so it defines a Host Anycast Service. + SATP is a mixture of a generic encapsulation protocol like GRE and a secure tunneling protocol as IPsec in tunnel mode. It can be used to build redundant virtual private network (VPN) connections. It supports peer to peer tunnels, where tunnel endpoints can be any combination of unicast, multicast or anycast hosts, so it defines a Host Anycast Service. Encryption is done per packet, so the protocol is robust against packet loss and routing changes. + To save some header overhead it uses the encryption techniques of SRTP. +
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119.
-- cgit v1.2.3