draftlowekampp2psipnodefetch00 - PowerPoint PPT Presentation
Title:
draftlowekampp2psipnodefetch00
Description:
Should be able to define remote management usage for centrally administered overlay ... ID only delivered to specific node, not to node responsible for Node-ID ... – PowerPoint PPT presentation
Number of Views:42
Avg rating:3.0/5.0
Title: draftlowekampp2psipnodefetch00
1
draft-lowekamp-p2psip-nodefetch-00
- Bruce Lowekamp
- 11/19/2008
2
NodeFetch Summary
- Some usages will require node-specific
information. - Current Store/Fetch methods identify objects by
Resource-ID, not Node-ID. - Proposal
- Add a set of Node-specific methods to base draft
to provide this functionality for usages
requiring it
3
Motivation
- Diagnostics
- draft-ietf-p2psip-base
- draft-zheng-p2psip-diagnose
- future?
- Administration
- Should be able to define remote management usage
for centrally administered overlay - Service Discovery and Placement
- Some algorithms use Resource-IDs (ReDir) others
work by Node-ID (Hourglass)
4
Options With Store/Fetch
- Kind specifies how to interpret Resource-ID
- Assumes architecture where plugin is required to
implement each kind, rather than agnostic kinds - Check whether request is sent to Node-ID or
Resource-ID - Messages to Node-ID only delivered to specific
node, not to node responsible for Node-ID - Probe followed by Request to Node-ID
- Fails when overlay is unstable (hard to diagnose)
5
Proposal for NodeFetch
- Define new set of methods NodeFetch, NodeStore,
NodeRemove - Essentially identical to Fetch etc, except no
Resource-ID is encoded in the object. - Can be sent to
- Node-ID to administer specific node
- Resource-ID for peer responsible for resource
- Because of wide range of use-cases for these
operations, should be part of base document.
Recommended
CrystalGraphics Presentations
