Re: [Rmt] FLUTE v2

<Rod.Walsh@nokia.com> Tue, 07 June 2011 06:45 UTC

Return-Path: <Rod.Walsh@nokia.com>
X-Original-To: rmt@ietfa.amsl.com
Delivered-To: rmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3FF411E8081 for <rmt@ietfa.amsl.com>; Mon, 6 Jun 2011 23:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id epQzh4BVim4L for <rmt@ietfa.amsl.com>; Mon, 6 Jun 2011 23:45:37 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 1D93B11E807B for <rmt@ietf.org>; Mon, 6 Jun 2011 23:45:35 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p576jR4T009363; Tue, 7 Jun 2011 09:45:34 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 7 Jun 2011 09:45:28 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by nok-am1mhub-03.mgdnok.nokia.com ([65.54.30.7]) with mapi; Tue, 7 Jun 2011 08:45:27 +0200
From: <Rod.Walsh@nokia.com>
To: <luby@qualcomm.com>, <rmt@ietf.org>
Date: Tue, 7 Jun 2011 08:45:25 +0200
Thread-Topic: [Rmt] FLUTE v2
Thread-Index: Acwk3nuq2L7YXho0SdmvifrnPd1ATw==
Message-ID: <4DEDC905.6090607@nokia.com>
References: <CA12BCEE.D7B3%luby@qualcomm.com>
In-Reply-To: <CA12BCEE.D7B3%luby@qualcomm.com>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_4DEDC9056090607nokiacom_"
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Jun 2011 06:45:28.0153 (UTC) FILETIME=[7CC50C90:01CC24DE]
X-Nokia-AV: Clean
Subject: Re: [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: Tue, 07 Jun 2011 06:45:38 -0000

Hi Mike et al.

Yes v2. Sensible proposal, let's do that.

Now would be a good time to catalogue all (if any) remaining questions RMTers feel are still open, with a view to a June/July WGLC.

There are a few open questions (on the RMT list) still hanging, but my own understanding is that even the changes I do not understand the reasoning for don't actually harm any implementation. So personally, I will not be resurrecting any prior threads.

Likewise, those active in other SDOs that may be impacted by a standards track FLUTE would do us all a great favour by drawing attention to the imminent WGLC also in the WGs of those SDO and so offer a little extra time (just before the vacation season) for cross-SDO contentment and harmony. Please post to the RMT mail list activity on this as it occurs so that we don't inadvertently send redundant messages (and so that we can assume that an SDO is not yet in the loop where no RMT list email mentions it).

Cheers, Rod.



On 07/06/2011 03:17, ext Luby, Michael wrote:

Hi Rod,
Does your email below mean that you agree to change the revised FLUTE to
version number to 2 at this point?  If so, then I think this would help to
move the revised FLUTE on to the next step in the IETF process, since the
current draft of the revised FLUTE already has the FLUTE version number set
to 2, and thus no changes to the draft would be needed to move the revised
FLUTE to the next step, and as far as I know everyone else who has commented
is on board with making the revised FLUTE be FLUTE version 2 as the
practical path out of the possibilities.  If you meant something else, I
apologize for misinterpreting your email.
Best, Mike


On 5/9/11 4:39 AM, "Rod Walsh" <rod.walsh@nokia.com><mailto:rod.walsh@nokia.com> wrote:

> 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...
>
> http://www.ietf.org/mail-archive/web/rmt/current/msg01513.html
>
> ...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.

_______________________________________________
Rmt mailing list
Rmt@ietf.org<mailto:Rmt@ietf.org>
https://www.ietf.org/mailman/listinfo/rmt