Skip to main content

Trying to understand netpeergroup, worldpeergroup and private peergroup.

1 reply [Last post]
seiska
Offline
Joined: 2008-07-03
Points: 0

Hello,

I have some difficulties with trying to get grip on these basic concepts of netpeergroup, worldpeergroup and private peergroup.

First, is it safe to make assumption that netpeergroup is used to refer "bootstrap" peergroup which every peer create when they start JXTAplatform?

That question might seem stupid, but after reading several examples on different JXTA aspects, and seeing them name this "bootstrap" peergroup to netgroup or worldpeergroup, I just feel need to make sure I get this right.

After thinking this subject, my best guess would be...
netpeergroup can be named/considered worldpeergroup, when:
- to connect/find other peers/resources I use public group that is maintained/kept up by JXTA community

netpeergroup can be named/considered private peergroup, when:
- I provide direct addresses of one or more RDV peers in my network, as shown below:
networkConfigurator.addRdvSeedingURI("tcp://public-ip-of-rendezvous:port-of-rendezvous");
networkConfigurator.setUseOnlyRendezvousSeeds(true);

Or, is concept I just described as private peergroup something else?
And is private peergroup actually just peergroup which has some sort of authentication?

Second thing I dont understand is...
Can I or can I NOT make authentication to netpeergroup (the "bootstrap" group which every peer creates when they start JXTAplatform)?

My best guess would be that I need to have netpeergroup where I advertise secure peergroup which has authentication. And if/when peers successfully can login to this secure peergroup, they would go on and join business groups they need / have credentials. These business groups would have secure peergroup as parentgroup, while secure peergroup would have netpeergroup as parentgroup.

Does this three layer grouping make sence and follow logic of JXTA?

Or is it good idea to try to secure netpeergroup? (I dont know how this could even be done, but it would be very helpfull to know if its possible)

If I dont secure netpeergroup, then would that have some security issues?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
adamman71
Offline
Joined: 2007-01-31
Points: 0

> First, is it safe to make assumption that netpeergroup is used to refer "bootstrap" peergroup which every peer create when they start JXTAplatform?

Yes and no. The fundamental peergroup is the WorldPeerGroup (WPG) from which you can create other peergroups. You don't necessarily need to use the netpeergroup (NPG) to connect to the network, though it is frquently used as such.

> After thinking this subject, my best guess would be...
netpeergroup can be named/considered worldpeergroup, when:
- to connect/find other peers/resources I use public group that is maintained/kept up by JXTA community

No, the WPG and the NPG are two different groups. NPG is child of WPG.

> netpeergroup can be named/considered private peergroup...

No, NPG access is free, always. No credential access ever required.

> And is private peergroup actually just peergroup which has some sort of authentication?

Yes. Though extra work is required in JXTA/JXSE to make this work properly. Target release for this issue with most probably be Cheeseburger (i.e., the one following 2.6)

> Can I or can I NOT make authentication to netpeergroup (the "bootstrap" group which every peer creates when they start JXTAplatform)?

Cannot, should not (even with fiddling)

> My best guess would be that I need to have netpeergroup where I advertise secure peergroup which has authentication. And if/when peers successfully can login to this secure peergroup, they would go on and join business groups they need / have credentials. These business groups would have secure peergroup as parentgroup, while secure peergroup would have netpeergroup as parentgroup.

Yes, that is the idea.

> Does this three layer grouping make sence and follow logic of JXTA?

Yes, especially since a bug regarding child peer groups has been solved in 2.6 beta 2.

> Or is it good idea to try to secure netpeergroup?

Very bad idea.

> Not really. But if you don't want other peers to connect to your NPG, you may want to investigate infrastructure IDs, which is a kind of seclusion.

J.