SPPP “Transport” Specification • draft-cartwright-drinks-sppp-over-soap-01 • Status Update • Really just a couple updates, as Use Cases and Protocol were focus of this cycle. • Adopted as a WG Document • Discussed and considered four notable comments from IETF 77, also soliciting feedback on the mailing list • Use of thin SOAP/WSDL wrapper as the messaging envelope, rather than thick WSDL, lessens the value of SOAP. • Use of HTTP Digest as the authentication protocol rather than the WS security service is not really standards compliant. • Do not make the protocol transport agnostic, it is not necessary to do so. • Do not use XSD, just define XML via documentation and examples. • Decided to stick with the current approach as it is still the preferred approach of the design team for the original reasons. • Helps make the protocol transport/envelope agnostic. • HTTP Digest is a standard and is in keeping with other protocols. • Transport/Protocol agnostic is “easy” and avoids unnecessary coupling. • Using XSDs to define XML data structures is good practice, widely used, and highly beneficial.