IETF Logo Mail Archive

Re: [Roll] rpl routing and linux-kernel

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 23 July 2018 12:29 UTC

Return-Path: <abdussalambaryun@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 7A881130E74 for <roll@ietfa.amsl.com>; Mon, 23 Jul 2018 05:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 P0qf4kC1huQI for <roll@ietfa.amsl.com>; Mon, 23 Jul 2018 05:29:19 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 DFC36130DE1 for <roll@ietf.org>; Mon, 23 Jul 2018 05:29:18 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id 13-v6so775610ois.1 for <roll@ietf.org>; Mon, 23 Jul 2018 05:29:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=WGOfw/5KbgMhuqw4P5Wucg7LcFcPa0Ev5XRLhu89E3E=; b=qcm7KIKSqw4B7uV5OmHJnhKLa9JWkd/+rUBgagx1vQ5HTBUlSkRwnOpeixqka/678l 7IRAoK9AyBcQ10lP4qw6evwRl+5SfRJsUZq/uTzWkdh3PXH+d+rFBQvOLrpW7yfVSft6 2s5Fq3hpVCd8iNWSzgkl08ds3R0unxgG3YTHPH3J1pPsTvMjdBJwkWETXENN0pCqHNrT 3GHbVnXBRF6M7T6pY4e763hMpCbD903Kb6kkYfxddyetc7MDFXjXG2JZYAutrt8ExC6z 4qi/BikySKM91w1M3i+YV0FoEswO0z7maydf1Mxl1G12jhnFRxxMi/yt6M+tL2KSsL6m QfZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=WGOfw/5KbgMhuqw4P5Wucg7LcFcPa0Ev5XRLhu89E3E=; b=LF3/NSLx+LhAmRtUDZqweH6z948HcF1LBPuMz/V0QONqq2kSVXY4ZPvnZSwEEmOYXJ fRWxsBj0YZaFyvk2sIckSOsWEavi/nEwt53x5a8QocAKjhN5G2T1b5ulwWiR7+yGCvlK 4uodyOTcbgPg6z/S/Xt4A1jSvIq+ycoqju1dyr7FW4ECwl7bc6SaDmyYBU7Bs7t3yabF uq+LzID1myGCkEQ9q4J9b0STzLka8cKKmOAzDgyf3Dohw41wqVKtD4QcnFahT7qaz0rg K5vdgvNI/vfvAnA9xxfYgME5t/P+r9WV+amOs2oyIg78hjp0pG2YBVq5zBeavlMtSjL/ hnkw==
X-Gm-Message-State: AOUpUlEQG688TDwVi4VLWRZ+VRLmM3eoC1pbw4au7Bvai6Nh9ucWocgs +E17YPQPhOf0ZuVYv1ZS01tar9FQ/Fd/j0F+T1m5p9oB
X-Google-Smtp-Source: AAOMgpcNkVxUgIwLyMtNdjDW8dzpxAw3XgV1Rv3AeIoRjNpCoY59nWnf2OMYIpkoCpaHAAK1PFsiKQWtiePCFwLTh1c=
X-Received: by 2002:aca:dc08:: with SMTP id t8-v6mr8878392oig.226.1532348958148; Mon, 23 Jul 2018 05:29:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:d32:0:0:0:0:0 with HTTP; Mon, 23 Jul 2018 05:29:17 -0700 (PDT)
In-Reply-To: <17294.1531966560@localhost>
References: <CAO0Djp16_WUrKkbY-UQGdjLhO2gYitHQo=7iw4cn+fC_am5DdA@mail.gmail.com> <17294.1531966560@localhost>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 23 Jul 2018 14:29:17 +0200
Message-ID: <CADnDZ88GBypAiWRWVa7NQsRcNGdmvUK+DW+JuGcK7=s5C0ekYQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, rahul.ietf@gmail.com
Content-Type: multipart/alternative; boundary="000000000000528c620571a9cb20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/5HBfua4EO7S89S31ImMoVmQV0Es>
Subject: Re: [Roll] rpl routing and linux-kernel
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 23 Jul 2018 12:29:22 -0000

On Thu, Jul 19, 2018 at 4:16 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Hi, I'm not sure that the ROLL list is a good place for Linux-specific
> implementation questions.  In particular, it seems that most implementers
> are
> on monolithic embedded kernels (contiki, openwsn, etc.)
>

Why? I don't care about most implementers, I care about our RFCs
implemented and discussed in IETF lists, not outside, if we follow
implementers some day we will leave the ROLL list as they did !!!!

IMHO  ROLL list is a good place for implementing RFCs into Linux, I don't
agree that the questions are Linux specific, but implement specific.



> There are discussions on unstrung-workers@lists.sandelman.ca about Linux
> kernel integration (none recently through).
>
> Discussions also occur on linux-wpan@vger.kernel.org.
> It would be a good place to start a new thread.
>

but also IMHO we need to have some summary with discuss in this list about
implementations of WG RFCs.


>
> Rahul Jadhav <rahul.ietf@gmail.com> wrote:
>     > Hello ROLL,
>
>     > While trying to integrate RPL with linux kernel and we had certain
>     > design choices. In that context I have some specific questions,
>     > especially towards linux-kernel integration and not towards RPL
>     > protocol implementation itself. Assuming RPL implementation will be
> in
>     > userspace, questions are:
>
>     > 1. We can add/del routes using rtnetlink interfaces ... this can be
>     > used for the routes learnt by RPL as well ... But RPL needs to
>     > maintain some additional per-route information on the 6LBR ... To be
>     > very specific, we need to store parent information in context to
> every
>     > route. Is it possible to do it with rtnetlink? I didn't find an
> option
>     > to do that. If it ain't possible then what could be an alt approach?
>
>     > 2. RPL requires that certain extended ipv6 options be added in data
>     > flows .. What is the best way to do this? It is possible to do this
>     > with netfilter+libnfq but i m not sure whether this is the best
>     > approach.
>
>     > If there is anyone who tried this before, it would be great to have a
>     > discussion in person while we are in IETF102. Please let know if you
>     > are available for discussion.
>
>     > Thanks,
>     > Rahul
>
>     > _______________________________________________
>     > Roll mailing list
>     > Roll@ietf.org
>     > https://www.ietf.org/mailman/listinfo/roll
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>

v2.23.0 | Report a Bug | By Email