[Iot-directorate] Iotdir last call review of draft-ietf-rift-applicability-03
Samita Chakrabarti via Datatracker <noreply@ietf.org> Tue, 19 January 2021 17:13 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: iot-directorate@ietf.org
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D31623A164B; Tue, 19 Jan 2021 09:13:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Samita Chakrabarti via Datatracker <noreply@ietf.org>
To: iot-directorate@ietf.org
Cc: draft-ietf-rift-applicability.all@ietf.org, last-call@ietf.org, rift@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161107643776.13369.1591699344522715874@ietfa.amsl.com>
Reply-To: Samita Chakrabarti <samitac.ietf@gmail.com>
Date: Tue, 19 Jan 2021 09:13:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/c0Sq7kWNwtumj-a6u8_XRHyzTSA>
Subject: [Iot-directorate] Iotdir last call review of draft-ietf-rift-applicability-03
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 19 Jan 2021 17:13:58 -0000
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] Iotdir last call review of draf… Samita Chakrabarti via Datatracker
- Re: [Iot-directorate] Iotdir last call review of … wei.yuehua
- Re: [Iot-directorate] [E] Re: Iotdir last call re… Chakrabarti, Samita
- Re: [Iot-directorate] [E] Re: Iotdir last call re… Pascal Thubert (pthubert)
- Re: [Iot-directorate] [E] Re: Iotdir last call re… Chakrabarti, Samita
- Re: [Iot-directorate] [E] Re: Iotdir last call re… Pascal Thubert (pthubert)
- Re: [Iot-directorate] [E] Re: Iotdir last call re… Pascal Thubert (pthubert)