1 / 5

#4: Transport Document ( draft - ietf -drinks- sppp -over- soap)

This presentation by Syed Ali, representing Ken Cartwright, covers the latest updates to the draft IETF document on SPPP (Session Peering Policing Protocol) over SOAP. It outlines a concrete structure for SPPP operations, including object identities and response codes. Specific examples of SOAP-based SPPP requests and responses are provided, demonstrating compliance with protocol requirements. The document details how SPPP operations are modeled in XML and associates concrete response codes with their meanings. This is crucial for developers implementing SPPP in web services.

shika
Télécharger la présentation

#4: Transport Document ( draft - ietf -drinks- sppp -over- soap)

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. #4: Transport Document(draft-ietf-drinks-sppp-over-soap) Presenter: Syed Ali (On behalf of the author: Ken Cartwright)

  2. Updates • Concrete structure for all the SPPP operations • Concrete structure of the object identity for all the SPPP objects • Specific Response Codes and Messages supported by the transport • Concrete structure to encapsulate the responses of all SPPP operations • Included section on specific examples of “over the wire” SOAP based SPPP request and responses (previously in the protocol document) All of the above are In conformance with the requirements in the protocol I-D.

  3. Object Identity Mapping <complexType name="ObjKeyType"> <complexContent> <extension base="spppb:ObjKeyType"> <sequence> <element name="rant" type="spppb:OrgIdType"/> <element name="name" type="spppb:ObjNameType"/> <element name="type" type="spppb:ObjKeyTypeEnum"/> </sequence> </extension> </complexContent> </complexType>

  4. Example Operation Mapping • Concrete XML structure of each SPPP operation defined in the transport document:Like for “Add” operation: <element name="spppAddRequest"> <complexType> <sequence> <element name="clientTransId" type="spppb:TransIdType" minOccurs="0"/> <element name="minorVer" type="spppb:MinorVerType" minOccurs="0"/> <element name="obj" type="spppb:BasicObjType" maxOccurs="unbounded"/> </sequence> </complexType> </element>

  5. Example SPPP Response Type Mapping • Concrete Response codes delegated to the transport document:Like: +----------+-----------------------------+-----------------------------------------------------+ | Result | Result Message | Overall or Object Level | | Code | | | +----------+-----------------------------+----------------------------------------------------- + | 1000 | Request Succeeded. | Overall Response Code |

More Related