I commented about this on the PR, but that seems to have been dismissed, so again, for the list:
* I'm not convinced this is required to be a mandatory feature of SASL2, despite its obvious utility, but I'm not going to argue very strongly that it shouldn't be. * I *am* convinced that an id attribute has to be mandatory (and SHOULD be a UUIDv4). * I am also convinced that the human-readable software information shouldn't be mandatory. On Sat, 22 Oct 2022 at 22:29, Thilo Molitor <[email protected]> wrote: > I'm trying to rephrase and sum up here, what MattJ already said: https:// > mail.jabber.org/pipermail/standards/2022-October/038998.html > > Stable client-identifier: > This allows per-device tokens or even passwords. > It allows to present users with a list of devices that currently have > access > to their account. > > Software and Device: > The software and device information allows users to better identify their > clients than just using the opaque client-identifier: "Conversations on > Kiva's > iPhone" is far more descriptive than "0ba15cd[...]". > > @MattJ: Add it, if I'm missing something here > > -tmolitor > > > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
