Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-12-01 Thread Jan Scheurich
> From: ovs-dev-boun...@openvswitch.org > [mailto:ovs-dev-boun...@openvswitch.org] On Behalf Of Darrell Ball > Sent: Thursday, 30 November, 2017 01:15 > > On 11/27/17, 11:31 AM, "Ben Pfaff" wrote: > > Darrell, I think that you are working on some of the specific items that > Aaron liste

Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-29 Thread Darrell Ball
On 11/27/17, 11:31 AM, "Ben Pfaff" wrote: Darrell, I think that you are working on some of the specific items that Aaron listed. Can you comment on that? “1”: which is day 1 behavior, has been discussed on other threads on the mailing list for some weeks. I submitted a patch

Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-28 Thread Tiago Lam
Hi Aaron, On 11/28/2017 05:38 PM, Aaron Conole wrote: > Tiago Lam writes: > >> Hi all, >> >> Thanks, Darrell. That sounds reasonable to me, nothing to point there. > > I agree. We need to ensure that pollution of code doesn't occur. > >> But this leads me to my next question; With regards to

Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-28 Thread Aaron Conole
Tiago Lam writes: > Hi all, > > Thanks, Darrell. That sounds reasonable to me, nothing to point there. I agree. We need to ensure that pollution of code doesn't occur. > But this leads me to my next question; With regards to integrating > with SIP (or even SCTP), is there a list of the main us

Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-28 Thread Tiago Lam
Hi all, Thanks, Darrell. That sounds reasonable to me, nothing to point there. But this leads me to my next question; With regards to integrating with SIP (or even SCTP), is there a list of the main use cases to support, or something similar? I guess this is still early days, but for SIP for ex

Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-27 Thread Ben Pfaff
Darrell, I think that you are working on some of the specific items that Aaron listed. Can you comment on that? On Sat, Nov 25, 2017 at 07:37:23PM +, Darrell Ball wrote: > Let me clarify some general points. > > 1/ We will not be porting any code from the Linux kernel, whether it be SIP > m

Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-25 Thread Darrell Ball
Let me clarify some general points. 1/ We will not be porting any code from the Linux kernel, whether it be SIP module code or anything else. 2/ Furthermore, we will not be using proprietary code algorithms and other aspects from the Linux kernel. 3/ Furthermore, those people working in, havin

Re: [ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-25 Thread Tiago Lam
Hi Aaron (and all), Thank you for your email, I found it to be informative. Would you mind elaborating a bit more on point number 5 below? With regards to SIP (don't know about SCTP), a module [1] seems to already exist for the kernel, integrating with Netfilter / conntrack. So, in terms of sup

[ovs-dev] [CONNTRACK] Discussions at OvS 2017

2017-11-20 Thread Aaron Conole
(NOTE: This is a resend - I fat-fingered the ovs email. Apologies to those who got duplicates). This email is meant to summarize some of the discussions we had at OvS conference. The interest in the userspace conntrack is heating up. That's a good thing, but it means that we'll probably have so