+1
Last time I checked IETF moto was "Rough consensus and running code".
I see nothing wrong with announcements related to the second half of the
moto on the working group lists. It is proper and fitting.
In fact we need more of that, so that is clear which drafts and
proposals have working interoperable implementations.
After all, once upon a time, there used to be a precondition for
something to be considered a standard, namely: "Does it have more than 2
interoperable independent implementations".
A.
On 05/02/16 14:23, Carlos Pignataro (cpignata) wrote:
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]
<mailto:[email protected]>> wrote:
Is this a proper kind of message on IETF mailing lists?
------------------------------------------------------------------------
*From:*nvo3 <[email protected] <mailto:[email protected]>> on
behalf of Alberto Rodriguez-Natal <[email protected]
<mailto:[email protected]>>
*Sent:*Thursday, February 4, 2016 6:26 PM
*To:*[email protected] <mailto:[email protected]>list;[email protected]
<mailto:[email protected]>; SDN IRTF list;[email protected]
<mailto:[email protected]>;[email protected] <mailto:[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 formerLISPmob.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
[email protected] <mailto:[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
