Re: Loops (RE: CPIM changes)

Dave Crocker <[email protected]> writes:

> 3. RFC822 is a format standard, not a gateway service standard. The topic
> being discussed hear is about requiring loop control in a gateway for any
> instant messaging system.

Dave,

I would say the topic being discussed here is defining protocols and
data formats necessary to build an internet-scale end-user presence
awareness, notification and instant messaging system.  This is what
the description of our working group states.

After much discussion, we have decided to achieve this goal by relying
on other protocols to provide the part of the system that does not
impact our goal.  Loop detection is an essential part of any
internet-scale system, and loops cannot be detected without a common
syntax that can be understood by every protocol used to build the
system.  This means we must act.

It's the same story as with end-to-end security.  Common formats and
digest methods must be defined.  Once again, this means we must act.
We are charged with defining that which is needed to build a system,
not a group of loosely interacting services.

John




  [reminder: [email protected] for non-technical discussions, please]