E2E encryption for BOLT11/BOLT12 description/note field was this discussed before?

In the realm of cryptocurrency transactions, particularly those involving the Lightning Network, a significant privacy concern arises with how invoice descriptions are handled. Various implementations and services, such as BTCPayServer, LND, CLN, LDK, Breez SDK, and others, reveal that the note field within invoices is exposed in plaintext. This exposure occurs not just to the intended final receiver but also to the infrastructure handling and processing the invoice.

This lack of confidentiality becomes particularly problematic in transactions where sensitive data is conveyed through the invoice's description field. For example, when purchasing services like VPN subscriptions or eSIMs via custodial Lightning wallets, merchants typically include critical order metadata directly in the invoice. Such metadata often contains details about the order ID, the specific product or plan purchased, and sometimes the merchant or reseller's identity. Since the wallet provider issues and forwards these invoices, they gain access to detailed information about what was purchased, from whom, and when the transaction occurred.

The question then arises whether end-to-end encryption for the note or description field of these invoices has been adequately addressed within the community. If discussions or proposals are already existing on enhancing privacy for these description fields, accessing these would be crucial. If not, the need to develop and discuss new proposals becomes apparent, ensuring that user data transmitted via invoice descriptions is safeguarded from unnecessary exposure.