PSTN Internet Notification BOF (pin) Monday, March 15 at 1530-1730 ============================= Chair: Alec Brusilovsky BACKGROUND: With the proliferation and wide acceptance of the Internet, and more so with the convergence of the Internet and PSTN, there is an increasing desire for events occurring on the PSTN domain to be propagated to the Internet domain. The PIN attempts to fill this void. Entities on the Internet domain can receive the events generated by the PSTN domain and act appropriately. The major entities that comprise of the PIN protocol are the PIN Gateway, the PIN Server and various PIN clients. The Internet Draft "Need for PSTN Internet Notification (PIN) Services" will be published at IETF no later then February 19, 1999. DESCRIPTION: With the proliferation and wide acceptance of the Internet, and more so with the convergence of the Internet and PSTN, there is an increasing desire for events occurring on the PSTN domain to be propagated to the Internet domain. The protocol of the PINT working group is used to pass requests for service from an IP host to a telephone network, and to receive responses back from the telephone network. But some Interworking services require that requests for services go in the opposite direction: from a telephone network to an IP host. The Internet Draft "Need for PSTN Internet Notification (PIN) Services" is available from the official IETF directory and explains the need and gives some requirements for such requests for service and for notification. The PIN BOF will examine the sorts of Telephone Services that present requirements for such requests from a telephone network to a set of IP hosts. It is important that we agree on the scope of requests for service and notification that such services might generate. There are various working groups and protocols (most notably IPTEL, PINT, and MEGACO) which might have relevance for the sort of services we want to enable. In addition to a discussion of the scope and requirements of an eventual PIN working group, the PIN BOF will need to understand if those requirements are being fulfilled by these or other working groups. At the BOF there will be a series of short presentations of various solutions in industry use. These will be examined only to help us understand the scope of the services we want to support. Our goal is to decide whether or not a new protocol or protocol family is needed, and, if so, what its scope and requirements should be. AGENDA: 1. Agenda bashing, Introduction and Drivers - Alec Brusilovsky, Lucent - 5 min. 2. Goals of this BOF - Steve Bellovin, AT&T - 5 min. 3. PIN Services and Proposed Architecture - Vijay Gurbani, Lucent - 5 min. 4. PIN Services for Advanced Caller ID Delivery, Lev Slutsman, AT&T - 5 min. 5. Definition of requirements and protocols that would enable notification - Goutam Shaw, Bridgewater - 5 min. 6. PIN as a Services Enabler - Stephen Cohoon, SBC - 5 min. 7. SAINT Service Taxonomy. Summary of the needs for PIN - Services and associated problems and requirements - Lawrence Conroy, Siemens - 10 min. 8. Break - 15 min. (if needed). 9. Proposed WG goals + discussion (what are PIN Services, the building block approach, scope of the proposed WG, pure Notification or Session Initiation, why PIN events can or cannot be addressed by "pure" MEGACO or RTP events, requirements for PIN Services, etc.) - 40 min. 10. Proposed WG Charter + discussion - 20 min 11. Conclusion - 5 min. Total: 120 minutes