[Rmt] last call on Raptor publication
Lorenzo Vicisano <lorenzo@cisco.com> Mon, 05 June 2006 19:15 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnKXp-0008Ee-HN; Mon, 05 Jun 2006 15:15:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnKXn-0008EZ-Hd for rmt@ietf.org; Mon, 05 Jun 2006 15:15:19 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnKXm-0003L8-7I for rmt@ietf.org; Mon, 05 Jun 2006 15:15:19 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-4.cisco.com with ESMTP; 05 Jun 2006 12:15:17 -0700
X-IronPort-AV: i="4.05,211,1146466800"; d="scan'208"; a="1819520278:sNHT77198534"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k55JFHZh022674 for <rmt@ietf.org>; Mon, 5 Jun 2006 12:15:17 -0700
Received: from lorenzo-u10.cisco.com (lorenzo-u10.cisco.com [128.107.162.143]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k55JFH9s000931 for <rmt@ietf.org>; Mon, 5 Jun 2006 12:15:17 -0700 (PDT)
Received: (lorenzo@localhost) by lorenzo-u10.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA15277 for rmt@ietf.org; Mon, 5 Jun 2006 12:15:17 -0700 (PDT)
X-Authentication-Warning: lorenzo-u10.cisco.com: lorenzo set sender to lorenzo@cisco.com using -f
Date: Mon, 05 Jun 2006 12:14:54 -0700
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: rmt@ietf.org
Message-ID: <20060605191454.GB4586@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
DKIM-Signature: a=rsa-sha1; q=dns; l=2386; t=1149534917; x=1150398917; c=relaxed/simple; s=sjdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lorenzo@cisco.com; z=From:Lorenzo=20Vicisano=20<lorenzo@cisco.com> |Subject:last=20call=20on=20Raptor=20publication; X=v=3Dcisco.com=3B=20h=3D5HYp3SKxvDwjCpREZE7X1k8Kkkc=3D; b=D3Pd4iBNc8JeWJU94RAcnApmWoKAJOghPIx+o7RcUudf38/iP/1ZZZreqAIllr5+Q2ol404N 7QCRvCGr2VjoCZaN6l9oPXNKcmfW/jgEqWqQCCqpHrgH7o4TflczY1J9;
Authentication-Results: sj-dkim-2.cisco.com; header.From=lorenzo@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Subject: [Rmt] last call on Raptor publication
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
Errors-To: rmt-bounces@ietf.org
As you know, Digital Fountain changed the IPR statement for the FEC ID Raptor (draft-ietf-rmt-bb-fec-raptor-object) withdrawing the "RAND" terms (please see the email that Mark Watson sent to this list, attached below). This thread is to settle once for all the position of the RMT WG on this issue, in particular regarding whether and how the WG wants to sponsor raptor for publication. We have the options of: a) asking the IESG to publish raptor as a Standard-Track document (as originally planned). b) abandoning raptor as a WG standard c) asking the IESG to publish raptor as experimental or informational. Note that this might create problems with the IANA allocation of FEC IDs etc. This issue was already discussed on this list and at the last IETF meeting (Dallas). So far we have had some comments in favor of option a) and no comments against it. Please express your opinion by June 19th. If we have no feedback by then, we will assume that the WG wishes to go for a), given the previous discussions. thank you, Lorenzo ################# Mark's email attached below ####################### All, As most of you are aware, Digital Fountain has to date been promoting our core technology, DF Raptor, as an open standard in IETF RMT and elsewhere, for any and all applications. This mail is to let you know about a change to that strategy: As a result of a recent, significant new relationship that is crucial to Digital Fountain with a prime contractor in the defense industry, our approach going forward will be to promote Raptor as an open standard for specific markets and applications including of course 3GPP and DVB standards where Raptor has already been adopted and others in future. However, this means revising the IPR statement that we have made to the IETF regarding draft-ietf-rmt-bb-fec-raptor-object because, whilst we still offer RAND terms for specific standards such as 3GPP and DVB, we are no longer able to offer RAND terms independent of market and application. Going forward, there are several options regarding draft-ietf-rmt-fec-raptor-object, including not publishing it at all. This is of course a decision for the IETF and Digital Fountain will not take a position in that discussion. Best regards, Mark Watson Digital Fountain _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt
- [Rmt] last call on Raptor publication Lorenzo Vicisano
- Re: [Rmt] last call on Raptor publication Marshall Eubanks
- Re: [Rmt] last call on Raptor publication Marshall Eubanks
- Re: [Rmt] last call on Raptor publication Mike Luby
- Re: [Rmt] last call on Raptor publication Marshall Eubanks
- Re: [Rmt] last call on Raptor publication Magnus Westerlund
- Re: [Rmt] last call on Raptor publication Marshall Eubanks
- Re: [Rmt] last call on Raptor publication Mark Handley