Hi Aaron, On 11/28/2017 05:38 PM, Aaron Conole wrote: > Tiago Lam <[email protected]> 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 use cases to >> support, or something similar? I guess this is still early days, but >> for SIP for example, I'd imagine that supporting the INVITE and >> respective 200 OK and inspecting the SDP to set up the expectations >> for the RTP connections would be a good first step. But what other >> methods are of interest out there? > > I'll answer from my perspective. > > I'll ask our customers for more firm requirements. I know we have > customers who are looking to adopt OvS on their hardware, and process > 100000s of calls per second, who are looking at what exists as far as > ovs features goes. I think you've outlined the important messages as > far as SIP goes. > > As for SCTP, that I'm less aware. I know we have customers who use SCTP > for processing messages (and newer AAA services use DIAMETER which has > some dependency on SCTP). > > Does that help understand?
Thanks, that certainly helps giving some perspective. It will be interesting to see how this evolves. This also answers my question "Has any work started around this?". I'd be very keen to help on that. Regards, Tiago. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
