Download
1 / 6
60 likes | 179 Vues
The WGLC for the SPPP Protocol draft-ietf-drinks-spprov-09 was issued in April, receiving feedback from Dean Willis. Key comments addressed capitalization inconsistencies, spelling issues, the coherence of terminology, and clarifications on authentication, authorization, and transport protocol. Notably, it was determined that no IANA registry is needed for response codes. Updates include specifying that time values must be in absolute UTC without timezone offsets. Further clarity on error handling is also proposed, favoring a single "stop and rollback" approach. Next steps will focus on implementing these updates.
E N D
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 Guidance on transport protocol Whether an IANA registry is needed for response codes Time values Security Considerations section
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
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
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.
