From 6edcc55bb9bbacf976b6d1693277c6475aee8e20 Mon Sep 17 00:00:00 2001 From: Othmar Gsenger Date: Thu, 19 Apr 2007 11:00:42 +0000 Subject: +html --- internet-draft-satp.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'internet-draft-satp.xml') diff --git a/internet-draft-satp.xml b/internet-draft-satp.xml index 876bbda..f8c1704 100644 --- a/internet-draft-satp.xml +++ b/internet-draft-satp.xml @@ -47,7 +47,7 @@
- SATP is somehow a mixture of an generic encapsulation protocol as GRE and a secure tunneling protocol as IPsec in tunnel mode. To save some header overhead it uses the encryption technices 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 as defined in rfc1546 + SATP is somehow a mixture of an generic encapsulation protocol as GRE and a secure tunneling protocol as IPsec in tunnel mode. To save some header overhead it uses the encryption technices 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
This section gives an overview of possible usage scenarios. Please note, that the protocols used in the figures are only examples and that SATP itself does not care about either transport protocols or encapsulated protocols. Routing is not done by SATP and each implemetation MAY choose it's own way of doing this task (e.g. using functions provided by the operating system). SATP is used only to encapsulate and encrypt data. -- cgit v1.2.3