++ Overlays probably the most sustainable artifact of network virtualization trend. Good to distill distinct overlay notions into practical code base combining them. Further build from there in parallel to formal interface standardization.
--szb > On Feb 5, 2016, at 6:53 AM, MORTON, ALFRED C (AL) <[email protected]> wrote: > > +1 Carlos, and Running Code has *always* been of interest here. > Al > > From: Nfvrg [mailto:[email protected]] On Behalf Of Carlos Pignataro > (cpignata) > Sent: Friday, February 05, 2016 9:24 AM > To: Alexander Vainshtein > Cc: SDN IRTF list; [email protected] list; [email protected]; [email protected]; > [email protected]; Alberto Rodriguez-Natal > Subject: Re: [Nfvrg] [nvo3] OpenOverlayRouter released! > > Sasha, > > It seems to me to be extremely relevant and very proper, as we want more open > source software connections with the IETF. > https://www.ietf.org/meeting/91/2014.11.13_DWard-IETF-91.pdf > https://www.internetsociety.org/publications/ietf-journal-march-2015/open-standards-open-source-open-loop > > “Within the IETF, we face numerous issues around our own life cycle. […] What > does the subject matter of popular, network-centric OSS projects imply might > be missing at the IETF?” > > “How to Make the IETF Relevant in this Environment > > • Fix, change, or reinvent the liaison process because it will be critical to > collaboration with OSS projects. In fact, don’t even use the liaison process > as a model. > • Embrace Open Source projects.” > > Thanks, > > — Carlos. > > > On Feb 5, 2016, at 12:54 AM, Alexander Vainshtein > <[email protected]> wrote: > > Is this a proper kind of message on IETF mailing lists? > > > From: nvo3 <[email protected]> on behalf of Alberto Rodriguez-Natal > <[email protected]> > Sent: Thursday, February 4, 2016 6:26 PM > To: [email protected] list; [email protected]; SDN IRTF list; [email protected]; > [email protected] > Subject: [nvo3] OpenOverlayRouter released! > > Hi all, > > We would like to announce the first release of OpenOverlayRouter (OOR - > spelled "double-O-R"), an open-source project, under the Apache 2.0 License, > to instantiate programmable overlays. OOR is edge-oriented and multiplatform > (Android, Linux and OpenWRT) with the aim to offer a flexible and > easy-to-deploy overlay infrastructure. OOR is based on the former LISPmob.org > code. > > > * Who can use it * > > OOR is intended for end-users looking for easy multihoming, companies with > strong presence at the edge, startups interested in overlay solutions and > researchers exploring new scenarios. > > > * Supported protocols * > > OOR is interoperable with OpenDaylight and supports several protocols for > both the data and control plane. On the control plane, it supports NETCONF > for provisioning and management and LISP for operational state exchange. On > the data plane, it supports IPv4 and IPv6 overlays with LISP and VXLAN-GPE > encapsulations. The roadmap includes L2 overlays, further encapsulations and > support for SFC headers. > > > * Code * > > You can find all the details and get the code at: > http://openoverlayrouter.org/ > > > Thanks! > The OpenOverlayRouter team > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
