Presence and IntComm WG

[Jorj Bauer <>]

> The PIC.edu project does not require use of the package and will  
> certainly include institutions which may be further along and who  
> know enough to make different decisions.  In fact, these members are  
> the ones that we would like a lot of participation from right now so  
> that their experiences and lessons learned can be shared.  This will  
> help us build the best base config.
> - Tim

It was a little more than that. We were discussing possible protocol  
development, which would require modifying servers (at first) and  
possibly clients (down the road).

We discussed that everyone would be able to run their preferred server  
as part of the pic.edu "1.0" project, but that some advanced features  
and development (for a future version of pic.edu) would require  
something more specific (whether that be the exact same code, or  
locally developed patches elsewhere to do the same thing). There was  
no discussion as to whether or not these two would run concurrently or  
consecutively (although I don't see any reason why they wouldn't run  
concurrently as, for example, a production and a development  
environment with the same institution, communicating respectively with  
other production and development environments).

Farther down the road, if the PICwg develops protocol additions/ 
modifications, I would hope they would be adopted as standards and  
thus would wind up in the products that everyone is using (both server- 
side and client-side).

-- Jorj

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Attachment: PGP.sig
Description: This is a digitally signed message part