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

Iain Sharp <isharp@atis.org> Wed, 18 March 2020 09:54 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 BD37E3A0858 for <add@ietfa.amsl.com>; Wed, 18 Mar 2020 02:54:59 -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 53TsLIpwCqeA for <add@ietfa.amsl.com>; Wed, 18 Mar 2020 02:54:55 -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 4FA5D3A084D for <add@ietf.org>; Wed, 18 Mar 2020 02:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=atis.org; s=mimecast20190423; t=1584525294; 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=MXyTjwuQsJ3b7UT5XZnzkvUDirr8PPumjPnVvePn9RQ=; b=Ze3X68724mdKShuMEk2l/gIXXPMBRZzdydehLllif6YWrGaxL1jMqmxjjAWYFIwNWSTUCw rSBdR14J1FFWgvVSng265dLalqPnBo2Z+/fXNPl/yqKQneNuqzJ7gQ8yqAOOTNbEXfKgI+ NsYoDkgycLFxXv8CV4DfCVTxraxTuqg=
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11lp2173.outbound.protection.outlook.com [104.47.56.173]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-340-89HW2btBNzmcgxxt0tgypg-1; Wed, 18 Mar 2020 05:54:52 -0400
X-MC-Unique: 89HW2btBNzmcgxxt0tgypg-1
Received: from MN2PR10MB4221.namprd10.prod.outlook.com (2603:10b6:208:1d7::18) by MN2PR10MB3199.namprd10.prod.outlook.com (2603:10b6:208:12c::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2814.21; Wed, 18 Mar 2020 09:54:48 +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; Wed, 18 Mar 2020 09:54:48 +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+5PMvwFTEGB0tUi0gRR2ugmuUKhLMJ3QgAFng2CAADBRQIAACf6ggAFDzICAAATc8A==
Date: Wed, 18 Mar 2020 09:54:47 +0000
Message-ID: <MN2PR10MB4221032C150BC81ADC23A1C1B0F70@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> <MN2PR10MB4221CE6BFB9C0BD6BCA66493B0F60@MN2PR10MB4221.namprd10.prod.outlook.com> <787AE7BB302AE849A7480A190F8B933031475A0A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933031475A0A@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: f97123a9-5e5d-4be9-543a-08d7cb226523
x-ms-traffictypediagnostic: MN2PR10MB3199:
x-microsoft-antispam-prvs: <MN2PR10MB3199B8D00BDB12BCC33B3643B0F70@MN2PR10MB3199.namprd10.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 03468CBA43
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39840400004)(366004)(136003)(376002)(396003)(346002)(199004)(26005)(186003)(2906002)(966005)(66476007)(53546011)(55016002)(508600001)(66446008)(52536014)(6506007)(9686003)(66556008)(66946007)(64756008)(5660300002)(71200400001)(110136005)(76116006)(8936002)(15650500001)(8676002)(81156014)(81166006)(66574012)(316002)(33656002)(7696005)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR10MB3199; 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: 5XPxADK1+KaabujWS3r7en7L1Na8c6MRwAtG46ai0qQZO5ZEqY+/mnGC8OmQavXdNHl1kd1gEvjpaXpES4Dvm3nA6JO16bhdik84ljMKa/AJi/FHpRbNYzCv/AhFthXZdyB5UL04np2xfxCA8YFRz9MKDUHtBwsJIawhGjFZK9eDFdSNTvInGLeHDR0BjES9SYyyC/E57YBELPxJUc4GMCmM+zuuaAv/ELi3RdITqio0ojdOpwSZgZXLjxUg3huTbzuzY0lVD7F7z91IiUrfDxA0VTCsvzIZRa9A5a9ZLCOsxzyfzVmaYNMFI4DQnnRDr69hG2DPWiAMVQC24A17Mg9InG52ldp+d0q+KAZDpdwGhpLe/QIdd2tQS4MHhUQZM6eN7e928U9n0z1nMprxljlJhOAnF9ucMVmFTnBBVn1zbmVgGKAs/XCrsMUpvuvY7VrznBjWqbg0PbaOub/juWk9qbQ4WvoumIshXZ10ti8hxdaIdygtX4x3pmjRZjPUFyzxEG1dAkPP2WkTmXOLSQ==
x-ms-exchange-antispam-messagedata: b2Jcj1nFs6X5xEQJ9hBahlbIF/J8mTkxs6YzNnCTm6i52J2yKA79D6yyEOaHzr74bWesYtOteqCE67GWH6TeoP7lcLtPZ5xXuRxDvBNKk8/t0HCNBsB1slnc4hTrYfwanoKeUvfd1O5wmNYga/qLeA==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: atis.org
X-MS-Exchange-CrossTenant-Network-Message-Id: f97123a9-5e5d-4be9-543a-08d7cb226523
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Mar 2020 09:54:48.0095 (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: TFYaVJajB1fo+sVB3l5cgnQcJ61rFiof/hL3znBh/9w1j2Oo89LhTMgYOhtYBRK4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR10MB3199
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/haXt_TcDIgt9yDdgq9qAg3bEERc>
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 09:55:00 -0000

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"

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. 

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