[Rmt] FW: http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-basic-schemes-rev ised-05.txt comment / question

Mark Watson <mark@digitalfountain.com> Fri, 31 October 2008 17:32 UTC

Return-Path: <rmt-bounces@ietf.org>
X-Original-To: rmt-archive@megatron.ietf.org
Delivered-To: ietfarch-rmt-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 048673A6C83; Fri, 31 Oct 2008 10:32:01 -0700 (PDT)
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 E64A13A6C7C for <rmt@core3.amsl.com>; Fri, 31 Oct 2008 10:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.166
X-Spam-Level:
X-Spam-Status: No, score=0.166 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_NUMERIC_HELO=2.067]
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 GBTKxlG5nnMw for <rmt@core3.amsl.com>; Fri, 31 Oct 2008 10:31:55 -0700 (PDT)
Received: from server515.appriver.com (server515f.exghost.com [72.32.253.82]) by core3.amsl.com (Postfix) with ESMTP id DE9B028C2C7 for <rmt@ietf.org>; Fri, 31 Oct 2008 10:30:51 -0700 (PDT)
Received: by server515.appriver.com (CommuniGate Pro PIPE 5.2.7) with PIPE id 95104076; Fri, 31 Oct 2008 12:30:48 -0500
Received: from FE1.exchange.rackspace.com ([72.32.49.5] verified) by server515.appriver.com (CommuniGate Pro SMTP 5.2.7) with ESMTP id 95104065 for rmt@ietf.org; Fri, 31 Oct 2008 12:30:47 -0500
Received: from 34093-C4-EVS1.exchange.rackspace.com ([192.168.1.90]) by FE1.exchange.rackspace.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 31 Oct 2008 12:30:49 -0500
Received: from 76.222.192.62 ([76.222.192.62]) by 34093-C4-EVS1.exchange.rackspace.com ([192.168.1.101]) via Exchange Front-End Server owa.mailseat.com ([192.168.1.6]) with Microsoft Exchange Server HTTP-DAV ; Fri, 31 Oct 2008 17:30:49 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Fri, 31 Oct 2008 10:16:43 -0700
From: Mark Watson <mark@digitalfountain.com>
To: rmt@ietf.org
Message-ID: <C5308B8B.2FC8F%mark@digitalfountain.com>
Thread-Topic: http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-bas ic-schemes-revised-05.txt comment / question
Thread-Index: AcjoU+4taVXWRmqNSzW7bd2eEcIQ4xTKIO9o
In-Reply-To: <CA98EF1C4A4BE74C8D16FC021DAB774C0301C95B@34093-EVS4C1.exchange.rackspace.com>
Mime-version: 1.0
X-OriginalArrivalTime: 31 Oct 2008 17:30:49.0912 (UTC) FILETIME=[6AB7D380:01C93B7E]
X-Policy: GLOBAL - UNKNOWN
X-Primary: mark@digitalfountain.com
X-Note: This Email was scanned by AppRiver SecureTide
X-Virus-Scan: V-
X-Note: FCH-SI:0/SG:0
X-GBUdb-Analysis: 1, 192.168.1.90, Ugly c=1 p=-0.996385 Source White
X-Signature-Violations: 0-0-0-10529-c
X-Note: Spam Tests Failed:
X-Country-Path: UNITED STATES->PRIVATE->UNITED STATES->UNITED STATES
X-Note-Sending-IP: 72.32.49.5
X-Note-Reverse-DNS: fe1.exchange.rackspace.com
X-Note-WHTLIST: mark@digitalfountain.com
X-Note: User Rule Hits:
X-Note: Global Rule Hits: 90 91 92 93 97 98 166
X-Note: Mail Class: VALID
Cc: mikes@digitalfountain.com
Subject: [Rmt] FW: http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-basic-schemes-rev ised-05.txt comment / question
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: <https://www.ietf.org/mailman/private/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>
Content-Type: multipart/mixed; boundary="===============0431607457=="
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org

All,

I received the attached comment privately. I¹m going to interpret this as a
last call comment. I agree with the comment and propose to specify in the
­06 draft that the symbol length L is obtained from the FEC Object
Transmission Information.

...Mark


------ Forwarded Message
From: Michael Spann <mikes@digitalfountain.com>
Date: Thu, 17 Jul 2008 16:27:35 -0500
To: Mark Watson <mark@digitalfountain.com>
Conversation: 
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-basic-schemes-revi
sed-05.txt comment / question
Subject: 
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-basic-schemes-revi
sed-05.txt comment / question

Section 3.4.2 of draft-ietf-rmt-bb-fec-basic-schemes-revised-05 states

   receiver uses the source block length received out-of-band as part of

   the FEC Object Transmission Information to determine the length X in

   bytes of the source block, and allocates space for the X bytes that

   the source block requires.  The receiver also computes the length L

   of the encoding symbol in the payload of the packet by substracting

   the packet header length from the total length of the received packet

   (and the receiver checks that this length is the same in each

   subsequent received packet from the same source block).  After

typo aside (substracting?), shouldn¹t L be taken from the FEC Object
Transmission Information like X was?  What happens in the unlikely case that
the initial value for Y was selected to be N-1 and the final, potentially
short symbol was sent first?

mike


------ End of Forwarded Message

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