IETF Logo Mail Archive

Re: lastcall@ietf.org

Ted Lemon <mellon@fugue.com> Wed, 04 September 2019 12:48 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 3CD7E120115 for <ietf@ietfa.amsl.com>; Wed, 4 Sep 2019 05:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 tCXWDBiic4fK for <ietf@ietfa.amsl.com>; Wed, 4 Sep 2019 05:48:08 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 1D528120106 for <ietf@ietf.org>; Wed, 4 Sep 2019 05:48:08 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id n7so24189006qtb.6 for <ietf@ietf.org>; Wed, 04 Sep 2019 05:48:08 -0700 (PDT)
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=4ph7y8ETX0bT2NU353lQa7g/0o4CmmjR1y2KhzMqO0o=; b=CA08Fzz7ZuL6LRYI0cG+TrtxaXWseR0A8BbXj611a/EjvN8zB6QuSe58iGnPhsQvf1 tuq7b3/8kVX2EPZw9nPSG79ZOiSX+a35pRBpMy99eNwVMdH+SxerlrN3y7pzlPNy3UnO QPAGfvxEGFs2SdhR2jT7NXZlhLf6iLiOAfel7W9mSL4etTR0D2SfR94Ut4gObgBAwWrE mX/8OmdErfMc1Sv2traU0rh09R6jaIghOQC1YIQvspCZi40Rjfa+DTmvRvjcP4FoLfpB eAat70uVezMh93mcytxbg1o7AeFI52RidyI1ryfmW/50wA/eeJPHbq9HaEZhypUWIP3O lOmw==
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=4ph7y8ETX0bT2NU353lQa7g/0o4CmmjR1y2KhzMqO0o=; b=gIVIqqutKXLGGHIEdCMm6yyQNbc4SyT3G76CTD8nMzfy5j30g19Pwg01J0gvKeOYQS MgtVNrv4y0npEHc3OxyWWBd+/OdxQ0A5FInFh48Y4qycVzc8mHTSJ6QsVtoN42Gw+QCl vUf4Me8UhIROp3YVk5uPYy5pR57tuwAjWxPX852GfTnb/Bl3Jz503ADZ+H8pQgbRQODN M0Z3SmQ57cjhKIqULZm1rO8gogpGPlzuWiE1pIBVepFB0A6TToS6kJW547RuZ5PWrQzt /lJx1ubJdNZIINMxxkoxpByCntnGmslyokH8KnqXa/BvzJad6CI2gWcxw4HQoAh55PcM TGnQ==
X-Gm-Message-State: APjAAAXdi4AOEdov+AwTQ+q4Jkc2jvdyYdzMfZVO5iDqVWQ4EvVeHmAH Lpcd7Jc9wdbI6J8BFeGtkPOJkg==
X-Google-Smtp-Source: APXvYqyanw3U29EHgRA0Ovm0HFMfON0Xef+TFWhOC7XviYMIIoQI9TAVmDLHGqAkdzSXw8HGXUDveA==
X-Received: by 2002:ac8:67c7:: with SMTP id r7mr38931570qtp.372.1567601287104; Wed, 04 Sep 2019 05:48:07 -0700 (PDT)
Received: from [10.0.10.46] (c-73-186-137-119.hsd1.nh.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id m19sm10736480qke.22.2019.09.04.05.48.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Sep 2019 05:48:06 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <5A8D7D09-F910-4A7A-8D30-2EC7CED3495F@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D4A2ED7E-49E3-4919-980E-DA6A89B18686"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3578.1\))
Subject: Re: lastcall@ietf.org
Date: Wed, 04 Sep 2019 08:48:03 -0400
In-Reply-To: <9E92AA0B-4D83-4B89-A0B8-E4527F28DC1D@isode.com>
Cc: Rob Sayre <sayrer@gmail.com>, IETF discussion list <ietf@ietf.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <CAChr6SzEavDBiw5U3CxFruk6cbfHXy=JCubvYMvZq1hG9-ijcA@mail.gmail.com> <9E92AA0B-4D83-4B89-A0B8-E4527F28DC1D@isode.com>
X-Mailer: Apple Mail (2.3578.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wVnwlPa1PYHS84JhFxnA6M-nzxg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 04 Sep 2019 12:48:10 -0000

On Sep 4, 2019, at 4:36 AM, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
> Yes, IESG is actively working on this. Stay tuned.

It would be nice if it were the case that one could be assured that if new business were brought up on the IETF mailing list, that people who unsubscribed from it could be notified somehow that such a discussion was occurring.  Otherwise we still have to be subscribed to ietf@.   At present I think a lot of people who should be involved in such discussions aren’t because ietf@ is so noisy.   I think that to do this well requires human effort, and that it would be generally beneficial to the IETF if someone were responsible for this and had the resources to actually do it.

v2.23.0 | Report a Bug | By Email