Goals

From BOXP

Jump to: navigation, search

Contents

Project goals

  • Create and approve the complete specification of the BOXP protocol.
  • Create specifications of the service subprotocols and multiple wide use subprotocols, including IM, VoIP and CTP.
  • Develop an universal, cross-platform implementation of the protocol.
  • Offer a painless adoption model.
  • Gain support from big IT companies.
  • Form IONH and raise funds.

BOXP

  • Universal peer-to-peer application level protocol for the secure transportation of data packets.
  • Extensible functionality by higher level protocols -- subprotocols.
  • Single delegated user identification and authentication network.
  • Not dependant on IP and DNS, users are identified by User ID, sessions are identified by Session ID.
  • Transported via any available protocol (e.g. TCP, UDP, DCCP or inside a HTTP request)
  • Binary, machine-oriented format.

Content Transfer Protocol

  • Subprotocol of BOXP for text and multimedia content sharing.
  • Replacement of HTTP, formats like RDF, Atom, older protocols like NNTP, Gopher.
  • Not relying only on client-server architecture.
  • Content identified by owner (not always same as author) and ID.
  • Content separated from description and interface.
  • Distributed downloads.
  • Very extensible search options.
  • Search via other peers, not single engine.
  • Subscription functions as it should (content is delivered to the subscriber when it's created, instead of subscriber polling for new content)
  • Multiple versions of the same content available. (e.g. different formats, different languages)

See also

Problems