Re: To "lose the argument in the WG"

Ted Lemon <mellon@fugue.com> Sun, 19 February 2017 00:41 UTC

Return-Path: <mellon@fugue.com>
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 8C06B1296AC for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 J8ib8QMj2E2I for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:41:33 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E61B1296AF for <ietf@ietf.org>; Sat, 18 Feb 2017 16:41:33 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id k15so65426134qtg.3 for <ietf@ietf.org>; Sat, 18 Feb 2017 16:41:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=FGIK1K2IbMDUnCG2xDAFHShAXvi1ftj8qDpbbd+4kJk=; b=QOiU5K2996n7DcqglTmwv7wLzpQ1FR5rFoNFMp4hm/sn/WvY35K2Pd7C+/pWSLtGsh z1DN5etJWF35xM4CEXELG+XxuhDR3OVDS6CKqmOrBPu7Oljq8yRgHe2D4i10yx+iCdue mx0TMnrt0kzia8FtoPv7/qOwAbZHiPFDtRr54Zl7HTBmIChBuylmdNU4vxfXS0MYQT4/ sJfFc8RQzBuwWu7UWyPvIE5MuKmO0FC4vWyrRQuzEaaamNJ9EIdgo1W41WQaCZSQ3Yg4 uYsR0pHdB5+AP6bGLL8UIxO1hs1KJpaVd0hJGWt94ew2He60K+5mmaPFBxUYU2sRa4rY 2eqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=FGIK1K2IbMDUnCG2xDAFHShAXvi1ftj8qDpbbd+4kJk=; b=oUrF9CH6o4xdOQ6M2QUmUkmcatgZztlvX4nxbw7JmjS+h0RTs7Zw7Petxicj3MIUqr 7Og14KdOdgbT4KifI2ocZH8bd8jgcZe4Zd6O/4vROoFuRZH6GAxUyokj8DRloA+4p0/q mylJJ+U5509QiGZaV8NY/EfATc4FXKtPPSF4T7gSyQrOLeyzr/K2gfWp+aJtLstxue0e JV61CbgTRLNsvvIUOOVb+eeuLOAg5atU9x0nRQhh/7fraWE606Ov4t/obUFcrfUzvydC /SGAcfQ93hbFWfttILRWmH0DZ4Y/etMhYyMrag7PwGHOWsqn/mpRVle3F+98DCcHXCfR /UOQ==
X-Gm-Message-State: AMke39m0jl64qoUxjMB2yBpfNo74Pd/yyDGmpFrpzFcvlfjIL07oV1DN+OkGoPM87RhIiQ==
X-Received: by 10.237.55.196 with SMTP id j62mr13315461qtb.36.1487464892219; Sat, 18 Feb 2017 16:41:32 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id x13sm9353580qtc.51.2017.02.18.16.41.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Feb 2017 16:41:30 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <EF9DE86E-C964-4E92-BA48-B1555786C19B@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_76357102-0246-4D44-A253-9BF6B83FDC16"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Sat, 18 Feb 2017 19:41:20 -0500
In-Reply-To: <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CgEVevUIekzDoT3e8kY_AwOm4UE>
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 19 Feb 2017 00:41:34 -0000

On Feb 18, 2017, at 6:59 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> It is up to the Working Group Chair and Responsible Area Director to assess whether the WG output falls within the WG Charter.

This is technically true, but it's worth pointing out that working group charters are approved first by the IETF, and only _then_ by the IESG.   If the IESG decides that the working group charter is much broader than the IETF agreed it is, then that is a process failure. 

In practice the IETF often leaves these issues entirely to the IESG, so in practice this isn't necessarily a problem, but in principle it is, and you can't know whether the IETF said nothing about a charter because we agreed with the scope, or because we didn't look at it; in the former case, the IETF actually does have a position on the scope of the charter—it's just unstated, because it agrees with what was proposed.   Going beyond that scope would definitely be a process failure.