DDF Registry

Must Have

• • This may be my identity node contact information or any other node contact information that I have within my registry information contact list.
  • a node includes all federation methods and related property information
  • Additional node information should be included if present (e.g., Describe or any other node-specific information stored as part of the registry information)

As an administrator, I want to unpublish registry information that I published to an external node so that the information is no longer exposed there

• Examples of changes:
  
  • new IPs/URIs
  • FQDN
  • timeouts

As an administrator, I want to be able to configure an external registry information provider, which will then be polled periodically for registry information to add to my local contact list, so that I can have registry information for other nodes with which to configure federation (automatically or otherwise).

• can edit polling interval

Federation Method Preference

As an administrator, I want to be able to choose my preferred order of the federation methods I can use, so that I can determine the priority for automatic federation configuration against nodes discovered through registry information exchange.

• Reasons for preference might include bandwidth requirements, secure/public, etc
• Default priority provided out-of-the-box should be discussed

• A disabled node is still available for publish/unpublish to external registry information providers, property editing, etc. - but is not visible or available for any functional operations in the local node

As an administrator, I want to preview/view the registry contact information present at an external registry information provider, so that I can decide whether or not to configure that node as a provider of registry information for my local contact list

As an administrator, I want to be able to remove a configuration of an external registry information provider so that I no longer use it to retrieval registry contact list information updates

As an administrator, I want to delete registry contact record to my contact list (including all of its information)

As an administrator, I want to edit a registry contact record in my contact list (including adding federation methods and editing any related properties or adding new ones)

• Example properties to edit
  • change timeouts
  • change service uris
• Need to flag somehow that it has been edited
• If the registry contact entry came from an external registry information provider, then any edited or new properties or federation methods should be considered local "overrides" of the external information, and the changes should be maintained through subsequent refreshes/updates of that registry contact entry from the external provider
  • In this case (locally edited or expanded registry contact entries that came from an external registry information provider), I should be able to see that I have different values than those coming from the external provider, and be able to view/compare them.

As an administrator, I want a view of my registry information contact list, from which I can configure it, its population and exposure to/from external nodes, and manage my node's use of it for federation and other purposes.

• I should be able to see (through icons, coloring, columns, presentation, or somehow) the nature of each registry contact list entry:
  • Where it came from (my identity node, published to me, pulled from an external provider, created locally)
  • Edit/override status (if it came from an external provider or publisher, have I edited it to differ from the externally provided information)
  • Federation configuration (am I currently federated with it, or is it disabled? What method am I using to federate with it?)
  • As far as I can tell, if I'm federated with it, what is the coarse status of that federation? (e.g., green/yellow/red)
  • Any visibility restrictions of the entry with respect to external node requests for my contact list entries?
• I should be able to select or click on a registry contact list entry to view more detailed information and configuration options, including but not limited to the above

• the initial contents of my registry contact list will be the identity node (i.e., myself)
• default behavior is to ask during installation for an external registry information provider
• default behavior is to deny incoming registry information requests.
• default behavior is to deny incoming publish requests.

• The default will be to publish my identity node upon configuration.
• Optionally, I can publish additional contacts at this time.

• include/exclude other nodes
• include/exclude identity node