Multicore AssociationJ. MaloyTIPC Working GroupEricssonWork-in-ProgressA. StephensWind RiverMay 30, 2006
TIPC: Transparent Inter Process Communication Protocol
Status of this Memo
This document is a "work-in-progress" edition of the specification for version 2 of the TIPCprotocol, and has NOT yet been approved by the TIPC Working Group.This document is currently being updated to reflect the capabilities of TIPC as implementedby versions 1.5 and 1.6 of the Open Source TIPC project (see
). Assuch, it may refer to features of TIPC that have not yet been implemented, or to featuresthat have been implemented differently than the text currently indicates.
Copyright (C) The Multicore Association (2006).This document and the information contained herein are provided on an "AS IS" basis andTHE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IFANY), AND THE MULTICORE ASSOCIATION DISCLAIM ALL WARRANTIES, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THEINFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIESOF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD","SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to beinterpreted as described in .
This document describes TIPC, a protocol specially designed for efficient communicationwithin clusters of loosely coupled nodes.TIPC is a reliable transport protocol typically operating on top of L2 packet networks, but itshould also work well on higher-level protocols such as DCCP, TCP, or SCTP.TIPC offers the following services to its users:A functional addressing scheme providing full addressing transparency over thewhole cluster.A topology information and subscription service, providing up-to-dateinformation about functional and physical topology.Lightweight, highly reactive connections reporting errors or destinationunreachability within a fraction of a second.A reliable multicast service, based on functional addressing, but using theunderlying network multicast service when possible.Acknowledged, loss-free, error-free, non-duplicated transfer of user data, bothin connectionless and connection-oriented mode.
ulticore Association TIPC Working Group Work-in-Progress: TIPC: Tr...http://tipc.sourceforge.net/doc/draft-spec-tipc-02.html1 of 759/13/2010 3:39 PM