[core] Comments on draft-ietf-core-resource-directory-11

[Jim Schaad <[e-mail]>]

1.  In section 5.2 para 2 - Not sure if this is wrong or not.  However I
would think that rt=core.rd-group is used to discover the URI path for RD
group operations not rt=core.gp.  I note that core.gp is not listed in the
set of valid rt values in the template.

2.  I am unclear of the proper interactions of the following items:
  * The anchor attribute - does it override the context query parameter
  * What happens if  a full URI is given as the target?  How does this
interact w/ the context query parameter?

3.  For simple registration.  If the client has needed to find the RD so it
knows where to do the post, why is the post not done to the RD rather than
to the /.well-know/core point?

4.  It is not clear to me what if the patch payload of  {data} should be
accepted.  Looking at the document as JSON, there is always an array wrapper
around it so that this template never matches the resulting document.  It
seems as if this should always be [{data}] instead.  Is there an implicit
add of the array if absent?  If you have a pattern of {data} and you match
multiple items, is that an error?

5.  Is there an implication that if the resources associated with an
endpoint expire, that the endpoint expires from all of its groups as well?
Is there a different way that endpoints are registered with the RD?

6.  Can an endpoint register zero items with an RD?

7.  should there be some text on interactions between ETag and page/count
query parameters?  What happens if there is a an update of the registry in
the middle of doing a sequence of queries about the links using these
options?


Jim


Typo
s/ecample.com/example.com/