Re: [Add] [EXTERNAL] DRDP: response to feed backs provided during the meeting

Daniel Migault <> Fri, 27 March 2020 00:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9403E3A0A46 for <>; Thu, 26 Mar 2020 17:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Tadfru3GTSvR for <>; Thu, 26 Mar 2020 17:46:21 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::a32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ECB333A0C93 for <>; Thu, 26 Mar 2020 17:46:20 -0700 (PDT)
Received: by with SMTP id m131so2259137vkh.3 for <>; Thu, 26 Mar 2020 17:46:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k6X5rbIPaF/3ZLFL7fe3JGyEIYZnuHhaUakqC4aGeoA=; b=KaLKUUs5fsbWuWpxcnTtZ+pURcTPMM19Q9Ho3L0lTEMhMingsgyRO4yrci+c9NJMs7 ks8XYuGzzmBPDyOpX4B2U21s6NFXsicFBxlq4XqU43VQHRu9nCPmlIcwPU6IWONRBzxS 2Odk1lJgEUnK8Lc/PojtdXEE/6lQqCdK0LC167DUG5NyUAIBm3n7oSBh0T4lejnfANMx DZZRcxX1w5gm+KRfiXYwk+YG9Vo+0LWJpMX42gc6W36eaRBRkgJSCyzLjpObuGVaAp/w 1jPOCMEnBwi4jVWaXSR0KyQQWJekHVp9FLprCeW7tz6TVd88mWsc5jCfqRh/DFIPPf6M imGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k6X5rbIPaF/3ZLFL7fe3JGyEIYZnuHhaUakqC4aGeoA=; b=c6xgCvTWQvzR8Dzxv22BSon3S5P04l+4t/XAcDPNMf0dxvkJ+zLF5S+BEDOYMyhZED jklOdSyI7ag3B+NbHyN1Eh62O39SM+RlFVyxQt9WgSGBEMCx0l1BmhGm48mzh0sxsWEk 6WMC7XH4VbxxeHmO0cvnl5DYgXdtA9vReONLwuF3FsvyHocQ2+U2kuKnYiu/bv2CIi1F 0EmiWINrfSEBCl2lIYEPbGYOPJr6Db5rTh3F8iDG0IYDZ4wCclOWXVAqCkLq+wOK3Ilg tOa2Ewnuzucig5d7nVny9wylE58eLTHPTMwIpMwY/OxMANmrC6Gg5X7m4PsVafudNPXz ff0A==
X-Gm-Message-State: ANhLgQ0K6GgLsAt84qN20aF1OS0JGsTv6i1vIiFwrRAVfwWbSrbBOf0M PmDqH4cJEeSOuXyf4/I0NKzZPBIZEgGogz05hsA=
X-Google-Smtp-Source: ADFU+vuJTEv37r7rf0CB+YDb6B+J53RT4ZW4rWmsXey8lyL9zoRyIvpI+gy2420NFvaqEfaFhDn9q72bMP2GUBD7FsQ=
X-Received: by 2002:a1f:60d5:: with SMTP id u204mr9303947vkb.55.1585269979832; Thu, 26 Mar 2020 17:46:19 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Daniel Migault <>
Date: Thu, 26 Mar 2020 20:46:08 -0400
Message-ID: <>
To: "Deen, Glenn (NBCUniversal)" <>
Cc: ADD Mailing list <>
Content-Type: multipart/alternative; boundary="0000000000000564ca05a1cb6ea3"
Archived-At: <>
Subject: Re: [Add] [EXTERNAL] DRDP: response to feed backs provided during the meeting
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Mar 2020 00:46:24 -0000

Thanks for the feed backs Glenn. This is also an opinion I share. The main
motivation for using DNS is that DNS is for sure supported by the DNS
As the repo is expected to simply return a list of domains.  One way to do
could consist in listing the resolving domains in TXT RRsets. Another way
could consists in listing these domains using PTR RRsets which would enable
sanity check over the domain name.

The current document uses the second method and the repo designated by would be represented as:
       PTR resolving_domain_0
       PTR resolving_domain_n

One inconvenient of using DNS seems that I am not aware of mechanisms to
compress the list of resolving domain beyond the compression provided by
RFC1035. I suspect such compression will be less efficient than gzipping
the entire list but in a txt file.


On Thu, Mar 26, 2020 at 7:52 PM Deen, Glenn (NBCUniversal) <> wrote:

> Without hat.
> On 3/26/20, 4:26 PM, "Add on behalf of Daniel Migault" <
> on behalf of> wrote:
> Hi,
> Thank you for the feed backs provided during the meeting. Here
> is a response to three concerns raised during the meeting. Feel
> free to let me know your thoughts.
> 1.. One comment was that having a unique centralize repository of
> resolving domains for public resolvers was a terrible idea. I
> agree with this as it implies a complex governance. I will update
> the draft and let it as "a" repositories for resolving domains
> instead. I however believe that repositories of resolving domain
> share a common format so one is able to switch easily and move
> from one repo to the other.
> Isn’t the DNS itself a global repository of domains?   Could something be
> signed and published in it?
> Yours,
> Daniel
> --
> Daniel Migault
> Ericsson

Daniel Migault