Re: [Add] New Version Notification for draft-btw-add-home-04.txt

mohamed.boucadair@orange.com Wed, 18 March 2020 10:47 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 41C723A10FD for <add@ietfa.amsl.com>; Wed, 18 Mar 2020 03:47: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 8JryNMIrM_RH for <add@ietfa.amsl.com>; Wed, 18 Mar 2020 03:47:53 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23F163A10FC for <add@ietf.org>; Wed, 18 Mar 2020 03:47:53 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 48j6FM5wF9zBsGL; Wed, 18 Mar 2020 11:47:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1584528471; bh=uQH9X82C5549pNJts48kZpitHvHTxjYzoc2tQP1771k=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Vl2DPqOeRoO86k48rti5SgD88cvVRhCE4VAqMQQ/Qb5nEaXDQ6bGAQ5fO109ckqAq wsLEAU65ESyGxVm1wChLEwpwj1kjoRCqD7WI1sqoM2knwrFL2DA4sB/jlCO7YhhfJU BJqTkPhqrn211500fDg9eF1lTQaEYRTiyfqe4uShT+N7AaDS0XicirmYXraK+iiG/v P6RLkdNrqdlVSxQMkVvYBGahaOjCYRmCEHF46IL1qTl1cdKvCvKle2LvksdMRm+P3H cTdroYqAiVfy8WS+aYhIr5LtWDhpOn+UW9amx1ZmQO/oAtQZwc0f4aoncrao9qZizq 9pn+ax3zidMxg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.38]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 48j6FM51cGzCqkj; Wed, 18 Mar 2020 11:47:51 +0100 (CET)
From: mohamed.boucadair@orange.com
To: Iain Sharp <isharp@atis.org>, "ADD Mailing list (add@ietf.org)" <add@ietf.org>
Thread-Topic: New Version Notification for draft-btw-add-home-04.txt
Thread-Index: AQHV+5PMvwFTEGB0tUi0gRR2ugmuUKhLMJ3QgAFng2CAADBRQIAACf6ggAFDzICAAATc8IAACQfw
Date: Wed, 18 Mar 2020 10:47:50 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031475AA4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <158436402635.23433.14803005914378943431@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B9330314712F9@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <MN2PR10MB422152A3FBA5A157F5FACB44B0F60@MN2PR10MB4221.namprd10.prod.outlook.com> <787AE7BB302AE849A7480A190F8B9330314722A5@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <MN2PR10MB4221CE6BFB9C0BD6BCA66493B0F60@MN2PR10MB4221.namprd10.prod.outlook.com> <787AE7BB302AE849A7480A190F8B933031475A0A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <MN2PR10MB4221032C150BC81ADC23A1C1B0F70@MN2PR10MB4221.namprd10.prod.outlook.com>
In-Reply-To: <MN2PR10MB4221032C150BC81ADC23A1C1B0F70@MN2PR10MB4221.namprd10.prod.outlook.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.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/5tKrNOqwqoF6rfcgR_7AF7QTN9c>
Subject: Re: [Add] New Version Notification for draft-btw-add-home-04.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: Wed, 18 Mar 2020 10:47:56 -0000

Re-,

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Iain Sharp [mailto:isharp@atis.org]
> Envoyé : mercredi 18 mars 2020 10:55
> À : BOUCADAIR Mohamed TGI/OLN; ADD Mailing list (add@ietf.org)
> Objet : RE: New Version Notification for draft-btw-add-home-04.txt
> 
> Hi
> 
> Thanks for the clarification text.
> 
> > (2) is definitely out of scope.
> 
> That being the case, then maybe a revision of the title to this would
> be useful: "DNS-over-HTTPS and DNS-over-TLS Server Discovery and
> Deployment Considerations for Home Networks and Mobile Tethering"

[Med] This would exclude the case of a terminal (without any tethering activated) that connects to the mobile network and retrieves the discovery information (using RA, for example).

