Gnutella2 - User contributions [en]

User:Ag/monobook.js

2007-10-03T22:18:38Z

Ag:

User:Ag/monobook.js

2007-10-03T22:11:04Z

Ag:

importScript('User:AzaToth/twinkle.js');
TwinkleConfig = {
revertMaxRevisions : 50,
userTalkPageMode : 'window',
showSharedIPNotice : true,
openTalkPage : [ 'agf', 'norm', 'vand' ],
openTalkPageOnAutoRevert : false,
openAOLAnonTalkPage : false,
summaryAd : " using [[WP:TWINKLE|TW]]",
deletionSummaryAd : " using [[WP:TWINKLE|TW]]",
protectionSummaryAd : " using [[WP:TWINKLE|TW]]",
watchSpeedyPages : [ 'g3', 'g5', 'g10', 'g11', 'g12' ],
watchProdPages : true,
openUserTalkPageOnSpeedyDelete : [ 'g1', 'g2', 'g10', 'g11', 'g12', 'a1', 'a7', 'i3', 'i4', 'i5', 'i6', 'i7', 'u3', 't1' ],
watchRevertedPages : [ 'agf', 'norm', 'vand', 'torev' ],
markRevertedPagesAsMinor : [ 'agf', 'norm', 'vand', 'torev' ],
deleteTalkPageOnDelete : false,
watchWarnings : true,
markAIVReportAsMinor : true,
markSpeedyPagesAsMinor : true,
offerReasonOnNormalRevert : true,
orphanBacklinksOnSpeedyDelete : {orphan:true, exclude:['g6']}
};

User:Ag

2007-10-03T22:08:10Z

Ag:

Umm, hello.

URN

2007-09-27T23:17:13Z

Ag:

==Uniform Resource Name==

A Uniform Resource Name is used to identify a file on the network by providing a unique key (taken from the files hash).

===Examples:===

urn:sha1:YNCKHTQCWBTRNJIV4WNAE52SJUQCZO5C
:A URN representing a specific MP3 file of the "I have a dream" speech by Martin Luther King, using the files [[SHA1]] hash.

urn:tree:tiger:BL5OM7M75DWHAXMFZFJ23MU3LVMRXKFO6HTGUTY
:The URN of the same file, this time using it's [[TigerTree]] root hash.

SHA1

2007-09-27T22:51:40Z

Ag:

== SHA1 ==

===More information:===

