North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: botnets: web servers, end-systems and Vint Cerf [LONG, sorry]

  • From: Roland Dobbins
  • Date: Mon Feb 19 12:24:18 2007
  • Authentication-results: rtp-dkim-1; [email protected]; dkim=pass ( sig from verified; );
  • Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=985; t=1171905421; x=1172769421; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;; [email protected]; z=From:=20Roland=20Dobbins=20<[email protected]> |Subject:=20Re=3A=20botnets=3A=20web=20servers,=20end-systems=20and=20Vin t=20Cerf=20[LONG,=20sorry] |Sender:=20 |To:=20NANOG=20<[email protected]>; bh=nRnvt/YNrkqjidULLaGLq8fxooOCoFAzwt6m6GcUDOA=; b=KX0YPmO1bVuQubjjUQptpW9XumVmqcAb2Zhy1EArneW8Rk4W+GuTVvLsnT30ip+C1OrRJYkX ClszabPjKq8wNaczlZ4MyArYnRhKAqqM3KYEBJrRasBSwo8hsDFzcpHB;

I look forward to your paper on "the end to end concept, and
why it doesn't
apply to email" ;)

I think the problem here is that people invoke something they think of as 'the end-to-end principle', but actually isn't.

from < endtoend.pdf>:


. . . functions placed at low levels of a system may be redundant or of little
value when compared with the cost of providing them at that low level.


*That* is the actual 'end-to-end principle'. The imposition of hierarchy in application-layer email routing (or DNS infrastructure, etc.) has nothing to do with the actual end-to-end principle, except as a good example of honoring it.

Roland Dobbins <[email protected]> // 408.527.6376 voice

The telephone demands complete participation.

-- Marshall McLuhan