Real-Time Systems

, Volume 12, Issue 3, pp 329–345 | Cite as

Report Dagstuhl Seminar on Time Services Schloß Dagstuhl, March 11. – March 15. 1996

  • Danny Dolev
  • Rüdiger Reischuk
  • Fred B. Schneider
  • H. Raymond Strong
clock synchronization network time protocol time service fault tolerance 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    John Rushby and Friedrich von Henke. Formal verification of algorithms for critical systems. IEEE Transactions on Software Engineering, 19(1):13–23, Jan. 1993.Google Scholar
  2. 2.
    John Rushby. A formally verified algorithm for clock synchronization under a hybrid fault model. In Thirteenth ACMSymposium on Principles of Distributed Computing, pages 304–313, Los Angeles, CA, August 1994. Association for Computing Machinery.Google Scholar
  3. 3.
    Natarajan Shankar. Mechanical verification of a generalized protocol for Byzantine fault-tolerant clock synchronization. In J. Vytopil, editor, Formal Techniques in Real-Time and Fault-Tolerant Systems, volume 571 of Lecture Notes in Computer Science, pages 217–236, Nijmegen, The Netherlands, January 1992. Springer-Verlag.Google Scholar
  4. 4.
    Paul S. Miner. Verification of fault-tolerant clock synchronization systems. NASA Technical Paper 3349, NASA Langley Research Center, Hampton, VA, Nov. 1993.Google Scholar
  5. 5.
    Paul S. Miner, Shyamsundar Pullela, and Steven D. Johnson. Interaction of formal design systems in the development of a fault-tolerant clock synchronization circuit. In 13th Symposium on Reliable Distributed Systems, pages 128–137, Dana Point, CA, October 1994. IEEE Computer Society.Google Scholar

Copyright information

© Kluwer Academic Publishers 1997

Authors and Affiliations

  • Danny Dolev
    • 1
  • Rüdiger Reischuk
    • 2
  • Fred B. Schneider
    • 3
  • H. Raymond Strong
    • 4
  1. 1.Computer Science Dept.Hebrew UniversityJerusalemIsrael
  2. 2.Med. Universität zu Lübeck, Institut für Theoretische InformatikLübekGermany
  3. 3.Dept. of Computer ScienceCornell UniversityIthaca
  4. 4.IBM Almaden Research, Dept. K53/802San Jose

Personalised recommendations