Re: [v6ops] draft-shytyi-v6ops-danir-01.txt

Erik Kline <ek@google.com> Tue, 24 April 2018 08:59 UTC

Return-Path: <ek@google.com>
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 77EAC124BFA for <v6ops@ietfa.amsl.com>; Tue, 24 Apr 2018 01:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 3pLkPaCp-oYl for <v6ops@ietfa.amsl.com>; Tue, 24 Apr 2018 01:59:05 -0700 (PDT)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF01E12025C for <v6ops@ietf.org>; Tue, 24 Apr 2018 01:59:04 -0700 (PDT)
Received: by mail-wr0-x22d.google.com with SMTP id s18-v6so48467568wrg.9 for <v6ops@ietf.org>; Tue, 24 Apr 2018 01:59:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hidIS5/kQaICGcuoQ/Qz1SWOmMoGODvC//kozVcPLAs=; b=eu803Ycrc10ZadR61HtXomUzQGqlrDvgKFyA9w3uaUP2oCxHBSF1P1SKv9g1nPw+NA KCRMrlS1tUf4g6jU7u0sImXoucW3oJZiWUNHeXRNm3vRBHmeJBdd76whEEeEcu7td3u4 dynCyUP//2olweyBNzyO/AhrnXCO8YKgxxfbMoprtxV+Qfn9SaQ1sAsDHYy8nxUMcpmd InFMlaTrS5P1Qs5Ef5UJpU+uC5fgG6kPkp3vgHzV+NxZ5nrfIiwPbRvppUb2em6J4kTa J0bX06/y22vhD94xwwsOIa8rdYwpJJb2H8IqZ8bgXXkSlegl95TMdrHGQabiX0y2PSzK +S/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hidIS5/kQaICGcuoQ/Qz1SWOmMoGODvC//kozVcPLAs=; b=ktPOhwjZBn/dzX+6I/APVY+CryIq60GBvQM80v1zVYIqGUv4R1ogyqJIPjx1ESCkfP TdHV7DC/3ekrHIuAftSpZAIXN1d7ESPkvtFkXSgYiQA+fFDMyHJaJ1krPZKeiorcuvaV 6AWDWrQfHnAh3vL6mrDSvnkL8nv641UjadkN21z/iKhKxjNQ+xl4tmmMoRchVuy+XNeg tMPVKKVLQ6K9GM+kOsugBGKP9bkI0SuXT6zQtIEPLSrw7gxBaZf17aCi31/Fs/o/H3MG V0PCGxctAQFbgvkPqlcQur+0e9aDBizuiN0rPFuQ8+ulQ8W3e9dO1IjwEW3Hx1J+TbOM WZ8w==
X-Gm-Message-State: ALQs6tBSMilD1ymsVH6aAahAusDO/y2Vgyq41IPU3BN4ljdS/2EQVd+N ipqeHGTatxbrdN7wLvcMkvClECkET6g4x7jgiE+s0w==
X-Google-Smtp-Source: AIpwx4+NK788D4lNP18uO5OLpw+YqOeK2AzzApe/qmP1ASKLXGpJP6KXFdjD1aiJAMMa0sVJPS+hOESNYdwqbQLg9Gg=
X-Received: by 10.28.6.149 with SMTP id 143mr11973753wmg.61.1524560342711; Tue, 24 Apr 2018 01:59:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.146.143 with HTTP; Tue, 24 Apr 2018 01:58:41 -0700 (PDT)
In-Reply-To: <1c36fb79-beee-7446-efe7-822c932a249c@gmail.com>
References: <162dab02960.c629492b49487.3795432881225509607@shytyi.net> <CAAedzxoASXFBhaCRi2bwHJuDWcE8WMvw0JZ5A-jQvTGa05Jg3A@mail.gmail.com> <decc656a-171a-6bff-41ce-93b798b85ec1@gmail.com> <1c36fb79-beee-7446-efe7-822c932a249c@gmail.com>
From: Erik Kline <ek@google.com>
Date: Tue, 24 Apr 2018 17:58:41 +0900
Message-ID: <CAAedzxpVDJvbPFb9ivVfdqEaQepQ56gsR2+2P_kLpv8-cvcwEA@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a11442348b49521056a945d5f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/5LADs_rvMrhvk-F37-W0PaHoPSE>
Subject: Re: [v6ops] draft-shytyi-v6ops-danir-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 24 Apr 2018 08:59:07 -0000