> 
> I think that would really help make clear that the topic is 1) and not
> 2).
> 
> On terminology, 3GPP uses "UE" for the device that attaches to the
> mobile network which is one thing that confused me when reading the
> document.

[Med] I hear you. I think that changing "UE" to "host" would avoid the confusion.   

> 
> Regards
> 
> Iain
> 
> -----Original Message-----
> From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> Sent: 18 March 2020 09:30
> To: Iain Sharp <isharp@atis.org>; ADD Mailing list (add@ietf.org)
> <add@ietf.org>
> Subject: [EXT] RE: New Version Notification for draft-btw-add-home-
> 04.txt
> 
> Hi Iain,
> 
> (2) is definitely out of scope.
> 
> I added this NEW text to my local copy:
> 
>    Hosts and/or CPEs may be connected to multiple networks; each
>    providing their own DNS configuration using the discovery
> mechanisms
>    specified in this document.  Nevertheless, it is out of the scope
> of
>    this specification to discuss DNS selection of multi-interface
>    devices.  The reader may refer to [RFC6731] for a discussion of
>    issues and an example of DNS server selection for multi-interfaced
>    devices.
> 
> Thank you.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Iain Sharp [mailto:isharp@atis.org] Envoyé : mardi 17 mars 2020
> > 16:46 À : BOUCADAIR Mohamed TGI/OLN; ADD Mailing list (add@ietf.org)
> > Objet : RE: New Version Notification for draft-btw-add-home-04.txt
> >
> > Thanks Mohamed,
> >
> > Good points. I see two cases in mobile:
> > 1) Where the mobile device is acting as a gateway between a cellular
> > network and a local Wi-Fi network. This is what is often called
> > "tethering" or a "personal hotspot"
> > 2) The behaviour of the operating system and the applications on the
> > mobile UE itself.
> >
> > From what you have said, it sounds like your intention is to cover
> > case 1). I agree this has similarities to the residential case so I
> > can see the sense in covering them together.
> >
> > However, case 2) is the typical case for a mobile which isn't being
> > used as a personal hotspot. This case has its own issues: for
> example,
> > mobile UEs frequently move between Wi-Fi and cellular coverage and
> may
> > be simultaneously connected to both. Each access type may have a
> > different local DNS service.
> >
> > If you can add clarity to the scope the text and title that seems
> > sensible. If you want to cover case 2) fully then that might need an
> > expanded discussion in the text.
> >
> >
> > Regards
> >
> > Iain
> >
> >
> >
> >
> > -----Original Message-----
> > From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> > Sent: 17 March 2020 14:02
> > To: Iain Sharp <isharp@atis.org>; ADD Mailing list (add@ietf.org)
> > <add@ietf.org>
> > Subject: [EXT] RE: New Version Notification for draft-btw-add-home-
> > 04.txt
> >
> > Hi Iain,
> >
> > Thank you for sharing the comments.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Iain Sharp [mailto:isharp@atis.org] Envoyé : mardi 17 mars
> 2020
> > > 13:38 À : BOUCADAIR Mohamed TGI/OLN; ADD Mailing list
> (add@ietf.org)
> > > Objet : RE: New Version Notification for draft-btw-add-home-04.txt
> > >
> > > Thanks all for creating this draft.
> > >
> > > A few general comments:
> > >
> > > - I am not sure what the terms "LAN" and "CPE" mean in the context
> > of
> > > a mobile network.
> >
> > [Med] CPE (or home routers) can get connectivity via a Fixed
> network,
> > cellular network, or both (called, hybrid CPEs). "LAN" refers to the
> > home network if you will. We are using these two notions
> independently
> > of how the WAN connectivity is provided.
> >
> >
> >  I think that probably the "LAN" is meant to be the
> > > mobile network itself and the "CPE" is the mobile network's
> Internet
> > > gateway (GGSN, P-Gateway etc.).
> >
> > [Med] Actually, PGW can be seen as an access router in an ISP
> network.
> >
> >  Actually it is quite hard to model
> > > mobile networks with all the layers of tunnelling etc.,
> particularly
> > > if you include "tethering" of external devices to mobile UEs. Some
> > > more clarity on this area and showing the mapping to normal mobile
> > > network terminology would be helpful.
> >
> > [Med] Point taken. We will see how to make things more clear. We may
> > point the reader to:
> > * https://tools.ietf.org/html/rfc6459 (generic architecture)
> > * https://tools.ietf.org/html/rfc7849#section-3 (CPE, devices with
> > tethering features).
> >
> >
> > >
> > > - Section 3.2: There may be other scenarios that are relevant -
> e.g.
> > > the "Internal CPE" talking to a "3rd Party DNS Provider".
> >
> > [Med] Agree. We discuss that particular one in Section 8.2 (see
> Figure
> > 14). We may add cite it in 3.2.
> >
> > >
> > > Editorial comments:
> > >
> > > - Section 3.1: "If a DNS client supports both DoT and DoH, the
> > client
> > > try to establish DoH/DoT sessions..." should be "If a DNS client
> > > supports both DoT and DoH, the client *MAY* try to establish
> DoH/DoT
> > > sessions..." perhaps.
> > >
> >
> > [Med] Fixed. Thank you.
> >
> > > Regards
> > >
> > > Iain
> > >
> > > -----Original Message-----
> > > From: Add <add-bounces@ietf.org> On Behalf Of
> > > mohamed.boucadair@orange.com
> > > Sent: 16 March 2020 13:12
> > > To: ADD Mailing list (add@ietf.org) <add@ietf.org>
> > > Subject: [EXT] [Add] TR: New Version Notification for draft-btw-
> add-
> > > home-04.txt
> > >
> > > Hi all,
> > >
> > > We updated the draft to take into account the comments received so
> > > far. The main changes are as follows:
> > > * Add new sections to discuss unmanaged CPE scenarios (Sections
> 3.2
> > > and 8.2)
> > > * Add a new section to discuss URI templates discovery (Section
> 5).
> > >
> > > Cheers,
> > > Med
> > >
> > > -----Message d'origine-----
> > > De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > > Envoyé : lundi 16 mars 2020 14:07 À : Tirumaleswar Reddy.K; Neil
> > Cook;
> > > Dan Wing; BOUCADAIR Mohamed TGI/OLN; Tirumaleswar Reddy Objet :
> New
> > > Version Notification for draft-btw-add-home-04.txt
> > >
> > >
> > > A new version of I-D, draft-btw-add-home-04.txt has been
> > > successfully submitted by Mohamed Boucadair and posted to
> > the
> > > IETF repository.
> > >
> > > Name:		draft-btw-add-home
> > > Revision:	04
> > > Title:		DNS-over-HTTPS and DNS-over-TLS Server Discovery and
> > > Deployment Considerations for Home and Mobile Networks
> > > Document date:	2020-03-16
> > > Group:		Individual Submission
> > > Pages:		25
> > > URL:            https://www.ietf.org/internet-drafts/draft-btw-
> add-
> > > home-04.txt
> > > Status:         https://datatracker.ietf.org/doc/draft-btw-add-
> home/
> > > Htmlized:       https://tools.ietf.org/html/draft-btw-add-home-04
> > > Htmlized:       https://datatracker.ietf.org/doc/html/draft-btw-
> add-
> > > home
> > > Diff:           https://www.ietf.org/rfcdiff?url2=draft-btw-add-
> > home-
> > > 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.
> > >
> > >
> > >
> > >
> > > 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.
> > >
> > > The IETF Secretariat
> > >
> > >
> > > --
> > > Add mailing list
> > > Add@ietf.org
> > > https://www.ietf.org/mailman/listinfo/add