@Michael, @Christian I am re-reading RFC7252, Section 5.7.2:
Unless a proxy is configured to forward the proxy request to another proxy, > it MUST translate the request as follows: the scheme of the request URI > defines the outgoing protocol and its details (e.g., CoAP is used over UDP > for the "coap" scheme and over DTLS for the "coaps" scheme.) For a > CoAP-to-CoAP proxy, the origin server's IP address and port are determined > by the authority component of the request URI, and the request URI is > decoded and split into the Uri-Host, Uri- Port, Uri-Path and Uri-Query > Options. This consumes the Proxy-Uri or Proxy-Scheme option, which is > therefore not forwarded to the origin server. > I suppose you are referring to this implicit configuration of the proxy that would forward to the JRC anything received on a link-local address, if the request does not have the Uri-Host option? It seems to be OK, and doesn't prevent much of the CoAP proxy functionality for other purposes. I am waiting for the confirmation from Christian of there is any other RFC7272 pitfall with this before doing the changes in the draft. I kind of liked the 6tisch.arpa "thing", but no argument with ~13-byte savings :-). Mališa On Sat, May 19, 2018 at 3:17 PM Michael Richardson <mcr+i...@sandelman.ca> wrote: 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 [ > ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on > rails [ > > > _______________________________________________ > 6tisch mailing list > 6tisch@ietf.org > https://www.ietf.org/mailman/listinfo/6tisch >
_______________________________________________ 6tisch mailing list 6tisch@ietf.org https://www.ietf.org/mailman/listinfo/6tisch
