Re: [Roll] rpl routing and linux-kernel

João Pedro Taveira <joao.p.taveira@gmail.com> Mon, 30 July 2018 23:58 UTC

Return-Path: <joao.p.taveira@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 96A04130E61 for <roll@ietfa.amsl.com>; Mon, 30 Jul 2018 16:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 0lVnpSMlNjAJ for <roll@ietfa.amsl.com>; Mon, 30 Jul 2018 16:58:18 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 599BA130F66 for <roll@ietf.org>; Mon, 30 Jul 2018 16:58:18 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id e7-v6so14649205wrs.9 for <roll@ietf.org>; Mon, 30 Jul 2018 16:58:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=dd3VBcb0DrBBiDAmyWSCZLVfnFKQ+4R0JrXVMs/QLCg=; b=nXVn2ERIkx7nRIk34RoPncd4yL7kLOsNnZuBOQ6/0O45eL9OXJihfdW6InI8ueUPIn 4tWHogXh/6otEvExAgdv6dM5RKq8rv9s9YPFsopK6yYkV/tgR+4VKt06ftLHPdt9DKfz jBNGQFMkG4D/4uXvPoLl/Vn6AvmbUMZ+iM1SnmRM3jVGuzRRGFUFw/A8xOWWK2VQgWgy 5ula+yrcdwAsnLpnObeE9rsMEMHNN28JeqG0lDaVwfLJW/Prvy/5WmIHKOiWwXRQjxie ywz/1KAI/6yyyv+cRV5eQSz2WnOvG0niomLcpJ4uGqcKoLzJbx0Mqqrl0r7Y49g9DYCY J3ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=dd3VBcb0DrBBiDAmyWSCZLVfnFKQ+4R0JrXVMs/QLCg=; b=MwGvmkDPAZrH6IXOFDDqAdCauSBUVBmCwLZ2QJz4BFO15L6SwFD3wP/TpJmmdBNOr0 QedAYIKSgWwtXk0rwyODpWyOzEhrKmsC4olpN2d7/tdQUdxgC7JbZcPtPJHbh+p/kgBJ kCsspyrM/9VnnqH8GUPx7ebKMfhemasvkgwSgOaTxNf3nQa3hqyA+ugmJsKmnDgO9h1H z6iTi3cjmLcvZX6gxVCzaWAVtKBCxO9wxZoLig+b0uGaerZWlhsAlDTSY3x9LRF3qm0T Tx254oxJOs4D75cN+ksj3B+qV23GpoyfMl8Yi6T+qT8SRzNwXwaePD3oLnvmlgphMi6a 364w==
X-Gm-Message-State: AOUpUlEu9jtZ0DfqF3knyG95iIlynqMBNxWV+IFxv205cB7LnhKG48qs 8dUkF3P9aCxlt0z9/lLZC6W8Glgf
X-Google-Smtp-Source: AAOMgpctwzftG0P+tbMEV8um5xmTLHs2o5T93KZkPMMgxhxnOjIGwoi9530bLZhQjEwAL7uHnLyX1w==
X-Received: by 2002:a5d:494c:: with SMTP id r12-v6mr19342477wrs.66.1532995096426; Mon, 30 Jul 2018 16:58:16 -0700 (PDT)
Received: from ?IPv6:2001:8a0:6a52:4102:ca69:cdff:fe98:c1b4? ([2001:8a0:6a52:4102:ca69:cdff:fe98:c1b4]) by smtp.gmail.com with ESMTPSA id d7-v6sm15007574wro.92.2018.07.30.16.58.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jul 2018 16:58:15 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A79B9D15-4E29-48A3-B05C-A5C4209A3814"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: João Pedro Taveira <joao.p.taveira@gmail.com>
X-Mailbutler-Link-Tracking-Uuid:
In-Reply-To: <CADnDZ88GBypAiWRWVa7NQsRcNGdmvUK+DW+JuGcK7=s5C0ekYQ@mail.gmail.com>
Date: Tue, 31 Jul 2018 00:58:09 +0100
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, rahul.ietf@gmail.com
Message-Id: <AE849528-1B5D-4E22-ACA7-C87277C32D99@gmail.com>
References: <CAO0Djp16_WUrKkbY-UQGdjLhO2gYitHQo=7iw4cn+fC_am5DdA@mail.gmail.com> <17294.1531966560@localhost> <CADnDZ88GBypAiWRWVa7NQsRcNGdmvUK+DW+JuGcK7=s5C0ekYQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/px83YdNJ-3Mu4MVq5YhOcfO98ks>
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, 30 Jul 2018 23:58:22 -0000

Hi,

Rahul, I watch the youtube video of ROLL session (thanks to Michael last mail to list) and I notice you ask about RPL implementations in linux kernel. About my kernel implementation attempt history, roadmap and status, please check https://github.com/joaopedrotaveira/linux-rpl/issues/1 <https://github.com/joaopedrotaveira/linux-rpl/issues/1>. There’s a link with my initial plan and my failures.

If we could try to make it happen, it would great. Send me your questions to my email or make presure on github repo. I just would like to move this subject to any other channel.

Abdussalam, I agree with Michael, there are discussions about this subject were they should be. And IMHO, I never leaved, I’m still here.

Best Regards,
João Pedro Taveira

> On 23 Jul 2018, at 13:29, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> 
> 
> 
> On Thu, Jul 19, 2018 at 4:16 AM, Michael Richardson <mcr+ietf@sandelman.ca <mailto: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 <mailto:unstrung-workers@lists.sandelman..ca> about Linux
> kernel integration (none recently through).
> 
> Discussions also occur on linux-wpan@vger.kernel.org <mailto: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 <mailto: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 <mailto:Roll@ietf.org>
>     > https://www.ietf.org/mailman/listinfo/roll <https://www.ietf.org/mailman/listinfo/roll>
> 
> -- 
> Michael Richardson <mcr+IETF@sandelman.ca <mailto:mcr%2BIETF@sandelman.ca>>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org <mailto:Roll@ietf.org>
> https://www.ietf.org/mailman/listinfo/roll <https://www.ietf.org/mailman/listinfo/roll>
> 
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org <mailto:Roll@ietf.org>
> https://www.ietf.org/mailman/listinfo/roll <https://www.ietf.org/mailman/listinfo/roll>
________________________________________
João Pedro Taveira Pinto Silva
e-mail: joao.p.taveira@gmail.com <mailto:joao.p.taveira@gmail.com>
github: joaopedrotaveira <https://github.com/joaopedrotaveira>
linkedin: joaopedrotaveira <https://www.linkedin.com/in/joaopedrotaveira>