1 / 9

#3: Protocol Document ( draft- ietf -drinks- spprov )

#3: Protocol Document ( draft- ietf -drinks- spprov ). Presenter: Syed Ali (On behalf of the authors: Ken Cartwright, Syed Ali, Alex Mayrhofer and Jean-Francois Mule). Since IETF#81…. Re-organized “ split ” between the documents, following the interim

kenaz
Download Presentation

#3: Protocol Document ( draft- ietf -drinks- spprov )

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. #3: Protocol Document(draft-ietf-drinks-spprov) Presenter: Syed Ali (On behalf of the authors: Ken Cartwright, Syed Ali, Alex Mayrhofer and Jean-Francois Mule)

  2. Since IETF#81… • Re-organized “split” between the documents, following the interim • Updated the security section, based on comments and discussions • Addressed data validation by defining constraints for the schema • Re-introduced the Registrar ID (‘rar’) as part of the BasicObjType • Incorporated xsd:token (for identifiers) instead of xsd:string • Removed Examples (this is now in the transport document)

  3. Document Reorganization After: Before:

  4. The Idea…

  5. Schema-specific Changes… Before: After: <complexType name="ObjKeyType” abstract="true"> <annotation> <documentation> ---- Generic type that represents the key for various objects in SPPP. ---- </documentation> </annotation> </complexType> <complexType name="ObjKeyType"> <sequence> <element name="rant” type="spppb:OrgIdType"/> <element name="name” type="spppb:ObjNameType"/> </sequence> </complexType>

  6. Operations and Object Identity • Concrete structure of all the SPPP operations (the “verbs” ) delegated to the transport specification. • Operations specified in normative text in the protocol document. • Concrete structure of the object identity (the object “key”) for all the SPPP objects delegated to the transport specification. • Object identity attributes specified in normative text in the protocol document. • Object identity structure defined in an abstract form in the protocol document.

  7. Response Types and Codes… • Response Types normatively defined in the protocol document in a transport-independent fashion | Response Type | Description |+-------------------------------+------------------------------------------------------------- + | Request Succeeded | Any conforming specification MUST define a | | | response to indicate that a given request | | | succeeded. | • Concrete structure of the SPPP responses for all SPPP operations delegated to transport document.

  8. Security Considerations (now) Addressed… • Non-repudiation (RFC 4949) • Information disclosure • Replay attacks • Man-in-the-middle attacks

  9. TBDs • Terminology • e.g., remove the prefix “sppp” from name of the XML structures in transport document • Internationalization • See mailing list for more information • Editorial nits

More Related