Permalink
Browse files

more lapses

  • Loading branch information...
1 parent 613e450 commit e0ee4b6a23fe4ed21de6b75c8e9c42220e14e74c @gritzko committed Apr 13, 2010
Showing with 26 additions and 25 deletions.
  1. +2 −1 doc/draft-ietf-ppsp-grishchenko-swift.nroff
  2. +24 −24 doc/draft-ietf-ppsp-grishchenko-swift.txt
@@ -476,6 +476,7 @@ message (type 7) to announce the fact:
.ti 0
4.5. Peer exchange and NAT hole punching
+.fi
Peer exchange messages are common for many peer-to-peer protocols. By exchanging peer IP addresses in gossip fashion, peers relieve central coordinating entities (the trackers) from unnecessary work. Following the example of BitTorrent, swift features two types of PEX messages: "peer connected" (type 5) and "peer disconnected" (type 6). Peers are represented as IPv4 address-port pairs:
.nf
05 7F000000 1F40
@@ -563,7 +564,7 @@ The most theoretically correct way is to run swift on top of IP, as another tran
.ti 0
5.2. UDP
-.nf
+.fi
Currently, swift-over-UDP is the default deployment option. Effectively, UDP allows to use IP with minimal overhead, it also allows userspace implementations.
Besides the classic 1KB packet scenario, the bin numbering allows to use swift over Jumbo frames/datagrams. Both data and acknowledgments may use e.g. 8KB packets instead of "standard" 1KB. Hashing scheme stays the same.
Using swift with 512 or 256-byte packets is theoretically possible with 64-bit byte-precise bin numbers, but IP fragmentation might be a better method to achieve the same result.
@@ -636,7 +636,12 @@ Internet-Draft swift April 2010
4.5. Peer exchange and NAT hole punching
- Peer exchange messages are common for many peer-to-peer protocols. By exchanging peer IP addresses in gossip fashion, peers relieve central coordinating entities (the trackers) from unnecessary work. Following the example of BitTorrent, swift features two types of PEX messages: "peer connected" (type 5) and "peer disconnected" (type 6). Peers are represented as IPv4 address-port pairs:
+ Peer exchange messages are common for many peer-to-peer protocols. By
+ exchanging peer IP addresses in gossip fashion, peers relieve central
+ coordinating entities (the trackers) from unnecessary work. Following
+ the example of BitTorrent, swift features two types of PEX messages:
+ "peer connected" (type 5) and "peer disconnected" (type 6). Peers are
+ represented as IPv4 address-port pairs:
05 7F000000 1F40
(connected to 127.0.0.1:8000)
@@ -661,11 +666,6 @@ Internet-Draft swift April 2010
certain ranges of data (e.g. BitTorrent's REQUEST message), live
streaming protocols quite often do without to save round trips.
Explicit requests are often needed for security purposes; consider
- that BitTorrent can only verify hashes of complete pieces that might
- consist of multiple blocks requested from many peers. As swift has no
- such implications, it is supposed to work both ways. Namely, a peer
- SHOULD send out requested pieces, while it also may send some other
- data in case it runs out of requests or on some other reason. To
@@ -674,6 +674,11 @@ Grishchenko Expires October 12, 2010 [Page 12]
Internet-Draft swift April 2010
+ that BitTorrent can only verify hashes of complete pieces that might
+ consist of multiple blocks requested from many peers. As swift has no
+ such implications, it is supposed to work both ways. Namely, a peer
+ SHOULD send out requested pieces, while it also may send some other
+ data in case it runs out of requests or on some other reason. To
emphasize that, request messages are named HINTs; their only purpose
is to coordinate peers and to avoid unnecessary data retransmission.
A peer SHOULD to process HINTs sequentially. HINT message type is 8.
@@ -717,11 +722,6 @@ Internet-Draft swift April 2010
implementation for all peers.
-5.2. UDP
-
- Currently, swift-over-UDP is the default deployment option. Effectively, UDP allows to use IP with minimal overhead, it also allows userspace implementations.
- Besides the classic 1KB packet scenario, the bin numbering allows to use swift over Jumbo frames/datagrams. Both data and acknowledgments may use e.g. 8KB packets instead of "standard" 1KB. Hashing scheme stays the same.
- Using swift with 512 or 256-byte packets is theoretically possible with 64-bit byte-precise bin numbers, but IP fragmentation might be a better method to achieve the same result.
@@ -730,6 +730,19 @@ Grishchenko Expires October 12, 2010 [Page 13]
Internet-Draft swift April 2010
+5.2. UDP
+
+ Currently, swift-over-UDP is the default deployment option.
+ Effectively, UDP allows to use IP with minimal overhead, it also
+ allows userspace implementations. Besides the classic 1KB packet
+ scenario, the bin numbering allows to use swift over Jumbo
+ frames/datagrams. Both data and acknowledgments may use e.g. 8KB
+ packets instead of "standard" 1KB. Hashing scheme stays the same.
+ Using swift with 512 or 256-byte packets is theoretically possible
+ with 64-bit byte-precise bin numbers, but IP fragmentation might be a
+ better method to achieve the same result.
+
+
5.3. TCP
If ran over TCP, the swift becomes functionally equivalent to
@@ -765,19 +778,6 @@ Internet-Draft swift April 2010
-
-
-
-
-
-
-
-
-
-
-
-
-

0 comments on commit e0ee4b6

Please sign in to comment.