IETF Logo Mail Archive

Re: [Rmt] FLUTE revision

"Gillies, Don" <dgillies@qualcomm.com> Wed, 26 January 2011 07:28 UTC

Return-Path: <dgillies@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 2D0A23A6946 for <rmt@core3.amsl.com>; Tue, 25 Jan 2011 23:28:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, 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 WsgpJHnqY3YK for <rmt@core3.amsl.com>; Tue, 25 Jan 2011 23:28:39 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id B4F883A6939 for <rmt@ietf.org>; Tue, 25 Jan 2011 23:28:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=dgillies@qualcomm.com; q=dns/txt; s=qcdkim; t=1296027098; x=1327563098; h=from:to:subject:thread-topic:thread-index:date: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: x-originating-ip:content-type:content-transfer-encoding: mime-version; z=From:=20"Gillies,=20Don"=20<dgillies@qualcomm.com>|To: =20"rmt@ietf.org"=20<rmt@ietf.org>|Subject:=20RE:=20[Rmt] =20FLUTE=20revision|Thread-Topic:=20[Rmt]=20FLUTE=20revis ion|Thread-Index:=20Acu7/s3bu02S0/6jkUWpHOn8pWpptAAsUGeAA CE/sQAADUPTgAAP619Q|Date:=20Wed,=2026=20Jan=202011=2007:3 1:37=20+0000|Message-ID:=20<C6B80B17C44541438510B42A18D01 B7A04E378@nasanexd01g.na.qualcomm.com>|References:=20<C96 4AE1C.89AF%luby@qualcomm.com>=20<4D3FC721.3070807@tut.fi> |In-Reply-To:=20<4D3FC721.3070807@tut.fi> |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|x-originating-ip: =20[172.30.39.5]|Content-Type:=20text/plain=3B=20charset =3D"us-ascii"|Content-Transfer-Encoding:=20quoted-printab le|MIME-Version:=201.0; bh=nmHUK9u+4fguxwvMlXeKjCBKy9CkxPdb8oeZfMHiCwo=; b=T1rsUUvdhWXiPN0N0bBv5g22zPeVkdAA/EnIMl9fey+ZkLOS4aIwG2Hx XIDEDIBeen8efsO0L12whxIrf6GcNX7uwExWAHWK2Zb9t/Pc2WLv9YqJL AX1YKR7Sm8RGkW8ZE7DQCLQJRsRhcoc5SAAeQ2vEWVW0YnPhLmEjiOOjw s=;
X-IronPort-AV: E=McAfee;i="5400,1158,6237"; a="72016387"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 25 Jan 2011 23:31:38 -0800
X-IronPort-AV: E=Sophos;i="4.60,378,1291622400"; d="scan'208";a="24930643"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 25 Jan 2011 23:31:38 -0800
Received: from NASANEXD01G.na.qualcomm.com ([fe80::c0c6:d0ab:610c:4263]) by nasanexhc05.na.qualcomm.com ([::1]) with mapi id 14.01.0218.012; Tue, 25 Jan 2011 23:31:38 -0800
From: "Gillies, Don" <dgillies@qualcomm.com>
To: "rmt@ietf.org" <rmt@ietf.org>
Thread-Topic: [Rmt] FLUTE revision
Thread-Index: Acu7/s3bu02S0/6jkUWpHOn8pWpptAAsUGeAACE/sQAADUPTgAAP619Q
Date: Wed, 26 Jan 2011 07:31:37 +0000
Message-ID: <C6B80B17C44541438510B42A18D01B7A04E378@nasanexd01g.na.qualcomm.com>
References: <C964AE1C.89AF%luby@qualcomm.com> <4D3FC721.3070807@tut.fi>
In-Reply-To: <4D3FC721.3070807@tut.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.30.39.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Rmt] FLUTE revision
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: Wed, 26 Jan 2011 07:28:41 -0000

I had one more question about FLUTE FDTs after reading the r12 FLUTE spec.

Is it required that the FDT have a table entry for the FDT itself (i.e. should the
FDT be self-describing?)  So for a typical flute session does TOI=0 have to appear
in the table of attributes?

I could not tell if the FDT had to reference itself.  Since only TOI and URI are 
required for a file in the FDT, it seems useful to me to have the URI in case I
wanted to fetch the latest version of an FDT via unicast.

- Don Gillies
Qualcomm Incorporated

v2.40.4 | Report a Bug | By Email | System Status