Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

I. Arieh Cimet

dblp:61/1431 · DBLP profile ↗
← Back
4ranked-venue papers
3as first author
0since 2021 · last 1989
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 2 · 2 first-authorComputer networks · 2 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%
Theoretical computer science
2 papers
Distributed computing theory · 100%
Computer networks
1 paper
Routing and switching · 100%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Routing and switching › switching networks
spanning tree protocol
0.011988
A protocol to maintain a minimum spanning tree in a dynamic topology · SIGCOMM 1988
Distributed computing theory
distributed graph algorithms
0.011988
A protocol to maintain a minimum spanning tree in a dynamic topology · SIGCOMM 1988
Distributed systems › distributed algorithms
distributed synchronization
0.011986
A resilient distributed protocol for network synchronization · SIGCOMM 1986
Distributed systems
fault tolerance
0.011986
A resilient distributed protocol for network synchronization · SIGCOMM 1986
Distributed computing theory › timing models
asynchronous networks
0.011986
A resilient distributed protocol for network synchronization · SIGCOMM 1986

Methods — techniques the papers use, named apart from their topics

message complexity analysis · 0.0distributed protocol · 0.0distributed algorithm · 0.0
YearPublicationVenuePosition
1989 On the design of resilient protocols for spanning tree problems
abstract
A method to design resilient protocols for spanning tree problems is proposed. The method consists of a generic resilient protocol that can be used for any spanning tree problem. A resilient protocol for a particular spanning tree problem can be obtained by adjusting various run-time parameters of the generic protocol. The generic protocol is designed by using the concepts of replacement sets that contain the links that can be used to replace a link that fails and replacement values that measure the change in the spanning tree when a link in a replacement set is used to recreate a spanning tree. The approach is as general as the common approach (for the case of spanning trees) because the generic protocol can solve a new spanning tree problem without an individual design. The protocols obtained with this method are efficient and easy to implement and verify because they are all derived from the generic protocol.>
I. Arieh Cimet, Srikanta P. R. Kumar
ICDCS1
1988 A protocol to maintain a minimum spanning tree in a dynamic topology
abstract
We present a distributed protocol for updating and maintaining a minimum-weight spanning tree (MST) in a network with changing topology. The protocol can respond to multiple link/node failures and recoveries that can occur at arbitrary times. Given that an arbitrary finite number of topological changes occur during a period, the protocol finds the MST corresponding to the latest network, within finite time after the last change. The message complexity of the protocol is O(m|E|+k|V|) when k link recoveries and m link failures occur, where |V| and |E| are the total number of nodes and links, respectively.
I. Arieh Cimet, Srikanta P. R. Kumar
SIGCOMM2
1987 A Resilient Distributed Algorithm for Minimum-Weight Spanning Trees
I. Arieh Cimet, Srikanta P. R. Kumar
ICPP1
1986 A resilient distributed protocol for network synchronization
abstract
We present a resilient distributed protocol that enables a synchronous algorithm to run on an asynchronous network. The protocol is resilient in the sense that it can continue providing network synchronization in the presence of topological changes in the underlying communication network of a distributed system. These changes are caused by link/node failures and recoveries that occur while running the protocol. In general, the protocol is a useful tool in the design of resilient distributed algorithms as it isolates the algorithm from the characteristics of the communication network.
I. Arieh Cimet, Srikanta P. R. Kumar
SIGCOMM1