summaryrefslogtreecommitdiff
path: root/internet-draft-satp.txt
diff options
context:
space:
mode:
Diffstat (limited to 'internet-draft-satp.txt')
-rw-r--r--internet-draft-satp.txt126
1 files changed, 63 insertions, 63 deletions
diff --git a/internet-draft-satp.txt b/internet-draft-satp.txt
index 4292da6..88fd5eb 100644
--- a/internet-draft-satp.txt
+++ b/internet-draft-satp.txt
@@ -116,11 +116,11 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
1. Introduction
SATP is somehow a mixture of a generic encapsulation protocol like
- GRE [3] and a secure tunneling protocol as IPsec [4] in tunnel mode.
+ GRE [4] and a secure tunneling protocol as IPsec [5] in tunnel mode.
To save some header overhead it uses the encryption technices of SRTP
[1]. 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 [5]
+ a Host Anycast Service [6]
1.1. Notational Conventions
@@ -249,6 +249,14 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
Figure 2
+ When the unicast hosts wants to transmit data to one of the anycast
+ DNS servers, it encapsulates the data and sends a SATP packet to the
+ anycast address of the routers. The packet arrives at one of the
+ routers, gets decapsulated and routed to the DNS server. This method
+ can be used to tunnel between a clients and networks providing
+ anycast services. It can also be used the other way to virtually
+ locate a unicast service within anycasted networks.
+
2.1.3. redundant tunnel connection of 2 networks
An example of SATP used to connect 2 networks
@@ -265,14 +273,6 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
|de/encapsulated| path |de/encapsulated|
- Figure 3
-
- Network A has multiple routers, that act as gateway/tunnel endpoints
- to another network B. This is done to build a redundant encrypted
- tunnel connection between the two networks. All tunnel endpoints of
- network A share the same anycast address and all tunnel endpoints of
- network B share another anycast address. When a packet from network
- A gets transmitted to network B, it first arrives on one of network
@@ -281,6 +281,14 @@ Gsenger Expires September 2, 2007 [Page 5]
Internet-Draft secure anycast tunneling protocol (satp) March 2007
+ Figure 3
+
+ Network A has multiple routers, that act as gateway/tunnel endpoints
+ to another network B. This is done to build a redundant encrypted
+ tunnel connection between the two networks. All tunnel endpoints of
+ network A share the same anycast address and all tunnel endpoints of
+ network B share another anycast address. When a packet from network
+ A gets transmitted to network B, it first arrives on one of network
A's border routers. Which router is used is determined by network
A's internal routing. This router encapsulates the package and sends
it to the anycast address of the network B routers. The SATP packet
@@ -289,61 +297,23 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
2.2. Encapsulation
- SATP does not depend on which lower layer protocols is used, but it's
- most likely used on top of IP or UDP. This section should only
- discuss some issues on IP and UDP in combination with anycasting and
- tunnels.
+ SATP does not depend on which lower layer protocols is used, but this
+ section gives an example of how packets could look like.
- Examples of SATP used with different lower layer and payload
- protocols
- +------+-----+-------------------------------+
- | | | + ---------------+------ |
- | IPv6 | UDP | SATP | Ethernet 802.3 | ... | |
- | | | +----------------+-----+ |
- +------+-----+-------------------------------+
- Tunneling of Ethernet over UDP/IPv6
- +------+-----+---------------------------+
- | | | +------+-----+-----+ |
- | IPv4 | UDP | SATP | IPv6 | UDP | RTP | |
- | | | +------+-----+-----+ |
- +------+-----+---------------------------+
- Tunneling of IPv6 over UDP/IPv4 with RTP payload
- +------+-------------------------------+
- | | + ---------------+------ |
- | IPv6 | SATP | Ethernet 802.3 | ... | |
- | | +----------------+-----+ |
- +------+-------------------------------+
- Tunneling of Ethernet over IPv6
- +------+---------------------------+
- | | +------+-----+-----+ |
- | IPv4 | SATP | IPv6 | UDP | RTP | |
- | | +------+-----+-----+ |
- +------+---------------------------+
- Tunneling of IPv6 over IPv4 with RTP payload
-Gsenger Expires September 2, 2007 [Page 6]
-
-Internet-Draft secure anycast tunneling protocol (satp) March 2007
-
- Figure 4
- When using UDP no flow control or retransmission is done, neither by
- UDP nor anytun. The encapsulated protocol HAS TO take care of this
- tasks if needed. UDP however has a checksum of the complete UDP
- datagram, so a packet gets discarded if there is a biterror in the
- payload
@@ -362,17 +332,47 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
+Gsenger Expires September 2, 2007 [Page 6]
+
+Internet-Draft secure anycast tunneling protocol (satp) March 2007
+ Examples of SATP used with different lower layer and payload
+ protocols
+ +------+-----+-------------------------------+
+ | | | + ---------------+------ |
+ | IPv6 | UDP | SATP | Ethernet 802.3 | ... | |
+ | | | +----------------+-----+ |
+ +------+-----+-------------------------------+
+ Tunneling of Ethernet over UDP/IPv6
+ +------+-----+---------------------------+
+ | | | +------+-----+-----+ |
+ | IPv4 | UDP | SATP | IPv6 | UDP | RTP | |
+ | | | +------+-----+-----+ |
+ +------+-----+---------------------------+
+ Tunneling of IPv6 over UDP/IPv4 with RTP payload
+ +------+-------------------------------+
+ | | + ---------------+------ |
+ | IPv6 | SATP | Ethernet 802.3 | ... | |
+ | | +----------------+-----+ |
+ +------+-------------------------------+
+ Tunneling of Ethernet over IPv6
+ +------+---------------------------+
+ | | +------+-----+-----+ |
+ | IPv4 | SATP | IPv6 | UDP | RTP | |
+ | | +------+-----+-----+ |
+ +------+---------------------------+
+ Tunneling of IPv6 over IPv4 with RTP payload
+ Figure 4
@@ -406,13 +406,13 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
to occure very frequently, the encapsulated protocol can do a
retransmission and all fragments will arrive at the new server.
+ If the payload ip headers's Don't Fragment (DF) bit is set, than the
+ DF bit of the outer ip header HAS TO be set as well.
+3.2. ICMP messages
-
-
-
-
-
+ ICMP messages MUST be relayed according to rfc2003 section 4 [3].
+ This is needed for path MTU discover
@@ -519,7 +519,7 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
4.7. payload type field
The payload type field defines the payload protocol. ETHER TYPE
- protocol numbers are used. See IANA assigned ethernet numbers [6] .
+ protocol numbers are used. See IANA assigned ethernet numbers [7] .
The values 0000-05DC are reserverd and MUST NOT be used.
Some examples for protocol types
@@ -628,15 +628,18 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
+ [3] Perkins, C., "IP Encapsulation within IP", RFC 2003,
+ October 1996.
+
6.2. Informational References
- [3] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina,
+ [4] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina,
"Generic Routing Encapsulation (GRE)", RFC 2784, March 2000.
- [4] Kent, S. and R. Atkinson, "Security Architecture for the
+ [5] Kent, S. and R. Atkinson, "Security Architecture for the
Internet Protocol", RFC 2401, November 1998.
- [5] Partridge, C., Mendez, T., and W. Milliken, "Host Anycasting
+ [6] Partridge, C., Mendez, T., and W. Milliken, "Host Anycasting
Service", RFC 1546, November 1993.
@@ -665,9 +668,6 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
-
-
-
Gsenger Expires September 2, 2007 [Page 12]
Internet-Draft secure anycast tunneling protocol (satp) March 2007
@@ -675,7 +675,7 @@ Internet-Draft secure anycast tunneling protocol (satp) March 2007
URIs
- [6] <http://www.iana.org/assignments/ethernet-numbers>
+ [7] <http://www.iana.org/assignments/ethernet-numbers>