The IEEE Conference on Local Computer Networks 30th Anniversary (LCN'05)l 2005
DOI: 10.1109/lcn.2005.71
|View full text |Cite
|
Sign up to set email alerts
|

Functional Principles of Registry-based Service Discovery

Abstract: As Service Discovery Protocols (SDP)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2005
2005
2006
2006

Publication Types

Select...
2

Relationship

1
1

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 10 publications
(7 reference statements)
0
3
0
Order By: Relevance
“…For discovered services to be useful, it is important that the consistency guarantees are specified clearly. We specify the requirements for consistency maintenance in service discovery protocols in the Service Discovery Principles [9], where the Configuration Update Principles require the User and/or Registry to always eventually regain consistency with the Manager after the service changes. The User detects the change in the Manager, and regains consistency by obtaining the correct view of the service, either from the Manager directly (2-party Configuration Update Principle), or via the Registry (3-party Configuration Update Principle).…”
Section: Consistency Maintenance Principlesmentioning
confidence: 99%
See 1 more Smart Citation
“…For discovered services to be useful, it is important that the consistency guarantees are specified clearly. We specify the requirements for consistency maintenance in service discovery protocols in the Service Discovery Principles [9], where the Configuration Update Principles require the User and/or Registry to always eventually regain consistency with the Manager after the service changes. The User detects the change in the Manager, and regains consistency by obtaining the correct view of the service, either from the Manager directly (2-party Configuration Update Principle), or via the Registry (3-party Configuration Update Principle).…”
Section: Consistency Maintenance Principlesmentioning
confidence: 99%
“…The User rediscovers the Manager through (a) broadcast/multicast query with its requirements, where the matching Manager replies with the updated service description, or (b) broadcast/multicast periodic announcement of the Manager, where the User then queries the Manager for the service description, or (c) unicast query to the Registry for the service During communication failure through message loss [10], retransmissions and acknowledgements through SRC1 and SRN1 are useful, as long as subscription remains valid. SRC2 and SRN2 are necessary for satisfying the eventual consistency guarantee in the Configuration Update Principles [9]. In Section 5, we show that during short-term interface and node failures (where nodes recover from failures before the subscription expires), SRN2 is the most effective technique.…”
Section: Purge-rediscoverymentioning
confidence: 99%
“…Further, we have used our consistency conditions to distinguish between latency associated with failure detection and latency due to failure restoration. Other researchers [34] have used our consistency conditions together with a model-checking program to verify a system design. These results indicate the value of formalizing service guarantees.…”
Section: Service Guaranteesmentioning
confidence: 99%