diff options
| -rw-r--r-- | internet-draft-satp.html | 6 | ||||
| -rw-r--r-- | internet-draft-satp.txt | 6 | ||||
| -rw-r--r-- | internet-draft-satp.xml | 4 |
3 files changed, 8 insertions, 8 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> diff --git a/internet-draft-satp.txt b/internet-draft-satp.txt index 8e45c55..6c0b332 100644 --- a/internet-draft-satp.txt +++ b/internet-draft-satp.txt @@ -569,8 +569,9 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007 [2] Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998. - [3] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", - RFC 3068, June 2001. + [3] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. + Norrman, "The Secure Real-time Transport Protocol (SRTP)", + RFC 3711, March 2004. [4] Partridge, C., Mendez, T., and W. Milliken, "Host Anycasting Service", RFC 1546, November 1993. @@ -611,7 +612,6 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007 - Gsenger Expires September 2, 2007 [Page 11] Internet-Draft secure anycast tunneling protocol (satp) March 2007 diff --git a/internet-draft-satp.xml b/internet-draft-satp.xml index f8c1704..7e36bc8 100644 --- a/internet-draft-satp.xml +++ b/internet-draft-satp.xml @@ -47,7 +47,7 @@ </front> <middle> <section title='Introduction'> - <t>SATP is somehow a mixture of an generic encapsulation protocol as <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="RFC3068">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 an generic encapsulation protocol as <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> </section> <section title="Motivation and usage scenarios"> <t>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.</t> @@ -228,7 +228,7 @@ HEX <references> &rfc2784; &rfc2401; - &rfc3068; + &rfc3711; &rfc1546; </references> </back> |