Re: Operations requirement: no hop-by-hop

> At 2:21 PM -0500 2/13/04, Keith Moore wrote:
> >I don't see that this is a requirement, but I do think it would be
> >a useful design choice if we could make it work.
> 
> I see it as a requirement for some of the other requirements we have, 
> like definitive delivery notices and tracking.

I see those as goals also, rather than requirements.
Requirements are things that cannot be compromised, and I can't tell yet 
whether we can actually insist on one-hop routing without sacrificing
other important goals.  (for instance, I suspect sites will be reluctant
to expose internal network MTAs to the outside world, even though my
own belief is that this would work best for everyone)

but if I were to start today to try to actually design a new mail system,
I'd design it to be one-hop and see how well that worked.

--
He not busy being born, is busy dying.		- Bob Dylan