Esko Dijk <[email protected]> wrote: > I added some comments on below questions on Github > https://github.com/anima-wg/constrained-voucher/issues/51 .
> In summary, you can ask for both resources of type ace.est and
> ace.brski by doing a wildcard query:
> GET /.well-known/core?rt=ace.*
Right.
> However this not only returns the two (intended?) resources ace.est and
> ace.brski, but also all the subtypes of these which is:
> ace.est.rv, ace.est.vs, ace.est.es, ace.est.ra
I think that we'd want them all anyway, but if course, we'd get anything else
under ace. (other than est and brski).
> Note that the '/' in the rt name is not permitted by RFC 6690, it
> should be a '.' to indicate the hierarchy here. Created issues #54 for
> this.
Understood, thank you for the fix.
> This gets exactly the main resources but not the sub-resources below it
> separately. From the main resources the sub-resources are automatically
> inferred (i.e. the standard names 'rv', 'vs', 'es', and 'ra'.)
> Doing this will reduce the amount of data transferred over the
> constrained network but adds an extra message roundtrip.
Yes, exactly.
> Note that in my opinion all this discovery adds unnecessary complexity
> and overhead in the constrained node/network, so I created a proposal
> to also allow the .well-known resources that BRSKI is already using.
> Why make something less efficient than the unconstrained protocol and
> force clients to use it ... ?
I also agree.
In my opinion the only reason to do this discovery is to enable multicast RD,
such as I think that brski-ae really wants to do.
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
