1 / 6

SPPP Protocol

SPPP Protocol. Session Peering Provisioning Protocol draft-ietf-drinks-spprov- 09. Progress. WGLC was issued in April Comments received from Dean Willis Capitalization inconsistencies and spelling issues Coherence on use of terminology Clarification on authentication and authorization

colm
Download Presentation

SPPP Protocol

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 Protocol Session Peering Provisioning Protocol draft-ietf-drinks-spprov-09

  2. Progress WGLC was issued in April Comments received from Dean Willis Capitalization inconsistencies and spelling issues Coherence on use of terminology Clarification on authentication and authorization Guidance on transport protocol Whether an IANA registry is needed for response codes Time values Security Considerations section

  3. Updates • Capitalization inconsistencies and spelling issues • Coherence on use of terminology • Clarification on authentication and authorization • Proposed mandatory SOAP-based transport • No need for a IANA registry for response codes

  4. Updates • Time Value • MUST BE absolute UTC time • Timezone offset in the value are disallowed • “Security Considerations” section • still leans on the transport protocol for all matters of confidentiality, authentication, and authorization

  5. Progress • 5.1.1.1 Update Request • Current spec notes that there is a choice of error handling as “stop and rollback” or “stop and commit”. Further, it is left to the implementers to exercise it as a matter of policy • For clarity, and to eliminate interoperability issues, the design team agreed that the text needs to be modified in favor of a single “stop and rollback” option.

  6. Next Steps

More Related