Re: Changes to the way we manage RFPs

tom petch <daedulus@btconnect.com> Wed, 26 February 2020 10:04 UTC

Return-Path: <daedulus@btconnect.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 2ABED3A11F9; Wed, 26 Feb 2020 02:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 Jyl7ypyZX97W; Wed, 26 Feb 2020 02:04:57 -0800 (PST)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2124.outbound.protection.outlook.com [40.107.22.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D07693A11B0; Wed, 26 Feb 2020 02:04:56 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZM2vcXJFG93TTlAX6fd5OosIDG/wh7SbaM2nBi9wJnp2v4JqIr5OQJpF15d5301xygFXiF+ga6jYEvWYStXZE/Ltg0ABc/Am+rG2Wmt0K5+XAaeMut/bM/mvsbKEz3m26m32FyK23aedRduNGibKR3vbeH73qseFPE3FI0JMra9zQLiFQ69wgrpvI2BRFP1bxZ4U2Ip6dr5UpI6TE/9RoJ1unrB8S4lEVcQL9JeZWpFzuf0Gdx5Yi5Sv8lKqfuvlGG1sr6pBE5e9Jye03pWOstUTZEuFK5XUBkrxSd4jKPIpbfiLctjN23VE/zuJgILrXEBVI6dRWYGLXqRu1Jhqvw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NOq4TbqlA6fJX8c6JmwonbtxU+vnfM7dnLKIZzJV9Tw=; b=fD9Rhq8doMnDDaelY7t3Rj6N9RGcIcKEUnxC12uoVdZbiWv+/F2GQM8JmZB3iPKdk3tEdumB+FmHfD5oSLVX2UPyXRu/v3genbs66Bd7vhivgBbRyXVk4DuTYxzPsk5GsFu/RA+Ae5OEcjPOkdNYBy7BNzMYObcLdgHTg4mZFMf445wPrJP3KyZo8xrRE4ExYvNSoMHaoHryzkn8oNXozbl01io+Hkxz1BI4ON90FV1AoVOypgWO4PJlfMNWw32N9fzib1vEnvQPvjXZiw8Uh4egDPHX/YyDwUAmwNpbS6Ht8FRFvNMFw9G41091E1h6mIS9Q+beOOy7I3ayrbL3jw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NOq4TbqlA6fJX8c6JmwonbtxU+vnfM7dnLKIZzJV9Tw=; b=vh3B2hPpZi+SwN3ZuK1UhphfeYCiyGRgWU3OCcAIzXkIzE8TEp+lT8CJf8orXzk3N7vzs48jKi1h0sSSYi3GEmmJpCAI7p6ICB+lZpVbcUB9JTtdAAU8gU5MGRBK7JZzibpB9FLF4YXNvyTWiyY21B7sMIEwU3bVEXxdyHBma8s=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com;
Received: from VI1PR07MB3502.eurprd07.prod.outlook.com (10.170.237.22) by VI1PR07MB3469.eurprd07.prod.outlook.com (10.170.237.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.6; Wed, 26 Feb 2020 10:04:54 +0000
Received: from VI1PR07MB3502.eurprd07.prod.outlook.com ([fe80::f888:6f80:7ae9:71ce]) by VI1PR07MB3502.eurprd07.prod.outlook.com ([fe80::f888:6f80:7ae9:71ce%5]) with mapi id 15.20.2772.012; Wed, 26 Feb 2020 10:04:54 +0000
From: tom petch <daedulus@btconnect.com>
Subject: Re: Changes to the way we manage RFPs
To: Jay Daley <jay@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <52c88899-8f4e-c92e-d147-e5437c903467@gmail.com> <8AB21B37-3B6F-4BCF-BF35-FB57639FDF8C@ietf.org>
Cc: ietf@ietf.org, IETF Executive Director <exec-director@ietf.org>
Message-ID: <5E5642C0.1040304@btconnect.com>
Date: Wed, 26 Feb 2020 10:04:48 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <8AB21B37-3B6F-4BCF-BF35-FB57639FDF8C@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: LO2P265CA0137.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9f::29) To VI1PR07MB3502.eurprd07.prod.outlook.com (2603:10a6:802:1a::22)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (81.131.229.19) by LO2P265CA0137.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9f::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.2750.18 via Frontend Transport; Wed, 26 Feb 2020 10:04:53 +0000
X-Originating-IP: [81.131.229.19]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: b08c1ea7-dc10-4704-013e-08d7baa35398
X-MS-TrafficTypeDiagnostic: VI1PR07MB3469:
X-Microsoft-Antispam-PRVS: <VI1PR07MB3469AAD5BCBEEEDCA108CD35C6EA0@VI1PR07MB3469.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 0325F6C77B
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(366004)(39860400002)(396003)(346002)(376002)(136003)(189003)(199004)(6486002)(66556008)(66946007)(66476007)(26005)(8676002)(53546011)(81166006)(5660300002)(81156014)(186003)(4326008)(16526019)(36756003)(956004)(16576012)(2906002)(33656002)(52116002)(110136005)(86362001)(8936002)(478600001)(2616005)(87266011)(6666004)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB3469; H:VI1PR07MB3502.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: OdR2JPVXlM8mazvHZ42f6LzNWKIYxWL8QKndQR2a1wgm55MGPTPKTTqqvwb6zdKLd7i95SplL+cSVMR5qZVc79JznDFUI+y9fTIYYjnqE8th2PqvTk9j30W229gL2aRcUt/ZgIk32P0AZwT8SHacOBevDxWZ3d2+xSRUAwAk8L/DcJI+VcBfh+3DUhySzruqNgL54o2jq7uZhOZIHim4GdImzet/k1MdbOfOeq8sHqJxRXVwzumHrOr5uf23jyPECmVzrl1XPhZIkdj6Cd+NR6Xcrkv0ufNk2wtgqHFdJlEJGkiTeBICZsDMxkxl36y2csw6+nugYqRAEhwXu6V44c0jffrAXw0eAjQCFkUcf9GuHYIET19X6TsVGDcUm5cKxWm5ffHoanvI+mIGXNA50S04ivB8Jxt4clrOyyCZgKLFuKzHtUVGAMUzIZIXrh+3
X-MS-Exchange-AntiSpam-MessageData: cIy4mBKASUSH3j6xSb9Xww7rJGDgUjV2BPbvcfAxMGPtR8ntYJf0nfn2rLRa5zJdNcUxxNsBsLj9nAiaer2aQTL9fe63TmKaUMJGrO6oU8MAvNP1RnZdgNdB//2gPZS/jkVquWfuCGFANlrBExF2jA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b08c1ea7-dc10-4704-013e-08d7baa35398
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Feb 2020 10:04:54.3249 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: nkjDyGWfNNiSlUKRbCUAmpHjoMvh0Pmc/OmrNEcmHrkSTL9kdXLwnAitRwiCTPaMFn4CYy1L6QhMJoiokTT9Ew==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3469
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pmMMlgcFsQ6A3HfZ88461WeTBBU>
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, 26 Feb 2020 10:04:59 -0000

On 26/02/2020 05:22, Jay Daley wrote:
> Brian
>
> (sent from my
>
>> On 26/02/2020, at 4:56 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> Hi Jay,
>>
>> I fully understand the arguments for this change. However, I think it would be good to continue to send a *summary* of the CFP messages to ietf-announce, for community awareness. Ditto for the "Award of contract" messages.
>
> Those are two of the three types of RFP message sent to IETF-announce and coincidentally two of the three types planned for rfp-announce (the third one being “Here’s the Q&A for this RFP”).  In other words, I don’t want rfp-announce to grow on volume.
>
> It would useful for me to understand why subscribing to rfp-announce is not an option?  In the context of the IETF’s high usage of mailing lists, this seems like a particularly low barrier to entry.

[tongue in cheek] Because it is impossible to subscribe to any IETF 
lists.  I send a message to subscribe, or unsubscribe or ... and the 
mailer generates a response which I never get.  My ESP - one of the 
larger in the world - has a policy of silently discarding what it 
regards as spam, the rules for which are company confidential. 
Empirically, I see that any short message, such as
'This is a test'
or
'Confirm'
is silently discarded whereas
'This has been padded with a load of semantic rubblis blss ball blaa to 
circumvent teh uneanted intrucion ao an errant ESP etc etc'
gets through.

Unless and until the IETF includes such information - how about a copy 
of Note Well? - in the confirmation message, then confirmation messages 
never arrive and so it is impossible to complete the three way handshake 
and to subscribe to any IETF mailing list.  Of course, when I say ESP, 
it just could be another organisation such as Cloudflare, that is making 
this impossible.  All I know  is that the confirmation message never 
arrives.

Tom Petch










>
> Jay
>