[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: http://www.ietf.org/internet-drafts/draft-ietf-opes-protocol- reqs-00.txt



Title: RE: http://www.ietf.org/internet-drafts/draft-ietf-opes-protocol-reqs-00.txt

+1

abbie

> -----Original Message-----
> From: Eric Burger [mailto:eburger@xxxxxxxxxxxxx]
> Sent: Monday, June 03, 2002 1:30 PM
> To: Markus Hofmann
> Cc: OPES Group
> Subject: RE:
> http://www.ietf.org/internet-drafts/draft-ietf-opes-protocol-r
> eqs-00.txt
>
>
>
> We're struggling with the very issue in the CATS work group. 
> In the CATS
> case, we were hoping OPES would either come up with a
> solution or make it
> acceptable to punt for now.
>
> My vote is to punt.
>
> -----Original Message-----
> On Behalf Of Markus Hofmann:
>
> [snip]
> Nevertheless, one might wonder whether the benefits that could be
> expected from chaining callout servers outweight the increased
> complexity, in particular with respect to trust relationships,
> privacy, security, etc. Therefore, I'd be little bit hesitant to put
> more specific requirements for callout server chaining on the calloout
> protocol.
>
>