Last Call: <draft-ietf-rmt-bb-fec-raptorq-06.txt> (RaptorQ Forward Error Correction Scheme for Object Delivery) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 03 June 2011 15:24 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B5AE070F; Fri, 3 Jun 2011 08:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level:
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1w8b-Ub02oLm; Fri, 3 Jun 2011 08:24:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C39CE06E9; Fri, 3 Jun 2011 08:24:37 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-rmt-bb-fec-raptorq-06.txt> (RaptorQ Forward Error Correction Scheme for Object Delivery) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <20110603152437.32759.93640.idtracker@ietfa.amsl.com>
Date: Fri, 03 Jun 2011 08:24:37 -0700
Cc: rmt@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 15:24:38 -0000

The IESG has received a request from the Reliable Multicast Transport WG
(rmt) to consider the following document:
- 'RaptorQ Forward Error Correction Scheme for Object Delivery'
  <draft-ietf-rmt-bb-fec-raptorq-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-06-17. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

This is a second IETF Last Call. At IESG request, an updated IPR disclosure 
related to this document was filed by Qualcomm Incorporated to clarify the 
licensing terms vis-a-vis different applications of the technology.  
See the following link: https://datatracker.ietf.org/ipr/1553/
Because of this updated IPR disclosure, an additional RMT Working Group Last Call 
was conducted.  The only resultant working group email discussion to the revised IPR
was that it was an improvement in that it more clearly covered unicast as well as
multicast use cases of the technology.  The following URL points to the mailing
list archive message thread regarding this additional WGLC:
 
http://www.ietf.org/mail-archive/web/rmt/current/msg01547.html

Although IPR is in place, this forward error correction
technique is just one of several types that the RMT WG has specified and other,
unencumbered techniques have been defined.  Thus, the RMT WG had  previously discussed 
this matter concluding that it wished to publish this document regardless of the IPR
since this new FEC code is one of multiple alternatives that can  be used to implement
the RMT higher-level protocols, as such the possible IPR covering this does not
preclude the unencumbered implementation of the RMT Protocols.  The IPR licensing terms presented by Qualcomm appear to be reasonable.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-rmt-bb-fec-raptorq/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-rmt-bb-fec-raptorq/