Hi

there are some proposals out about a buddy search on the p2p networks.
This is almost meant as a GUID search on the gnutella or p2p net.
A GUID it the unique general user id.
Each node or client has a unique number created.

So the p2p system could be used to search for this number.
But what we need before, is a DHT - A Database or HashTable to save the GUIDS.

I want to suggest to make a MULTI-HASH Table.

So this table should have and save:

- GUID of Gntuella client: urn:guid:myguidinhex
- IP adress of the gntuella client: urn:IP:myipadress
- WASTE key of the client: urn:waste:mywastekey
- AOL name: urn:aol:myaolname
- Yahoo name: urn:yahoo:myyahooname
- MSN name: urn:msn:mymsnname
- ICQ number: urn:icq:myicqnumber
- Jabber Name and/@ Server: urn:jabber:myjabbername@...
- Emule Client ID-hahs and ed2k-Server, which you are on, if.
urn:emule:myemuleclienthashinhex
- VIRTUAL ANTS ID of the client urn:ants:the_ip_adressofanyneighbour
- VIRTUAL MUTE ID of the client urn:mute:the_ip_adressofanyneighbour
- VIRTUAL ANTS ID of the client urn:ants:the_ip_adressofanyneighbour
- For jetiants: it must be clear, that this jabber ID is not searchable over g2
network.

this should be defined by magnet uri group, how the standard of the term is.

All these information should be used to create an IP tp IP Messenger without a
central server.
So please do not only use the GUID only, include the WASTE key as well and the
AOL name (as it is given und provided e.g. in shareaza). Shareaza could use the
WASTE key for a search of a buddy as well.

As well the whole thing should consider third generation p2p virtual ID
adresses.

Messaging in third generation p2p will be created in the next few months.

There must be considered, that the ID of a node in 3.gen p2p could not refer to
an IP adress, only to the IP adress of a neighbour or one hop (more) away
neighbour.

This offers a new design to third generation, which is not bad. This means you
search for the IP adress, which knows over at least one hop the ID adress.

Example:
someone wants to send me a message over ants.
Is it risky to give him any IP adress of a connected neighbour?
I guess a little bit, because in a case of a two node attack.

But normaly if a neighbour and his IP is saving all the IDīs of its connected
ants nodes,
the Gnutella 2 protocl could easily find the IP adress and the ID over gnutella
2 protocol.

It is like a GUID search in gntuella. Not only MY IP is given, but my neighbour
is knowing my ID, so HIS IP adress is used, then the last hop is done over ants
protocol.

This would work very good.

G2 Hubs with 4 IDīs of ants.
And the IP adress of the ants-HUB is then adressed over g2 protocol.

So include in a GUID search on gntuella 2 network as well a HUB with 4 VIRTUAL
IDs of the ANT network.

Then THESE ANT-G2-HUBS are the IP adress for 4 ant nodes.
These Hubs are not sharing on gntuella, just taking part in the GUID /ANTS-ID
search of a new Buddy-G2-Network, which is open for all p2p apps like WASTE or
Gnutella or ANTS, MUTE.

The ANT-G2-HUB then is in the gnutella network not a HUB, but a NODE.
This node then is only sharing ID-hashes and can connect regular normally to the
g2 network of file-hubs of g2 network.

(This would allow to download via ANT-G2-Hubs as well files from the G2 network
to ants network. Its a gate keeper function.)

Simply but true.