Re: [Iot-directorate] [E] Re: Iotdir last call review of draft-ietf-rift-applicability-03

"Chakrabarti, Samita" <samita.chakrabarti@verizon.com> Wed, 20 January 2021 04:56 UTC

Return-Path: <samita.chakrabarti@verizon.com>
X-Original-To: iot-directorate@ietfa.amsl.com
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB923A0CFF for <iot-directorate@ietfa.amsl.com>; Tue, 19 Jan 2021 20:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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=verizon.com header.b=WQ9Sigue; dkim=pass (2048-bit key) header.d=verizon-com.20150623.gappssmtp.com header.b=gJ/UpW9i
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 9QV6FJJxiAs1 for <iot-directorate@ietfa.amsl.com>; Tue, 19 Jan 2021 20:56:04 -0800 (PST)
Received: from mx0b-0024a201.pphosted.com (mx0b-0024a201.pphosted.com [148.163.153.92]) (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 0CAF83A0CFC for <iot-directorate@ietf.org>; Tue, 19 Jan 2021 20:56:03 -0800 (PST)
Received: from pps.filterd (m0098281.ppops.net [127.0.0.1]) by mx0a-0024a201.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10K4qAYw051162 for <iot-directorate@ietf.org>; Tue, 19 Jan 2021 23:56:03 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon.com; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=corp; bh=aTqfwV19Be5y9d42cTBaGC/FNUD9BYZtT8wLrd8MqGQ=; b=WQ9SigueWjRZgUDLdjGWsOYVsCI9vfJfqT1zxQbdqjgXkqo6RTxjzumQa1DyEjSlY4iX apQ8j2l32n+FKTaY2yNMNLk9SN3YV+27CzVbnTiWGDbtxgebNfhdMYNerf0HG4wpyX7y dXsehHkLRs8V26hXOOxBhY6OfcLZUUDHFh0=
Received: from mail-oo1-f71.google.com (mail-oo1-f71.google.com [209.85.161.71]) by mx0a-0024a201.pphosted.com with ESMTP id 3668x6sky1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <iot-directorate@ietf.org>; Tue, 19 Jan 2021 23:56:03 -0500
Received: by mail-oo1-f71.google.com with SMTP id x37so17849697ooi.6 for <iot-directorate@ietf.org>; Tue, 19 Jan 2021 20:56:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aTqfwV19Be5y9d42cTBaGC/FNUD9BYZtT8wLrd8MqGQ=; b=gJ/UpW9iIFH5EXrjZCyvmNuzlgyLyM6uFlg8p81hjcWFztpfcGWfQtBPbvMVzUTIDM 56qAZtRvbwpdqeFbBvBvIpUELJGp6dx3amIn2OhfApp2x+IxeecGRIHQgsLmZMNq7KxF y7+RnAEGMB3Ckdx493YrWb1kGY/7+eqXAASdbjg2wAYj71jqflR2SZ0EfGj1JsTDGoHv xNh2rOyhbasTNknsk7jap3spHzPitjGvh3Q0EokEMqBEoumm9yN4mrrZLJdkGogBKSn4 dqAnnkKSMdFukHMXFffBFopIwYR69g1lJfY4NblvKHIV9r0/K/qTlqsJbVMAlJLkaoyC gr9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aTqfwV19Be5y9d42cTBaGC/FNUD9BYZtT8wLrd8MqGQ=; b=lmCkNUDUrjnh422bK4zwV110vkPDu3bzE6vE8SBXAzGFOchjKadFzJgH9ufEdjrgul xN4YEOjOsluVqzmEmaFuB8dZUpa8T0M9voleS559upYLcmb8ZmUVa12YfxPIxco0X920 A+xmp4S3Ex5UggqKLkRw16TA7zLaQARQE2g28ZXZ6p3n3EExj66PphINn4fzBKPOO1rq tOtJA0rxynq5VFgNS1Ow8bNJrLRD56+AlHFRA0r2z/YJLP8YrCcsqRzAeuEqebIppWwA TnYXTxGbXZ0mlNWNLVa8jnFc32Lb0GxOMrOVQgJRcKYTZsQQPAWoa+Tog5saa3jMf+q+ QBCw==
X-Gm-Message-State: AOAM5317KOGP1RSSafgIafk0oq94B9voGFiNGWsZJe1s9kyjVDM1z6/b 1JIh7aigW1Fx8iFpgzFOlsXjeAgy0DbgPXCvGHVjbBbEUMHGnAUp93ngGGa2G7zA13ayLODwAhG Y19fbFkQpt0JbC2liaVbZ4QbGCx79w/oiq3U=
X-Received: by 2002:aca:be09:: with SMTP id o9mr1888173oif.9.1611118562163; Tue, 19 Jan 2021 20:56:02 -0800 (PST)
X-Google-Smtp-Source: ABdhPJwFA7F8J5VElRTBYo4yHCWi9eO8Tp+g6UKBq/GalR5uGWdvQY85Mnu7AizdMnaEhBB05mnPyike9YfBn8e4+38=
X-Received: by 2002:aca:be09:: with SMTP id o9mr1888155oif.9.1611118561613; Tue, 19 Jan 2021 20:56:01 -0800 (PST)
MIME-Version: 1.0
References: <161107643776.13369.1591699344522715874@ietfa.amsl.com> <202101200916077178344@zte.com.cn>
In-Reply-To: <202101200916077178344@zte.com.cn>
From: "Chakrabarti, Samita" <samita.chakrabarti@verizon.com>
Date: Tue, 19 Jan 2021 23:55:50 -0500
Message-ID: <CAHYRG6O75M96DvTTXbWLOv9UZgz-vbPuYWdab+eUhc-f4ZASbg@mail.gmail.com>
To: wei.yuehua@zte.com.cn
Cc: noreply@ietf.org, IETF IoT Directorate <iot-directorate@ietf.org>, rift@ietf.org, last-call@ietf.org, draft-ietf-rift-applicability.all@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008e9e8705b94dc51a"
X-mailroute: internal
X-Proofpoint-Spam-Reason: orgsafe
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/nlDM6ccUK8BluDlEAul2QCIxHXo>
Subject: Re: [Iot-directorate] [E] Re: Iotdir last call review of draft-ietf-rift-applicability-03
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for the IoT Directorate Members <iot-directorate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-directorate/>
List-Post: <mailto:iot-directorate@ietf.org>
List-Help: <mailto:iot-directorate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2021 04:56:06 -0000

Hi Yuehua,

That was a question to the authors. I am sure Pascal Thubert, one of the
authors can help.
What I meant is the typically IOT network of special devices (sensors,
cameras,  mini-robots etc. battery operated devices)  form  a separate
network (mesh or  RPL-RFC6550  like DAG) which runs  IOT routing protocols,
but the network is connected to the regular IP(v6/v4) network through a
gateway which can speak to both sides. Now the question is - if this
scenario requires any special applicability mentioning in this draft or
not?

Thanks for your prompt response,
-Samita

On Tue, Jan 19, 2021 at 8:16 PM <wei.yuehua@zte.com.cn> wrote:

> Dear Samita Chakrabarti,
>
> Thank you for the comments.
>
> I will fix the definition and term issue which has been raised by several
> reviewers.
>
> About the  IoT applicability, would you please offer me more information
> about IoT network concerning "a root gateway/switch of
> a IoT  network"?
>
>
> Thank you.
>
>
> *Best Regards,*
>
>
>
> *魏月华 Yuehua Wei*
>
> M: +86 13851460269 E: wei.yuehua@zte.com.cn
>
>
> 原始邮件
> *发件人:*SamitaChakrabartiviaDatatracker
> *收件人:*iot-directorate@ietf.org;
> *抄送人:*draft-ietf-rift-applicability.all@ietf.org;last-call@ietf.org;
> rift@ietf.org;
> *日 期 :*2021年01月20日 01:14
> *主 题 :**Iotdir last call review of draft-ietf-rift-applicability-03*
> Reviewer: Samita Chakrabarti
> Review result: Ready with Nits
>
> I have reviewed  draft-ietf-rift-applicability from IoT point of view.
>
> The document describes routing in the Fat Tree ( mostly CLOS architecture)
>
> applicability. I do not find any impact of this work on the IETF IoT networks.
> The document methods and RIFT/Fat trees generally are not used in IETF IoT
>
> protocols.  However RPL uses  directed graphs with a different protocol.  I did
>
> not see any direct IoT applicability of this document to IoT networks. However,
>
>  for larger IoT devices and switches one might extract some ideas out of this
>
> document in the future.  Though I don't see direct IoT applicability, I still
>
> wish to ask a question to the authors: will they view a root gateway/switch of
> a IoT  network  to act as a leaf in the fat tree architecture ( example: DC
>
> scenario) ?  If so, please consider adding a paragraph on IoT applicability in
> RIFT.
>
>
> In general, the document is full of acronyms that might be too familiar with
>
> the routing area group ( PoD, TOF, ...), but it will help if the document has a
>
> definition of terms section or a pointer to such document in the beginning ;
>
> alternately, it can  add the acronyms in the relevant diagrams to understand
> their usage.
>
>
>
> --
> Iot-directorate mailing list
> Iot-directorate@ietf.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_iot-2Ddirectorate&d=DwICAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8&m=r0RnyF5_YfoOjDsulOZzbPiTJgF2X0QeztKL85meS84&s=0nQPW9Fvbw6Pe3vUh8aln_MHMOuu5mwVfULNBl_knKA&e=
>