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

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

Return-Path: <barryleiba.mailing.lists@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 A788D1A0743; Tue, 18 Mar 2014 11:21:11 -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 V8Ik_i3bUt_P; Tue, 18 Mar 2014 11:21:10 -0700 (PDT)
Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 2E7DF1A077B; Tue, 18 Mar 2014 11:18:56 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id jx11so7604819veb.3 for <multiple recipients>; Tue, 18 Mar 2014 11:18:47 -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=MVt2379YF8IW2Wk+I7T/MBTHF63Hl8aOZnAklXPr5eM=; b=dAwtHjTmKufpAu4FsDqKGAJ1nSneebkFNiYAM3aGAe/YLJ5SeFQx+dbaEWSQl4oN8e 7txY1YT5mZpilaFV9UUHuhSsnOGhwVmmIHtYCI1QF6k3V/irWGhwOLHjmlyYIVO1RBA1 H9Ts9hd92sMvlpxHjOzoFmRhD0DKbIJysAR+6mjmEmiseIN37IK1nEWTuZ2gMRz78u4U mQon7ceTmBLi+xpu71E+ZFsyt6BEZVP4ZeXzYPFhSO0WTynLcm37Ip6S45EMxhA6fhan 9QKp/xRUffNmuD5epKvnqx8UlclREwXttdUWnWKyh+/561TTT9xvgqiD5jxHWga7c1MU YlOQ==
MIME-Version: 1.0
X-Received: by 10.58.55.170 with SMTP id t10mr4874981vep.29.1395166727709; Tue, 18 Mar 2014 11:18:47 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Tue, 18 Mar 2014 11:18:47 -0700 (PDT)
In-Reply-To: <53288174.6050209@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>
Date: Tue, 18 Mar 2014 14:18:47 -0400
X-Google-Sender-Auth: YCLpz9Hz9nmtGhllfSA662PNSCA
Message-ID: <CAC4RtVCnHd6UPDChmu+ge_LV+FD9RyAjkbTtjeMWXd2=hZAT2A@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/NxI9NXp9O6C5rszdiAgKY6swKik
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 18:21:11 -0000

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.

I think we're likely in agreement on this, but, as I say, I want to
put it out there clearly.

Barry