VoIP Meeting Requirements 22/03/2006 – Saverio Niccolini and Fabio Vena

Agenda - Roll Call - Requirements statement (each participant) - Identification of common requirements - Identification of requirements difficult to be integrated in a common framework - AoB

Meeting Objectives Discuss about VoIP Deployment requirements the output will serve as an input to the next meetings on Architecture Authentication and Authorization Peering Accounting and Billing Security Equipments and Experiences

Roll Call Joao Pereira (FCCN) Fabio Vena (SWITCH) Antonio Pininzotto (CNR) Jan Ruzicka (CESNET) Saverio Niccolini (NEC) Erik Dobbelsteijn (SURFNET)

Requirements statement FCCN (Joao Pereira) dialing schemes preserve the PSTN numbers already in use use E.164 dialing scheme integrate SIP URIs in the dialing scheme (for people ready to use them) reduce number of ISDN connections to the operators (costs saving) preserve the telephony infrastructures in the universities infrastructure independent of the Telco operator meet legal requirements (lawful interception) management system available integration of eduroam mobility support audio/video support integration of value added services (messaging, collaboration, voic )

Requirements statement Jan Ruzicka (CESNET) standardized protocol multi-protocol environment (need for translators) multi-vendor environment dialing scheme mix of numbers and SIP URIs E911 services audio/video support integration of value added services (conferencing, recording, streaming, phone books, reservation systems, messaging, collaboration, voic ) AAI infrastructure local domain inter-domain usage of peering points SBC IP-to-IP gateway seamless mobility (on and off call mobility) NAT/FW traversal soft-phones usage accounting (mainly for statistic reasons) meet legal requirements (lawful interception) security (signaling and media) management local system testing systems for troubleshooting, monitoring

Requirements statement Fabio Vena (SWITCH) dialing scheme SIP.edu compliance preserve the PSTN numbers already in use use E.164 dialing scheme symmetric approach to SIP.edu audio/video support integration of value added services (conferencing, recording, presence, instant messaging) management at the universities accounts and setup are managed there sharing of expensive resources billing directly to the universities

Requirements statement Erik Dobbelsteijn (SURFNET) services for which institutions are the customers security SPIT prevention trust relationship management at the universities accounts and setup are managed there usage of existing AAI infrastructure compliance with H.350 ENUM support SIP-based optional support for H.323 integration of GDS (nice to have) peering platform per country integration of VoIP providers audio/video support H.239 wide codecs support

Requirements statement Saverio Niccolini (NEC) peering architectures and best practices security SPIT prevention authentication and trust

Requirements statement Antonio Pininzotto (CNR) dialing scheme SIP.edu compliance preserve the PSTN numbers already in use use E.164 dialing scheme IP trunking audio/video support value added services security multi-vendor environment

Common requirements We resumed following common requirements Nationwide SIP deployment Use of standardized protocols will assure the support of value added services(video, presence, IM...) Preserve PSTN numbers, use of ENUM Using of existing AAI infrastructure Coordination in authentication and trust for SPIT protection

Problematic requirements for a common framework

AoB Discusion about dedicated SIP Taskforce, after TF-VVC SIP Workshop Terena Conference Do we need hands-on, practical part? We have to clarify which kind of people will participate Base workshop on Video conference, invite people to bring along webcams Perhaps base on openSER, instead of SER