On 24 April 2018 at 17:44, Alexandre Petrescu
<alexandre.petrescu@gmail.com> wrote:
> I mean: I think there is no difference from a regular  CPE behaviour, where
> CPE has an LTE interface for connection to the Internet.
>
> Why do you ask?

Because it calls into question the necessity of having such a document.

It sounds like you're saying that this is essentially documenting
things that are already documented elsewhere.

> Le 23/04/2018 à 18:06, Alexandre Petrescu a écrit :
>>
>> Hi Erik,
>>
>> Thanks for the comment.
>>
>> Le 19/04/2018 à 08:53, Erik Kline a écrit :
>>>
>>> I've only scanned the document quickly, but I'm curious: in which
>>> ways is this different from regular CPE behaviour where, say, the CPE
>>> has an LTE interface for connection to the Internet?
>>
>>
>> There is probably no difference: the CPE connects its LTE interface to
>> the Internet, just like the ARM or the laptop in figures on pages 7 and
>> 8 respectively connect their modem or USB dongles. The CPE, just like
>> the ARM, or like the laptop, will run a DHCPv6 Prefix Delegation Client.
>>
>> We could describe that CPE-with-LTE in a new figure, if necessary. But I
>> would request to be hinted by someone explaining that DHCPv6_PD on CPE with
>> LTE interface was tried and it worked with a /56.
>>
>> (there are a few kinds of CPE using LTE to go to Internet: either use an
>> internal LTE modem card, or an USB dongle or maybe a user's smartphone;
>> in this latter case the DHCPv6-PD Client would not run on the CPE but on
>> the smartphone, and so there would be more differences than what we
>> describe in the draft; so only someone who tried DHCPv6-PD on CPE with
>> cellular and made it work would hint about how it worked).
>>
>> Alex
>>
>>>
>>> On 19 April 2018 at 06:36, Dmytro Shytyi <ietf.dmytro@shytyi.net> wrote:
>>>>
>>>> Dear v6opsers,
>>>>
>>>> We are happy to introduce the new version (v.01) of the DANIR draft.
>>>> It has a new figure that describes the setting that works entirely with
>>>> DHCPv6-PD.
>>>> Please have a look by following the next link:
>>>> https://tools.ietf.org/html/draft-shytyi-v6ops-danir-01
>>>>
>>>>
>>>> Name:        draft-shytyi-v6ops-danir
>>>> Revision:    01
>>>> Title:        DHCPv6_PD, PDP and NDP Implementation in IoT Router
>>>> (DANIR)
>>>> Group:        Individual Submission
>>>> Pages:        18
>>>> Abstract:
>>>> This document provides a description of the implementation of Dynamic
>>>> Host Configuration Protocol version 6 Prefix Delegation, Neighbour
>>>> Discovery Protocol and of the use of the Packet Data Protocol in an
>>>> Internet of Things Router. This Internet of Things Router is
>>>> connected on a cellular network; it is a DHCPv6-PD Client and it
>>>> requests a /56 pool of prefixes from the server; the DHCPv6-PD server
>>>> is placed in the PGW and is a part of the cellular infrastructure.
>>>> After the pool of prefixes is delegated, the Internet of Things
>>>> Router derives sub-prefixes from the prefix pool; each one of these
>>>> sub-prefixes is aimed at one ingress interface.
>>>>
>>>> After the Internet of Things Router finishes the network prefix
>>>> assignment procedure, it advertises the network prefixes on the
>>>> ingress links by using the Neighbour Discovery protocol. Finally,
>>>> when Hosts receive the sub-prefixes via Router Adverticement
>>>> messages, they configure the Global Unique Address with the Stateless
>>>> Address Auto-configuration protocol.
>>>> _____________
>>>> Dmytro SHYTYI
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops