[saag] New draft of the "pushpull delivery" specification is available
Atul Tulshibagwale <[email protected]>
| Newsgroups | gmane.ietf.saag |
|---|---|
| Message-ID | <CANtBS9eiQC-SKP69inNHdbKPUTZadUx24iU-TSsuRW_98AFGqQ@mail.gmail.com> |
Hi all, There were two drafts shared in the Saag mailing list (and in Bangkok) relating to the delivery of SETs: - Pushpull delivery - which provided a way for bidirectional communication of SETs between peer services - Multi-SET push delivery - which provided a way for a Transmitter to communicate multiple SETs in a single push delivery HTTP request, and provided an appropriate means of acknowledging previously received SETs. Since for the most part, the "pushpull delivery" covered the Multi-SET delivery mechanism, we decided to merge the two drafts into one draft. This draft has been submitted to the datatracker here: "Push and Pull Based Security Event Token (SET) Delivery <https://datatracker.ietf.org/doc/draft-tulshibagwale-saag-pushpull-delivery/> ". Thanks to Michael Jones for his earlier review of the separate documents. Those comments (mentioned in emails here <https://mailarchive.ietf.org/arch/msg/id-event/Sgamt9zeDlREM2LgCgZeLgJ2HhA/> and here <https://mailarchive.ietf.org/arch/msg/id-event/-L70NaS912ZelfzZRdxZt1aZErY/>) apply to this document too, but have been addressed in this email <https://mailarchive.ietf.org/arch/msg/id-event/VYR5FoCl-3XCfZufsnxQXuia6sQ/> . I invite everyone to please review this new draft. Thanks, Atul _______________________________________________ saag mailing list -- [email protected] To unsubscribe send an email to [email protected]