Re: DTNWG proposal is a terribly bad idea
Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 20 July 2014 17:19 UTC
Return-Path: <abdussalambaryun@gmail.com>
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 4B85B1B2877; Sun, 20 Jul 2014 10:19:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 2cEQpdgagaDs; Sun, 20 Jul 2014 10:19:53 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC2C51B28B2; Sun, 20 Jul 2014 10:19:52 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id n3so3202942wiv.4 for <multiple recipients>; Sun, 20 Jul 2014 10:19:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rEBx2naDUV7gxkuaNleSWt9H5qLOIV0SbmsJW26aefs=; b=rlXJSmlWhTGl4SEKvss+JtkYPBgfMoe+30gxHWzwezP4noZ2k41Dy77D3XqcCViYB5 zHcNJcZRdzUQxD6Q//mXbfhMz7nqBleDbPFFp/JeiaI/ev+cHoL6daRn8Dec6+4/qEzr sKrJlIapywfdRL79VMu/QIDujLB7JA7T7HmgImh2CyzX+AocgtGIs40A7Hw6kTtAiq8t 1nM5qj8OIYitqBG2Lc0VsdvceQXfmd2S/AumSpXa7CQo6ELPn0mJg1Hlaz3cWpS6Ji+V DVRAscTxFKv3wggN8ids1OG7MQzUUju9mLuNtzd+hCmgXpLMYIMmV8OXVdleTnWGmkHg cCHA==
MIME-Version: 1.0
X-Received: by 10.194.92.115 with SMTP id cl19mr15191941wjb.29.1405876791210; Sun, 20 Jul 2014 10:19:51 -0700 (PDT)
Received: by 10.180.102.7 with HTTP; Sun, 20 Jul 2014 10:19:51 -0700 (PDT)
In-Reply-To: <53CAD4EB.2090502@acm.org>
References: <1405740483446.13356@surrey.ac.uk> <53CAD4EB.2090502@acm.org>
Date: Sun, 20 Jul 2014 18:19:51 +0100
Message-ID: <CADnDZ88ge=dNM-3vHZY6smDg-FMCBG0dCTo5bn4G4POoQsXieg@mail.gmail.com>
Subject: Re: DTNWG proposal is a terribly bad idea
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Avri Doria <avri@acm.org>
Content-Type: multipart/alternative; boundary="047d7bfcf88ebcf91104fea332d3"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xGa1q8LNzCIPSgEk5If-CVp3UrE
Cc: "ietf@ietf.org" <ietf@ietf.org>, "dtn@ietf.org" <dtn@ietf.org>
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: Sun, 20 Jul 2014 17:19:54 -0000
I also think it is a good idea to start this WG which I support, we don't need to focus on the protocol proposed in 5050 but on the DTN use cases and any protocol can be our start discussion/comparison of new DTN experimental drafts. AB On Saturday, July 19, 2014, Avri Doria wrote: > > > On 18-Jul-14 23:28, l.wood@surrey.ac.uk <javascript:;> wrote: > > I think that having an IETF workgroup push the technically > > flawed Bundle Protocol through on standards track, after years > > of poor development and unfixed problems > > > I thought that the work of a WG was to take the work done by a RG and > make it production worthy, I.e.fix whatever flaws and experimental > deficiencies there might be in the outputs. > > I know you have had another solutions in mind since the beginning of > time, but many of us have found RFC5050 and some of the other work done > in the DTNRG to offer useful solutions to our communications requirements. > > And building on the IETF tradition that, for the most part, the IETF > works on protocols and the market decides which it wants to use, I think > taking the work of the DTNRG and the expereince that many of us having > using that protocols and turning some of it into production worthy > protocols is a really good idea. Then the world can decide whether they > want to use them or not. > > As I missed the initial announcement, I am glad you pointed it out, as I > just subscribed and am in general support the idea of a proposal for a > DTNWG. > > thanks > > avri > >
- DTNWG proposal is a terribly bad idea l.wood
- Re: [dtn-interest] DTNWG proposal is a terribly b… Vint Cerf
- Re: [dtn-interest] DTNWG proposal is a terribly b… Nabil Benamar
- Re: DTNWG proposal is a terribly bad idea Avri Doria
- Re: DTNWG proposal is a terribly bad idea Abdussalam Baryun
- Re: DTNWG proposal is a terribly bad idea Pete Resnick
- Re: DTNWG proposal is a terribly bad idea Vint Cerf
- RE: [dtn-interest] DTNWG proposal is a terribly b… l.wood
- Re: [dtn-interest] DTNWG proposal is a terribly b… Vint Cerf
- RE: [dtn-interest] DTNWG proposal is a terribly b… l.wood
- RE: [dtn-interest] DTNWG proposal is a terribly b… Tom Chaffee
- Re: [dtn-interest] DTNWG proposal is a terribly b… Eric Travis
- Re: [dtn-interest] DTNWG proposal is a terribly b… Masataka Ohta