On 27-Sep-25 09:10, Christian Amsüss wrote:
On Sat, Sep 27, 2025 at 08:47:00AM +1200, Brian E Carpenter wrote:
On your point 2: when CoRE link format, that contains links with an IP literal
in the URI,
Especially, it is *guaranteed* to fail if the IP literal is an IPv6
link-local address, since the URI cannot express the interface ID,
because the browser community has categorically refused the necessary
extension to the URI syntax. (RFC 6874 is obsolete.)
I don't think this is guaranteed to fail, at least not for CoAP clients.
At least one CoRE document (RFC9176) has talked about link-local address
in web links (and thus URLs) specifically, and taken a
split-horizon-like view: As long as the request is made through a
link-local address, the server *can* represent link-local addresses as
long as it learned them on the same interface.
Yes, but the context here was sending a URI to a different host, and that
is pretty certain to fail.
GRASP relies on exactly what you describe: if you learn a link-local address
via GRASP discovery, you *must* associate it with the same interface. It isn't
hard, but quite a lot of software gets this wrong in my experience, because
it's (badly) adapted from IPv4 code.
Brian
BR
Christian
_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]
