Discovery session

From ITUwiki

Jump to: navigation, search
  • Root of all roots
    • P2P approaches, via your friends, social networking
    • Putting things into context when you want to resolve something
    • If you find the Service Provider, you can find where to resolve it (Liberty)
Liberty includes concept of discovery service used to locate services appropriate to user as well as appropriate identity services
Bootstrap can include use of WS-Addressing endpoint reference containing pointer to service, this ERP can be found in WSDL, directory
Liberty Discovery mechanism
  • Bootstrap problem
    • You need to start somewhere
      • In liberty there's a service description (XML) attached to the endpoint identifier
      • You need to know what _type_ of ID it is
  • Do we need a list of Discovery start points?
  • Uniform mechanism!
  • How do I (user/equipment) know where to attach (Application/Identity provider)
  • How to get from an identifier to get to a source which can tell you something about it
  • What are we trying to discover?
    • Find the service associated to the ID
  • YADIS was discussed as an approach which makes use of DNS initially but then quickly delegates
  • Global registry or a set of well known rules?
  • Reverse lookup
    • In Handles there is no reverse-lookup but some apps can do that on their own
    • OID: Do I want the system to be complete? (probably not)
      • perhaps we don't need a discovery mechanism for OID
  • Structure of the identifier
    • Should be flexible (hierarchical vs flat)
  • Subgroup within the architecture
    • architecture components related to discovery
    • the rest of the WG will take a broader scope on the issue
  • Discovery Vs Resolution
    • Use resolution to avoid the need for root discovery
    • Resolving where to resolve
  • DEADLINES
    • End of March (2 weeks before the next meeting): 1st draft of «Tony insert title»
      • contribute this document to SG13 and 17 by the same time
Personal tools