Re: [core] draft-ietf-core-resource-directory = GET /rd

[Michael Koster <[e-mail]>]

I would propose returning links for all registration resources in the RD as shown in slide 4 of the attached deck (JSON format shown). This would include the most recent setting of the "lt" or lifetime parameter as a link target attribute as shown. 

> On Sep 4, 2017, at 8:27 AM, Jim Schaad <[e-mail]> wrote:
> 
> Yes that is what I had in mind.  It would be useful to add a ttl attribute
> as well.
> 
> Jim
> 
> 
>> -----Original Message-----
>> From: peter van der Stok [mailto:[e-mail]]
>> Sent: Monday, September 4, 2017 1:46 AM
>> To: Jim Schaad <[e-mail]>
>> Cc: [e-mail]; [e-mail]
>> Subject: Re: draft-ietf-core-resource-directory = GET /rd
>> 
>> Hi Jim,
>> 
>> Personally, I like the idea.
>> That would mean that all registration resources are returned.
>> In the next version of the RD, location or endpoint identifies the
> registration.
>> Uniqueness of links is specified in section 5.3.4, already commented on by
>> you.
>> Your request means returning all locations with the ep, lt, d, and et
> attributes
>> and the associated scheme://authority:port value.
>> 
>> Correct?
>> 
>> Peter
>> 
>> Jim Schaad schreef op 2017-08-31 03:59:
>>> I am wondering if there should be a GET action defined against the
>>> resource directory object.  Currently, if an entity does a
>>> registration for an endpoint it gets back a location for that
>>> registration.  If a second entity modifies the endpoint and wants to
>>> update the registration, it currently has no method to get the
>>> location associated with the endpoint and cannot make a second new
>>> registration since the <domain, endpoint> pair is required to be
>>> unique.
>>> 
>>> Thus
>>> 
>>> Interaction: EP -> RD
>>> Method: GET
>>> URI Template: {+rd}{?ep,d}
>>> 
>>> Content-Format: application/link-format (or variants)
>>> 
>>> <rd/0099>;ep=endpoint1,<rd/0098>;ep=endpoint1;domain=beta, ...
>>> 
>>> Jim
> 
> _______________________________________________
> core mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/core