Re: [lisp] [nvo3] OpenOverlayRouter released!

"Paul Quinn (paulq)" <> Fri, 05 February 2016 15:08 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 90A631B3A3E; Fri, 5 Feb 2016 07:08:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4BLEp98-Wc1k; Fri, 5 Feb 2016 07:08:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 196271B3A38; Fri, 5 Feb 2016 07:08:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=17518; q=dns/txt; s=iport; t=1454684918; x=1455894518; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=tNEwPRwA2KLU79mx4PYh/E9zytfHpTDsQ2gVEuIWZ7Q=; b=DG+Nrp2RSO/lhDtsgSOjlfwdCaHdxb08ZteuQ1uFWOtBP8C5KwXuMF71 sZLKTO74hv1r0Alg3obmn+yvNIQQPLHXKPB6x241x1yHw0beZ8Pu7L0+C HDufm3utsEUGoOOgSL3DZWOzEntxu5qgH/kLb81UdHhjZoWlH61ffgtcA 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.22,401,1449532800"; d="scan'208,217"; a="74193303"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Feb 2016 15:08:37 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u15F8bbt024595 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 Feb 2016 15:08:37 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 5 Feb 2016 09:08:36 -0600
Received: from ([]) by ([]) with mapi id 15.00.1104.009; Fri, 5 Feb 2016 09:08:36 -0600
From: "Paul Quinn (paulq)" <>
To: "Carlos Pignataro (cpignata)" <>
Thread-Topic: [nvo3] OpenOverlayRouter released!
Thread-Index: AQHRX2j1xsTPugnWN0uqwhbV/LDzPp8dWS8AgACOMACAAAyNAA==
Date: Fri, 5 Feb 2016 15:08:36 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_720EE3ED688E4DB58CF64B2D9F357348ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: Alexander Vainshtein <>, SDN IRTF list <>, " list" <>, "" <>, "" <>, "" <>
Subject: Re: [lisp] [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: Fri, 05 Feb 2016 15:08:40 -0000

Well said Carlos!  Code FTW!

On Feb 5, 2016, at 9:23 AM, Carlos Pignataro (cpignata) <<>> wrote:


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<>

nvo3 mailing list<>