Re: [Doh] Maybe moving draft-ietf-doh-resolver-associated-doh to draft-sah-resolver-information

tirumal reddy <> Thu, 23 May 2019 09:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3D2CD1200F8 for <>; Thu, 23 May 2019 02:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 o3B70MErxQIU for <>; Thu, 23 May 2019 02:24:14 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 30BDD12008B for <>; Thu, 23 May 2019 02:24:14 -0700 (PDT)
Received: by with SMTP id g24so1557054iti.5 for <>; Thu, 23 May 2019 02:24:14 -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=AD40ayrchvSbBam7ASnr12gXAghZyMstmhXUea5zN8M=; b=reyECCWAdY/MxOSid6L+6DiUjJTZPUlgBcH85/khH8FvAS/sM7H9dC7byIqBowGuRE 6xESJ8CFGiFbKVYS/j5aU+++nLaU4SzQk+C1Au4GltOYBm0b1ZWRBCyziANRHY0mBCWL Kcli1jO2QHUidV8zabaGFe+u+aQJfCpgo9PWPD9pQIXzhVXbsmXgLM2eImxDb0pNVrNb n+jRbBlHWczbiu2q9GeKcMtTtM394OVNFijgzMNwTaljn1Pf5JtSxgKCGcOOs4/iYt01 JIEl7bOGDZNR6Jpi6MFpIWWSLnl1p6Mf5Nimow15q1n3a6qy6gL0VWNpCipDpI0E3dfU ZcbA==
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=AD40ayrchvSbBam7ASnr12gXAghZyMstmhXUea5zN8M=; b=cF1qt0p2zh7amke3LzDY5m3GJWw02/K7iHUazcP9BW5IPY2NyPHsrWaKGZyLyaj/47 56jEpkEh9xuaYdOuFZjLsGMzSF/1h9HTLAx3jUEwt7O5ZaKe09f8lRncFaqLja99QZCH 1w/DLXeroEP37DxoetJWvMtHSO86lPUAzy/CHkpHO8//LeJVnGNuytOCCWKlXHExeB37 i3HkyeBDkU8uKovip4oWBI4o2aAM5movDB1P4pqcoLREwqFIeBPV0nt0uKlxkIrXgvgk iyOCk82U1N+hGUJmVIY8hpindaIkbhG60vLyQaNxbqRw3LqcNxqL5KlK363/o/ot9pOC mnwQ==
X-Gm-Message-State: APjAAAW8XjjTlkiQ/fL9aruadWXKertIrTFm1xT3o1kpp6UnoAMv+oDL D2jDOj+qKL7qpQOuFxNhXaRI5x8dsqJ+nXDGv8A=
X-Google-Smtp-Source: APXvYqxVXpee0Wp7IhbPnZcz9hhb96Dky8IjTNtoE2URB3PLuHgluXJ+QljthSQbOh2PMi/wdJ/8NZDIxs/2igX2pvA=
X-Received: by 2002:a24:1d8f:: with SMTP id 137mr12494020itj.66.1558603452039; Thu, 23 May 2019 02:24:12 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: tirumal reddy <>
Date: Thu, 23 May 2019 14:54:00 +0530
Message-ID: <>
To: Paul Hoffman <>
Cc: doh WG <>
Content-Type: multipart/alternative; boundary="0000000000001ac73705898aa51b"
Archived-At: <>
Subject: Re: [Doh] Maybe moving draft-ietf-doh-resolver-associated-doh to draft-sah-resolver-information
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 May 2019 09:24:16 -0000

Hi Paul,

If DOH is supported by the DNS server, why can't the DNS client query for
the URI resource record type [RFC7553] ?


On Thu, 23 May 2019 at 04:19, Paul Hoffman <> wrote:

> Greetings again. For those in the DOH WG who are not also in the DNSOP WG,
> you may not have seen that Puneet Sood, Roy Arends and I have new drafts
> that would replace draft-ietf-doh-resolver-associated-doh. During IETF 104,
> and on this list, people asked why the mechanisms in
> draft-ietf-doh-resolver-associated-doh were only for DoH. In response, we
> created draft-sah-resolver-information and draft-sah-resinfo-doh. The
> former is a general way of asking resolvers for information about them; the
> latter is the definition of the DoH-related information.
> We've used the DNSOP WG mailing list to get input on the drafts, with the
> hope that the DNSOP WG will adopt the drafts soon so we can move the work
> from draft-ietf-doh-resolver-associated-doh to the more general solution.
> We have not yet asked for WG adoption, but will likely do so after people
> see these new drafts.
> Both Google and Mozilla have said here that they look forward to a way to
> find the DoH server associated with a user's resolver, so we hope that the
> work can move forward at a reasonable pace. However, if people in this WG
> think we're doing it wrong by having a general mechanism for querying
> resolvers, please speak up here.
> --Paul Hoffman
> _______________________________________________
> Doh mailing list