JXTA. Anand Prabhakar. JXTA. jux·ta·pose; v. tr. jux·ta·posed, jux·ta·pos·ing, jux·ta·pos·es. To place side by side, especially for comparison/contrast
jux·ta·pose; v. tr. jux·ta·posed, jux·ta·pos·ing,
jux·ta·pos·es. To place side by side, especially for comparison/contrast
Any entity on the network implementing one or more JXTA protocols. A peer could be anything from a mainframe to a mobile phone or even just a motion sensor. A peer exists independently and communicates with other peers asynchronously.
Peers with common interests can aggregate and form peer groups. Peer groups can span multiple physical network domains.
Used for joining and leaving peer groups. This protocol recognizes four discrete steps used by peers
The JXTA Content Manager Service, referred to as CMS, allows sharing and retrieving of content -- represented by a unique content ID --within a peer group. The CMS also features a content advertisement that provides metadata about the content. In addition, the service allows content management on the local peer. And it lets a peer browse and download content from remote peers.
The security requirements of a P2P system are similar to any other computer system. The dominant requirements are confidentiality, integrity, and availability.
These translate into specific functionality requirements that include authentication, access control, audit, secure communication, encryption and non-repudiation.
Given that JXTA is defined around the concepts of peers and peer groups, one can envision a security architecture in which peer IDs and group IDs are treated as low-level subjects (just like uid and gid), codats are treated as objects (just like files), and actions are those operations on peers, peer groups, and codats.
JXTA provides the following security primitives: