Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
What standards? By you mentioning section 3.1.1 I assume that you are referring to RFC4408? We now have the Standard Track RFC7208, which obsoletes RFC4408.
Let me quote the beginning of http://tools.ietf.org/html/rfc7208#section-3.1
“SPF records MUST be published as a DNS TXT (type 16) Resource Record (RR) [RFC1035] only.”
Also, if you take a look at some of the big players, such as gmail.com, yahoo.com and fastmail.com, you’ll see that all of them only use the TXT records for their SPF info.
In short, not being able to create records of the SPF type is a feature, not a bug.