Thanks for the discussion and feedback. This discussion showed consensus for adoption. Multiple participants noted that the update is necessary to maintain alignment with the evolving MS/TP standards used in building automation.
Dear Kerry, Please submit a workgroup draft revision when you are ready. Thanks, Carles and Shwetha On Thu, Dec 18, 2025 at 11:48 PM Kerry Lynn <kerlyn= [email protected]> wrote: > Michael et al. > > On Thu, Dec 4, 2025 at 3:17 PM Michael Richardson <[email protected]> > wrote: > >> >> I'm for adopting rfc8163-bis. >> I think that I read -00 a few months ago. >> >> Given the update that Dave Robin mentions, is the ANSI/ASHRAE 135 update >> upwards compatible? >> >> The main change to the ANSI/ASHRAE 135 BACnet since RFC 8163 is a name > change of MS/TP to Multidrop Serial Bus/Token Passing, along with > terminology changes in the spec to reflect this, e.g. :s/master/manager. > > Are there wire-changes against RFC8163? Please add a changes-since-8163 >> section. >> > No. The only technical change is fixing an errata that was discovered > after RFC 8163 was published. > > >> Can 8163 continue to run over the updated spec? >> > Yes. No wire format changes. > > >> Can 8163 and 8163-bis interoperate? >> > Yes. No wire format changes. > > Cheers, Kerry > >> >> -- >> Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting >> ) >> Sandelman Software Works Inc, Ottawa and Worldwide >> >> >> >> >> _______________________________________________ >> 6lo mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> > _______________________________________________ > 6lo mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ 6lo mailing list -- [email protected] To unsubscribe send an email to [email protected]
