Re: [6lo] review of 6lo use cases draft

Laurent Toutain <laurent.toutain@imt-atlantique.fr> Mon, 02 March 2020 09:42 UTC

Return-Path: <laurent.toutain@imt-atlantique.fr>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E825E3A10F0; Mon, 2 Mar 2020 01:42:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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=imt-atlantique.fr
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 asAcqXWLSk74; Mon, 2 Mar 2020 01:42:43 -0800 (PST)
Received: from smtp1.enst.fr (smtp1.enst.fr [137.194.2.138]) by ietfa.amsl.com (Postfix) with ESMTP id 329333A10EE; Mon, 2 Mar 2020 01:42:42 -0800 (PST)
Received: from zproxy110.enst.fr (zproxy110.enst.fr [137.194.2.192]) by smtp1.enst.fr (Postfix) with ESMTPS id 1914E215A1; Mon, 2 Mar 2020 10:42:36 +0100 (CET)
Authentication-Results: smtp1.enst.fr; dkim=pass reason="1024-bit key; unprotected key" header.d=imt-atlantique.fr header.i=@imt-atlantique.fr header.b=H8RVVDeW; dkim-adsp=pass; dkim-atps=neutral
Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 102D281B5F; Mon, 2 Mar 2020 10:42:36 +0100 (CET)
Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id EwDW3FMCfwYn; Mon, 2 Mar 2020 10:42:35 +0100 (CET)
Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 6A8B381B5D; Mon, 2 Mar 2020 10:42:35 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy110.enst.fr 6A8B381B5D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1583142155; bh=k9pYjCJgDr16d8HfvG9cl1TQ9d+sAcPoJtH6V6YzLk4=; h=MIME-Version:From:Date:Message-ID:To; b=H8RVVDeWhHThziZmutwNZ4aENzSgk7x4PvAHhsGbUqWTZ1ENGn52+I/NLZ3DTrpVt s2XyGfzm1TUKy3/Q7jL2Zs9pn+TNGt+XpI1ICOQObORiZFp1+HDfRuxMHyBUL3OerP KTL+L8WmKOnakScVtNns9oGf8w9JCHOyVf6V91U8=
X-Virus-Scanned: amavisd-new at zproxy110.enst.fr
Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id wMz39VrpNtAr; Mon, 2 Mar 2020 10:42:35 +0100 (CET)
Received: from mail-yw1-f51.google.com (mail-yw1-f51.google.com [209.85.161.51]) by zproxy110.enst.fr (Postfix) with ESMTPSA id 06FFD8155E; Mon, 2 Mar 2020 10:42:35 +0100 (CET)
Received: by mail-yw1-f51.google.com with SMTP id j186so10650269ywe.0; Mon, 02 Mar 2020 01:42:34 -0800 (PST)
X-Gm-Message-State: APjAAAX3ptE/zYWZP84S5mgMWz1lO6vcWwZE6sSdLQWqo6Pao7PhadaF cSM5sfBO4CIPrkejTEL9VUWjyL0x/aBqYNaiXDs=
X-Google-Smtp-Source: =?utf-8?q?APXvYqxNKTTNTbJosyajMO3YZl3vnGbM2Uqp4DoBMicB?= =?utf-8?q?i/Si7SqYl3PU4Uy8Prg0kxXRjCzIY2RtIaSEEiAZ0UcfFdE=3D?=
X-Received: by 2002:a81:5a42:: with SMTP id o63mr15686174ywb.367.1583142153900; Mon, 02 Mar 2020 01:42:33 -0800 (PST)
MIME-Version: 1.0
References: =?utf-8?q?=3C23993=5F1582532152=5F5E538638=5F23993=5F304=5F12=5F?= =?utf-8?q?DA7944B3=2E70DB2=25dominique=2Ebarthel=40orange=2Ecom=3E?= <CACt2foEaPegJOJuKgQzau057AJUipA2NTii8z+j9CR0Nbeey7A@mail.gmail.com>
In-Reply-To: <CACt2foEaPegJOJuKgQzau057AJUipA2NTii8z+j9CR0Nbeey7A@mail.gmail.com>
From: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Date: Mon, 2 Mar 2020 10:43:31 +0100
X-Gmail-Original-Message-ID: <CABONVQYseqGLEXbqUDauDDAZc-5rCgZ2cbnbDPLzDgS_uQjGZw@mail.gmail.com>
Message-ID: <CABONVQYseqGLEXbqUDauDDAZc-5rCgZ2cbnbDPLzDgS_uQjGZw@mail.gmail.com>
To: Yong-Geun Hong <yonggeun.hong@gmail.com>
Cc: "BARTHEL Dominique IMT/OLPS" <dominique.barthel@orange.com>, "draft-ietf-6lo-use-cases@ietf.org" <draft-ietf-6lo-use-cases@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b65806059fdc01f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Q2Wd8xwbh7km-V6dtbQ4jtS5Pcg>
Subject: Re: [6lo] review of 6lo use cases draft
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2020 09:42:47 -0000

Hi YongGeun,

Here is my review of the PLC document. It is a valuable document with a
good synthesize of different standards.It helps to understand the
environment and apply 6lo.

§ 3.3 MTU

