Pascal Thubert (pthubert) <[email protected]> wrote: > I understood so far sar the CoAP URI host is the same as the http host: > header parameter. If I m correct then this is normally a string with > the dns name and port to reach the server. Without it, the proxy > wouldn’t know how to reach the server in the first place. Without it, a > multihomed server wouldn’t know which instance it reached. This is why > I understood it became mandatory in http 1.1.
1) apparently it's not mandatory in CoAP (I thought it was until a few minutes ago). We can save ~15 bytes here. 2) The proxy knows where the JRC is because it's been told the IP address of the JRC, either implicitely (it's the DODAG root, aka 6LBR), or explicitely via the response. Remember that we can type https://[fde4:8dba:82e1::1234]/ or, in this case, we want the pledge to say: coap://[fe80::1234]/j, which the Join Proxy forwards to coap://[fde4:8dba:82e1::1234]/j (of ourse, using OSCORE). -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] [email protected] http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
