Hello Bill, You mention "the advantages of using native CBOR encoding". So this refers to the CBOR encoding of (DNS) service properties, which would avoid parsing of the old DNS format. As I understand there's a wish of people to avoid having a DNS data parser in devices in the ACP, since the already-present CBOR parser can then be used instead.
Now if we would have such DNS-in-CBOR format, it would be more generally useful in IETF and not just in ANIMA. Do you agree? If the format is more generally useful it could be defined in either one of the CBOR, CoRE, or DNSSD WGs. (Although the latter may not be willing to renew something that's "already good") And we need to keep in mind the effort of the CoRE WG (still ongoing draft-ietf-core-href) to define a better encoding of the URI -> the CRI, in CBOR. It isn't trivial to cover all properties of the URI correctly. It takes a lot of effort. If we still decide to do this in ANIMA WG context I would just go for the simplest possible subset of DNS-SD that fulfills the use cases and not try to be complete. Regards Esko -----Original Message----- From: Anima <[email protected]> On Behalf Of William Atwood Sent: Monday, November 7, 2022 15:56 To: Anima WG <[email protected]> Subject: [Anima] ANI Autoconfiguration via DNS Item 08 in the ANIMA agenda for IETF 115. draft-eckert-anima-grasp-dnssd presents standards for the data structures (GRASP objectives) that will be required to effect autoconfiguration of basic services such as syslog, NTP, and DNS, using GRASP. draft-eckert-anima-services-dns-autoconfig presents standards for actually providing these services, using the objectives defined in draft-eckert-anima-grasp-dnssd. A strong argument is given in section 1 of draft-eckert-anima-grasp-dnssd, showing that the reliability and security of GRASP, and the advantages of using native CBOR encoding and GRASP flooding, justify the effort to define a GRASP-specific approach, rather than just using GRASP to carry the packets of the needed services. Clearly these services are essential to any running distributed system, and standardizing their on-the-wire representation will likely reduce potential problems with incompatible software in the future. I therefore encourage the WG to adopt these two drafts as Working Group documents. Bill Atwood -- Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046 Distinguished Professor Emeritus fax: +1 (514) 848-2830 Department of Computer Science and Software Engineering Concordia University ER 1234 email:[email protected] 1455 de Maisonneuve Blvd. West http://users.encs.concordia.ca/~bill Montreal, Quebec Canada H3G 1M8 _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
