Re: [saag] Discovery: can it be solved

Martin Thomson <mt@lowentropy.net> Mon, 15 November 2021 20:45 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1D793A0952 for <saag@ietfa.amsl.com>; Mon, 15 Nov 2021 12:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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_MSPIKE_H2=-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=lowentropy.net header.b=pNpdrXK2; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JZNyMThK
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 D3cx6UbTEx7E for <saag@ietfa.amsl.com>; Mon, 15 Nov 2021 12:45:33 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6056F3A0945 for <saag@ietf.org>; Mon, 15 Nov 2021 12:45:33 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 75D613201D0C for <saag@ietf.org>; Mon, 15 Nov 2021 15:45:32 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Mon, 15 Nov 2021 15:45:32 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=Rtljlcfr5I8TV2TQ8HCpj3Hx4ycDu45 ZzIMPi+qo7co=; b=pNpdrXK2X5QX2g6KHhLLmwTkLZRHXIrYmLomtTeME7HiKhU 4JmonYuU6vP3kUMcCXik/THL72nfCgJSJxl8tCyGFkkgcbOGvuEFbtelfSP3sbfk DWtFfRa5D1V9zsoBG28Z9CfnUaJyMpKeAAUG7PZWmF+EdLqzxvlj5zUGjw4GDVYZ f73h/FtWjtf84Fr31chDDHkBRAzGEbCrQ/d2QhfXi2Pq17EPpqbhckYy1it0AJQm IAM+stZeS03fY/47HuYF3epSUxJ3seZL+RMeGE8rQbuUDOr8IJ4g104aWKruVGuE 3KHifIldWvl8+KL7ezSoxjU9xLYnK9q7C9Pb4FQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Rtljlc fr5I8TV2TQ8HCpj3Hx4ycDu45ZzIMPi+qo7co=; b=JZNyMThK8YFdLkVRRCEFiR V+zKfjBH9TrauUji3hg8njyNEQeWLk2Lj4Bv8i1mamwudBa1oypvq3YnLyOIMtbp nWtaSvv31klMsrMU41jyD1WgQ2fyaBpq9g4jfxeYOaREjN/ey3N770YdaEz6KdAn Za2LyaHZ1k3dPKLNM7X1VrCAGekWbaCYFdFf5A5XC0PE8yi/hq8p0EL4l4zvnROV MiiY9wparbBzSvn1Yy491cFg2/3P4QDlc1wbrHw0/An2lOwEW4ikiHvV235cwcYm RvKkWnpFktZO2XYqHmQPRp7CR4bLssUmHNEpDJA16KhFzXZc59R54zj1o0qMnNxA ==
X-ME-Sender: <xms:68aSYTVbJ-K0jbxCzvyQqTUSm51wv9zCMOJqiQXVadl9DXnubGJSZg> <xme:68aSYbmPhfmBHuMXuH2OfSDJwxL6FLIbP6tBXLQ14OxiV9qMzJ_RH8UCEgkDz5Wwx yZp_C6U4ZgV7KtEV5U>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrfedtgdduudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpedtgedvieduffelveduve duleeivdegleekhfeifefhieevtdetvedvfeefledukeenucffohhmrghinhepuhhsvghn ihigrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:7MaSYfa_6iAT3Hbki8dQrCaDTVTBdTe9-2fUzKeB9qxwYmSCXlPzxw> <xmx:7MaSYeUrFnyw9LMzSvklbgY6SvVEPg4U1hJ9bRPR753i_kioGR6eMw> <xmx:7MaSYdkyQArzf2p0emZlhqNSdUCWjW7ZcSGXR-o3XbATPSgKWkD7fg> <xmx:7MaSYZwXsj4c4Lg8BmMpsL0VUXS-3HVSnATJm9v6jShIGKixwAaXpQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E8CA73C0C6F; Mon, 15 Nov 2021 15:45:31 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-1371-g2296cc3491-fm-20211109.003-g2296cc34
Mime-Version: 1.0
Message-Id: <b31468dc-2959-40b0-81ba-1ec2dad012e4@www.fastmail.com>
In-Reply-To: <b52fb7cf1e494fbfa84d0b88587bdca8@huawei.com>
References: <CACsn0cnEJR6otnxoYL8SZsKT830YtEMhNU8AV2FM+iHcM+BT5A@mail.gmail.com> <b52fb7cf1e494fbfa84d0b88587bdca8@huawei.com>
Date: Tue, 16 Nov 2021 07:45:11 +1100
From: Martin Thomson <mt@lowentropy.net>
To: saag@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/iOAmPZIHehdFUcZLe_rwhXoUCrg>
Subject: Re: [saag] Discovery: can it be solved
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Nov 2021 20:45:39 -0000

I'm personally not interested in more novel techniques for getting bits from point A to point B.  PIR has applications - it might be that Tor is one - but I don't think that framing this as sampling from a larger dataset is the right way to approach the problem. Maybe global and globally consistent knowledge is part of an answer, but if topological information were sufficient, then I suspect we'd not be discussing this.  For example, DHCP/RA provides information that is very topologically relevant.

The questions here are more fundamental.  What security basis do we have for clients retrieving critical information from the network? How does that affect the security of those clients? How might that shape how the services that are discovered can be deployed? What does that do to the diversity of those services?

At some level, the question of IP intermediation (aka routing) has been solved.  We assume virtually nothing from IP forwarding and routing, but also expect very little from those providing that service.  (The same is largely true for Tor, with some interesting caveats.)  The services Watson lists provide more advanced capabilities and come with associated risks. For example, DNS resolution creates a privacy exposure for clients. That means that it isn't so easy to allow arbitrary others to provide these services.

On Mon, Nov 15, 2021, at 23:48, Antoine FRESSANCOURT wrote:
> Hello Watson,
>
> I agree with you that discovery is a topic to address in the 
> development and deployment of privacy-preserving solutions. Indeed, if 
> we want to avoid having to retrieve a full view of a network's topology 
> to discover intermediaries / trusted peers, we need a way to make a 
> more targeted discovery secure against deanonymization attacks.
>
> I think I mentioned this during the Q&A of the talk I gave during the 
> PEARG meeting at the last IETF, but some people in the Tor community 
> have presented a way to retrieve information about intermediaries 
> without having to retrieve the whole topology. This work called PIR-Tor 
> can be read here:
> https://www.usenix.org/legacy/events/sec11/tech/full_papers/Mittal.pdf
>
> I think private information retrieval is an interesting potential 
> solution to the private discovery problem, in particular in its 
> information-theoretic form. All in all, I am really interested in 
> investigating this question, and I think PEARG is a good working group 
> to make progress on the matter.
>
> Best regards,
>
> Antoine Fressancourt
>
>
> -----Original Message-----
> From: saag [mailto:saag-bounces@ietf.org] On Behalf Of Watson Ladd
> Sent: Saturday, November 13, 2021 4:57 PM
> To: IETF SAAG <saag@ietf.org>
> Subject: [saag] Discovery: can it be solved
>
> Dear Saag,
>
> It seems that a large number of proposals, from OHAI, DOH, Privacy Pass 
> and most recently some IP privacy work have received the same kind of 
> pushback around 'discovery': the argument that we need a mechanism for 
> clients to find a large list of available and willing intermediaries. 
> The challenge here is that we have not seen a proposal, and it doesn't 
> seem to answer the real issues about diversity of intermediates, user 
> trust in what they discover, or address any of the very real issues 
> around user experience.
>
> I think this is a necessary discussion to have once rather than 
> constantly relitigate.
>
> Sincerely,
> Watson Ladd
>
> --
> Astra mortemque praestare gradatim
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag