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.

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.

Chairs, could we have some guidance?

Brian

> -----Original Message-----
> From: John W Noerenberg II [mailto:jwn2@qualcomm.com]
> Sent: Thursday, August 23, 2001 6:38 PM
> To: Rosen, Brian
> Cc: geopriv@mail.apps.ietf.org
> Subject: RE: Requirements Document
>
>
> At 9:34 AM -0400 8/23/01, Brian Rosen wrote:
> >Well the charter is fixed. The requirements have to be applicable to
> >a broad spectrum of use cases.
>
> Certainly our goal is the protocol will be broadly applicable. But
> you can't get there by trying to account for every possible use. It
> is impossible to imagine all the potential applications. That is a
> guarantee this group will simply flail. First, find a problem you
> can solve. We've decided to focus on HTTP and HTML. Once we have
> experience incorporating privacy considerations of location
> information into those protocols, then we have a basis to generalize
> to other situations.
> --
>
> john noerenberg
> jwn2@qualcomm.com
>
> --------------------------------------------------------------
> ------------
> Peace of mind isn't at all superficial, really. It's the
> whole thing.
> That which produces it is good maintenance; that which disturbs it
> is poor maintenance.
> -- Zen and the Art of Motorcycle Maintenance, Robert M.
> Pirsig, 1974
>
> --------------------------------------------------------------
> ------------
>
Received on Fri Aug 24 08:22:11 2001