Re: grrp-reqs-06, 3.2 Identification and Authentication [3]

[Kent Crispin <kent@songbird.com>]

On Wed, Feb 14, 2001 at 03:32:00PM -0500, Jordyn A. Buchanan wrote:
[...]
>  I'm 
> prepared to acknowledge that we're not dealing with the full scope of data 
> policy elements, but I don't think that means we should give up on solving 
> the problems that we can or hastily adopting a transport mechanism that may 
> or may not be well suited for the protocol we develop.

I'm not sure that there is any conflict here.

>>Note these data collection policies are not specific to any particular datum
>>(or object) within a flow between R-* entities, any more than are the A & I
>>policies.
> 
> Yes they are.  A couple of examples:

[examples]

Granted, but I don't think this is a major point.

>>How the data policies are implemented is (implementation specific). How they
>>are announced, let alone "negociated" is a protocol requirement, assuming that
>>policy differences do in fact exist. I think they do.
> 
> I agree they exist, but my point is that these policies are likely to be 
> announced and negotiated out-of-band on a contractual or regulatory 
> basis.  Additionally, they are unlikely to change with regularity, so 
> there's no need for dynamic negotiation to occur.

I don't read Eric's statement above as a contradiction to that point.  

-- 
Kent Crispin                               "Be good, and you will be
kent@songbird.com                           lonesome." -- Mark Twain