lemonade-4----Page:11
1 2 3 4 5 6 7 8 9 10 11
|
draft-ietf-lemonade-firewall-binding-00 Next steps: Should an OPTIONS HTTP request be supported to allow a client to probe HTTP binding capabilities, such as which protocol a given URL is bound to, or whether chunking is supported? Should separate content types exist for IMAP and SMTP since the entity body in the HTTP request is different? Standardizing the form of the URL for the binding may permit firewall administrations to impose better filtering. Produce more rigorous rules for mapping IMAP and SMTP ABNF to SOAP, REST, and DAV. Provide ways to declare supported bindings or select a binding. |