Opened 5 years ago

#416 new protocol defect

rt for groups

Reported by: consultancy@… Owned by: resource-directory
Priority: major Milestone:
Component: resource-directory Version:
Severity: Active WG Document Keywords:
Cc:

Description

Question Jim:
If I am doing a look up for groups, what does it mean to specify that you
are looking for a specific resource type? Should this not be supported for
groups or does this mean that the RD is expected to only return those
endpoints where a resource exists of the specified resource type?
answer Michael:
It looks like some updates may have been missed in the group and group lookup sections. In addition to the points below, we should look it over carefully again. Thanks again for the careful review.

A group lookup (using the lookup resoure rd.lookup-group) returns a list of links to group resources where endpoints in the group contain resources that satisfy the match criteria. So if I specify a resource type in a group query, the result is expected to be a list of group resources where each group contains one or more endpoints that in turn contain one or more resources of the resource type specified in the query. We should specify that a group is included in the returned list of groups if any link in any endpoint in the group contains a matching target attribute e.g. "rt".

The examples of group lookups need to be corrected. The "href" value or string in angle brackets should contain the location path that was returned when the group is registered. I think we also need to clarify that registering a group with "con=" will set the multicast address for the group and will be returned on group lookups as "con=" rather than substituting the multicase address for the href location. (section 6.1) I guess the description of "con" is a copy/paste from the registration section.

I think the statement about using an endpoint domain attribute as a group domain attribute may need to be removed. I think a group may contain endpoints with different domain attribute values.

Change History (0)

Note: See TracTickets for help on using tickets.