diff options
| author | Othmar Gsenger <otti@anytun.org> | 2007-04-19 11:04:34 +0000 |
|---|---|---|
| committer | Othmar Gsenger <otti@anytun.org> | 2007-04-19 11:04:34 +0000 |
| commit | 728ef4ad2d31c1e83e32f4e95065d404335209c1 (patch) | |
| tree | 8196f1ef0723ff42d3b7de9de45b72e02a336d2c /internet-draft-satp.html | |
| parent | +html (diff) | |
fixed srtp ref
Diffstat (limited to 'internet-draft-satp.html')
| -rw-r--r-- | internet-draft-satp.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/internet-draft-satp.html b/internet-draft-satp.html index acaa7b2..49d0dd0 100644 --- a/internet-draft-satp.html +++ b/internet-draft-satp.html @@ -186,7 +186,7 @@ Copyright © The IETF Trust (2007).</p> <a name="rfc.section.1"></a><h3>1. Introduction</h3> -<p>SATP is somehow a mixture of an generic encapsulation protocol as <a class='info' href='#RFC2784'>GRE<span> (</span><span class='info'>Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina, “Generic Routing Encapsulation (GRE),” March 2000.</span><span>)</span></a> [1] and a secure tunneling protocol as <a class='info' href='#RFC2401'>IPsec<span> (</span><span class='info'>Kent, S. and R. Atkinson, “Security Architecture for the Internet Protocol,” November 1998.</span><span>)</span></a> [2] in tunnel mode. To save some header overhead it uses the encryption technices of <a class='info' href='#RFC3068'>SRTP<span> (</span><span class='info'>Huitema, C., “An Anycast Prefix for 6to4 Relay Routers,” June 2001.</span><span>)</span></a> [3]. It supports peer to peer tunnels, where tunnel endpoints CAN be any combination of unicast, multicast or anycast hosts, so it defines a <a class='info' href='#RFC1546'>Host Anycast Service<span> (</span><span class='info'>Partridge, C., Mendez, T., and W. Milliken, “Host Anycasting Service,” November 1993.</span><span>)</span></a> [4] +<p>SATP is somehow a mixture of an generic encapsulation protocol as <a class='info' href='#RFC2784'>GRE<span> (</span><span class='info'>Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina, “Generic Routing Encapsulation (GRE),” March 2000.</span><span>)</span></a> [1] and a secure tunneling protocol as <a class='info' href='#RFC2401'>IPsec<span> (</span><span class='info'>Kent, S. and R. Atkinson, “Security Architecture for the Internet Protocol,” November 1998.</span><span>)</span></a> [2] in tunnel mode. To save some header overhead it uses the encryption technices of <a class='info' href='#RFC3711'>SRTP<span> (</span><span class='info'>Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.</span><span>)</span></a> [3]. It supports peer to peer tunnels, where tunnel endpoints CAN be any combination of unicast, multicast or anycast hosts, so it defines a <a class='info' href='#RFC1546'>Host Anycast Service<span> (</span><span class='info'>Partridge, C., Mendez, T., and W. Milliken, “Host Anycasting Service,” November 1993.</span><span>)</span></a> [4] </p> <a name="anchor2"></a><br /><hr /> <a name="rfc.section.2"></a><h3>2. @@ -418,8 +418,8 @@ The appan</h3> <td class="author-text"><a href="mailto:dino@procket.com">Farinacci, D.</a>, <a href="mailto:tony1@home.net">Li, T.</a>, <a href="mailto:stan_hanks@enron.net">Hanks, S.</a>, <a href="mailto:dmm@cisco.com">Meyer, D.</a>, and <a href="mailto:pst@juniper.net">P. Traina</a>, “<a href="ftp://ftp.isi.edu/in-notes/rfc2784.txt">Generic Routing Encapsulation (GRE)</a>,” RFC 2784, March 2000.</td></tr> <tr><td class="author-text" valign="top"><a name="RFC2401">[2]</a></td> <td class="author-text"><a href="mailto:kent@bbn.com">Kent, S.</a> and <a href="mailto:rja@corp.home.net">R. Atkinson</a>, “<a href="ftp://ftp.isi.edu/in-notes/rfc2401.txt">Security Architecture for the Internet Protocol</a>,” RFC 2401, November 1998 (<a href="ftp://ftp.isi.edu/in-notes/rfc2401.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2401.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2401.xml">XML</a>).</td></tr> -<tr><td class="author-text" valign="top"><a name="RFC3068">[3]</a></td> -<td class="author-text">Huitema, C., “<a href="ftp://ftp.isi.edu/in-notes/rfc3068.txt">An Anycast Prefix for 6to4 Relay Routers</a>,” RFC 3068, June 2001.</td></tr> +<tr><td class="author-text" valign="top"><a name="RFC3711">[3]</a></td> +<td class="author-text">Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “<a href="ftp://ftp.isi.edu/in-notes/rfc3711.txt">The Secure Real-time Transport Protocol (SRTP)</a>,” RFC 3711, March 2004.</td></tr> <tr><td class="author-text" valign="top"><a name="RFC1546">[4]</a></td> <td class="author-text"><a href="mailto:craig@bbn.com">Partridge, C.</a>, <a href="mailto:tmendez@bbn.com">Mendez, T.</a>, and <a href="mailto:milliken@bbn.com">W. Milliken</a>, “<a href="ftp://ftp.isi.edu/in-notes/rfc1546.txt">Host Anycasting Service</a>,” RFC 1546, November 1993.</td></tr> </table> |