RE: Requirements Document

Well the charter is fixed. The requirements have to be applicable to
a broad spectrum of use cases. If you want to try to write examples of
an in-band mechanism, I'll participate and try to be helpful AFTER we
get the requirements that in fact are applicable to the broad spectrum
agreed.

Brian

> At 9:09 AM -0400 8/21/01, Brian Rosen wrote:
> > > >You can't write a requirement defining HOW a delegation
> >> >mechanism must work
> >>
> >> Why not? Consider dns referrals. That mechanism seems to have
> >> worked pretty well.
> >In one protocol it could. If delegation can be done by a variety
> >of mechanisms in a variety of protocols, then the requirements would
> >have to be pretty broad. That is the case here.
>
> It's better to keep the scope narrow. Demonstrate a delegation
> mechanism that works for location in one context. If we do that
> sufficiently well, others will find it useful. I'm not denying our
> charter's aim the result should be broadly applicable. I'm
> concerned, however, that if we try incorporate all possible cases,
> we'll spin our wheels.
>
Received on Thu Aug 23 09:34:18 2001