IETF Logo Mail Archive

Re: [Rmt] FLUTE revised 12

"Luby, Michael" <luby@qualcomm.com> Sun, 06 February 2011 22:30 UTC

Return-Path: <luby@qualcomm.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 C457D3A6B0D for <rmt@core3.amsl.com>; Sun, 6 Feb 2011 14:30:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level:
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 EkVGq+-EVtW5 for <rmt@core3.amsl.com>; Sun, 6 Feb 2011 14:30:31 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 4775A3A6A3C for <rmt@ietf.org>; Sun, 6 Feb 2011 14:30:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=luby@qualcomm.com; q=dns/txt; s=qcdkim; t=1297031434; x=1328567434; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:user-agent: acceptlanguage:content-type:mime-version; z=From:=20"Luby,=20Michael"=20<luby@qualcomm.com>|To:=20Ro d=20Walsh=20<rod.walsh@nokia.com>|CC:=20"rmt@ietf.org"=20 <rmt@ietf.org>,=20David=20Harrington=20<dharrington@huawe i.com>|Date:=20Sun,=206=20Feb=202011=2014:30:31=20-0800 |Subject:=20Re:=20[Rmt]=20FLUTE=20revised=2012 |Thread-Topic:=20[Rmt]=20FLUTE=20revised=2012 |Thread-Index:=20AcvGLvEWKEu5xsQWThi0Qr+xpLYiaQAHoU6x |Message-ID:=20<C9746107.91CB%luby@qualcomm.com> |In-Reply-To:=20<9F28EEB2-AFCC-4851-B4C8-E25FE1FC4C18@nok ia.com>|Accept-Language:=20en-US|Content-Language:=20en-U S|X-MS-Has-Attach:|X-MS-TNEF-Correlator:|user-agent:=20Mi crosoft-Entourage/13.8.0.101117|acceptlanguage:=20en-US |Content-Type:=20multipart/alternative=3B=0D=0A=09boundar y=3D"_000_C974610791CBlubyqualcommcom_"|MIME-Version:=201 .0; bh=4vil7cO1jqDaVRVHgxYHV8DhiUEEMmPmKgQ+mjGKTmw=; b=yNnZaHKOLpDt3+QqfntTTwMINSQS2qG8U/Ig+urMZFGHGZXVCG9enD08 VPgyqOQqO7zTjjozca1qsWdN5Gx84igq1YaBBDWWEQfYdk0DjrDUmzpN8 /roYgxaytLcyH50rDWwk2CW7HoQFyQHZ+F95mXtuqMOynVmUW2+tDGhz8 s=;
X-IronPort-AV: E=McAfee;i="5400,1158,6249"; a="73218988"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 06 Feb 2011 14:30:33 -0800
X-IronPort-AV: E=Sophos; i="4.60,433,1291622400"; d="scan'208,217"; a="48480217"
Received: from nasanexhub02.na.qualcomm.com ([10.46.143.120]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-MD5; 06 Feb 2011 14:30:33 -0800
Received: from nasclexhc02.na.qualcomm.com (10.227.147.13) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.3.83.0; Sun, 6 Feb 2011 14:30:33 -0800
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.112]) by nasclexhc02.na.qualcomm.com ([10.227.147.13]) with mapi; Sun, 6 Feb 2011 14:30:33 -0800
From: "Luby, Michael" <luby@qualcomm.com>
To: Rod Walsh <rod.walsh@nokia.com>
Date: Sun, 06 Feb 2011 14:30:31 -0800
Thread-Topic: [Rmt] FLUTE revised 12
Thread-Index: AcvGLvEWKEu5xsQWThi0Qr+xpLYiaQAHoU6x
Message-ID: <C9746107.91CB%luby@qualcomm.com>
In-Reply-To: <9F28EEB2-AFCC-4851-B4C8-E25FE1FC4C18@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.8.0.101117
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C974610791CBlubyqualcommcom_"
MIME-Version: 1.0
Cc: David Harrington <dharrington@huawei.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [Rmt] FLUTE revised 12
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: Sun, 06 Feb 2011 22:30:35 -0000

Hi Rod,
A good place to start is to look at section 11, the change log.  A lot of the changes were across the different specs (ALC & LCT and FEC BB), moving the functionality around from FLUTE to LCT or ALC, etc.  These changes are really difficult to undo the already existing revised RFCs for LCT, ALC and FEC BB.  Also, some XML changes, etc.

What is your main concern with having this be FLUTE version 2 instead of FLUTE version 1?
Best, Mike


On 2/6/11 10:52 AM, "Rod Walsh" <rod.walsh@nokia.com> wrote:

Hi all

Do we have an answer on the question: why is a non-backwards compatible FDT schema necessarily?

 (I.e. I am concerned that the right path forward might be to discard changes which remove backwards compatibility, and so far we are collectively ignoring this elephant in the room. What did I miss?)

Cheers, Rod.



On 4 Feb 2011, at 17:40, "ext Luby, Michael" <luby@qualcomm.com> wrote:

David, Other RMTers,

There is now version 12 of FLUTE revised available as an Internet Draft.  The major change in version 12 compared to version 11 is to change the FLUTE version number from 1 to 2.  This was changed in all the references to the FLUTE version, and there is wording added to Section 3.1 on the requirements around the FLUTE version number in operation for both senders and receivers.  Also, the FLUTE version number is added as an optional parameter in Section  6.  The change log in Section 11 is also updated.  There are also a few grammatical fixes/improvements/clarifications.

I would like to thank Don Gillies for spending the time and enthusiastically getting up to speed on FLUTE (and also ALC and LCT and FEC BB) in a detailed way and helping to carefully craft the changes in this late stage draft, he did a wonderful job (and in the final RFC he should be thanked in the acknowledgements for his contributions).  However,  I take complete responsibility for all errors or issues that are introduced into this version 12 from version 11.  (So, read it over carefully and make sure that it is ok, etc.).

Thanks, Mike
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www.ietf.org/mailman/listinfo/rmt

v2.23.0 | Report a Bug | By Email