[dnssd] ARCING BoF and mailing list

Ted Hardie <ted.ietf@gmail.com> Thu, 28 January 2016 17:24 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B16471A8AEA for <dnssd@ietfa.amsl.com>; Thu, 28 Jan 2016 09:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 GMeAWZCRGSFy for <dnssd@ietfa.amsl.com>; Thu, 28 Jan 2016 09:24:05 -0800 (PST)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6A3A1A8AE0 for <dnssd@ietf.org>; Thu, 28 Jan 2016 09:24:04 -0800 (PST)
Received: by mail-qg0-x22f.google.com with SMTP id e32so44838120qgf.3 for <dnssd@ietf.org>; Thu, 28 Jan 2016 09:24:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=61DR7MWyER12FX7pxJaYwZZszNos1FjUeHnaOi/tgIM=; b=UM0N7W+it1vXtGXg01u68mMEV/3jawkam81SblTuu5AUYGZlHmxaja3y4xVL7Cpb5H I+n7+Ctx0bG7iM0bkBo+QNdIGoHAVb7RtyG3IesCRbFp9U5+iH7RC5FeavFa4UeJXuzs qTXVLWBd5kfXV4uU6uP3VPhJhXsvWAWhVsbumyBxPjB4J+elbJ0N4gEnwGm3HWy88g9l kwoyoPIbLgU9gwA6T8/tOHbzvLZ2vOLy9RoG1ohv0IuEP7O6nFAAPyAY9C+pJ2Dky7vb auyYYogBmCP4booz+nvQMDYpTi0Jx2Z+vi4ZZGQkmIo33V6cn2koRv3r5eAxC0iiuzAW QcFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=61DR7MWyER12FX7pxJaYwZZszNos1FjUeHnaOi/tgIM=; b=H6VA+rT5blxjeru/zrUFlbz2JfPYAfttimpcRVWKt7/VODFO8nMQQrMz8KTbtOEQ2F YeifOoGO5aITXMIBFRSTrHBL60uhuX9xXfKKtUKg/XyYtiISO6F/kIqsogGlATlWVrPy byN1xJgRiFf+7COfjdoZ+XcebL+8KTqndyduQ8jeS6jFvRf9X+onyHpj6pm334G/uhAT 1qm2azZnD3qt47rMsrkLn6XuAdaSYg36Ygd4qJqH0qMMyYD52zrb1mGZS4eTe0Wc618Z mJM5dm8lf8wcaM4plG4ffTSEjRZ7fVUJdAVoI+S2I6hGqVgFagW9MSsRVNsxJRK3V3vS 2UkA==
X-Gm-Message-State: AG10YORVwwGCw9WM88eocJYUjJIjwTtK0GQEjQgkm0slmVLir/p1ghJS+pRoi+c8uHITZaTh82Llm48L/LDbFw==
X-Received: by 10.140.94.68 with SMTP id f62mr5143514qge.0.1454001844077; Thu, 28 Jan 2016 09:24:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.55.14.211 with HTTP; Thu, 28 Jan 2016 09:23:44 -0800 (PST)
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 28 Jan 2016 09:23:44 -0800
Message-ID: <CA+9kkMBiJF+Bm13FjbH+VBPQoDXaAmM=aN+sVWyvmCEXxeY4aA@mail.gmail.com>
To: dnssd@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>, Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary="001a11394c9e6b4a5a052a682f5f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnssd/_UD4B-JZEeZkkZeLFDEk5MqygiQ>
Subject: [dnssd] ARCING BoF and mailing list
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 17:24:06 -0000

Howdy,

Andrew Sullivan, Suzanne Woolf and I have put a request in for a BoF at
IETF 95 (arcing <http://tools.ietf.org/bof/trac/>) that is trying to take a
slightly different squint at how to manage alternative resolution contexts
like that of mDNS, .onion, or similar.  We're trying to look beyond recent
issues about RFC 6761 and special use name
​ to see if there are different architectural approaches to the general
problem.

​
There's a stab at a problem statement draft
<https://www.ietf.org/internet-drafts/draft-hardie-resolution-contexts-01.txt>
available, building off of work that's already been done in DNSOP and other
places.  There is also a mailing list set up for early discussion (
arcing@ietf.org), and we'd appreciate anyone interested in the topic
joining the discussion there.

Apologies if you get multiple copies; it must mean we *really* want you to
join.

thanks,

Ted, Andrew, Suzanne