> > If we had known that we'd spend 2 years in the RFC-editor Q waiting for > DTLS1.3, then maybe we would have done the document differently. > >> Except that neither one works for L3 networks multicast IMHO (i am getting no >> response to that request i sent meaning at least nobody knows or cares), and >> COAP >> does not provide unicast discovery like DNS-SD from all i know. > > RD is a core part of RFC7252: > https://www.rfc-editor.org/rfc/rfc7252.html#section-7
This section discusses both service discovery and resource discovery, which employ Web Linking (e.g., with the Link-Format RFC 6690). (Be careful with the abbreviation RD, as that is usually taken to mean resource directory, as in RFC 9176. RD is useful here on its own, but also works with CoAP resource discovery, see https://www.rfc-editor.org/rfc/rfc9176.html#section-5.1 Together with https://www.rfc-editor.org/rfc/rfc9176.html#section-4.1.1 this is a viable alternative to relying on subnet-wide multicast to work well.) > you can do it multicast or unicast, and RFC9148 does that. (It = CoAP Resource Discovery?) Grüße, Carsten _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
