netdev - Re: [RFC 2/9] ipv6: sr: add code base for control plane support of SR-IPv6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 1 Sep 2016 15:21:07 +0200
From:   David Lebrun <david.lebrun@...ouvain.be>
To:     Roopa Prabhu <roopa@...ulusnetworks.com>
CC:     <netdev@...r.kernel.org>
Subject: Re: [RFC 2/9] ipv6: sr: add code base for control plane support of
 SR-IPv6

On 08/29/2016 05:31 PM, Roopa Prabhu wrote:
> This looks fine. But, i am just trying to see if this can be rtnetlink.
> Have you considered it already ?.
> We would like to keep the API consistent or abstracted to accommodate SR-MPLS in the
> future too. so, any abstraction there will help.
> 
> what is your control-plane software using this ?
> quagga or any-other routing daemon ?
> 
> Thanks,
> Roopa
> 

rtnetlink is used for the routing part through the lwtunnels. In this
specific patch, the API is intended to configure namespace-wide
parameters such as a map of hmackeyid -> hashfn,secret, without
connection to particular routes. I agree that the tunsrc parameter could
be provided through rtnetlink, but the hmac data cannot (which by the
way does not exist for SR-MPLS).

The "control plane software" that currently uses that is simply a
patched version of iproute2 with SR support (which I will submit when
this patch series is hopefully merged). (e.g. ip sr set hmac blahblah)

More advanced control plane softwares are currently under development
and will be presented in upcoming academic publications.

David

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)