1 / 3

Simple Notification and Alarm Protocol (SNAP) draft-shapira-snap-05

Simple Notification and Alarm Protocol (SNAP) draft-shapira-snap-05. IETF-56 Update. Noam Shapira Noam.shapira@comverse.com. Status. Seems that each time we think we are there, rejections come up (some times reopening previous decisions!) We need to decide:

abram
Download Presentation

Simple Notification and Alarm Protocol (SNAP) draft-shapira-snap-05

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. Simple Notification and Alarm Protocol (SNAP)draft-shapira-snap-05 IETF-56 Update Noam Shapira Noam.shapira@comverse.com

  2. Status • Seems that each time we think we are there, rejections come up (some times reopening previous decisions!) • We need to decide: • Do we want SNAP to conform with the “Server to Server Protocol requirements” – if so, SNAP will need to have substantial changes (like subscription). Or, • Do we want SNAP to do some “must do changes” (like security) and close it as soon as possible Evolution of ISENS : Rifkin/Khare

  3. How do we continue? We want to close it for the next IETF meeting – but: We need to decide if Server to Server draft is a pre-requisite – if so it might take longer Hope more participation from lemonade members – in order to finally close the draft Evolution of ISENS : Rifkin/Khare

More Related