As you say, L2 hides frame size through its own fragmentation procedure,
maybe it good be good to remind that these protocols offer different
modulations and MTU associated with these modulations.
It may have an impact on performance.

$ 3.4 Routing Protocols

I don't understand the classification, RPL and LOADng can be compared, but
the middle item is more linked to a specification than a protocol.

§ 4.4 ND

This part seems to focus on a PLC network with route-over. Is mesh-under
behavior is still accurate? will it change the ND behavior?

§5 Internet Connectivity.

I don't understand the use of LPWAN for Internet connectivity. It does not
appear in figure 5.

Hope it helps,

See you

Laurent

On Tue, Feb 25, 2020 at 3:56 AM Yong-Geun Hong <yonggeun.hong@gmail.com>
wrote:

> Dear Dominique.
>
> Thanks for your valuable comments.
> These comments will be helpful to improve the draft.
>
> Please, find my response inlines.
>
> I will update the draft to resolve the comments in a next revision.
>
> Best regards.
>
> Yong-Geun.
>
> On Mon, Feb 24, 2020 at 5:16 PM <dominique.barthel@orange.com> wrote:
>
>> Hello all,
>>
>> I have read https://tools.ietf.org/html/draft-ietf-6lo-use-cases-08 .
>> I found it easy to read and informative.
>> Here are a few comments for your consideration:
>>
>>    - I don't think there should be any RFC2116 language in this draft,
>>    since it describes use cases. I spotted MAY and SHOULD in Sections 1 and 5.
>>
>>              [Yong-Geun] Yes, in Section 1 and 5, you can find MAY and
> SHOULD. As you mention that it describes use cases, we will update the
> usage of MAY and SHOULD.
>
>>
>>    - The bullet list at the end of section 1 is unbalanced: 2 items are
>>    full sentences, 2 are just nominal groups
>>
>>              [Yong-Geun]  Yes, the current four items are unbalanced. I
> will balance the four items.
>
>>
>>    - Section 3.6 PLC: "wired technologies are more susceptible to cause
>>    interference". More than what technologies? Since wires are meant to guide
>>    energy, I would say that wired technologies cause less interference to the
>>    radio medium than wireless technologies, all other things being equal.
>>
>>               [Yong-Geun] Yes, you are right. I guess the existing
> sentence looks like a little ambiguous. The sentence you proposed looks
> like a more better. I will check again with PLC experts and update the
> sentence based on your suggestion.
>
>
>>    - Section 3.7 "In above clauses, various 6lo Link layer technologies
>>    and a possible candidate are described". Unclear which ones are the
>>    genuine 6lo technologies, which one is the possible candidate? Does it
>>    matter that one is only  "candidate"?
>>
>>              [Yong-Geun] Sorry, I forget the update of ‘possible
> candidate’ expression. In previous version (04) of this draft, it includes
> LTE MTC as one of example of a potential candidate but we decided to delete
> the potential candidate and focus on current 6lo link layer technologies. I
> will update the paragraph based on your comments.
>
>
>>
>>    - Section 3.7 "The following table shows that dominant paramters of
>>    each use case corresponding to the 6lo link layer technology".
>>    Incorrect sentence.
>>
>>              [Yong-Geun] Yes, this sentence includes typos and unclear
> expression. I will update.
>
>
>>
>>    - Table 2: looks like a mixture of technologies and applications.
>>    E.g. latency requirement = low for DECT-ULE, but only true for
>>    smart-metering, not for some other DECT-ULE use cases (home automation).
>>    Providing only one example of usage is a mis-representation of the
>>    technology.
>>
>>              [Yong-Geun] Thanks for your correction. To provide more
> correct information, it will be better to describe common (general)
> characteristics of each technology. But, in some point, we have a
> difficulty to capture common characteristics of each technology for
> different application in limited space. That is the reason why we mentioned
> the usage of each technology in the first row.. I will discuss other
> authors and try to find best way.
>
>
>>
>>    - In what respect are section 4 and 6 different? They both have
>>    descriptions of technology and use cases. Could they be merged?
>>
>>              [Yong-Geun] I agree that you can guess the section 4 and
> section 6 had no big difference. The main intention of section 6 is to
> provide 6lo use case examples of each 6lo link layer technology. But, in
> the section 6, we cannot guarantee the real deployment of described use
> case examples. That’s the reason why we provided the section 4. The main
> intention of section 4 is to provide *real* and *real* 6lo deployment
> scenarios and it includes G3-PLC and Netricity. So, the purpose of section
> 4 and section 6 is different. In my opinion, it is better to keep the
> separated sections.
>
>
>
>>
>>    - Section 10.1, Normative References. I wonder if this draft, being a
>>    use case description, should have any normative reference at all (except
>>    maybe for RFC2119). I'm not sure, seek advice.
>>
>>              [Yong-Geun] Thanks for your suggestion. The main Normative
> reference are related in section 5 Guidelines for adopting IPv6 stack. As
> you suggest, I will check again and seek advice.
>
>
>
>> Best regards
>>
>> Dominique
>>
>> _________________________________________________________________________________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>>
>> _______________________________________________
>> 6lo mailing list
>> 6lo@ietf.org
>> https://www.ietf.org/mailman/listinfo/6lo
>>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>