From c99c2593aa73dddbf535f005d55f374265ad18e9 Mon Sep 17 00:00:00 2001
From: Othmar Gsenger <otti@anytun.org>
Date: Mon, 18 Jun 2007 15:43:14 +0000
Subject: typo

---
 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 3c15f4d..9b65f16 100644
--- a/internet-draft-satp.xml
+++ b/internet-draft-satp.xml
@@ -50,7 +50,7 @@
     </front>
     <middle>
     <section title='Introduction'>
-        <t>SATP is somehow a mixture of a generic encapsulation protocol like <xref target="RFC2784">GRE</xref> and a secure tunneling protocol as <xref target="RFC2401">IPsec</xref> in tunnel mode. To save some header overhead it uses the encryption technices of <xref target="RFC3711">SRTP</xref>. It supports peer to peer tunnels, where tunnel endpoints can be any combination of unicast, multicast or anycast hosts, so it defines a <xref target="RFC1546">Host Anycast Service</xref></t>
+        <t>SATP is somehow a mixture of a generic encapsulation protocol like <xref target="RFC2784">GRE</xref> and a secure tunneling protocol as <xref target="RFC2401">IPsec</xref> in tunnel mode. To save some header overhead it uses the encryption techniques of <xref target="RFC3711">SRTP</xref>. It supports peer to peer tunnels, where tunnel endpoints can be any combination of unicast, multicast or anycast hosts, so it defines a <xref target="RFC1546">Host Anycast Service</xref>.</t>
       <section title='Notational Conventions'>
         <t>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  <xref target="RFC2119">RFC2119</xref>.</t>
        </section>
-- 
cgit v1.2.3