[Roll] DAO Projection - identifying storing, non-storing P-DAO

Rahul Jadhav <rahul.ietf@gmail.com> Wed, 13 June 2018 01:55 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 19533130DC2 for <roll@ietfa.amsl.com>; Tue, 12 Jun 2018 18:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 4Mf7qbVF7qqG for <roll@ietfa.amsl.com>; Tue, 12 Jun 2018 18:55:08 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 9F66A12D7F8 for <roll@ietf.org>; Tue, 12 Jun 2018 18:55:08 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id 128-v6so576669vkf.8 for <roll@ietf.org>; Tue, 12 Jun 2018 18:55:08 -0700 (PDT)
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=UBODpbqOYLn41PWGPHDsBuVoJMvo9x82HTwfjai/snk=; b=KRRVdlfEgUIV24BnD0ZYejNqCnfUSJpHlCAtrDU+zNYlc+0tIamtgKejJT8avkLOOZ FI6bt2IDIP4pMCvY9eTRzCovcAjkh4GUMSX/nwCTqQF5B70JD39hgv7M2jE4fiuuqSAR 7hc91tnHq6wkhgL7qe8umJvzeP0SdiLTu5DL3DhPOfijNOWyy8wfZ0iBrC/YIB2o8YFY tuj3PYmm+bD59I2ddWt7cco1JWmDtfaeIh4rB/3xGEEXoVzRsu4AGGUqRJR86Inzp0cu hrETOmXc8ON9H/aCMNUOORK9jzkaIPhC9va8VifwRTPJVjvM1DUb7Lxbpxi6dOCeQzc6 9viA==
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=UBODpbqOYLn41PWGPHDsBuVoJMvo9x82HTwfjai/snk=; b=LRfeb9T1CaMIpw6DkZeN0Uq33tl11TDdse1OMs3BXyK6jK1+yFG6lyW0uAH0x6Lwid EdCjx92fmvXfP+/zvmD7Ya5qeunS2JxmFe7YBVCTaM7UZjLw+UoqlalBQp8xrRUL4EfF 8/N5a3FOCZev/sahDX6q975tbyGflI3UGttqlsydhZEF0dZDrit5E/M2OSuYaEzXH5fy zAuWM8Hyl5Stwia5HC+TP9FATonkf0+TJ1iFTc5KAOQ+AU4RyJoabUBMAPYZEA8PB0rl wmYEOYKkMuEDCS1YOYXdt8Edtdf9QDghDGIeCK4ZAdwFbGwyU8PDA39TIa2rsz0AAhzI Hg2g==
X-Gm-Message-State: APt69E3eqPPEBJQgOsJ0LKfMrCFOEkchvyRstDbbGQYtlZ6TrQIZbB03 V6t112cRB3owDMRgoPMCqBmDNnUde1qg4P+HTtG9rg==
X-Google-Smtp-Source: ADUXVKJiwn3blLqauvWjCxR6EYKO9DVpeRYb5/p8kqsHpetc1gEONzGTvHuxaN+1dnQGch7x9qF2ETvGUlB7RkRjWGc=
X-Received: by 2002:a1f:420a:: with SMTP id p10-v6mr1850415vka.44.1528854907514; Tue, 12 Jun 2018 18:55:07 -0700 (PDT)
MIME-Version: 1.0
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Wed, 13 Jun 2018 07:24:56 +0530
Message-ID: <CAO0Djp1n9oQ3wDD0TFJZqKD70ZBHP5rXac+Hz7xzS88aQGnYsA@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/gjX4joaslka7gORMa1LqqnqDMKo>
Subject: [Roll] DAO Projection - identifying storing, non-storing P-DAO
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 13 Jun 2018 01:55:13 -0000

Hello Pascal, WG,

When i started implementing storing mode P-DAO, i faced one problem,
... as per the draft the only way to identify storing P-DAO from
non-storing P-DAO is that storing P-DAO has at-least 2 VIOs whereas
non-storing P-DAO has only one VIO.
The problem with implementation is that i need to traverse the whole
P-DAO before i know whether it is storing or non-storing P-DAO and
populate the route table accordingly. This way either i have
to buffer VIO/via temporarily and then act. Otherwise i have to have a
2-pass traversal through the P-DAO to check whether it is storing or
non-storing first and then act on the fields in later pass.

If we can have a flag somewhere in the P-DAO header to signal storing
or non-storing then it would make implementation much simpler.

For interested ones, part implementation of DAO projection code is at:
https://github.com/whitefield-framework/contiki/tree/dao_projection
It currently supports registration/unregistration of projected routes
using non-storing P-DAO with +/- ACKing.

Regards,
Rahul