Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard

SM <sm@resistor.net> Wed, 29 February 2012 16:54 UTC

Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D3721F86C4 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 08:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.649
X-Spam-Level:
X-Spam-Status: No, score=-102.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4oaaWJ8q9QW for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 08:54:05 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA8821F8684 for <ietf@ietf.org>; Wed, 29 Feb 2012 08:54:04 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1TGrwwQ027009 for <ietf@ietf.org>; Wed, 29 Feb 2012 08:54:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330534444; i=@resistor.net; bh=QfLJ7To4yRpa8CgRUh3nMACNR7oemeG69tVi0pozS4E=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=VaD5Uohjq3OafDLZFjxkQbKRfsdvqFbKIrF1iQn4v5JCrp39BUa8pRcWsuVMhu/M3 /NV6vymftCCfBIa+LzLTJ/f8FR+H79YQVI/YAVpgw5hQ7RfBX99PKw6eA8ZynXeTbw J/1sbDWRep64E79FWPqotQo49n9BpBWknzMIC2CM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330534444; i=@resistor.net; bh=QfLJ7To4yRpa8CgRUh3nMACNR7oemeG69tVi0pozS4E=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=iyKibsj3R61iVLL+1wKyVeQLinivkzq4XlNiOC65UMWKUYHwGm2UKgb1aAU9qemEe /iSNliTmk1gg/AoawBMOZy6Z5CehlW8itVgdfyRjEsAaUPyx7FFUJ6Ufgk3rDV/hu1 /gjg9fAlv9WM0q8+OxHYGAb10bGF6CC+pRr42zd0=
Message-Id: <6.2.5.6.2.20120229083209.0a4b6268@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 Feb 2012 08:53:01 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
In-Reply-To: <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr>
References: <CB72DAA8.19D17%ietfdbh@comcast.net> <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 16:54:08 -0000

At 07:53 29-02-2012, Vincent Roca wrote:
>I didn't see you initial email (I'm not not on the ietf@ietf.org 
>mailing list), which explains why you didn't receive any feedback.

That explains why the authors did not respond to the comments.  It 
does not explain why the working group asked the IETF Community to 
review the draft.  Or is the working group using ietf@ as a 
unidirectional transport? :-)

 From the Introduction Section:

   "This document defines FLUTE version 2, a protocol for unidirectional
    delivery of files over the Internet.  This specification is not
    backwards compatible with the previous experimental version defined
    in [RFC3926]"

The Write-up mentions that this draft represents the solid consensus 
of the working group.  It also mentions that "The document is of high 
quality and has been subject to extensive review in its Internet 
Draft and Experimental RFC forms.  The revised draft represents a 
modest set of changes from the original Experimental RFC 3926.  These 
changes are clearly described in the document".  This "modest set of 
changes" affects the IPR status of the document.  The question which 
one might ask is why do a modest set of changes then.

Regards,
-sm