IETF Logo Mail Archive

Re: [v6ops] DANIR questions draft-shytyi-v6ops-danir-04

Dmytro Shytyi <ietf.dmytro@shytyi.net> Wed, 13 November 2019 00:19 UTC

Return-Path: <ietf.dmytro@shytyi.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8C81201A3 for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2019 16:19:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=shytyi.net
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 M-ZvdTbGCXK5 for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2019 16:19:38 -0800 (PST)
Received: from sender11-of-o52.zoho.eu (sender11-of-o52.zoho.eu [185.20.211.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 400CF120044 for <v6ops@ietf.org>; Tue, 12 Nov 2019 16:19:38 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1573604374; cv=none; d=zohomail.eu; s=zohoarc; b=dM0owRLESy/KolsUtNy+8/zfmsHMcF4Cr7O/jwGXDuzEXCdXi3D3h2/a8YUPrhvS2HccxE80CHRHDFzlXNb7IZ1wVSHdDl9j1ZX7+zvF5eV13Wp9XxMUI7tBvoSR/L3jCCSMAUzaTT0CvhkyZWsIcF0hxebKfnyzo/J1jxjQfZE=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1573604374; h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=kecQyTlYZn+miXH0f2i3aJcFrAZLqfOmGqLa0hECug4=; b=FOv7/PvWqg7vE1XErCw2oghLCFejIwEE6dKrKSnYYZF62+BiFd6y/sPeCi7LZrMJgzY7Jviz+2m1UbgX+damSH2ZwI1AANjQZA26p3teKHeqoaLcPLYJEL+zOUmJxVDKqU67/TlUe1IOR6J5LWr7jbWbAwxVWMw7VdHBbxM0aFg=
ARC-Authentication-Results: i=1; mx.zohomail.eu; dkim=pass header.i=shytyi.net; spf=pass smtp.mailfrom=ietf.dmytro@shytyi.net; dmarc=pass header.from=<ietf.dmytro@shytyi.net> header.from=<ietf.dmytro@shytyi.net>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1573604374; s=hs; d=shytyi.net; i=ietf.dmytro@shytyi.net; h=Date:From:To:Cc:Message-Id:In-Reply-To:References:Subject:MIME-Version:Content-Type; l=19343; bh=kecQyTlYZn+miXH0f2i3aJcFrAZLqfOmGqLa0hECug4=; b=exB77/gak9lS4ZPVaAWsPN9qewwQWKuKy3ZO9oDiR+fFZlwLlDI6BwkxsC5OoT9s 7sEkd/mqhU4ufz+jEx5A6z6t9HzxUL/740Ck0uMKo+OjxsA5Fl5CsRdG6Z9dqVCgodk 640AEafpdcVtk27N8INAL7rrvJhnRPgYN5Np9hko=
Received: from sender.zoho.eu (172.26.23.79 [172.26.23.79]) by mx.zohomail.com with SMTPS id 1573604374323704.227312679889; Wed, 13 Nov 2019 01:19:34 +0100 (CET)
Received: from mail.zoho.eu by mx.zoho.eu with SMTP id 1573604374244543.5415894457697; Wed, 13 Nov 2019 01:19:34 +0100 (CET)
Date: Wed, 13 Nov 2019 01:19:34 +0100
From: Dmytro Shytyi <ietf.dmytro@shytyi.net>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, v6ops list <v6ops@ietf.org>
Message-Id: <16e622136e0.1124af1ab166077.189641254825395816@shytyi.net>
In-Reply-To: <CAO42Z2zfEJ6zHyZfqziesRTHf8ro8rLnq1NR98MkU4bOFdJ9hQ@mail.gmail.com>
References: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <da24a7fb-c64a-2caf-fda1-c28e53123d92@gmail.com> <CAO42Z2yZRXQ=2RRwQj+J_jHcf-76NEc1JQRe-jN9hfwndGxVuQ@mail.gmail.com> <CAO42Z2zfEJ6zHyZfqziesRTHf8ro8rLnq1NR98MkU4bOFdJ9hQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_470161_1626207155.1573604374241"
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dSqbfCWPx_z8-8p7UVB9f4oOckg>
Subject: Re: [v6ops] DANIR questions draft-shytyi-v6ops-danir-04
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Nov 2019 00:19:41 -0000

Hello Mark,



Please find my comments inline.

______________
Dmytro SHYTYI





---- On Tue, 12 Nov 2019 12:12:50 +0100 Mark Smith <markzzzsmith@gmail.com> wrote ----



Missed a few words, touchscreen keyboard!



On Tue, 12 Nov 2019, 22:09 Mark Smith, <mailto:markzzzsmith@gmail.com> wrote:





On Tue, 12 Nov 2019, 20:42 Alexandre Petrescu, <mailto:alexandre.petrescu@gmail.com> wrote:

Hello participants to v6ops WG,
 
 With respect to draft-shytyi-v6ops-danir-04, of which I am a co-author,
 I would like to ask:
 
 - do you think it is useful that smartphones run DHCPv6-PD clients on
    their 4G interfaces?





Broadly yes as that would be a conventional IPv6 router WAN behaviour.











Great. Thank you for this comment!



Trouble from that perspective with smartphones is how that fits with 3GPPs worldview.


- do you think a router behaviour where it runs a Client DHCPv6-PD on
    one side, derive sub-prefixes and subsequently run SLAAC RA on the
    other side - has been described somewhere else than in this DANIR
    draft?





Yes, it is described in RFC 7084. 











In the RFC 7084 the behaviour of IPv6 Customer Edge Router in home or small-office use is described. 

Citation: "ipv6 CE router - is  node intended for home or small-office
                             use that forwards IPv6 packets not
                             explicitly addressed to itself. "



In the Danir draft we consider IoT Router.



Where the IoT devices can be used to enable:

- numerous IoT applications in farming. (Comment: is home or small-ofice use?)

- remote health monitoring and emergency notification systems. (Comment: If we consider the human-wearable elements can we say that it is home/small-office use?)

- the integration of communications, control, and information processing across various transportation systems. (Comment: Transportation system is a home or a small-office?)

- the procedure to  acquire and analyze data from connected equipment, operational technology, locations and people. It helps to regulate industrial systems. (Comment: is it home/small-office use?)

....



Does the the RFC 7084  address the different environments above such as  DANIR daft addresses (DHCPv6_PD and NDP Implementation in IoT Router)?




I think a variation of DHCPv6







a variation of a DHCPv6 relay between the downstream and upstream interfaces would be better because a DHCPv6 relay is DHCPv6 option transparent.









As far as we mention the DHCP relay we have to consider DHCP clients...



So how we address the next information?

      Here is a feature request on Android for dhcpv6 client since Jun 3 2012...

https://issuetracker.google.com/issues/36949085

Seems that this feature request was taken into account so far....









between the downstream and upstream interfaces would be better because a DHCPv6 relay is DHCPv6 option transparent.



The combination of a client and a server limits the options that can be passed between the upstream and downstream interfaces. To support passing new options, they would have to be upgraded; a DHCPv6 relay wouldn't.



IPv6 CE Device DHCPv6 Option Transparency

https://tools.ietf.org/html/draft-smith-v6ops-ce-dhcpv6-transparency-00



Regards,

Mark.





Yours,
 
 Alex
 
 _______________________________________________
 v6ops mailing list
 mailto:v6ops@ietf.org
 https://www.ietf.org/mailman/listinfo/v6ops








_______________________________________________

v6ops mailing list 

mailto:v6ops@ietf.org 

https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email