While reviewing latest updates; one other issue came up: the draft (re latest in Github) currently mentions DNS-SD as a means for a Pledge to discover a Join Proxy. But for DNS-SD discovery I believe a service name is needed; see RFC 6763 Section 7. But there’s no service name yet defined for a Join Proxy.
Easiest solution would be to remove the entire DNS-SD sentence and reference. I.e. defer this to a future document. If not removed, we probably need to add a service name registration for Constrained Join Proxy such that it can advertise its service and port over DNS-SD/mDNS correctly. (Note: the above is unrelated to my earlier remark on requiring a service name for the Registrar’s JPY protocol support. This could also be discovered over DNS-SD/mDNS but would need a separate service name.) Best regards Esko IoTconsultancy.nl | Email/Teams: esko.d...@iotconsultancy.nl<mailto:esko.d...@iotconsultancy.nl> | +31 6 2385 8339
_______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
