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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 24 April 2018 09:07 UTC

Return-Path: <alexandre.petrescu@gmail.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 25080127286 for <v6ops@ietfa.amsl.com>; Tue, 24 Apr 2018 02:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 sQYc56gCJr7V for <v6ops@ietfa.amsl.com>; Tue, 24 Apr 2018 02:07:21 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA441271DF for <v6ops@ietf.org>; Tue, 24 Apr 2018 02:07:21 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w3O97J3f021460; Tue, 24 Apr 2018 11:07:19 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 09FBD20134B; Tue, 24 Apr 2018 11:07:19 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id EE98B202DE2; Tue, 24 Apr 2018 11:07:18 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w3O97IQa027010; Tue, 24 Apr 2018 11:07:18 +0200
To: Erik Kline <ek@google.com>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
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> <CAAedzxpVDJvbPFb9ivVfdqEaQepQ56gsR2+2P_kLpv8-cvcwEA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <8fb930be-12c8-88b2-6022-c574bd4ff4db@gmail.com>
Date: Tue, 24 Apr 2018 11:07:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAAedzxpVDJvbPFb9ivVfdqEaQepQ56gsR2+2P_kLpv8-cvcwEA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6NsRn7RA0ZVQjqnpXWv1q4kYAes>
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 09:07:24 -0000


Le 24/04/2018 à 10:58, Erik Kline a écrit :
> 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.

There is a fine distinction between documents and documents that work.

Alex

> 
>> 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