[http://en.wikipedia.org/wiki/SHA-1 SHA hash functions (Wikipedia)]

[http://www.faqs.org/rfcs/rfc3174.html US Secure Hash Algorithm 1 (SHA1) (RFC3174)]

TigerTree

2007-09-27T22:41:28Z

Ag:

== Tiger-Tree Hashing ==
Tiger-Tree Hashing is a way of verifying that small pieces of a file are valid, and free from corruption. Without a system such as TTH, an application would be unable to locate where corruption was occurring in a file, and would not be able to repair the errors.

In a tree hash, a file is broken up into small pieces, and each small piece of a file is hashed. These pieces are divided into sets according to some simple rules, and the hashes in each of these sets concatenated and hashed again. The process can be repeated some number of times (hence the diagram of a tree), until there remains one hash, called the root hash.

Refer to the [http://www.open-content.net/specs/draft-jchapweske-thex-02.html THEX protocol] for in depth infromation about Tree Hash EXchange and tree hashes in general. Refer to the [http://www.cs.technion.ac.il/~biham/Reports/Tiger/ Tiger Hash web page] for information about the Tiger Hash algorithm. Refer to the [http://sourceforge.net/projects/tigertree/ TigerTree project page on sourceforge] for the specifics on how the tiger hash algorithm has been implemented into a Merkle hash tree structure to create 'Tiger-Tree' hash sets.

Note that when encountering the word 'Tiger-Tree', an author may sometimes be referring to the Tiger Tree root hash, or at other times the entire hash tree structure.

Gnutella2-powered software

2007-09-23T15:42:22Z

Ag: /* Gnutella2 Clients */

==Gnutella2 Clients==

The following clients support Gnutella2:

<table width="100%" border="0" cellpadding="6" cellspacing="1" bgcolor="#A5CAD2">
<tr>
<th width="55%">Client Name</th>
<th width="23%">Platform</th>
<th width="22%">Support</th>
</tr>
<tr align="left" valign="top">
<td bgcolor="#FFFFFF">[http://www.shareaza.com Shareaza]<br>
Shareaza pioneered the Gnutella2 platform and continues to play an active role in its development. Connects to several additional networks as well.</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">Windows</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">Full 1.0 Support</td>
</tr>

<tr align="left" valign="top">
<td bgcolor="#F2F2F2">[http://www.gnucleus.com/ Gnucleus]<br>
Gnucleus is one of the first Gnutella clients and is an open source Gnutella2 client. It is based on GnucDNA, a Gnutella2 library.</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">Windows</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">Full 1.0 Support</td>
</tr>

<tr align="left" valign="top" class="normal">
<td bgcolor="#FFFFFF">[http://www.morpheus.com/ Morpheus]<br>
Morpheus is a mainstream P2P client which switched from the FastTrack network to the Gnutella network and now to the Gnutella2 network.</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">Windows</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">Uses GnucDNA</td>
</tr>

<tr align="left" valign="top">
<td bgcolor="#F2F2F2">[http://sourceforge.net/projects/agio/ Adagio]<br>
Adagio is a Gnutella2 server which aims to provide a very configurable, highly reliable cross-platform daemon.</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">Cross-Platform</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">1.0 Support</td>
</tr>

<tr align="left" valign="top">
<td bgcolor="#FFFFFF">[http://www.kiwialpha.com/ Kiwi]<br>
Lightweight client, based on GnucDNA</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">Windows</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">Uses GnucDNA</td>
</tr>

<tr align="left" valign="top">
<td bgcolor="#F2F2F2">[http://www.filescope.com/ FileScope]<br>
FileScope is a file sharing program that connects to multiple peer-to-peer (P2P) networks and allows for finding and downloading all types of files. Written in C#.</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">Windows</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">1.0 Support (Beta)</td>
</tr>

<tr align="left" valign="top">
<td bgcolor="#FFFFFF">[http://www.mldonkey.net/ MLDonkey]<br>
An open source deamon client. Has many different GUI's you can use. Also connects to many other networks in addition to Gnutella2.</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">Cross-Platform</td>
<td align="center" valign="middle" bgcolor="#FFFFFF">1.0 Support (Beta)</td>
</tr>

<tr align="left" valign="top">
<td bgcolor="#F2F2F2">[http://www.pocketg2.com/ Pocket G2]<br>
Pocket G2 is a Gnutella2 client written in VB.net for Pocket PCs.</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">Windows Mobile</td>
<td align="center" valign="middle" bgcolor="#F2F2F2">1.0 Support (Alpha)</td>
</tr>

</table>

TCP Stream Connection and Handshaking

2007-09-20T20:34:08Z

Ag: /* Node State Negotiation */

[[UDP_Transceiver|UDP Transceiver >>]] | [[Main_Page|Main Page]]

== Introduction ==

TCP stream connections are established between Gnutella2 nodes when they elect to
form a permeant link, creating the fundamental network topology of a highly
interconnected hub network serving dense clusters of leaf nodes.

== Initiation ==

TCP connections are initiated by leaf or hub nodes in an attempt to gain a connection
to a hub node. Leaf nodes are never the target of an outbound connection. The TCP
port number is not standardised, and must be stored with the IP address.

== Handshaking ==

Upon the establishment of a TCP stream connection between two Gnutella2 nodes, a
handshaking phase must be completed to negotiate the nature of the link and
exchange other necessary information.

This handshaking phase is the only part of the communication which remains
compatible with the old Gnutella network, allowing new connections to be negotiated
without fore-knowledge the capabilities of the other node. The handshaking process
has been well documented elsewhere, however, a short summary is provided here.

=== Handshake Stages ===

The Gnutella handshake process consists of three header blocks. The node which
initiated the connection sends an initial header block, of the form:

<pre>
<nowiki>
GNUTELLA CONNECT/0.6
Listen-IP: 1.2.3.4:6346
Remote-IP: 6.7.8.9
User-Agent: Shareaza 1.8.2.0
Accept: application/x-gnutella2
X-Hub: False
</nowiki>
</pre>

The receiver then responds with its own header block:

<pre>
<nowiki>
GNUTELLA/0.6 200 OK
Listen-IP: 6.7.8.9:6346
Remote-IP: 1.2.3.4
User-Agent: Shareaza 1.8.2.0
Content-Type: application/x-gnutella2
Accept: application/x-gnutella2
X-Hub: True
X-Hub-Needed: False
</nowiki>
</pre>

Finally, the initiator accepts the receiver's header block, and provides any final
information:

<pre>
<nowiki>
GNUTELLA/0.6 200 OK
Content-Type: application/x-gnutella2
X-Hub: False
</nowiki>
</pre>

The latter two stages may be replaced with an error condition if the connection is
being rejected. Appropriate error status codes are returned in this case, for example:

<pre>
<nowiki>
GNUTELLA/0.6 503 Too many connections
(more headers)
</nowiki>
</pre>

Note that only the HTTP-style error code should be interpreted by the software: any
descriptive text provided is for display purposes only and is not standardised.

== Headers ==

Important headers which are required or strongly recommended are detailed in the
following sections.

=== Addressing Headers ===

Two important headers to send on all connections are "Remote-IP" and "Listen-IP".
Both of these headers should be sent on the first transmission, meaning in the first
and second header blocks in the three block exchange.

The Remote-IP header contains the IP address from which the remote host is
connecting. This allows a remote host operating through some kind of network
address translation system, to learn its effective external address.

The Listen-IP header contains the IP address and port number that the local host is
listening for inbound TCP connections on. It should be listening for UDP datagrams
on the same port. The format of this header is "IP:PORT", eg "1.2.3.4:6346".

=== Identification ===

The User-Agent header is used to identify the client software operating on the
sending node. It should be sent on the first transmission, meaning in the first and
second header blocks in the three block exchange. Note that this is a descriptive
string that often includes a version number, and is not a "vendor code" as described
elsewhere.

=== Content Type (Protocol) ===

The Accept and Content-Type header exchange is used to negotiate the data
protocol that will be used in the connection, in this case Gnutella2. The Gnutella2
content type is "application/x-gnutella2", and this exchange follows standard HTTP
rules for negotiating content type.

The first step is to advertise support for the content type (Gnutella2) in the first
header block with "Accept: application/x-gnutella2". The responding node will then
indicate that it will send Gnutella2 content with "Content-Type: application/x-gnutella2",
and that it also supports Gnutella2 with "Accept: application/x-gnutella2".
The initiating host then confirms that it will be sending Gnutella2 with "Content-
Type: application/x-gnutella2" in the third header block. For more information on the
Accept/Content-Type exchange, consult a HTTP reference.

Note that the content type negotiation process is designed to be a "one-way"
process, i.e. a different content type can be negotiated for sending and receiving.
However, when the gnutella2 protocol is negotiated, both channels must use the
same content type. This means that a receiving node must not accept Gnutella2 if
the initiator did not advertise support for it, and if at the end of the handshake,
bidirectional Gnutella2 was not negotiated, the connection should be terminated.

=== Node State Negotiation ===

There are two node types in a Gnutella2 peer to peer network, a hub and a leaf, as
described in [[Node Types and Responsibilities]]. During the initial handshake,
the two parties must exchange their current node type and advise of their
capabilities, negotiating the node types they will adopt when the connection
completes, and indeed whether it should complete at all.

As the handshake sequence is compatible with Gnutella1, the headers involved in
negotiating node types should not be identical to those used to negotiate Gnutella1 to minimize network pollution.
states:

<pre>
<nowiki>
X-Hub: [True|False]
X-Hub-Needed: [True|False]
</nowiki>
</pre>

Both headers contain a Boolean value, "true" or "false", case insensitive.

The X-Hub header indicates whether the transmitting node is currently
operating as a hub. Hub nodes will send "X-Hub: True" while leaf nodes will
send "X-Hub: False".

The X-Hub-Needed header indicates whether the transmitting node would like
(and allow) the receiver to be a hub. A hub which sees no need for additional hubs in
its area of the network, will send "X-Hub-Needed: False", indicating to the
connecting node that it must operate in leaf mode if it wishes to connect. A hub
which sees a need for additional hubs, will send "X-Hub-Needed: True",
indicating that the receiving node should become a hub, if it is capable of doing so. A
leaf may send "X-Hub-Needed: True" to indicate that it is seeking a connection
to a hub.

The X-Hub header should be sent on all three of the header blocks to indicate
the current intended state of the node, while the X-Hub-Needed header should
be sent in the first two header blocks only, to indicate the desired status of the
receiver. If the nodes cannot agree on a satisfactory arrangement, the connection
will be terminated at or prior to the third header block with an appropriate message,
for example:

<pre>
<nowiki>
GNUTELLA/0.6 503 Too many hub connections
GNUTELLA/0.6 503 Too many leaves
GNUTELLA/0.6 503 I have leaves, can't downgrade to leaf mode
GNUTELLA/0.6 503 Leaf mode disabled
</nowiki>
</pre>

- NOTE: because X-Ultrapeer and X-Ultrapeer-Needed has been used on Gnutella2 for a longtime, there should be some backward compatibility code to comunicate with older nodes until they disappear.

=== Hub Address Exchange ===

It is desirable for connecting nodes to exchange the node addresses of other hubs on
the network to facilitate rapid connection. The Gnutella2 protocol includes highly
efficient methods to share hub addresses with peers once connected, but for a node
trying to connect and encountering only "full" hubs, learning new hubs to try is
helpful.

The X-Try-Hubs header was developed for this purpose. It contains a comma
separated list of hub node addresses and ports, along with a timestamp recording
the time the hub was last seen. For example:

<pre>
<nowiki>
X-Try-Hubs: 1.2.3.4:6346 2007-01-10T23:59Z, [..more..]
</nowiki>
</pre>

Hub addresses should not be sent unless the transmitter has reasonable knowledge
of the hub's existence and the timestamp is not too old.

=== Compression Negotiation and Encoding ===

The Gnutella2 architecture makes widespread use of "deflate" compression, due to
its high availability and ease of integration. Support of compressed TCP links is not a
requirement in the Gnutella2 standard, however, it is strongly recommended.

Deflate compression of a TCP link is negotiated with the pair standard HTTP headers
"Accept-Encoding" and "Content-Encoding". For example:

Header block one (initiator):

<pre>
<nowiki>
Accept-Encoding: deflate
</nowiki>
</pre>

Header block two (receiver):

<pre>
<nowiki>
Accept-Encoding: deflate
Content-Encoding: deflate
</nowiki>
</pre>

Header block three (initiator):

<pre>
<nowiki>
Content-Encoding: deflate
</nowiki>
</pre>

In this example, the initiator advertises support for receiving a deflated connection.
The receiver then indicates that it too supports receiving a deflated connection, and
that it intends to transmit deflated data. Finally, the initiator upon noting that the
receiver supports deflate, indicates that it too will transmit deflated data.

Note that unlike the content-type / protocol negotiation, deflated encoding can be
applied on either incoming, outgoing, or both channels of a connection.

For performance reasons, nodes should consider whether they can afford to support
additional deflated connections before advertising support for them, or agreeing to
provide a deflated data stream. In the Gnutella2 network topology, all links benefit
from compression, except the leaf to hub channel of the leaf/hub link. Exempting this
channel from compression, saves the leaf and more importantly, the hub, a
considerable CPU and RAM investment.

== Post Handshake Communication ==

After the third and final header block has been received by the initiator, subsequent
communication over the TCP stream occurs in the negotiated protocol, with the
negotiated encoding. This means that while the handshake sequence was backwards
compatible with Gnutella1, after Gnutella2 support has been negotiated, all
subsequent communication occurs in the Gnutella2 common protocol - an entirely
new system not backwards compatible with any other protocol.

TCP Stream Connection and Handshaking

2007-09-20T20:00:15Z

Ag: /* Content Type (Protocol) */

[[UDP_Transceiver|UDP Transceiver >>]] | [[Main_Page|Main Page]]

== Introduction ==

TCP stream connections are established between Gnutella2 nodes when they elect to
form a permeant link, creating the fundamental network topology of a highly
interconnected hub network serving dense clusters of leaf nodes.

== Initiation ==

TCP connections are initiated by leaf or hub nodes in an attempt to gain a connection
to a hub node. Leaf nodes are never the target of an outbound connection. The TCP
port number is not standardised, and must be stored with the IP address.

== Handshaking ==

Upon the establishment of a TCP stream connection between two Gnutella2 nodes, a
handshaking phase must be completed to negotiate the nature of the link and
exchange other necessary information.

This handshaking phase is the only part of the communication which remains
compatible with the old Gnutella network, allowing new connections to be negotiated
without fore-knowledge the capabilities of the other node. The handshaking process
has been well documented elsewhere, however, a short summary is provided here.

=== Handshake Stages ===

The Gnutella handshake process consists of three header blocks. The node which
initiated the connection sends an initial header block, of the form:

<pre>
<nowiki>
GNUTELLA CONNECT/0.6
Listen-IP: 1.2.3.4:6346
Remote-IP: 6.7.8.9
User-Agent: Shareaza 1.8.2.0
Accept: application/x-gnutella2
X-Hub: False
</nowiki>
</pre>

The receiver then responds with its own header block:

<pre>
<nowiki>
GNUTELLA/0.6 200 OK
Listen-IP: 6.7.8.9:6346
Remote-IP: 1.2.3.4
User-Agent: Shareaza 1.8.2.0
Content-Type: application/x-gnutella2
Accept: application/x-gnutella2
X-Hub: True
X-Hub-Needed: False
</nowiki>
</pre>

Finally, the initiator accepts the receiver's header block, and provides any final
information:

<pre>
<nowiki>
GNUTELLA/0.6 200 OK
Content-Type: application/x-gnutella2
X-Hub: False
</nowiki>
</pre>

The latter two stages may be replaced with an error condition if the connection is
being rejected. Appropriate error status codes are returned in this case, for example:

<pre>
<nowiki>
GNUTELLA/0.6 503 Too many connections
(more headers)
</nowiki>
</pre>

Note that only the HTTP-style error code should be interpreted by the software: any
descriptive text provided is for display purposes only and is not standardised.

== Headers ==

Important headers which are required or strongly recommended are detailed in the
following sections.

=== Addressing Headers ===

Two important headers to send on all connections are "Remote-IP" and "Listen-IP".
Both of these headers should be sent on the first transmission, meaning in the first
and second header blocks in the three block exchange.

The Remote-IP header contains the IP address from which the remote host is
connecting. This allows a remote host operating through some kind of network
address translation system, to learn its effective external address.

The Listen-IP header contains the IP address and port number that the local host is
listening for inbound TCP connections on. It should be listening for UDP datagrams
on the same port. The format of this header is "IP:PORT", eg "1.2.3.4:6346".

=== Identification ===

The User-Agent header is used to identify the client software operating on the
sending node. It should be sent on the first transmission, meaning in the first and
second header blocks in the three block exchange. Note that this is a descriptive
string that often includes a version number, and is not a "vendor code" as described
elsewhere.

=== Content Type (Protocol) ===

The Accept and Content-Type header exchange is used to negotiate the data
protocol that will be used in the connection, in this case Gnutella2. The Gnutella2
content type is "application/x-gnutella2", and this exchange follows standard HTTP
rules for negotiating content type.

The first step is to advertise support for the content type (Gnutella2) in the first
header block with "Accept: application/x-gnutella2". The responding node will then
indicate that it will send Gnutella2 content with "Content-Type: application/x-gnutella2",
and that it also supports Gnutella2 with "Accept: application/x-gnutella2".
The initiating host then confirms that it will be sending Gnutella2 with "Content-
Type: application/x-gnutella2" in the third header block. For more information on the
Accept/Content-Type exchange, consult a HTTP reference.

Note that the content type negotiation process is designed to be a "one-way"
process, i.e. a different content type can be negotiated for sending and receiving.
However, when the gnutella2 protocol is negotiated, both channels must use the
same content type. This means that a receiving node must not accept Gnutella2 if
the initiator did not advertise support for it, and if at the end of the handshake,
bidirectional Gnutella2 was not negotiated, the connection should be terminated.

=== Node State Negotiation ===

There are two node types in a Gnutella2 peer to peer network, a hub and a leaf, as
described in [[Node Types and Responsibilities]]. During the initial handshake,
the two parties must exchange their current node type and advise of their
capabilities, negotiating the node types they will adopt when the connection
completes, and indeed whether it should complete at all.

As the handshake sequence is compatible with Gnutella1, the headers involved in
negotiating node types should not be identical to those used to negotiate Gnutella1 to minimize network pollution.
states:

<pre>
<nowiki>
X-Hub: [True|False]
X-Hub-Needed: [True|False]
</nowiki>
</pre>

Both headers contain a Boolean value, "true" or "false", case insensitive.

The X-Hub header indicates whether the transmitting node is currently
operating as a hub. Hub nodes will send "X-Hub: True" while leaf nodes will
send "X-Hub: False".

The X-Hub-Needed header indicates whether the transmitting node would like
(and allow) the receiver to be a hub. A hub which sees no need for additional hubs in
its area of the network, will send "X-Hub-Needed: False", indicating to the
connecting node that it must operate in leaf mode if it wishes to connect. A hub
which sees a need for additional hubs, will send "X-Hub-Needed: True",
indicating that the receiving node should become a hub, if it is capable of doing so. A
leaf may send "X-Hub-Needed: True" to indicate that it is seeking a connection
to a hub.

The X-Hub header should be sent on all three of the header blocks to indicate
the current intended state of the node, while the X-Hub-Needed header should
be sent in the first two header blocks only, to indicate the desired status of the
receiver. If the nodes cannot agree on a satisfactory arrangement, the connection
will be terminated at or prior to the third header block with an appropriate message,
for example:

<pre>
<nowiki>
GNUTELLA/0.6 503 Too many hub connections
GNUTELLA/0.6 503 Too many leaves
GNUTELLA/0.6 503 I have leaves, can't downgrade to leaf mode
GNUTELLA/0.6 503 Leaf mode disabled
</nowiki>
</pre>

- NOTE: because X-Ultrapeer and X-Ultrapeer-Needed has been used on Gnutella2 for longtime, there should be some backword compatibility code to comunicate with older nodes until they disapper.

=== Hub Address Exchange ===

It is desirable for connecting nodes to exchange the node addresses of other hubs on
the network to facilitate rapid connection. The Gnutella2 protocol includes highly
efficient methods to share hub addresses with peers once connected, but for a node
trying to connect and encountering only "full" hubs, learning new hubs to try is
helpful.

The X-Try-Hubs header was developed for this purpose. It contains a comma
separated list of hub node addresses and ports, along with a timestamp recording
the time the hub was last seen. For example:

<pre>
<nowiki>
X-Try-Hubs: 1.2.3.4:6346 2007-01-10T23:59Z, [..more..]
</nowiki>
</pre>

Hub addresses should not be sent unless the transmitter has reasonable knowledge
of the hub's existence and the timestamp is not too old.

=== Compression Negotiation and Encoding ===

The Gnutella2 architecture makes widespread use of "deflate" compression, due to
its high availability and ease of integration. Support of compressed TCP links is not a
requirement in the Gnutella2 standard, however, it is strongly recommended.

Deflate compression of a TCP link is negotiated with the pair standard HTTP headers
"Accept-Encoding" and "Content-Encoding". For example:

Header block one (initiator):

<pre>
<nowiki>
Accept-Encoding: deflate
</nowiki>
</pre>

Header block two (receiver):

<pre>
<nowiki>
Accept-Encoding: deflate
Content-Encoding: deflate
</nowiki>
</pre>

Header block three (initiator):

<pre>
<nowiki>
Content-Encoding: deflate
</nowiki>
</pre>

In this example, the initiator advertises support for receiving a deflated connection.
The receiver then indicates that it too supports receiving a deflated connection, and
that it intends to transmit deflated data. Finally, the initiator upon noting that the
receiver supports deflate, indicates that it too will transmit deflated data.

Note that unlike the content-type / protocol negotiation, deflated encoding can be
applied on either incoming, outgoing, or both channels of a connection.

For performance reasons, nodes should consider whether they can afford to support
additional deflated connections before advertising support for them, or agreeing to
provide a deflated data stream. In the Gnutella2 network topology, all links benefit
from compression, except the leaf to hub channel of the leaf/hub link. Exempting this
channel from compression, saves the leaf and more importantly, the hub, a
considerable CPU and RAM investment.

== Post Handshake Communication ==

After the third and final header block has been received by the initiator, subsequent
communication over the TCP stream occurs in the negotiated protocol, with the
negotiated encoding. This means that while the handshake sequence was backwards
compatible with Gnutella1, after Gnutella2 support has been negotiated, all
subsequent communication occurs in the Gnutella2 common protocol - an entirely
new system not backwards compatible with any other protocol.