Endorsement of the "TIPC" project was approved by the Networking Community Group with four Core Contributors voting "+1" and no other votes.
Networking currently has no Facilitator, so as a Core Contributor, I'm assuming that role (just this once ;-}) to ask that you please instantiate this project; details from the submitter are below. (I'm no lawyer, and I'm not sure what the proper use of "Solaris" might be in this context. I don't see a reason why the community group can or should validate the proper project title, but using that word in the title of an OpenSolaris project seems at least redundant and possibly incorrect. It's not really a networking matter anyway, so if there's an issue here, please do work this out with the submitter off line.) Project ------- TIPC on Solaris Community sponsor ----------------- Networking Participants in the initial project team ---------------------------------------- Laurent Ganne ([EMAIL PROTECTED]) Renaud Métrich ([EMAIL PROTECTED]) One paragraph description ------------------------- TIPC (Transparent Inter Process Communication) is a protocol that was originally developped at Ericsson. Today TIPC is in the linux kernel since 2.6.16, and in vXWorks. This project is the porting of the Linux version of TIPC to Solaris. TIPC provides a logical network topology where nodes are grouped in clusters, and clusters are grouped in zones. cf. http://en.wikipedia.org/wiki/Image:TIPC_logical_topology_-_zone-cluster-node.png Some features of TIPC include : - the location transparency of services in a network. - an auto-discovery mechanism. - a reliable transport. - Connectionless, connection-oriented and multicast messaging. - a socket interface for user-land applications with a new socket address family AF_TIPC. Applications in a TIPC network typically communicate with one another by sending messages between communication endpoints called "ports". When an application creates a port, this port will have a unique ID within the TIPC zone. To provide location transparency, the application creating a port can bind a "port name" to this port, and specify the level of visibility or "scope" of this port : - zone scope, - cluster scope, - or node scope. TIPC then ensures that only applications within that portion of the network (i.e. the same node, the same cluster, or the same zone) can access the port using that name. Related Project --------------- Opensolaris project Volo: The port of TIPC on OpenSolaris, which requires to define a new socket address family, will be done without any change to the OpenSolaris kernel source code by relying on the Pluggable Socket Framework provided by the Volo OpenSolaris project. Additional information ---------------------- A full description of TIPC can be found in the Programmer's Guide and protocol Specification at http://tipc.sourceforge.net/documentation.html _______________________________________________ networking-discuss mailing list [email protected]
