Re: [apps-discuss] AD sponsoring draft-masotta-tftpexts-windowsize-opt-09

Joe Touch <touch@isi.edu> Tue, 18 March 2014 18:28 UTC

Return-Path: <touch@isi.edu>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F7171A0453; Tue, 18 Mar 2014 11:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level:
X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iD7Hiz97hrzS; Tue, 18 Mar 2014 11:28:05 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 919061A0401; Tue, 18 Mar 2014 11:28:05 -0700 (PDT)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s2IIOtEq013399 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 18 Mar 2014 11:25:00 -0700 (PDT)
Message-ID: <53288F78.7030503@isi.edu>
Date: Tue, 18 Mar 2014 11:24:56 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <53222FC1.7040009@bogus.com> <532367CA.4080807@isi.edu> <53247DCD.40002@bogus.com> <53249F15.7010802@isi.edu> <0f9fb6b8c92609346c3a4111f2c31349.squirrel@www.erg.abdn.ac.uk> <532870D8.4090106@bogus.com> <53288174.6050209@isi.edu> <CAC4RtVCnHd6UPDChmu+ge_LV+FD9RyAjkbTtjeMWXd2=hZAT2A@mail.gmail.com>
In-Reply-To: <CAC4RtVCnHd6UPDChmu+ge_LV+FD9RyAjkbTtjeMWXd2=hZAT2A@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/j8h8pLoJeKHnuxCQZ947QyuUISY
Cc: gorry@erg.abdn.ac.uk, tsv-area@ietf.org, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, Martin Stiemerling <martin.stiemerling@neclab.eu>
Subject: Re: [apps-discuss] AD sponsoring draft-masotta-tftpexts-windowsize-opt-09
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Mar 2014 18:28:10 -0000

On 3/18/2014 11:18 AM, Barry Leiba wrote:
> Just one bit here that Joel has touched on, but that I want to say clearly:
>
>> The authors need to make the case to the TSVWG (?) that this needs to become
>> a WG doc, and then we can all scrutinize/optimize it in public.
>
> 1. It's absolutely right to say that &WG (be that TSVWG or any other)
> needs to review a document that's being put forth for IETF consensus.
>
> 2. It's absolutely right to say that the comments that result from
> that review need to be addressed.
>
> 3. I believe it is *not* right to say that the document cannot go
> forward unless &WG accepts it as a working group product.  If they do,
> that's very nice.  If they reject it because of fundamental flaws that
> have not been adequately addressed, then loop back to #2.  But if they
> simply don't want it, that isn't a valid reason to stop the document
> from progressing.

Hazard to the Internet?

At the least, it would presumably have a very high hurdle for being 
standards-track.

But I don't understand why a protocol extension that would be considered 
harmful must be published by the RFC Editor.

Joe