IETF Logo Mail Archive

Re: [dispatch] Proposal for scantxt

worley@ariadne.com Mon, 05 December 2022 17:24 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 081FBC14F731 for <dispatch@ietfa.amsl.com>; Mon, 5 Dec 2022 09:24:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.681
X-Spam-Level:
X-Spam-Status: No, score=-1.681 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DFsE13YKFV6a for <dispatch@ietfa.amsl.com>; Mon, 5 Dec 2022 09:24:16 -0800 (PST)
Received: from resdmta-h1p-028597.sys.comcast.net (resdmta-h1p-028597.sys.comcast.net [96.102.200.13]) (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 9B040C14F692 for <dispatch@ietf.org>; Mon, 5 Dec 2022 09:24:16 -0800 (PST)
Received: from resomta-h1p-028516.sys.comcast.net ([96.102.179.207]) by resdmta-h1p-028597.sys.comcast.net with ESMTP id 2Bm9pwdi8AF5a2FAUpUkNw; Mon, 05 Dec 2022 17:22:14 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1670260934; bh=21WApqzmxVKjspdeTFpJPrP/JaGKHobG5U2syrRtF9M=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=q/8x3Hf75jlivB4MZzP2NIC1loGgsz2MKVUdrOrnN2hfEILELJJOlFKdjm1TtG/Au lUXGtFbHa8siPXlg7oedjT6jv86SOzqwlK7opQYwFPSXxGQc59L/mSPSJYpzzLUAMn b7MKkTBgU124qp3m6p8hXtvO2GDVkmDktjftGXIoxkeX6hG+ykmG4rVvggwGWmATcb Mh+yHa0m+qkZqMru6uXypN/c4Sj+ZMYM30MjUHQ37OEo6ItUZ58VcOfbC13wrI10H0 dDA6OaoF0s018rT568+qtt8NAyP+/bFqJ7erOkGfQ2bh8xwkI4/efpC7rQWV/y7Gm3 dIi2qY/32HWjw==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::da2d]) by resomta-h1p-028516.sys.comcast.net with ESMTPA id 2FAQpcKbIwYOJ2FARpyaCp; Mon, 05 Dec 2022 17:22:13 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 2B5HM9Vn154257 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 5 Dec 2022 12:22:09 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 2B5HM8pq154254; Mon, 5 Dec 2022 12:22:08 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Ollie IETF <ietf@olliejc.uk>
Cc: dispatch@ietf.org
In-Reply-To: <6YCGJlExPAx1MXtciVHWHwjHxjoDNQOk7Pvpwc0I04TweCI1_Z7fNCVI755J9XsSURiWc9bZF27FLQWGwmg_jfX5LoCwM7Pu-6At23jfnkc=@olliejc.uk> (ietf@olliejc.uk)
Sender: worley@ariadne.com
Date: Mon, 05 Dec 2022 12:22:08 -0500
Message-ID: <87k035ix4v.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/MuT2oVf0Xfw0z0LkB0ZDHNcr4uE>
Subject: Re: [dispatch] Proposal for scantxt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2022 17:24:21 -0000

Ollie IETF <ietf@olliejc.uk> writes:
> [...] would me noting some perceived benefits (and any
> negatives) for the different users and use-cases in the current docs
> help?

IMHO it would be *immensely* valuable to go into the possible benefits
for the various use-cases and the various classes of "users" (both the
scanners and the scanned).  And examples (like the one you gave) are
very helpful in clarifying that.  That motivates putting effort into the
proposal and also clarifies what the proposal needs to accomplish,
i.e. the scope of needed work.

In my experience, once a reasonable approximation to the scope is
achieved, then is the time to start enforcing "technical organization
and quality" onto the proposal.  (I have occasionally made technically
beautiful proposals for solutions to problems that nobody had.  They
were not adopted in the real world.)

Dale

v2.23.0 | Report a Bug | By Email