IETF Logo Mail Archive

Re: When the IETF can discuss drafts seriously?

Christopher Morrow <morrowc.lists@gmail.com> Thu, 21 December 2017 16:38 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5502126CD6; Thu, 21 Dec 2017 08:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=gmail.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 kwJ0YRF6hU9p; Thu, 21 Dec 2017 08:38:37 -0800 (PST)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 22196120727; Thu, 21 Dec 2017 08:38:37 -0800 (PST)
Received: by mail-vk0-x22c.google.com with SMTP id p144so4958690vke.11; Thu, 21 Dec 2017 08:38:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Ee5g+bGxE54gFXit/KIUqR9he93L7hCSwTwY6EGWWWg=; b=k4TkC9L0cO7d3u3S1WsRep3rk8QA3jjKQQZHj51LvpBcy/ah/YUEgYNcJ+JSdPQyFL vO2znvOXg7OESJVIh9fmdD9Qd9wfLyT5LJNqYExn9NWDZZQvHnQ7AR2ftUQL0NFKIdHY TLZ8MurZegiE1jM04TqxJ3oTQwE2katAjpm+woxRU43cVksKJn5SUyiZ8KZU0GfCrO8i 33VTjsO+qgBdZ5KRPMnifsSvO9bB/yqNmn7ERKsq/+rT8Sb37gGilyYBXx6tlyiH8Em1 Rm4D6ifn3QW9d90jH0snXsUBOhbcalYdi9P+HF2vknDsd5q5+h5B+I5MPHvdiVuwdXIH XKAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Ee5g+bGxE54gFXit/KIUqR9he93L7hCSwTwY6EGWWWg=; b=tnNqiVl1x6srHYu5cR4JSu6z90Y6H4gR6iF5Ctm7lemIpYRopfjJjL7LkQPbHyii2G OmTBB+uPECnyPPujpAhuAMb3bmKO30lUxApF7c7ISkf+rEJJDf0U+RQDRaBcDbS3EDv+ 8v1OuvklqSmvGIFhLLpfx+F65LxWE0f2WBGgl4w5RuUpnU+bGwSyvx/9u+d7zVNqnCbz BZ1bAeNdfgrcTwchQJReuSzcqiVpfNo2m+ngT70u+rXWoelVasJtzls2MR5287Jy/z71 SXpvSZF4/VfJGNMH/KWwk2TYtnrz4jlfFTajqqW/ACcW7shVE9igm88BIp/AGjEl7OJp SjdQ==
X-Gm-Message-State: AKGB3mIcc2AsYZW9eoWHJt8bT4zeOCuvOzb+ZIn9L3yeSA2kcnPj1eWt seu1qfPA8i5frMXiQe8UuAFxeJvJKwf4S8GiDmk=
X-Google-Smtp-Source: ACJfBoscsr1VF4GdV5lmiyS48ixy8gQt7Bj39cE13WvZcHu3xZLKWtKTdZwzhBTqYuuCTOJf1STiAp3dHyvKp/qy8QU=
X-Received: by 10.31.170.203 with SMTP id t194mr7082138vke.172.1513874316022; Thu, 21 Dec 2017 08:38:36 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.176.80.139 with HTTP; Thu, 21 Dec 2017 08:38:35 -0800 (PST)
In-Reply-To: <1F3AC01AA49DD3BE543CCB9E@PSB>
References: <AM4PR0401MB2241817BD0EEEE79B32C8CD2BD0F0@AM4PR0401MB2241.eurprd04.prod.outlook.com> <51b495e6-ee1d-4224-6c7c-dec0f8248cc9@cisco.com> <D6601576.27F3B%christer.holmberg@ericsson.com> <BBF5DDFE515C3946BC18D733B20DAD233AA98562@XMB122CNC.rim.net> <AM4PR0401MB22414952845433B8D59CCC90BD0C0@AM4PR0401MB2241.eurprd04.prod.outlook.com> <BBF5DDFE515C3946BC18D733B20DAD233AA98825@XMB122CNC.rim.net> <60324BD8-E91D-49C7-9AE6-C6E22C836AC8@fugue.com> <AM5P190MB0434A92C65FE8657EB533315AE0D0@AM5P190MB0434.EURP190.PROD.OUTLOOK.COM> <CAKW6Ri4oBtE7CsBNuDkd=pCM-ztHfo5xdGNG300e=RiJ2fODOg@mail.gmail.com> <1F3AC01AA49DD3BE543CCB9E@PSB>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Thu, 21 Dec 2017 11:38:35 -0500
X-Google-Sender-Auth: A6X1_wYan8ePXYaVFw6fLDksZMQ
Message-ID: <CAL9jLaaVhZpTkoPCWm9RnJXgebXgC1yMMUAXz78KPi5EuPh7cw@mail.gmail.com>
Subject: Re: When the IETF can discuss drafts seriously?
To: John C Klensin <john-ietf@jck.com>
Cc: Khaled Omar <eng.khaled.omar@outlook.com>, ietf <ietf@ietf.org>, rtgwg <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="001a114326c4d75b3a0560dc54d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/z_0ZRWFw92aaCcMTCVAH5NEphcE>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Dec 2017 16:38:44 -0000

The actual problem here is that the draft discussion's don't actually
belong on the IETF@ list though... They belong in their respective WG
lists, or perhaps on the IRTF list.

Can we just move the discussion(s) there? :)

On Thu, Dec 21, 2017 at 10:56 AM, John C Klensin <john-ietf@jck.com> wrote:

> Folks,
>
> May I suggest that we wind this discussion thread down.
>
> Whether correct or not, analyses of Khaled's character are
> probably not helpful and repetitive versions of them are less
> so.  The S/N ratio on the IETF list is never wonderful and this
> thread should not contribute to making it worse.
>
> At least IMO, Khaled has been given a number of quite
> constructive suggestions (both on-list and off) about how to
> proceed if he wants to do so.   Almost all of them include
> focusing on a problem statement and/or a careful and reflect
> literature review and analysis, but, if he wants to make
> progress, he needs to understand the details of those
> suggestions.
>
> Let's give him time to do that and see what, in the form of a
> draft focused on those topics, he comes up with and, in the
> process, try to reserve judgment about intentions, quality of
> listening, etc.
>
> best,
>     john
>
>

v2.23.0 | Report a Bug | By Email