1 / 8

Session Peering Protocol over SOAP I-D ( draft -ietf-drinks- spp- over- soap-01 )

Session Peering Protocol over SOAP I-D ( draft -ietf-drinks- spp- over- soap-01 ). Presenter: Vikas Bhatia (On behalf of the authors ). Note : This is not a new draft either! draft-ietf-drinks-spp-protocol-over-soap- 00 replaced draft-ietf-drinks-sppp-over- soap-07 (Jan, 2012 ).

len-benjamin
Télécharger la présentation

Session Peering Protocol over SOAP I-D ( draft -ietf-drinks- spp- over- soap-01 )

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. Session Peering Protocol over SOAP I-D(draft-ietf-drinks-spp-over-soap-01) Presenter: Vikas Bhatia (On behalf of the authors)

  2. Note: This is not a new draft either! draft-ietf-drinks-spp-protocol-over-soap-00 replaced draft-ietf-drinks-sppp-over-soap-07 (Jan, 2012 )

  3. Summary of updates in -00 and -01 • Made enhancements to result messages, result codes, and to the result message XML definition. • Made updates to the Security Considerations • Removed reference to “TransIdType” from the Protocol document

  4. Result Code related updates (1 of 2) • Result Code 2001 (“Request Too Large”)is “parameterized”: • Allows the SPPF server to specify maximum requests supported in a single SPP Protocol over SOAP operation • “Request Too Large. MaxSupported:[Maximum requests supported]” • Example: “Request Too Large. MaxSupported:1000” • Corrected the numbering of Result Codes: • Like 21* Result codes started with 2103, changed to start with 2100

  5. Result Code related updates (2 of 2) • Added restriction on min and max length of message in a response from the SPPF server: • Defined a type "MsgType" to add min length (3) and max length (255) to a result’s message text • Introduced enumeration "ResultCodeValType" to define all the Result Codes. • As a result “ResultCodeType” definition is as follows: <complexType name="ResultCodeType"> <sequence> <element name="code" type="sppfs:ResultCodeValType"/> <element name="msg" type="sppfs:MsgType"/> </sequence> </complexType>

  6. Security Considerations section updates Updated text in ‘Security Considerations’ section: • The text identifies DoS risk when the TLS server does not request a certificate from the client (As per the TLS specifications, it is optional for the TLS servers to request a certificate from the client)

  7. Also… Removed “TransIdType” from the Protocol document • Was already present in the Framework document

  8. Next Steps • Resolve open items and make updates • Close to WGLC?

More Related