SIP in higher education

[Ben Teitelbaum <>]

I have confirmed Alan Crosswell.  As we confirm attendees, please use
the Subject line format that I used above.  It will simplify things
later when we want to generate lists of anticipated attendees.

-- ben

--- Begin Message ---

• From: Alan Crosswell <>
• To: Dennis Baron <>, Steve Blair <>, Ben Teitelbaum <>
• Subject: Re: First SIP.edu Implementors Workshop
• Date: Fri, 14 May 2004 14:32:13 -0400
• Xref: curvaceous mail.inbox:53991

I like the registration technique:-) You can call me at
sip:

or call my phonemail at
sip:.
But you doesn't have to call me
Johnson.
/a


Dennis Baron wrote:
> This is an early invitation to the First SIP.edu Implementors Workshop.
> We wanted to make sure that you had the date on your calendar and are
> hoping that you will be able to attend. RSVP as soon as possible - we
> are trying to keep the group small and are limiting participation to
> 1-2 people per school. Comments or suggestions on the draft agenda
> are also welcome.
>
> - Ben, Dennis, and Steve
>
> --------
>
> First SIP.edu Implementors
> Wednesday, June 16th, 2004 8:00am - 4:00pm
> University of Pennsylvania
> http://voip.internet2.edu/SIP.edu/200406-workshop/ (draft)
>
> This workshop is primarily for campus data and telecommunications
> technologists who have implemented the initial SIP.edu architecture or
> who are in the course of implementing it. The goals for this one-day
> workshop are to:
>
> * Build a knowledge base for those that will follow in deploying
> SIP.edu;
>
> * Investigate areas that the SIP.edu community should pursue,
> individually or as a group, in order to leverage SIP as a core
> technology for new campus communications services and
> collaboration applications;
>
> * Expand the leadership group for SIP.edu;
>
> * Chart a course for scaling up campus and inter-campus SIP service
> deployment.
>
>
> Draft Agenda
> ------------
>
> * Welcome
> - Workshop goals and agenda review
>
> * SIP.edu Overview
> - Project goals and status
>
> * Campus Deployment Experience Reports
> - Reports from schools that have implemented SIP.edu
> - Proxy and gateway configuration issues
> - Campus directory integration issues
>
> * Directory best practices
>
> * Issues on the Horizon
> - SIP spam - how do we prepare for it?
> - Peering relationships - Free World Dialup and other requests
> for peering
> - Reverse SIP.edu - reaching SIP.edu URIs from legacy phones
> - Discussion: Do we need a SIP.edu community routing policy?
>
> * Moving SIP.edu forward
> - SIP.edu Cookbook - what's needed; next steps
> - SIP.edu as a foundation for better-than-POTS communication
> - Discussion: How do we get from sandboxes to services?


--- End Message ---