Re: [Rmt] Rmt Digest, Vol 77, Issue 5

Rod Walsh <rod.walsh@nokia.com> Mon, 14 February 2011 15:15 UTC

Return-Path: <Rod.Walsh@nokia.com>
X-Original-To: rmt@core3.amsl.com
Delivered-To: rmt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC8303A6D6B for <rmt@core3.amsl.com>; Mon, 14 Feb 2011 07:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.789
X-Spam-Level:
X-Spam-Status: No, score=-2.789 tagged_above=-999 required=5 tests=[AWL=0.810, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJ5rJ86nisuD for <rmt@core3.amsl.com>; Mon, 14 Feb 2011 07:15:50 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id E42EA3A6D6D for <rmt@ietf.org>; Mon, 14 Feb 2011 07:15:49 -0800 (PST)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p1EFFh6o003202; Mon, 14 Feb 2011 17:16:11 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Feb 2011 17:15:58 +0200
Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 14 Feb 2011 16:15:57 +0100
Received: from tr-hermia5-dhcp044120.europe.nokia.com (172.22.44.120) by clientsmtp.nokia.com (65.54.30.57) with Microsoft SMTP Server id 14.1.270.2; Mon, 14 Feb 2011 16:15:57 +0100
Message-ID: <4D594726.4030408@nokia.com>
Date: Mon, 14 Feb 2011 17:15:50 +0200
From: Rod Walsh <rod.walsh@nokia.com>
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
MIME-Version: 1.0
To: "ext brian.adamson@nrl.navy.mil" <brian.adamson@nrl.navy.mil>
References: <C9798543.94EE%luby@qualcomm.com> <D0B5C418-AEF5-4E4C-8983-6F2ADD3A64A3@nrl.navy.mil>
In-Reply-To: <D0B5C418-AEF5-4E4C-8983-6F2ADD3A64A3@nrl.navy.mil>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.22.44.120]
X-OriginalArrivalTime: 14 Feb 2011 15:15:58.0242 (UTC) FILETIME=[150BF820:01CBCC5A]
X-Nokia-AV: Clean
Cc: Michael Luby <luby@qualcomm.com>, rmt@ietf.org
Subject: Re: [Rmt] Rmt Digest, Vol 77, Issue 5
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 14 Feb 2011 15:15:50 -0000

On FLUTE, the Nordic part of the core team won't be in Prague, so it 
might be appropriate to formalise the FLUTE meeting with precise agenda 
and minutes so we maximise progress also with those on a tight travel 
budget.

For me the three hot issues are:
  - who takes actions to ensure a backwards compatible FLUTE is 
specified if humanly possible?
  - who sends (not IETF style) liaison communications (and do we 
consensus pre-comment) to related FLUTE SDOs to review FLUTE one last 
time? (And on what version - revised 12 contains the v2 conundrum, so 
let's not assume that one)
  - when does Rod find time to spend with Jani to get FLUTE-SDP updated? 
(And then bang the drum for "any final thoughts and possibly update" 
before WGLC).

More?

Cheers, Rod.


On 14/02/2011 16:22, ext brian.adamson@nrl.navy.mil wrote:
> I have submitted a meeting request for a small session.
>
>
> Brian Adamson
> brian.adamson@nrl.navy.mil
>
>
>
>
>
> On Feb 10, 2011, at 3:06 PM, Luby, Michael wrote:
>
>> Hi Brian,
>> I think it would be good to have a meeting to work out issues with FLUTE in
>> person (if people can make it to the meeting).  Also, I may be proposing a
>> new fec encoding id draft, in which case it would be good to make a decision
>> on whether this should be handled in rmt or submitted to wherever fec
>> encoding id proposals go after rmt shuts down.
>> Best, Mike
>>
>>
>> On 2/10/11 12:00 PM, "rmt-request@ietf.org"<rmt-request@ietf.org>  wrote:
>>
>>> If you have received this digest without all the individual message
>>> attachments you will need to update your digest options in your list
>>> subscription.  To do so, go to
>>>
>>> https://www.ietf.org/mailman/listinfo/rmt
>>>
>>> Click the 'Unsubscribe or edit options' button, log in, and set "Get
>>> MIME or Plain Text Digests?" to MIME.  You can set this option
>>> globally for all the list digests you receive at this point.
>>>
>>>
>>>
>>> Send Rmt mailing list submissions to
>>> rmt@ietf.org
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>> https://www.ietf.org/mailman/listinfo/rmt
>>> or, via email, send a message with subject or body 'help' to
>>> rmt-request@ietf.org
>>>
>>> You can reach the person managing the list at
>>> rmt-owner@ietf.org
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Rmt digest..."
>> _______________________________________________
>> Rmt mailing list
>> Rmt@ietf.org
>> https://www.ietf.org/mailman/listinfo/rmt
>>
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www.ietf.org/mailman/listinfo/rmt