Re: [dtn-interest] DTNWG proposal is a terribly bad idea

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 25 July 2014 08:33 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B671A008F for <ietf@ietfa.amsl.com>; Fri, 25 Jul 2014 01:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.608
X-Spam-Level:
X-Spam-Status: No, score=0.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cj09X6Rq5wms for <ietf@ietfa.amsl.com>; Fri, 25 Jul 2014 01:33:54 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C8C701A007A for <ietf@ietf.org>; Fri, 25 Jul 2014 01:33:53 -0700 (PDT)
Received: (qmail 48190 invoked from network); 25 Jul 2014 08:23:49 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 25 Jul 2014 08:23:49 -0000
Message-ID: <53D21669.7060304@necom830.hpcl.titech.ac.jp>
Date: Fri, 25 Jul 2014 17:33:45 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [dtn-interest] DTNWG proposal is a terribly bad idea
References: <1405740483446.13356@surrey.ac.uk> <CAHxHggd-FDtBsnLEtFQ_PMmOMX-qfsu9r00bDUnqK4c=OZdPQw@mail.gmail.com> <1406082066584.5322@surrey.ac.uk>, <CAKovV0xxboZ1khYKyaTxGe2jgCpP2f=+2PtKP5JaHMmszr-BBA@mail.gmail.com> <1406119182015.34201@surrey.ac.uk>
In-Reply-To: <1406119182015.34201@surrey.ac.uk>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/et3FyacSGhH1X7AvGLDUAiP6zkA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2014 08:33:57 -0000

l.wood@surrey.ac.uk wrote:

> I'd argue that, in ignoring the ramifications of the
> end-to-end principle, the effects of errors, and needing
> synchronized clocks, that the Bundle Protocol fundamentally
> ignores entropy.

It seems to me that DTN and the Bundle protocol is wrongly
architected. As the Internet is mostly non-disruptive,
disruption tolerating technologies should be used only
in the disruptive part of the Internet.

As the Internet allows for great variations in L2 technologies,
some L2, such as IEEE1394, does have synchronized clock within
a link without ignoring entropy, though it is useless to other
part of the Internet.

And, for the disruptive part of the Internet, at the application
layer, we already have a solution: SMTP, POP, IMAP and MX of DNS.

Don't try to solve an already solved old problem.

Protocols like Bundle may be used by a pair of SMTP relays,
communication between which is very disruptive, as is
stated in rfc821:

   SMTP is independent of the particular transmission subsystem and
   requires only a reliable ordered data stream channel.

though Bundle, it seems to me, is partly a link and partly
a transport protocol.

					Masataka Ohta