IETF Logo Mail Archive

Re: [Add] TR: I-D Action: draft-btw-add-home-00.txt

mohamed.boucadair@orange.com Mon, 09 March 2020 12:03 UTC

Return-Path: <mohamed.boucadair@orange.com>
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 EC7813A0E0D for <add@ietfa.amsl.com>; Mon, 9 Mar 2020 05:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 VOTFwZwXKTmZ for <add@ietfa.amsl.com>; Mon, 9 Mar 2020 05:03:54 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A45A3A0E09 for <add@ietf.org>; Mon, 9 Mar 2020 05:03:54 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 48bcMD2yZYz5wJs; Mon, 9 Mar 2020 13:03:52 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1583755432; bh=1IOnZEJ3Wq2S9/PxzmHJOtYD860NSunU7poHqxIMNNU=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=V9s0Vd5Gl0T4NabqxhQdB83KtB/wgOLkth22eppbja7vcMqNg+rOJZeYInx7CeSyT ezOvzP5Dszq3+5PeZqfN7lbeM602fCUVwOT+zHwTLfGQn3Y0p16rqkwVZo6mGHO8NQ VrP/LXJlGu75iTGRPk1imHA2Atp0ukkSU1oOzFxul1T+OIDaVM83Zog+7WcxcOv3+3 P/ZxKrigJACDQuON33xi0O9LRCqrk4jK/ORk1aBbZDvL8Kc6k6CncQmKf7B2qiO3gF 4IFSHC9hMDz4Bb3wiS7/N696AfqCW7ck7yl2zST4/tKU7qyW0q1O6cQfvn5iFkG/5N R1lturPJjdVhA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.95]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 48bcMD20XpzCqkm; Mon, 9 Mar 2020 13:03:52 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM24.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0487.000; Mon, 9 Mar 2020 13:03:52 +0100
From: mohamed.boucadair@orange.com
To: Martin Thomson <mt@lowentropy.net>, "add@ietf.org" <add@ietf.org>
Thread-Topic: [Add] TR: I-D Action: draft-btw-add-home-00.txt
Thread-Index: AQHV9aK6yBasY163pEamVw26CObm/KhAKDng
Date: Mon, 09 Mar 2020 12:03:51 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330314653F6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <158330934617.29404.4287578882183435520@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93303145E6CC@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <e00539d3-9c2f-4c20-88d7-b43a7e0674de@www.fastmail.com>
In-Reply-To: <e00539d3-9c2f-4c20-88d7-b43a7e0674de@www.fastmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/ArIjC-h2-C8pWP0wi7VblE_ijqg>
Subject: Re: [Add] TR: I-D Action: draft-btw-add-home-00.txt
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: Mon, 09 Mar 2020 12:03:56 -0000

Hi Martin,

Good point about the URI template. The draft already includes the following:

   If DoH is supported by the DNS server, the DNS client may request the
   URI resource record type [RFC7553] using the domain name discovered
   using DNS Reference Identifier DHCP/RA option (Section 4) to use the
   HTTPS URI scheme (Section 3 of [RFC8484]).

Other methods such as draft-ietf-dnsop-resolver-information can be considered as well. 

Wouldn't that be sufficient? 

Thank you.

Cheers,
Med

> -----Message d'origine-----
> De : Add [mailto:add-bounces@ietf.org] De la part de Martin Thomson
> Envoyé : lundi 9 mars 2020 00:37
> À : add@ietf.org
> Objet : Re: [Add] TR: I-D Action: draft-btw-add-home-00.txt
> 
> This seems very similar to draft-peterson-doh-dhcp and draft-peterson-
> dot-dhcp.  It claims to address both, but the mechanism is identical
> to the DoT piece.  There is a bunch more meat to the draft that I
> appreciate in terms of setting context.
> 
> How do you anticipate DoH servers being located using this?  I don't
> see any way you could acquire the URI template using the provided
> options.
> 
> On Wed, Mar 4, 2020, at 20:52, mohamed.boucadair@orange.com wrote:
> > Hi all,
> >
> > We submitted this new I-D.
> >
> > Comments and suggestions are welcome.
> >
> > Cheers,
> > Med
> >
> > -----Message d'origine-----
> > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part
> de
> > internet-drafts@ietf.org
> > Envoyé : mercredi 4 mars 2020 09:09
> > À : i-d-announce@ietf.org
> > Objet : I-D Action: draft-btw-add-home-00.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> >
> >         Title           : DoH/DoT Deployment Considerations for Home
> Networks
> >         Authors         : Mohamed Boucadair
> >                           Tirumaleswar Reddy
> >                           Dan Wing
> > 	Filename        : draft-btw-add-home-00.txt
> > 	Pages           : 17
> > 	Date            : 2020-03-04
> >
> > Abstract:
> >    This document discusses DoT/DoH deployment considerations for
> home
> >    networks.  It particularly sketches the required steps to use
> DoT/DoH
> >    capabilities provided by local networks.
> >
> >    One of the goals of this document is to assess to what extent
> >    existing tools can be used to provide a DoT/DoH service.  As an
> >    outcome, new DHCP and Router Advertisement Options are specified
> in
> >    order to convey a DNS Authentication Domain Name.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-btw-add-home/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-btw-add-home-00
> > https://datatracker.ietf.org/doc/html/draft-btw-add-home-00
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> > --
> > Add mailing list
> > Add@ietf.org
> > https://www.ietf.org/mailman/listinfo/add
> >
> 
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add

v2.23.0 | Report a Bug | By Email