Re: [Add] What to do in this potential working group
Martin J. Dürst <duerst@it.aoyama.ac.jp> Thu, 22 August 2019 09:51 UTC
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC460120813 for <add@ietfa.amsl.com>; Thu, 22 Aug 2019 02:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FROM_EXCESS_BASE64=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.com
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 u7wIVUt_1ahO for <add@ietfa.amsl.com>; Thu, 22 Aug 2019 02:51:43 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-eopbgr1300119.outbound.protection.outlook.com [40.107.130.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 041341200B2 for <add@ietf.org>; Thu, 22 Aug 2019 02:51:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FiJ8f2o65dcBQ7Z3i0ZmOI5IxRRd0SY8DeFa4JkIwzXTnQlQTZJle6x1yVN73jhl/Av3bqfB8AtDdIq6FH+fNBsroA/6Sfa9dStWouDcV46UCQv/FQgJLIbUTCn+NQKiulgt/FSUZ6ZxzvZ09X1r7RbcqnPKU9sn1PDUbpowNvstJVjulxe7uT2zqNqPFYpclvdfej8jYlZj0hXquV6sBJsTeJBt1bbnikuofFSQicTyXat1BOT8fs6YK0wZGx+GgJPugRxRLqMeLGy2fpi9caDb5xFumcTBsUuiL9QrKeyR2pUMooruumfAqT4k8/QQWQnyCo91XhnNMAP/e7DcvA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=A8Tx649jcsmaxPA/4qKNci4QD475spc/p/qAhVajO6s=; b=b6nAye9kstiBy3qUuQwzXz71lXegjpmJK+abHAqFUbgblhLpeRtln0c4HJdruCcnlB3ch1pZRaSys54zO6KfriePy+fli3sBu/+9AEQ7MuNSGn3ZF2veWWP+lx2D1s5vYgEiUWGqzXiWevDsyZSEnUbznMKMkzh0fkvHTkRcUuEhAa1dz399+4XNz/bOT/xAJU9Okw4tqSFuDRCyRcjk4eEDYrwFxkhbGXP65QhdmKede8hFqQBpSdRpnirKmzmM7svENtaQ+7ToX2N20LyrxRVkFeZkt/hnCRzFjURF9h699Z4paNwH6MHhS/DYlm3AJOtOlnJ8WFuwklm7MRWLFQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=A8Tx649jcsmaxPA/4qKNci4QD475spc/p/qAhVajO6s=; b=S5h+5mj7phL8W7WaRprUqfvAADk3c6zDPfXI40DYKFoSDZiM51uGID7lIjp2/Wf/7osYbzbVJ3bw/gTUMESgF/prPBxXbgycnd6IS5c6rSLjc+TB1dgusWbHBJMd8rsFo9ottMDV2Rm9ZZj66uoFTzHNkbQ+EZ3c/ZlBfa/HznQ=
Received: from TY2PR01MB3401.jpnprd01.prod.outlook.com (20.178.141.204) by TY2PR01MB4089.jpnprd01.prod.outlook.com (20.178.143.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.16; Thu, 22 Aug 2019 09:51:39 +0000
Received: from TY2PR01MB3401.jpnprd01.prod.outlook.com ([fe80::9538:388:6e72:4340]) by TY2PR01MB3401.jpnprd01.prod.outlook.com ([fe80::9538:388:6e72:4340%5]) with mapi id 15.20.2178.018; Thu, 22 Aug 2019 09:51:39 +0000
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
CC: ADD Mailing list <add@ietf.org>
Thread-Topic: [Add] What to do in this potential working group
Thread-Index: AQHVV5IhM8MdSBmqgkWbxFdpNks5+qcFRa+AgAAo9ICAAHAxAIAAJ4+AgAADcACAAAiTgIAA3NaA
Date: Thu, 22 Aug 2019 09:51:38 +0000
Message-ID: <2e44b80b-2264-b6b5-9062-6b05f627925c@it.aoyama.ac.jp>
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net> <CABcZeBMfOTjq-8hDDoKMtJvfHUA5nC8o60zuk-2Xe-ZhfwriJQ@mail.gmail.com> <766112E1-F532-4C6B-8CA8-A096671E02EE@piuha.net> <CA+9kkMAfuOwJu8_qJTuhAY4mUwR+tVUxr+k3QFHBk3byV672Ow@mail.gmail.com> <8f856492-f5da-9a02-f76d-67c2795b2ecc@cs.tcd.ie> <CA+9kkMD2h94zU9i-Gx5bkqc7np29A=zUnZKq3HkG0zVMzLFkxQ@mail.gmail.com> <4505d6b8-0521-dd2f-245d-8fa73e2313c3@cs.tcd.ie>
In-Reply-To: <4505d6b8-0521-dd2f-245d-8fa73e2313c3@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: TYAPR01CA0240.jpnprd01.prod.outlook.com (2603:1096:404:11e::36) To TY2PR01MB3401.jpnprd01.prod.outlook.com (2603:1096:404:d1::12)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [133.2.210.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b40dfa73-c02f-46fd-8558-08d726e653e9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(5600166)(711020)(4605104)(1401327)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7025125)(7027125)(7023125)(2017052603328)(7193020); SRVR:TY2PR01MB4089;
x-ms-traffictypediagnostic: TY2PR01MB4089:
x-microsoft-antispam-prvs: <TY2PR01MB408965F3581E34EEF477F8F7CAA50@TY2PR01MB4089.jpnprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01371B902F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(396003)(346002)(136003)(39840400004)(199004)(189003)(71190400001)(229853002)(81166006)(6436002)(6916009)(5660300002)(76176011)(52116002)(6486002)(256004)(14454004)(508600001)(186003)(102836004)(53546011)(14444005)(99286004)(6512007)(26005)(66946007)(66066001)(66556008)(66446008)(66476007)(71200400001)(64756008)(25786009)(446003)(2616005)(85202003)(2906002)(11346002)(8936002)(7736002)(4326008)(386003)(6506007)(81156014)(305945005)(8676002)(31696002)(86362001)(31686004)(316002)(786003)(53936002)(85182001)(3846002)(6116002)(476003)(6246003)(486006); DIR:OUT; SFP:1102; SCL:1; SRVR:TY2PR01MB4089; H:TY2PR01MB3401.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: RYlftg/RPb0e6ejlImTG0pVTR2ouunyrI1Lx5vl7NW5iApKaEavYUNAe+g9fdVP5k9C1Ab3LfYIA+9oRaYdTWFDPa4LmZ4TdicODf6wN7IepEKpV4GxIm4Z7AcCM3C5g79R+O03jNPGXjtbfjrKJHsrkvofskgDdfhvv/cLIoFJyZPXazRnuQ8XtCcNUqmdUCwejFfCxDmRq8T71aMRYAyd9IX896vdaFla5d54a6EoOdTvjZhl4NsEdJwn7kLL908BiKSW1TISED30x5/GOYOS+Ywqsx+wVowe/p4VNJQGCYyPBm91j3T0w0QN6i6dbw3uhoHVf/yqJCuvG0d8EId8yGbwAAGCEFKIu9z9PLgjZi7z+zT5toRUf2Uz/DmYr2DraAdG98qbv/Yz4TMbykr+JXMZ+nix2WdQVGThQK4M=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <C0E5174FE3EB88419CDE273A0E5E5860@jpnprd01.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: b40dfa73-c02f-46fd-8558-08d726e653e9
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Aug 2019 09:51:39.3058 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Bo6j82jxYHDn8lsomZxbzRjqD9VibuCBmDQmsAkQwoCv07i6WL3S7MQZvZhcQsI62ER5bPmU2gvcpbMJCc3f5w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY2PR01MB4089
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/S5AUAUhQ3IqCSjOYC4jUELy3jLI>
Subject: Re: [Add] What to do in this potential working group
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2019 09:51:46 -0000
Hello Stephen, others. On 2019/08/22 05:41, Stephen Farrell wrote: > But that wasn't quite what I intended. ISTM clear that having O(1) > TRRs in the world would be over-concentrated. I think it's maybe > equally clear that with a different per-LAN recursive (which is > kinda like today) it'd be extremely hard to authenticate those > as TRR-like entities - so perhaps O(10^7) is too many TRRs. I do > think considering "how many TRR-like things would be good" is a > relevant (research?) question that could affect protocol design > and implementations and deployments. > > For example, if there's an answer at all and O(100) were that > answer, that might change how a DoT/DoH client might usefully > spread it's queries over those vs. if the answer were O(10^4). I know where you want to get at, but due to the properties of the Big-O notation, O(1), O(10^7), O(100), and O(10^4) are all the same (because they are all constants, and constant factors are eliminated in Big-O thinking). Please check your sources if you don't remember this, or never have had the chance to study it. I can suggest sources if necessary. If you want to say "about 1" or "about 100", then ~1 or ~100 or so may be appropriate. In order (sic!) for Big-O notation to become useful, we have to assume we have a number of /n/ clients. Then, sensible answers involving Big-O notation may be O(n^0.5) or some such. O(n^0.5) would mean that a reasonable number of "TRR-like things" would be on the order of the square root of the number of clients. Of course I have no idea whether it would be O(n^0.5) or O(n^0.1) or O(log n) or any other kind of order. A first guess will put the result between 1 (not O(1)) and O(n), but that's obvious and not very useful. However, there should be people who understand the theoretical framework(s) that may give more precise answers. And there should be people who know how to design and run experiments to get some more precise ideas. Regards, Martin.
- [Add] What to do in this potential working group Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Orth
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Jim Reid
- Re: [Add] What to do in this potential working gr… Vittorio Bertola
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Vyncke (evyncke)
- Re: [Add] What to do in this potential working gr… Ted Lemon
- Re: [Add] What to do in this potential working gr… Jim Reid
- Re: [Add] What to do in this potential working gr… Ted Lemon
- Re: [Add] What to do in this potential working gr… Tommy Jensen
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ray Bellis
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ray Bellis
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Brian Dickson
- Re: [Add] What to do in this potential working gr… Brian Dickson
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… Adam Roach
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… David Conrad
- [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] data integrity and DNSSEC or DoH/DoT Stephen Farrell
- Re: [Add] data integrity and DNSSEC or DoH/DoT David Conrad
- Re: [Add] data integrity and DNSSEC or DoH/DoT Rob Sayre
- Re: [Add] data integrity and DNSSEC or DoH/DoT Stephen Farrell
- Re: [Add] Unstated assumptions in What to do in t… John Levine
- Re: [Add] data integrity and DNSSEC or DoH/DoT Brian Dickson
- Re: [Add] What to do in this potential working gr… Patrik Fältström
- Re: [Add] What to do in this potential working gr… Patrik Fältström
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Martin Thomson
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Daniel Stenberg
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] data integrity and DNSSEC or DoH/DoT Stephen Farrell
- Re: [Add] What to do in this potential working gr… Ray Bellis
- Re: [Add] What to do in this potential working gr… Martin J. Dürst
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Vittorio Bertola
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ralf Weber
- Re: [Add] data integrity and DNSSEC or DoH/DoT Ralf Weber
- Re: [Add] data integrity and DNSSEC or DoH/DoT Willem Toorop
- Re: [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] What to do in this potential working gr… Rubens Kuhl
- Re: [Add] data integrity and DNSSEC or DoH/DoT Paul Wouters
- Re: [Add] What to do in this potential working gr… Paul Wouters
- Re: [Add] data integrity and DNSSEC or DoH/DoT Livingood, Jason
- Re: [Add] What to do in this potential working gr… Livingood, Jason
- Re: [Add] What to do in this potential working gr… Livingood, Jason
- Re: [Add] What to do in this potential working gr… Livingood, Jason
- Re: [Add] What to do in this potential working gr… Adam Roach
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Rob Sayre
- Re: [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] What to do in this potential working gr… Vittorio Bertola
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Brian Dickson
- Re: [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Neil Cook
- Re: [Add] data integrity and DNSSEC or DoH/DoT Neil Cook
- Re: [Add] data integrity and DNSSEC or DoH/DoT Neil Cook
- Re: [Add] data integrity and DNSSEC or DoH/DoT Paul Wouters
- Re: [Add] data integrity and DNSSEC or DoH/DoT Christian Huitema
- Re: [Add] data integrity and DNSSEC or DoH/DoT Christian Huitema
- Re: [Add] data integrity and DNSSEC or DoH/DoT Brian Dickson
- Re: [Add] data integrity and DNSSEC or DoH/DoT Andrew Campling
- Re: [Add] data integrity and DNSSEC or DoH/DoT Vittorio Bertola
- Re: [Add] data integrity and DNSSEC or DoH/DoT Paul Wouters
- Re: [Add] data integrity and DNSSEC or DoH/DoT Vittorio Bertola
- Re: [Add] data integrity and DNSSEC or DoH/DoT Alec Muffett
- Re: [Add] data integrity and DNSSEC or DoH/DoT Alec Muffett