I don't have a strong opinion about option #2 appears to be slightly better.
I guess hard-cording URLs will not work.... -----Original Message----- From: Michael Richardson [mailto:[email protected]] Sent: 16 May 2018 14:16 To: Hannes Tschofenig Cc: [email protected] Subject: Re: [Ace] Early media-type registration for EST over CoAP Hannes Tschofenig <[email protected]> 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 [ ] [email protected] http://www.sandelman.ca/ | ruby on rails [ -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
