diff options
Diffstat (limited to 'papers/draft-gsenger-secure-anycast-tunneling-protocol-02.xml')
| -rw-r--r-- | papers/draft-gsenger-secure-anycast-tunneling-protocol-02.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/papers/draft-gsenger-secure-anycast-tunneling-protocol-02.xml b/papers/draft-gsenger-secure-anycast-tunneling-protocol-02.xml index b34df1e..f74eea1 100644 --- a/papers/draft-gsenger-secure-anycast-tunneling-protocol-02.xml +++ b/papers/draft-gsenger-secure-anycast-tunneling-protocol-02.xml @@ -51,7 +51,7 @@ <middle> <section title='Introduction'> <t>SATP is 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. 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 <xref target="RFC1546">Host Anycast Service</xref>. Encryption is done per packet, so the protocol is robust against packet loss and routing changes. - To reduce header overhead ncryption techniques of <xref target="RFC3711">SRTP</xref> are being used. + To reduce header overhead, encryption techniques of <xref target="RFC3711">SRTP</xref> are being used. </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> |