I can't do that.

Defender brings with it a major logistics nightmare when extended protocol messages have their format changed.

And, the issue of supporting multiple languages demands a robust 'product identifier' capable of distinguishing the OEM ID (for branded versions i.e. "LycosShare"), build number, alpha/beta/release status, and version number.

However, these messages have their TTL set to 1 now so it is strictly a servent to servent exchange.