[DNSOP] ARCING BoF and mailing list
Ted Hardie <ted.ietf@gmail.com> Thu, 28 January 2016 17:23 UTC
Return-Path: <ted.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B221A8ADC for <dnsop@ietfa.amsl.com>; Thu, 28 Jan 2016 09:23:37 -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 RBD4szI7lbUB for <dnsop@ietfa.amsl.com>; Thu, 28 Jan 2016 09:23:36 -0800 (PST)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 E1CE81A8AD7 for <dnsop@ietf.org>; Thu, 28 Jan 2016 09:23:35 -0800 (PST)
Received: by mail-qk0-x22a.google.com with SMTP id o6so13876967qkc.2 for <dnsop@ietf.org>; Thu, 28 Jan 2016 09:23:35 -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=vREWRKCLjyYOt4lFFPYRAGcS8kjdFN5G81p02COiwXw=; b=neCSTfr9fkva/SQIhKYQLXuyVT/GIlRP9w/ELUyHrfUJBH3jWqKJ6b5QEBUvy/ecuu mSCOwyDKa5+qbQaTS9//cL9hPXNU2ctpZoz6+DdV8KPVxCFlZKilvp25rBB5QSQwBcdD KViAfQuXnaA7wC2Y78I+HxdCnDfTPrU0MwqqCousRKcfn7osP+En/dgI1rpeHPlbHxcz w5RUP+bp/5/tBkm0vVy4pja81zXbU3g5QD5OxJN8TIj5PvYnYtVEfhLjqC92AsjxgCVA RYY6nfIFeFWCEzMILdDihLVxYMoveyzWyO1WYkF+J6TiqjcXcgLHcEtBV0u2H7BaJqC9 D6tQ==
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=vREWRKCLjyYOt4lFFPYRAGcS8kjdFN5G81p02COiwXw=; b=DZCRuz0/ZY5WeARQ70Oh/nvoBlH3zZejfwdehqSjer1Fvn6mRVTx0XnfEXQIoW5ugT PiW11fAUtKY5XtMtc23OfnyKqaxRpMrKwU1JZ4VgOHrDJHuGbc47SI4/5kOP7Me+iOst hMgvV9QQhO9T55EKCXRoO4AdZNrYrNav951l5Sj8GGJtdpMch7H8UOSkb4obBUU2c/GO XfSExdVy7PJfUnT6eNE6F+5dqgiiage2+8axceyfcuvqTr8grXUoh6H+mlY0VjQ7J35n S3Vr34VLn8OTXwVGTTP9bY/wQX/xvEdnlFQd4DoQR2NdO6x4lsY2CIbCwcdb058IxU7C 89Ig==
X-Gm-Message-State: AG10YOQBxPHgeW2ZHxSZrUeplfr0j0fPfCco9GY4/KHRwB8QIAmKA00Y/1FcOAcN6zFaJSv5NFGsH+hJo32baQ==
X-Received: by 10.55.74.141 with SMTP id x135mr5032965qka.20.1454001814959; Thu, 28 Jan 2016 09:23:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.55.14.211 with HTTP; Thu, 28 Jan 2016 09:23:15 -0800 (PST)
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 28 Jan 2016 09:23:15 -0800
Message-ID: <CA+9kkMAu4NJGkHmb5y1PWqUwVS7PPH9=95UqxT2Y9Z-aUNDRRQ@mail.gmail.com>
To: dnsop@ietf.org
Content-Type: multipart/alternative; boundary="001a114a7c6eaefc88052a682d18"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/gryl20n0YUe0JyNVDD2NPL6uzFk>
Subject: [DNSOP] ARCING BoF and mailing list
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 17:23:37 -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 here 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
- [DNSOP] ARCING BoF and mailing list Ted Hardie
- Re: [DNSOP] ARCING BoF and mailing list Paul Hoffman
- Re: [DNSOP] ARCING BoF and mailing list hellekin