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

Ezra N. Hoch

dblp:96/480 · DBLP profile ↗
← Back
13ranked-venue papers
3as first author
0since 2021 · last 2012
—ORCID · none

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

Security and privacy · 5 · 3 first-authorSystems, architecture and hardware · 3Theory of computation · 1

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
3 papers
Distributed systems · 100%
Theoretical computer science
1 paper
Distributed computing theory · 100%

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

TopicWeightPapersLastEvidence papers
Distributed systems
consensus
0.222012
An Optimal Self-Stabilizing Firing Squad · SIAM J. Comput. 2012
OCD: obsessive consensus disorder (or repetitive consensus) · PODC 2008
Distributed systems
fault tolerance
0.112012
An Optimal Self-Stabilizing Firing Squad · SIAM J. Comput. 2012
Distributed systems › fault tolerance
self-stabilization
0.112012
An Optimal Self-Stabilizing Firing Squad · SIAM J. Comput. 2012
Distributed systems › fault tolerance
byzantine fault tolerance
0.112008
OCD: obsessive consensus disorder (or repetitive consensus) · PODC 2008
Distributed systems
clock synchronization
0.112008
Fast self-stabilizing byzantine tolerant digital clock synchronization · PODC 2008
Distributed systems
distributed coordination and fault tolerance
0.112008
OCD: obsessive consensus disorder (or repetitive consensus) · PODC 2008
Distributed computing theory
self-stabilization
0.112008
Fast self-stabilizing byzantine tolerant digital clock synchronization · PODC 2008
Distributed systems › fault tolerance › failure models
crash failures
0.012012
An Optimal Self-Stabilizing Firing Squad · SIAM J. Comput. 2012
Blockchain and cryptocurrency security › consensus protocol
byzantine fault tolerance
0.012008
Fast self-stabilizing byzantine tolerant digital clock synchronization · PODC 2008

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

transient fault modeling · 0.2probabilistic convergence analysis · 0.2state machine replication · 0.1
YearPublicationVenuePosition
2012 An Optimal Self-Stabilizing Firing Squad
abstract
Consider a fully connected network where up to t processes may crash and all processes start in an arbitrary memory state. The self-stabilizing firing squad problem consists of eventually guaranteeing simultaneous response to an external input. This is modeled by requiring that the noncrashed processes “fire” simultaneously if some correct process received an external “go” input, and that they only fire as a response to some process receiving such an input. This paper presents FireSquad, the first self-stabilizing firing squad algorithm. A firing squad algorithm facilitates the use of algorithms that need to start in the same round. It allows a smooth transition between algorithms whose executions need to be disjoint. The FireSquad algorithm combines two forms of fault-tolerance properties: self-stabilization to allow recovery from arbitrary transient errors and resilience to crash failures to handle permanent ones. The FireSquad algorithm is optimal in two respects: (a) once the algorithm is in a safe state, it fires in response to a go input as fast as any other algorithm does, and (b) starting from an arbitrary state, it converges to a safe state as fast as any other algorithm does.
Danny Dolev, Ezra N. Hoch, Yoram Moses
SIAM J. Comput.2
2010 A Fault-Resistant Asynchronous Clock Function
Ezra N. Hoch, Michael Ben-Or, Danny Dolev
SSS1
2010 A hybrid multicast-unicast infrastructure for efficient publish-subscribe in enterprise networks
abstract
One of the main challenges in building a large scale publish subcribe infrastructure in an enterprise network, is to provide the subscribers with the required information, while minimizing the consumed host and network resources. Typically, previous approaches utilize either IP multicast or point-to-point unicast for efficient dissemination of the information.
Danny Bickson, Ezra N. Hoch, Nir Naaman, Yoav Tock
SYSTOR2
2010 Brief Announcement: Simple Gradecast Based Algorithms
Michael Ben-Or, Danny Dolev, Ezra N. Hoch
DISC3
2009 An Optimal Self-stabilizing Firing Squad
Danny Dolev, Ezra N. Hoch, Yoram Moses
SSS2
2008 Fast self-stabilizing byzantine tolerant digital clock synchronization
abstract
Consider a distributed network in which up to a third of the nodes may be Byzantine, and in which the non-faulty nodes may be subject to transient faults that alter their memory in an arbitrary fashion. Within the context of this model, we are interested in the digital clock synchronization problem; which consists of agreeing on bounded integer counters, and increasing these counters regularly. It has been postulated in the past that synchronization cannot be solved in a Byzantine tolerant and self-stabilizing manner. The first solution to this problem had an expected exponential convergence time. Later, a deterministic solution was published with linear convergence time, which is optimal for deterministic solutions. In the current paper we achieve an expected constant convergence time. We thus obtain the optimal probabilistic solution, both in terms of convergence time and in terms of resilience to Byzantine adversaries.
Michael Ben-Or, Danny Dolev, Ezra N. Hoch
PODC3
2008 OCD: obsessive consensus disorder (or repetitive consensus)
abstract
Consider a distributed system S of sensors, where the goal is to continuously output an agreed reading. The input readings of non-faulty sensors may change over time; and some of the sensors may be faulty (Byzantine). Thus, the system is required to repeatedly perform consensus on the input values.
Danny Dolev, Ezra N. Hoch
PODC2
2008 Self-stabilizing Numerical Iterative Computation
Ezra N. Hoch, Danny Bickson, Danny Dolev
SSS1
2008 Constant-Space Localized Byzantine Consensus
Danny Dolev, Ezra N. Hoch
DISC2
2007 Self-stabilizing and Byzantine-Tolerant Overlay Network
Danny Dolev, Ezra N. Hoch, Robbert van Renesse
OPODIS2
2007 Byzantine Self-stabilizing Pulse in a Bounded-Delay Model
Danny Dolev, Ezra N. Hoch
SSS2
2007 On Self-stabilizing Synchronous Actions Despite Byzantine Attacks
Danny Dolev, Ezra N. Hoch
DISC2
2006 Self-stabilizing Byzantine Digital Clock Synchronization
Ezra N. Hoch, Danny Dolev, Ariel Daliot
SSS1