Hannes Tschofenig <hannes.tschofe...@arm.com> wrote:
>> Hannes: do you have any opinion about the necessity of going through
>> /.well-known/core to get the short URL, vs just using a
>> /.well-known/est URL?
Yes, exactly. Is option #1 useful enough to justify the code to parse
links? Os is the code impact already paid for in your view?
> (RTT for the lookup vs extra bytes in the URL)
> Are you asking me about these two options:
> Option #1 - going through /.well-known/core
> REQ: GET /.well-known/core?rt=ace.est
> RES: 2.05 Content </est-root >; rt="ace.est"
> Option #2 - using a /.well-known/est URL
> REQ: GET /.well-known/est
> RES: 2.05 Content </est-root>; rt="ace.est"
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
