1 / 3

SPIRITS

SPIRITS. Chairs: Steve Bellovin <smb@research.att.com> Alec Brusilovsky <abrusilovsky@lucent.com>. Agenda. Goals of the session - Alec Brusilovsky - 3 min. Agenda bashing - General Discussion - 2 min.

lazar
Download Presentation

SPIRITS

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. SPIRITS Chairs: Steve Bellovin <smb@research.att.com> Alec Brusilovsky <abrusilovsky@lucent.com> San Francisco, CA

  2. Agenda • Goals of the session - Alec Brusilovsky - 3 min. • Agenda bashing - General Discussion - 2 min. • Issues from the mail exploder regarding the SPIRITS Protocol I-D - General Discussion - 15 min.   • subscribing to multiple DPs; • representing non-call related events • Source:www.ietf.org/internet-drafts/draft-ietf-spirits-protocol-04.txt • SPIRITS Protocol Security - General Discussion - 10 min • Source: www.ietf.org/internet-drafts/draft-ietf-spirits-security-00.txt • SPIRITS and mobility issues - General Discussion - 10 min. • Sources:www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-01.txt www.ietf.org/internet-drafts/draft-brusilovsky-spirits-is41-00.txt • SPIRITS Implementation - General Discussion  - 15 min. • Source:www.ietf.org/internet-drafts/draft-gurbani-spirits-implementation-00.txt • Conclusions - General discussion - 5 min. San Francisco, CA

  3. Goals and milestones achieved • Pre-protocol work: • Informational RFC2995 – • Pre-Spirits Implementations of PSTN-initiated Services; • Informational RFC3136 - The SPIRITS Architecture; • SPIRITS Protocol Requirements – current Informational RFC Candidate; • Protocol proposals: • INAP parameters for the SPIRITS protocol - • <draft-ietf-spirits-in-02.txt> • On selection of IN parameters to be carried by the SPIRITS Protocol <draft-unmehopa-spirits-parameters-00.txt> • SIP Events Package for the SPIRITS protocol <http://www.ietf.org/internet-drafts/draft-ietf-spirits-sip-evt-package-01.txt> San Francisco, CA

More Related