Re: [lisp] [sfc] [nvo3] OpenOverlayRouter released!

"Susan Hares" <> Mon, 08 February 2016 00:41 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 582BD1A871A; Sun, 7 Feb 2016 16:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -96.257
X-Spam-Status: No, score=-96.257 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.793, USER_IN_WHITELIST=-100] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id M-YI5f94TJs0; Sun, 7 Feb 2016 16:41:50 -0800 (PST)
Received: from (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D30D01A8716; Sun, 7 Feb 2016 16:41:49 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: "Susan Hares" <>
To: "'MORTON, ALFRED C \(AL\)'" <>, "'Carlos Pignataro \(cpignata\)'" <>, "'Alexander Vainshtein'" <>
References: <> <> <> <>
In-Reply-To: <>
Date: Sun, 7 Feb 2016 19:41:40 -0500
Message-ID: <00d601d16209$7a235a60$6e6a0f20$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D7_01D161DF.91505FA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEa13StjE5LHmI2LycE7tADVdmQWwJuieFbAe3+c14CVq6ciqBYyiYA
Content-Language: en-us
Archived-At: <>
Cc: 'SDN IRTF list' <>,,,,
Subject: Re: [lisp] [sfc] [nvo3] OpenOverlayRouter released!
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Feb 2016 00:41:52 -0000

+1 to Al and Carlos.  Running code has and should be of interest in IETF. 




From: sfc [] On Behalf Of MORTON, ALFRED C (AL)
Sent: Friday, February 05, 2016 9:53 AM
To: Carlos Pignataro (cpignata); Alexander Vainshtein
Cc: SDN IRTF list; list;;;; Alberto Rodriguez-Natal
Subject: Re: [sfc] [nvo3] OpenOverlayRouter released!


+1 Carlos, and Running Code has *always* been of interest here.



From: Nfvrg [] On Behalf Of Carlos Pignataro (cpignata)
Sent: Friday, February 05, 2016 9:24 AM
To: Alexander Vainshtein
Cc: SDN IRTF list; list;;;; Alberto Rodriguez-Natal
Subject: Re: [Nfvrg] [nvo3] OpenOverlayRouter released!




It seems to me to be extremely relevant and very proper, as we want more open source software connections with the IETF.


“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.”




— Carlos.



On Feb 5, 2016, at 12:54 AM, Alexander Vainshtein <> wrote:


Is this a proper kind of  message on  IETF mailing lists?



From: nvo3 <> on behalf of Alberto Rodriguez-Natal <>
Sent: Thursday, February 4, 2016 6:26 PM
To: list;; SDN IRTF list;;
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 <>  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: <> 

The OpenOverlayRouter team

nvo3 mailing list