IETF Logo Mail Archive

Re: [Sdn] [nvo3] OpenOverlayRouter released!

"MORTON, ALFRED C (AL)" <acmorton@att.com> Fri, 05 February 2016 14:53 UTC

Return-Path: <acmorton@att.com>
X-Original-To: sdn@ietfa.amsl.com
Delivered-To: sdn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 329701B39F8; Fri, 5 Feb 2016 06:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5vEmJgqLTTdF; Fri, 5 Feb 2016 06:53:24 -0800 (PST)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [204.178.8.22]) by ietfa.amsl.com (Postfix) with ESMTP id B4B9D1B39DB; Fri, 5 Feb 2016 06:53:23 -0800 (PST)
Received: from mail-green.research.att.com (H-135-207-255-15.research.att.com [135.207.255.15]) by mail-pink.research.att.com (Postfix) with ESMTP id EBA441229CE; Fri, 5 Feb 2016 09:56:12 -0500 (EST)
Received: from exchange.research.att.com (njfpsrvexg0.research.att.com [135.207.255.124]) by mail-green.research.att.com (Postfix) with ESMTP id AE332E1008; Fri, 5 Feb 2016 09:50:16 -0500 (EST)
Received: from NJFPSRVEXG0.research.att.com ([fe80::108a:1006:9f54:fd90]) by NJFPSRVEXG0.research.att.com ([fe80::108a:1006:9f54:fd90%25]) with mapi; Fri, 5 Feb 2016 09:53:22 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Date: Fri, 5 Feb 2016 09:53:21 -0500
Thread-Topic: [nvo3] OpenOverlayRouter released!
Thread-Index: AQHRX2j0avRNDVouIEKwOnMGpfvWQZ8dSGwAgACOLwD//7RG4A==
Message-ID: <4AF73AA205019A4C8A1DDD32C034631D2E26DF2A78@NJFPSRVEXG0.research.att.com>
References: <CA+YHcKE78m0L2AsoDtXxXamgHBqSKS0bk9TV63gexMDoGSi2dw@mail.gmail.com> <DB3PR03MB0780DA2CE529B076DCBBD9379DD20@DB3PR03MB0780.eurprd03.prod.outlook.com> <4E7E7ADA-2647-4B00-9968-36981056E8B1@cisco.com>
In-Reply-To: <4E7E7ADA-2647-4B00-9968-36981056E8B1@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_4AF73AA205019A4C8A1DDD32C034631D2E26DF2A78NJFPSRVEXG0re_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sdn/M0JSE0gLeJSkWEiOyioHI0gCY1A>
X-Mailman-Approved-At: Fri, 05 Feb 2016 06:54:42 -0800
Cc: SDN IRTF list <sdn@irtf.org>, "lisp@ietf.org list" <lisp@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "nfvrg@irtf.org" <nfvrg@irtf.org>, Alberto Rodriguez-Natal <arnatal@ac.upc.edu>
Subject: Re: [Sdn] [nvo3] OpenOverlayRouter released!
X-BeenThere: sdn@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List to Discuss SDN Research Group in the IRTF <sdn.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/sdn>, <mailto:sdn-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sdn/>
List-Post: <mailto:sdn@irtf.org>
List-Help: <mailto:sdn-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/sdn>, <mailto:sdn-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 14:53:26 -0000

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

From: Nfvrg [mailto:nfvrg-bounces@irtf.org] On Behalf Of Carlos Pignataro (cpignata)
Sent: Friday, February 05, 2016 9:24 AM
To: Alexander Vainshtein
Cc: SDN IRTF list; lisp@ietf.org list; sfc@ietf.org; nvo3@ietf.org; nfvrg@irtf.org; 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 <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:

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

________________________________
From: nvo3 <nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>> on behalf of Alberto Rodriguez-Natal <arnatal@ac.upc.edu<mailto:arnatal@ac.upc.edu>>
Sent: Thursday, February 4, 2016 6:26 PM
To: lisp@ietf.org<mailto:lisp@ietf.org> list; nvo3@ietf.org<mailto:nvo3@ietf.org>; SDN IRTF list; nfvrg@irtf.org<mailto:nfvrg@irtf.org>; sfc@ietf.org<mailto:sfc@ietf.org>
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<http://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/<http://webdefence.global.blackspider.com/urlwrap/?q=AXicJcqxDcJADABAS0zAIv95kQYqOmoooXIei7zk2JHjvMgejMQMzBMEV992A7cPwOsNYLw0qQuT1TBg4aziphyyDjCn9nQ5X3OT9mnXAjI9Ue5koWKRqXcqcqRcnJh-v3cfDzHqSKKVjHExnf371R4R_la7aigo&Z>


Thanks!
The OpenOverlayRouter team
_______________________________________________
nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3

v2.8.7 | Report a Bug | By Email