Re: Operations requirement: no hop-by-hop

On Sun, 15 Feb 2004, Paul Hoffman / IMC wrote:

> The mail-ng transport protocol should be designed to only know about 
> a single hop, from sender to recipient. The sender may have multiple 
> hops to a designated transport agent, and the receiving transport 
> agent may have multiple hops to a mailstore, but the transport 
> protocol should not make any accommodation for these additional hops 
> other than to allow them to add metadata to the transit stream. 
I completely agree with above way of designing mail-ng

> These requirements are to make the protocol more sensible and to limit 
> the responsibility of operators to just what they control.
I'd like to add here that protocol should not prevent operators and mail 
agents from making their own decisions about where to send the mail and 
that the protocol itself should allow for some kind of extension mechanism 
to announce or help in such decisions.

-- 
William Leibzon
Elan Networks
[email protected]