RE: Requirements Document

> I'm sorry, but if this group can't generate a solution
> for emergency calls in a SIP environment, we need to
> spin up a group RIGHT NOW for that purpose.

Given the difficulty this group had getting chartered, there's precious little
chance of chartering such a group, regardless of how urgent you believe the
need for such a group to be. So I strongly recommend that you try and work
towards getting an acceptable solution here.

> I do not read the charter as anywhere near that limiting.
> In fact, I read it as it will define an object suitable for
> a wide range of uses, and illustrate it with HTTP.

The primary goal is to meet the privacy and security requirements set forth in
the charter. This is absolute and nonnegotiable, and while this group may elect
to (and IMO should) provide mechanisms for emergency calls, a broader range of
scenarios much be dealt with as well.

A secondary goal is to produce a binding of the object/exchange mechanism this
group comes up with to HTTP.

I suppose it is possible that whatever this group decides is necessary
isn't well matched to HTTP. If that's the case then so be it -- privacy
and security concerns are paramount here.

                                Ned
Received on Thu Aug 30 10:22:38 2001