New updates to Office 365 Message Encryption

Caroline Shin Thanks for the updates above. Looks like you had some good announcements lined up for Ignite.

A couple of questions:

1. Turning off encryption of attachments is noted above for "consumer recipients." If an email is sent with an attachment using Encrypt-Only to a business recipient - I'm guessing your definition of consumer means gmail, yahoo, etc - will that attachment also be decrypted?
2. The PowerShell command to enable decryption of attachments is all or nothing for a tenant - right? 
3. For branding, it says "business-to-consumer" and "regardless of the recipient identity." Does the combination mean that while an Exchange Mail Flow rule can apply one of several templates for business-to-consumer emails, there is separately another way of applying a branded experience to ALL encrypted messages, regardless of whether they are "consumer" or "business"?
4. Encrypting PDFs - nice addition.
5. Revocation is noted as only being possible for the link-based experience. Is this a fundamental design limitation of OMEv2, or a cadenced release decision to delay revocation for non-link-based messages for later? From the way I understand it, even a message received natively in-line in a supported Outlook client has to check the authorisation of the recipient at open time, and therefore it should theoretically be possible to also revoke those messages (e.g., by revoking the encryption key of the message).
6. Revocation is only possible for admins. Any word on plans to enable the sender to do this too, since they have direct access to the sent message?

Sorry it's a long list. Trying to understand.