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
http://tipc.sf.net
). 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 Notice
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 .
Abstract
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.
[RFC2119]
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
Configurable congestion control both at bearer, link, and connection level.Data fragmentation conforming to discovered carrier MTU size.Bundling of multiple user messages into a single TIPC packet in situationswhere messages cannot be sent immediately.Transparent, link-level load sharing and redundancy, through support of heterogeneous multi-homing.A slim, non-layered protocol header allowing efficient protocolimplementations.Apart from common process-to-process communication, the design of TIPC even includesthe possibility to commmunicate process-to-kernel and kernel-to-kernel, still with fulladdressing and interface transparency.
Table of Contents
1.Introduction 1.1.Motivation 1.1.1.Existing Protocols 1.1.2.Assumptions 1.2.Architectural View 1.3.Functional View 1.3.1.API Adapters 1.3.2.Address Subscription 1.3.3.Address Distribution 1.3.4.Address Translation 1.3.5.Multicast 1.3.6.Connection Supervision 1.3.7.Routing and Link Selection 1.3.8.Neighbour Detection 1.3.9.Link Establishment/Supervision 1.3.10.Link Failover 1.3.11.Fragmentation/Defragmentation 1.3.12.Bundling 1.3.13.Congestion Control 1.3.14.Sequence and Retransmission Control 1.3.15.Bearer Layer 1.4.TIPC Terminolgy 1.5.Abbreviations2.TIPC Features 2.1.Network Topology 2.1.1.Network 2.1.2.Zone 2.1.3.Cluster 2.1.4.Node 2.1.5.Secondary Node 2.2.Addressing 2.2.1.Location Transparency 2.2.2.Network Address 2.2.3.Port Identity 2.2.4.Port Name 2.2.5.Port Name Sequence 2.2.6.Multicast Addressing 2.2.7.Publishing Scope 2.2.8.Lookup Policies 2.2.9.Name Translation
ulticore Association TIPC Working Group Work-in-Progress: TIPC: Tr...http://tipc.sourceforge.net/doc/draft-spec-tipc-02.html2 of 759/13/2010 3:39 PM
2.2.10.Distributed Naming Table 2.3.Topology Services 2.3.1.Inquiry 2.3.2.Subscriptions 2.3.3.Functional Topology 2.3.4.Physical Topology 2.4.Ports 2.4.1.Port State Machine 2.5.Connections 2.5.1.Connection Setup 2.5.2.Connection Shutdown 2.5.3.Connection Abortion 2.5.4.Connection Supervision 2.5.5.Flow Control 2.5.6.Sequentiality Check 2.6.Links 2.6.1.Link Creation 2.6.2.Link Activation 2.6.3.Link MTU Negotiation 2.6.4.Link Continuity Check 2.6.5.Sequence Control and Retransmission 2.6.6.Message Bundling 2.6.7.Message Fragmentation 2.6.8.Link Congestion Control 2.6.9.Bearer Congestion Control 2.6.10.Link Load Sharing vs Active/Standby 2.6.11.Link Changeover 2.6.12.Link Deletion 2.7.Routing 2.7.1.Routing Algorithm 2.7.2.Routing Table 2.7.3.Routing Table Updates 2.8.Multicast Transport 2.8.1.Conditional Cluster Broadcast 2.8.2.Conditional Tunneled Retransmission 2.8.3.Piggybacked Acknowledge 2.8.4.Coordinated Acknowledge Interval 2.8.5.Replicated Delivery 2.8.6.Congestion Control 2.9.Fault Handling 2.9.1.Fault Avoidance 2.9.2.Fault Detection 2.9.3.Fault Recovery 2.9.4.Overload Protection3.TIPC Packet Format 3.1.TIPC Payload Message Header 3.1.1.Payload Message Header Format 3.1.2.Payload Message Header Field Descriptions 3.1.3.Payload Message Header Size 3.2.TIPC Internal Header 3.2.1.Internal Message Header Format 3.2.2.Internal Message Header Fields Description 3.3.Message Users 3.3.1.Broadcast Protocol 3.3.2.Message Bundler Protocol 3.3.3.Link State Maintenance Protocol 3.3.4.Connection Manager
ulticore Association TIPC Working Group Work-in-Progress: TIPC: Tr...http://tipc.sourceforge.net/doc/draft-spec-tipc-02.html3 of 759/13/2010 3:39 PM
Search History:
Result 00 of 00
00 results for result for
p.
3.3.1. Broadcast Protocol for Transparent Inter Process Communication Protocol mathhoang vietnam_hoangminhnguyen
TICP for everyone
1.1K
Reads
2
Readcasts
99
Embed Views
More From This User
Notes
Load more
