Re: [dns-privacy] Datatracker State Update Notice: <draft-ietf-dprive-rfc7626-bis-04.txt>

S Moonesamy <sm+ietf@elandsys.com> Wed, 13 May 2020 17:43 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF033A0045 for <dns-privacy@ietfa.amsl.com>; Wed, 13 May 2020 10:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 XV04oDPnGAPQ for <dns-privacy@ietfa.amsl.com>; Wed, 13 May 2020 10:43:36 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id A5A4F3A0062 for <dns-privacy@ietf.org>; Wed, 13 May 2020 10:43:36 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.121.210]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 04DHhNeN014717 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 May 2020 10:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1589391815; x=1589478215; i=@elandsys.com; bh=Nv1YCTYvknTKkfh8ozVWcO2omi6uqbSkkq74xGEEFXs=; h=Date:To:From:Subject:In-Reply-To:References; b=sK0/GOCB8tuy0gpdC2ThdyUWvhULUdypTEoHXj2xeQz35dwF/8KY/d22YunL/BLtX 0DYddEwFawCBOhC7fjMHUedgYM44jvChMaNW6E46pcz99UEyN9XVESQi55PgcAp8vm 71PVNq/7JdRzvuaIZQe4TykbJU/Me331hh1zXKt4=
Message-Id: <6.2.5.6.2.20200513095536.0aca0bb8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 13 May 2020 10:10:09 -0700
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>, dns-privacy@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAHbrMsBrB-BGog8kjE0WRBpNVZ16z-nBSpKXXzUYrfwm1bY68A@mail.g mail.com>
References: <157955609351.1744.15099511006231348523.idtracker@ietfa.amsl.com> <F6C06842-9D76-45DF-84A0-B0C4D724E66E@sinodun.com> <CABcZeBPVocy593=WJM2k3Ytrwg36qc_1d4VQH3otRM5qyvZwLA@mail.gmail.com> <1388052392.1781.1586274052101@appsuite-gw1.open-xchange.com> <CABcZeBNi2LKvGFcmTM0uC+rFEVm5tgw6Zo1LS_CoO5=Zo0zqSA@mail.gmail.com> <C03AC6C2-9DCB-448A-B906-3062BD616E31@sinodun.com> <CAMOjQcGrWXFpStp=iVbo1jVN3qnen8rC71SyXv6evY2-MgUdxg@mail.gmail.com> <3345FB83-A19A-4542-8A8E-C535884B157F@sinodun.com> <CABcZeBPP6J=a=hW6BLcMnKawupa3RjjpYAzgZ317=ryLy39n+A@mail.gmail.com> <8CEFE3CB-A88C-4BBC-95B8-9850142DB5EE@sinodun.com> <CABcZeBPF41eq-HYXdYScx7bqYyUO7-oH6zWKqj7Ka23u8x_E4A@mail.gmail.com> <ACA9854E-00B7-4776-A850-E5069C672121@cisco.com> <CABcZeBOxN7iNTLFUw7JDc4ZGH_u4awys3g52de29CuOyQv2JUQ@mail.gmail.com> <C8B168D0-F719-405F-892F-14573A7C568D@sinodun.com> <CABcZeBPGAgqSPKWXKaL6kK5CYzgK+RmwFrMwhc6ED7aGnV_ayA@mail.gmail.com> <8AB227E2-F968-47C4-9EB6-40A988263892@sinodun.com> <4fc44293-cdd9-24b7-cf26-1451a3652f73@huitema.net> <541315765.30668.1589285684382@appsuite-gw2.open-xchange.com> <CAHbrMsBrB-BGog8kjE0WRBpNVZ16z-nBSpKXXzUYrfwm1bY68A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/TdNOWPkxYGT_odBl2QWJMcEaEu4>
Subject: Re: [dns-privacy] Datatracker State Update Notice: <draft-ietf-dprive-rfc7626-bis-04.txt>
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2020 17:43:39 -0000

Hi Ben,
At 08:12 PM 12-05-2020, Ben Schwartz wrote:
>That seems quite contentious to me.  Decentralization of the DNS is 
>_also_ a privacy threat: running your own recursive leaks your IP to 
>every authoritative (far worse than ECS!), pinning yourself to a 
>unique recursive makes you uniquely identifiable as you move across 
>the network, and using a recursive whose identity is unknown is 
>obviously a privacy concern.

I commented about "centralization" within the context of IETF work on 
several occasions.  My opinion is likely clouded by past 
experience.  With respect to privacy, I spent around two years 
getting the IESG to take it seriously.

 From what I recall of what is written in RFCs, DNS is described as a 
distributed database.  There are some advantages of it being 
distributed, or if I may say so, decentralized.  For example, some 
countries might wish to have some degree of control over their 
ccTLD.  System failures do not generally affect a majority of users.

There are obviously privacy implications.  Within an IETF context, it 
would make surveillance easier if everything is one provider.

Regards,
S. Moonesamy