Due to previous ipal name collision discovered last week the project has been renamed PRISP, big thanks to GertJan Hagenaars for this name. Again if people would like to participate, this project will develop opensource software (or framework and database schema for such software) to help ISPs in tracking setup of new network services and connections. This would include allocation of ip addresses and database of such allocations, database of circuits and network devices, administration and colloboration on actual provisioning process for new connections (both for physical circuits and logical connections such as for colo customer), etc. At some distant future project homepage will be located at www.prisp.org currently there is a sourceforge project info at: http://sourceforge.net/projects/prisp/ If you're interested in helping, please join the mail list: http://lists.sourceforge.net/mailman/listinfo/prisp-discuss Or send email to prisp-discuss-subscribe@lists.sourceforge.net with usual "subscribe" in subject and body For reference for those who may join mail list after this message, below is the first email that is starting real project discussions (there have been some smaller discussions last week on different mail lists but we're starting it all again to keep track of this in archives): -------------------------------------------------------------------------- Date: Mon, 15 Mar 2004 13:40:26 -080D (PST) From: "william(at)elan.net" <wi0liam@elan.net> To: prisp-discuss@lists.sourceforge.net Subject: Open discussion - service provisioning components We'll open the discussion with what people would like to see in the service provisioning database software. Try to think of what network engineers are doing when setting up new customer and which settings might be general enough to be part of some database as well as which of those settings can be automated in some way. Might also be good if in your reply, you order these settings by how they come up in the actual provisioning process. -- William Leibzon Elan Networks william@elan.net