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

Yong-Geun Hong <> Tue, 25 February 2020 02:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 416443A0795; Mon, 24 Feb 2020 18:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HJzStGz-hx6Q; Mon, 24 Feb 2020 18:56:24 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AD4FC3A0794; Mon, 24 Feb 2020 18:56:23 -0800 (PST)
Received: by with SMTP id q8so12349795ljb.2; Mon, 24 Feb 2020 18:56:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T0NQOOQjl4be8Wa7FI0SGJ/uMIC3S5XyF3IFTNWE51g=; b=WGRiHlSIc+kDyhn2x3XMIfAtpzKz5czS8lgF8CDgMVw/uyfG5Pt+8pC7fMxAdj+OV2 JvyX74WXoRScrxeiaDDXXJAOo1ONzskds/Jre/K9Q1TJGfIEANwOOxcbupy9gP49LhQy EaRQjhhpmX4aU9u5k3bBBaYm8Sz2wrB0O5pVtQJwprIbiESG1yU2J5U/c+kdi5ww+3QV FG/dV7LIh41BHlgLVszdSfIXFhuarxTsXs+K1e+5Fx2Lt/5lDliwvnl8z8oQWeCLn+BO Nt1b+ZL0ASp8jTV3fb1gIA+FTXzBQcx2c+PrvYjRz1e37TlNs6cpvm+gugSSLxFZNmiB +TCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=T0NQOOQjl4be8Wa7FI0SGJ/uMIC3S5XyF3IFTNWE51g=; b=MtbiO0QzCYo3k+NZHnQvqZXDOolCaKFaK6mViwBpdRkpYh/6WVxgore6aV6Nk+uRaM WT7ccxotxfBxmqZ8TTFXpoS02XBUN4TpccjJedxpF1EWMzIudoBF6OQ0LYH5yQyAnscw wMmwBOWbInmCCMom/Pvg4ph88MFVoGpFo45FNqqThgFyKrRzU2/L+ERHhhFM6k555THz l/Lb5L1FfKgSDJWMxwcssYd3eZdcInQxhS4YzQlvavRnaW5wGaXs2FqLK4ia9LUd2UUx 3kqV50D5DNSdMH2AaR6HJF2qu/l5ZLccRTSZtioMFdf4hhLe9tPdpL3Z1M79B5yjLbeW hL8Q==
X-Gm-Message-State: APjAAAWkqWTf7F/WN75x91w0lWuAX3kZWlc1BERq81ZXeu7OMsVN8PHm 4rrHGnLZCyYRGgyokxS36Tr/i/IlOZ3yyIMoEsLfCZoQ
X-Google-Smtp-Source: APXvYqz4RJtr26cGx70eqQ29zVTJkbl9F7lPP3URyTUcg+9ihDNj0OMmQJ+jMDjRfO9Fp4TX/CxlweNEJjPHEDO8UNE=
X-Received: by 2002:a05:651c:2c7:: with SMTP id f7mr31204597ljo.125.1582599381776; Mon, 24 Feb 2020 18:56:21 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Yong-Geun Hong <>
Date: Tue, 25 Feb 2020 11:56:10 +0900
Message-ID: <>
Cc: "" <>, "" <>
Content-Type: multipart/alternative; boundary="000000000000f8fe6d059f5da14f"
Archived-At: <>
Subject: Re: [6lo] review of 6lo use cases draft
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Feb 2020 02:56:26 -0000

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.


On Mon, Feb 24, 2020 at 5:16 PM <> wrote:

> Hello all,
> I have read .
> 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