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

Barry Leiba <barryleiba@computer.org> Tue, 18 March 2014 19:14 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCC761A0455; Tue, 18 Mar 2014 12:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 osnx5xricKmp; Tue, 18 Mar 2014 12:14:46 -0700 (PDT)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B0AB61A044C; Tue, 18 Mar 2014 12:14:45 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id e9so8576980qcy.1 for <multiple recipients>; Tue, 18 Mar 2014 12:14:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wqDPN+7tA/aj+zHTWDKkvriiLIRs4M/ctDnlyQby0uQ=; b=syMc+Q0YVyIrjsuVHI8AOTv1WCInddlNWDZ55YC+CLI+msIpeQZB7nvH/K6knvy8RY vSsBdnzd3GEcfH/ALyWIEplLJuvZ7JADIdVH7/Xz8BQWTUCCFy/icgvUGbO+WndZvrTz e+mbtni5lG6VknIUTF2mnroSYbSxaz34DdMY3qmQKwfDxegSMl+q1vvhumVOvHY4IshA Jca8qzeafuZscNXsKInkb4VYxCs/TMSYwzdBXAwdz15nlixxvLU+aKKJi2aO4I6FJJ/7 wOIx2FVgXyKGDeQ0vIZx5cYKV+EUZiTtB0NJWf4JwgdDBbOw+ssBH/k1tGNgrwqkJQdJ t5Bw==
MIME-Version: 1.0
X-Received: by 10.140.93.77 with SMTP id c71mr35659057qge.53.1395170077239; Tue, 18 Mar 2014 12:14:37 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.42.136 with HTTP; Tue, 18 Mar 2014 12:14:37 -0700 (PDT)
In-Reply-To: <53288F78.7030503@isi.edu>
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> <53288F78.7030503@isi.edu>
Date: Tue, 18 Mar 2014 15:14:37 -0400
X-Google-Sender-Auth: aZNG_2a6sEPRCsxj1ia1zYVSzNo
Message-ID: <CALaySJLx=uHqtxG0m=vhxqN8LGtkouBPazwh_YVQSZo6P2TNsQ@mail.gmail.com>
Subject: Re: [apps-discuss] AD sponsoring draft-masotta-tftpexts-windowsize-opt-09
From: Barry Leiba <barryleiba@computer.org>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/tsv-area/vP8lxFYlpsvaNbMuZ_1YmNg_7HY
Cc: joel jaeggli <joelja@bogus.com>, tsv-area@ietf.org, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, Martin Stiemerling <martin.stiemerling@neclab.eu>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Mar 2014 19:14:47 -0000

>> 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?

Hazard to the Internet would be a fundamental flaw that would have to
be addressed, of course.

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

Nothing considered harmful.  I thought I was clear that those things
need to be sorted out.

I'm just saying that lack of interest from some particular working
group isn't a reason to block publication.  Serious flaws, or lack of
interest from everyone... that's different.

Barry