[Rmt] FLUTE v2

<Rod.Walsh@nokia.com> Mon, 09 May 2011 14:27 UTC

Return-Path: <Rod.Walsh@nokia.com>
X-Original-To: rmt@ietfa.amsl.com
Delivered-To: rmt@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 715E3E077E for <rmt@ietfa.amsl.com>; Mon, 9 May 2011 07:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1ghKJaOXWzVL for <rmt@ietfa.amsl.com>; Mon, 9 May 2011 07:27:43 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com []) by ietfa.amsl.com (Postfix) with ESMTP id 894B8E077C for <rmt@ietf.org>; Mon, 9 May 2011 07:27:42 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com []) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p49Bdhtq004377 for <rmt@ietf.org>; Mon, 9 May 2011 14:39:57 +0300
Received: from smtp.mgd.nokia.com ([]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 9 May 2011 14:39:40 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([]) by nok-am1mhub-03.mgdnok.nokia.com ([]) with mapi; Mon, 9 May 2011 13:39:40 +0200
From: <Rod.Walsh@nokia.com>
To: <rmt@ietf.org>
Date: Mon, 9 May 2011 13:39:44 +0200
Thread-Topic: FLUTE v2
Thread-Index: AcwOPce/nj8EBm4mQ4qFjHTwA5ZJ0A==
Message-ID: <484630C0-8527-4A25-970A-A51739BCCCC3@nokia.com>
References: <20110506054943.29436.39522.idtracker@ietfa.amsl.com>
In-Reply-To: <20110506054943.29436.39522.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 09 May 2011 11:39:40.0650 (UTC) FILETIME=[C87F94A0:01CC0E3D]
X-Nokia-AV: Clean
Subject: [Rmt] FLUTE v2
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 14:27:44 -0000

Hi all

It's pretty clear that as a group and individuals we are short of the energy and determination to tie-up every loose thread of the RMT adventure. For me, the one and only issue preventing FLUTE staying at the sensible and consistent v1 status was highlight by Mike...


...running through all the specs and the multitude of related SDO adoptions takes a lot of footwork and singular dedication. I'm am not in such a position to do that nowadays. Even running through the maze of security IDs and RFCs to get FLUTE-SDP finished has taken months to get done on-the-side.

So unless we have an energetic and enthusiastic spec miner who is willing to take on the task Mike pointed out, then I propose we push forward to a v1.1.

(just kidding, we should all the way to 1.9 :)

And thus, with Jani's energy and hard work, I can focus on the finished flute-SDP (coming any day now).

Cheers, Rod.