[Roll] ROLL-NSA extension for PRE
Rahul Jadhav <rahul.ietf@gmail.com> Sun, 24 February 2019 17:41 UTC
Return-Path: <rahul.ietf@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3B2112958B for <roll@ietfa.amsl.com>; Sun, 24 Feb 2019 09:41:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yxaiYw-Apm-P for <roll@ietfa.amsl.com>; Sun, 24 Feb 2019 09:41:15 -0800 (PST)
Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90A1512941A for <roll@ietf.org>; Sun, 24 Feb 2019 09:41:15 -0800 (PST)
Received: by mail-vk1-xa35.google.com with SMTP id e131so1591580vkf.10 for <roll@ietf.org>; Sun, 24 Feb 2019 09:41:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Z2VPKCUsj2ET8idzJGwaeQ2goPKRq7/0PcekV5z8hFs=; b=pvATcBA7qeqsr5TSXUrAKHKSuxQHJ1Quwk+PYM91JGKNVU2FWJI/JCB+A1rA6DUDaR V7abOE1H4myZjFUwvQcujjwAuQI3iUETm2dVNWce45P1hu+fvOQw2EznxlqfB2Aidbma +N/jJgxEZ+5ebanzMcYh0mNm+hsgyv/FvJXjl9rrJHGn3grYZdhdwlKhYMJMYPKdqeFm dm9XR9XbuEY+mAp6HtyZt6XFuQ/J5YSjnAcd621R/R+O5rJR7d8T0rXpXhm5RLR7eJS+ rYFngym4seSKALe4kqEdnxxQzKFHvl7bWUttPtYiN/fsW7NUamNnXsra4c25AXkAQ9Cg ShJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Z2VPKCUsj2ET8idzJGwaeQ2goPKRq7/0PcekV5z8hFs=; b=de2e+oYNqDpvztgDnM7T+GiE/773M6p7VcnmM1hNL+4Wwem1dKOiTtJuVUso9KmS6f vdnPa0crPz8Po+Q/SIA+PFMeMJXrDu3s1JD35aV32e4kBN5j0FPellk4CMIZTx8HH7c6 uBnkxsr/8TI7Lq8thXnnGOTEv+YWhQnGLXQiI8TyQx1heaofzs9SIli1GGhIxyIeV9ku Ut87cWNmrraHiZnmB41I4IJI8vWPxra7aa5QluX5XltEFK/TeEwKK09Dl5aZytPBTNkf shA9M+btcKafWGuIcc78byZsLk7wwuRNigC1NOXgHHtYUFGvmHmtOjitPh+u/q4T2fgn APdA==
X-Gm-Message-State: AHQUAuZ2PrLDW8G7MuM5LL7GGNr90uj3rfgURenXsyHEinbMOs+X48mN EzoT1sb2scWD+4bMjs7/1uE14prTlfqiUGL+bCqW4DcJ
X-Google-Smtp-Source: AHgI3IZkixv4451MR597Etmyw6wQwlru9GhyDUX1a1blnJxZllvTLB5nBF0ucfkuOu2t0Djz8r6dvPUix86Re6KEcf4=
X-Received: by 2002:a1f:2acb:: with SMTP id q194mr7210085vkq.92.1551030074032; Sun, 24 Feb 2019 09:41:14 -0800 (PST)
MIME-Version: 1.0
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Sun, 24 Feb 2019 23:11:02 +0530
Message-ID: <CAO0Djp2c8wgsNhvDatscMdsh8hUTUkU0x3s_q50nNk6tiA-gjA@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/Av_HnMYEtY_FRHN0JVDrPEUYOFI>
Subject: [Roll] ROLL-NSA extension for PRE
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Feb 2019 17:41:18 -0000
Hello All, Following is my review of draft-ietf-roll-nsa-extension-00: PRE could be an interesting technique that can be applied to subset of traffic which is critical or requires low-latency. The draft talks about extending NSA to send the node's parent-set in the DIO such that the receiving child node could use this information to choose the alternate paths appropriately. 1. Section 3 talks about three policies for alternative parent selection. As i understand different nodes could use any of the policies (strict, medium, relaxed) without having to worry about interop. Also it will be optimum to choose strict policy followed by medium and relaxed respectively. Is this correct? 2. Regarding compression, i didnt find a dispatch-like bit identifying whether the PS addresses are compressed or not. Isn't it required for the recipient to know whether the PS is compressed? 3. Most of the text is 6tisch specific and specifically says 6tisch nodes whilst explaining the technique. I believe the technique is generically applicable to non-6tisch scenarios as well. True? 4. I think a section on reparenting is needed. How would the child node behave when its parent is reparenting? During reparenting, the parent might send its updated DIO with its new parent set. The implications of using CA strict policy in this case might result in child choosing a different AP which certainly is not desirable if the parent still has connectivity to its old parent and the reparenting is done based on metric changes. 5. I am wondering if it is possible to attach a field "such as min-priority [1]" field which is a derivative of the metric calculation in context to every parent in the parent-set. This greatly helps the child nodes in deciding the CA policy to use even though as I understand that the parent-set is already attached in NSA in the decreasing preference order. Regards, Rahul [1] draft-richardson-6tisch-roll-enrollment-priority-01
- [Roll] ROLL-NSA extension for PRE Rahul Jadhav
- Re: [Roll] ROLL-NSA extension for PRE Remous-Aris Koutsiamanis