Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 01 March 2024 00:49 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E4DC14F5FF; Thu, 29 Feb 2024 16:49:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 nUmSGv4lpqQi; Thu, 29 Feb 2024 16:49:24 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4837C14F5F8; Thu, 29 Feb 2024 16:49:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id CA3033898E; Thu, 29 Feb 2024 19:49:23 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LRJgnEHrIPWM; Thu, 29 Feb 2024 19:49:22 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1B4C83898D; Thu, 29 Feb 2024 19:49:22 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1709254162; bh=daaC/+zPCbjeUQRulo+yoCUUu8YwYPEL8V3FwiJ1IVw=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=McLe5fQoCYjbhE4dqYRCc3TOrLk7YsHz6UBGcZF3z2mMu1v5KAFGyKjNvkSpdGKNN ubEOj8FCwohhX0U2vdQeaXE1H9na7EBjx0LDuN/nmGvllnEPqxZoxH7yGxbrndX1U4 scL1viY8N8640Ed2uFrZ8k0fSF585T8JEuCjE2RFFtMibSs27wL19hZTw2Rcnotco5 +be6k5qXOfyVv0+iWR25Ox037J3OSHWepWXBWGbLSBZSlrO5/O5QuBSsljdncCFRue VQZNRpgz+TKXh1XCm5abZ8uB9YZAyC7m2S35Dv6g8vO87b+3Ts47zclRH+WRQ3wTAt RJfF+Y1H9LjfQ==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 11411873; Thu, 29 Feb 2024 19:49:22 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@lear.ch>
cc: Christian Huitema <huitema@huitema.net>, "sec-ads@ietf.org" <sec-ads@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, draft-ietf-opsawg-mud-acceptable-urls@ietf.org
In-Reply-To: <e15571db-8758-4eeb-b7e2-0a33ed888a34@lear.ch>
References: <8a2c556a-905b-46f9-926c-03f09ed98f32@lear.ch> <66588cac-0f33-4924-920f-6b4dbd5c2964@huitema.net> <51cc9f21-748b-4527-9809-f51c11cd9144@lear.ch> <cc555621-e17e-44b1-97e2-6802d263fa8c@huitema.net> <e15571db-8758-4eeb-b7e2-0a33ed888a34@lear.ch>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 29 Feb 2024 19:49:22 -0500
Message-ID: <9364.1709254162@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/I-MoahgLOp43OKH5qSqxtAAs3zs>
Subject: Re: [OPSAWG] Last Call Review of draft-ietf-opsawg-mud-acceptable-urls-10
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2024 00:49:29 -0000

Eliot Lear <lear@lear.ch> wrote:
    > The data we are talking about scales to number of devices X number of
    > MUD-URL changes.  This can further be reduced by whether or not the MUD
    > file actually exists.  These are not large #s in the home, and in the
    > enterprise, we have iron for such cases.

Also, if you have 1000 instances of device-type X, then one could put all the
potential MUD-URLs into a single table, and then reference them from the
device X definition.  That is, 3rd normal form it, and do data deduplication.
Such a table also can keep one from retrieving the same MUD file (and
signature) 1000 times.

If you really had a problem with the number of URLs stored, which I don't
think anyone will really have.

I don't think we need to keep track of malicious URLs that we ignored.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide