On Sat, 19 Nov 2022 at 15:14, Dave Cridland <[email protected]> wrote:
>
> 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.

I agree that neither of these should be mandatory, and that's why they
aren't. If there are reasons for clients not to include them, they
don't have to. Not including them may have consequences - e.g. the
FAST spec depends on the client id being present so wouldn't be
usable, and if the software info isn't included then the user will be
less informed about what is connecting to their account. For such
reasons, it is recommended that they are included. But mandatory, no.

Regards,
Matthew
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to