From: David Lebrun <david.lebrun@uclouvain.be>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [RFC 2/9] ipv6: sr: add code base for control plane support of SR-IPv6
Date: Thu, 1 Sep 2016 15:21:07 +0200 [thread overview]
Message-ID: <57C82B43.80100@uclouvain.be> (raw)
In-Reply-To: <57C4554F.9000905@cumulusnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-09-01 13:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 15:52 [RFC 0/9] add support for IPv6 Segment Routing David Lebrun
2016-08-26 15:52 ` [RFC 1/9] ipv6: implement dataplane support for rthdr type 4 (Segment Routing Header) David Lebrun
2016-08-31 14:51 ` Nicolas Dichtel
2016-09-01 13:11 ` David Lebrun
2016-09-01 13:58 ` Nicolas Dichtel
2016-08-31 17:13 ` Stephen Hemminger
2016-08-26 15:52 ` [RFC 2/9] ipv6: sr: add code base for control plane support of SR-IPv6 David Lebrun
2016-08-29 15:31 ` Roopa Prabhu
2016-08-31 14:57 ` Nicolas Dichtel
2016-09-01 13:21 ` David Lebrun [this message]
2016-09-05 10:05 ` Nicolas Dichtel
2016-08-31 14:59 ` Nicolas Dichtel
2016-08-31 17:10 ` Stephen Hemminger
2016-09-01 13:25 ` David Lebrun
2016-09-01 17:15 ` Stephen Hemminger
2016-08-31 17:11 ` Stephen Hemminger
2016-08-31 17:11 ` Stephen Hemminger
2016-08-26 15:52 ` [RFC 3/9] ipv6: route: export symbol ip6_route_input David Lebrun
2016-08-26 15:52 ` [RFC 4/9] ipv6: sr: add support for SRH encapsulation and injection with lwtunnels David Lebrun
2016-08-29 14:52 ` Roopa Prabhu
2016-09-01 13:32 ` David Lebrun
2016-08-26 15:54 ` [RFC 5/9] ipv6: sr: add core files for SR HMAC support David Lebrun
2016-08-26 15:54 ` [RFC 6/9] ipv6: sr: implement API to control SR HMAC structures David Lebrun
2016-08-26 15:54 ` [RFC 7/9] ipv6: sr: add calls to verify and insert HMAC signatures David Lebrun
2016-08-26 15:54 ` [RFC 8/9] ipv6: add source address argument for ipv6_push_nfrag_opts David Lebrun
2016-08-26 15:54 ` [RFC 9/9] ipv6: sr: add support for SRH injection through setsockopt David Lebrun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57C82B43.80100@uclouvain.be \
--to=david.lebrun@uclouvain.be \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).