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

Iain Sharp <isharp@atis.org> Tue, 17 March 2020 15:46 UTC

Return-Path: <isharp@atis.org>
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 F1B4F3A079A for <add@ietfa.amsl.com>; Tue, 17 Mar 2020 08:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=atis.org
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 VXEe1Fx8teK1 for <add@ietfa.amsl.com>; Tue, 17 Mar 2020 08:45:59 -0700 (PDT)
Received: from us-smtp-delivery-174.mimecast.com (us-smtp-delivery-174.mimecast.com [63.128.21.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB1883A07A2 for <add@ietf.org>; Tue, 17 Mar 2020 08:45:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=atis.org; s=mimecast20190423; t=1584459957; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rl77sUP3jGzbkchGdjH8Q6w3gArf0BTcmxoUBbfD9KE=; b=YUz5uyjBgbcS+Q1509PRi1yq21d7SsEApgoUu1APtwQLJ6bIi++UvzWAzegGh9uE8yM0iL UGM+BTVdnP7jbP6P0Igjc8M0+ZiCwSn03UWwXsEvWeY60uprK6QykmsIA412aNWC30aBvB NZC9laHGc65Pem6znZWug1oHIiw2Vvc=
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12lp2170.outbound.protection.outlook.com [104.47.55.170]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-298-9Q4LnrEJNgmWjV0OOBL_BQ-1; Tue, 17 Mar 2020 11:45:50 -0400
X-MC-Unique: 9Q4LnrEJNgmWjV0OOBL_BQ-1
Received: from MN2PR10MB4221.namprd10.prod.outlook.com (2603:10b6:208:1d7::18) by MN2PR10MB3280.namprd10.prod.outlook.com (2603:10b6:208:126::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2814.18; Tue, 17 Mar 2020 15:45:46 +0000
Received: from MN2PR10MB4221.namprd10.prod.outlook.com ([fe80::ac24:54cd:e384:8008]) by MN2PR10MB4221.namprd10.prod.outlook.com ([fe80::ac24:54cd:e384:8008%6]) with mapi id 15.20.2814.021; Tue, 17 Mar 2020 15:45:46 +0000
From: Iain Sharp <isharp@atis.org>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "ADD Mailing list (add@ietf.org)" <add@ietf.org>
Thread-Topic: New Version Notification for draft-btw-add-home-04.txt
Thread-Index: AQHV+5PMvwFTEGB0tUi0gRR2ugmuUKhLMJ3QgAFng2CAADBRQIAACf6g
Date: Tue, 17 Mar 2020 15:45:45 +0000
Message-ID: <MN2PR10MB4221CE6BFB9C0BD6BCA66493B0F60@MN2PR10MB4221.namprd10.prod.outlook.com>
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>
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330314722A5@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [87.112.238.100]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4c32eb5d-60c8-49ac-9e58-08d7ca8a423e
x-ms-traffictypediagnostic: MN2PR10MB3280:
x-microsoft-antispam-prvs: <MN2PR10MB328018D76480BC8AD23DCF3CB0F60@MN2PR10MB3280.namprd10.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0345CFD558
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39840400004)(396003)(376002)(346002)(366004)(199004)(66946007)(66476007)(64756008)(76116006)(66556008)(66446008)(8676002)(6506007)(53546011)(2906002)(5660300002)(52536014)(86362001)(508600001)(110136005)(316002)(81156014)(7696005)(81166006)(8936002)(15650500001)(9686003)(55016002)(966005)(71200400001)(186003)(66574012)(26005)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR10MB3280; H:MN2PR10MB4221.namprd10.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: koud7IzYjdrvVq12gVo45UnKf1zqdOcUjIgV/cpnSPpTLIRgNM/pyPZciGKXhfhlijuxYaxtsqwEO0GmNRBwpW4Vn+y4CrXZRAQ9jgU3Az/wBYARifAwQs7L0yx8pV2NGevI38T6qgYHYOkRsIHiOqw8OQdVqkzbrqcJRBX69gAcl8pmytt7NE7IuY/G5SB44Ma8YRhHnc1Ofu16iDvWBZDQMO4lICg8FzrCzDQvbZ6sgBqwiPHb6pFPVS+z7lsaKdWKXLiTRCnU+QSWm+n6wWSF00N1y9Q3HUrfKlZmoL0dwe5aNrijFdjY1xj0YvJfk1uNrRF7dQ/myKZb/4Hsdd/dNEjfmv5/0QhvB7wyMzA4WuWHgXPnkiuWzVYJHSI+f5PCngo/XFaeZB3VeSFCn7+e+oyLm4LIwjknsWKAAwaTzAaWl5Yp4LiWI1vCcPbYa6dObWm593l6muw1pHkPHa50exTOfeD0ivNiVuuLZEs=
x-ms-exchange-antispam-messagedata: zwpIA/9CVXvilVee8l9Ww/0zBs40AfYRGH+XBbLqIL7zD7QoEpX+8CxSvXtJ/Tzb54R30bZ3K0cjbj1BEBu4JEeIKG+5d0YibbSbDBo4OSLNUz8Ln+KYpegQKAPE8ClH0nUASyUXSrE/mCtqJ+5qsQ==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: atis.org
X-MS-Exchange-CrossTenant-Network-Message-Id: 4c32eb5d-60c8-49ac-9e58-08d7ca8a423e
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2020 15:45:45.9841 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 1c6cdebf-458e-4ef3-8f8e-96f15ccaa2b3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: a16+rwbfQKcdeCrVZwbLM2ezkoFaoQUMhI2Mx4QqmSej1u/sq9sgU0zNJagIy60D
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR10MB3280
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: atis.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/xnDCgB20pUnYB-pRAbcyzYBaRVs>
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: Tue, 17 Mar 2020 15:46:02 -0000

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