Delivery-Date: Tue, 12 Jan 2016 13:44:43 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 3C7101E0424;
	Tue, 12 Jan 2016 13:44:41 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0E0473623D;
	Tue, 12 Jan 2016 18:44:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0A9A628379
 for <tor-talk@lists.torproject.org>; Tue, 12 Jan 2016 18:44:33 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Ygxqu4yJ-tf2 for <tor-talk@lists.torproject.org>;
 Tue, 12 Jan 2016 18:44:32 +0000 (UTC)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com
 [IPv6:2a00:1450:400c:c09::231])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id B28B8204BF
 for <tor-talk@lists.torproject.org>; Tue, 12 Jan 2016 18:44:29 +0000 (UTC)
Received: by mail-wm0-x231.google.com with SMTP id f206so335439994wmf.0
 for <tor-talk@lists.torproject.org>; Tue, 12 Jan 2016 10:44:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=VTm2DBmp9DwPrdtyx+CSqhlhq4JI/l4eWdKVyVbJcYU=;
 b=B7EUtAJQnJZmUGE9y/rRntQkaam1t50YI6Z5sAeYK81/WHmk00mRYFZRQP3Q+KSEiQ
 EZZMi+/oGTuZXyFsS2VN1fSqFVLYqhw4YFeCNnKgFZMqv872HF7+omFX4UfSFoDkAFvB
 +weMd4Tz3oTF3lDdT49Fhd2ielN2OSRWeqaPf3vtoNGpW1tK02PulQmjkUdC23EVgBU0
 dIQl2R5oSTqB2L/weYs/i5acg7dYnYzHhZim8j6L6hc+YvhcZDqEpQn8XwS+D1xULgG9
 Nyj37x8yjRxMY2cqi0MFQcUQK/k0IyNJYrJpV21tBTeCr9M4wTmumop6RXNLfAC8mzvB
 Z1tQ==
MIME-Version: 1.0
X-Received: by 10.28.72.68 with SMTP id v65mr22105853wma.41.1452624266894;
 Tue, 12 Jan 2016 10:44:26 -0800 (PST)
Received: by 10.28.31.79 with HTTP; Tue, 12 Jan 2016 10:44:26 -0800 (PST)
Date: Tue, 12 Jan 2016 10:44:26 -0800
Message-ID: <CAP-cguVXdvcDJKgLHb8o_5MjfFzvt1+Gtaiw1G7NUm9QtgbBXw@mail.gmail.com>
From: Joshua Hull <joshbuddy@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Onion service discovery
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

I've been thinking about how to get onion services transparently selected
over non-onion services in order to drive adoption. It seems to me that a
simple strawman proposal would be that before attempting to connect to a
domain name, do a lookup for a specific type of TXT record, ensure it's
being served over DNSSEC, and if both things are true, prefer that record.

However, I can't seem to find much documentation on preferred mechanisms
for discovering onion services. Is there something similar to the scheme I
mention above already in use that someone could point me to?

*j*
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

