1 / 4

SPPP Transport

SPPP Transport. Session Peering Provisioning Protocol draft-ietf-drinks- sppp-over-soap-04. Progress. WGLC was issued in April Comments received from Manjul Maharishi

bisa
Download Presentation

SPPP Transport

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SPPP Transport Session Peering Provisioning Protocol draft-ietf-drinks-sppp-over-soap-04

  2. Progress WGLC was issued in April Comments received from Manjul Maharishi Comment: Suggested additional explanation of the overall structure, using Document Literal Wrapped WSDL style and SOAP. Action: Updated the text describing the use of the Document Literal Wrapped style of WSDL and SOAP. Comment: References need to be tightened up. Action: Improved the references section (SOAP, WSDL, HTTP) Comment: Spelling and grammar improvements. Action: Cleaned up some spelling and grammar. Issued updated draft, 04.

  3. Progress • Comments received from Peter Saint-Andre (received late last week, so no action taken yet) • Comment: A few sentences need to to be updated for clarity. • Comment: The selected normative reference for WSDL is inappropriate, not supporting the statement that WSDL is standardized and widely adopted. • Comment: When mentioning that SOAP faults are not being explicitly used within SPPP SOAP mapping, refer to an appropriate section of the SOAP specification, or describe how SOAP faults would be handled if they do occur. • Comment: Make the text more explicit where it states that implementations must support HTTP over TLS. • Comment: Ensure that the WSDL name spaces are correctly specified. • Comment: When stating that the “client SHOULD authenticate the server” provide a reference to how this could/should be done (e.g. reference 2818). • Comment: Where section 7.3 states that encryption “may” not be used in some closed networks or debugging scenarios, improve the wording and meaning. • Comment: Improve the IANA considerations section, and refer to RFC 3688 on how to do so.

  4. Next Steps • Address Peter’s Comments. • Go to next last call.

More Related