IMG_4389.JPGThe International Multimedia Telecommunications Consortium (IMTC) held its 21st Annual Multimedia Products and Services Interoperability Testing Event, SuperOp! 2016, at Loews Royal Pacific Resort in Orlando, Florida, May 14-20, 2016.


Need more background on the event? Check out the this blogpost leading up to it, Get Ready to Interoperate at IMTC SuperOp 2016!


Okay, now to the results.


The SIP Interconnect Activity Group testing drew at least 16 product teams from companies including Blue Jeans Networks, Cisco Systems, Huawei, Intel, Pexip, Polycom, Sonus Networks , Sorenson Communications, Spirent Communications, Vidyo, and Wipro. Testing focused on key aspects of videoconferencing/telepresence interoperability, with the IMTC SIP Interconnect best practices and associated test cases documents providing a framework within which to test and report results. Interworking across implementations was quite broad, extending beyond that covered within the best practice documents, including SIP/WebRTC interworking via gateways provided by several participants.

 

Most of the companies participating had been to previous SuperOp events, and while there were many new faces, representatives from most companies included a mix of seasoned SuperOp attendees along with the newcomers. As a result, the level of interworking and the sophistication of the test scenarios was more advanced than in previous years. New interoperability issues were identified, some of which were resolved during the week with corresponding changes being fed back into the best practices and test cases documents. Others challenges require more consideration and will be addressed by future SIP Interconnect AG member meetings.

 

The group recently published an official update to its SIP Video Profile Best Practice, IMTC1015. Official publications of the groups Role Base Video Best Practice and SIP Security Best Practice are planned within the next year. New participants, findings, and questions are welcome and encouraged. To get started, visit the IMTC member portal and subscribe to the SIP Interconnect mailer.

Screen Shot 2016-05-06 at 9.49.21 AM.pngThe International Multimedia Telecommunications Consortium (IMTC) is all set to host the 21st Annual IMTC Multimedia Products and Services Interoperability Testing Event, SuperOp! 2016, taking place at Loews Royal Pacific Resort in Orlando, Florida, May 14-20, 2016.

 

Testing includes communication technologies such as WebRTC, UC SDN, H.26x SVC, SIP over IPv6, SIP and H.323 Video Conferencing, Telepresence/TIP, MPEG-DASH streaming, IMS, VoLTE, RCS, Video over LTE, and many others. The IMTC is not a standards body; rather, it produces best practices outlining how to use existing standards to produce solutions that interwork well with those produced by other vendors. It also provides test case document that structure testing at the event and provide quantitative results of the level of interoperability among with implementation represented at the event.

 

One of the IMTC activity groups that participates actively each year in this event is the SIP Interconnect AG. This group provides a forum for IMTC member companies to collaborate and pool resources on issues and extensions to enterprise communication applications that are based on the IETF's RFC 3261, SIP: Session Initiation Protocol. With its best practices documents providing a shared foundation, the group identifies and tackles challenges and opportunities with interoperability, operation, and integration of SIP based applications with emerging communication and networking technologies.

 

The main activities of the group are to:

Screen Shot 2016-05-06 at 9.44.42 AM.png

        • Organize interoperability test efforts (both virtual and face-to-face)
      • Provide a forum for members to agree on an overall SIP profile for communication applications, including where it involves interconnecting with other application and network technologies (e.g. WebRTC, SDN, IPv6)
      • Educate members on recent developments in SIP standards and market evolution

 

Screen Shot 2016-05-06 at 9.48.18 AM.pngThe work of the SIP Interconnect AG and findings from last year's SuperOp resulting in the recently released IMTC 1015, SIP Video Profile Best Practices, Implementation Guide.

 

You can find an overview presentation covering this and other best practice documents produced by the SIP Interconnect AG at SIP Video Conferencing Interoperability Review.

Rome was not built in a day, and neither was a complete reference implementation of the MEF's LSO architecture. However, at the Euro16 Hackathon in Rome last week, a group of talented developers made great progress in that direction. For those not intimately familiar with MEF, the LSO architecture, or the corresponding open source initiatives, here is a bit of background.

 

MEF, a standards organization with its roots in carrier ethernet, noticed that network service orchestration is the key pain point of service providers today.  MEF targeted this by defining Lifecycle Service Orchestration (LSO), an umbrella architecture with APIs enabling agile, assured and orchestrated network services worldwide. It includes inter-provider interfaces ("east/west") as well as intra-provider ("north/south") interfaces.

lso.png

MEF refers to the network powered by LSO as the “Third Network". The Third Network is a revolution in service provider networking. It combines Internet agility and ubiquity with service assurance, offers unprecedented levels of user control of the network, and delivers dynamic, on-demand service experience. It is expected that other SDOs will implement parts of this architecture. Toward that goal, MEF is working with ETSI-NFV, ONF, TMF and others, and it has launched a set of open source initiatives through which such as OpenDaylight, OpenStack, and OPNFV are being enhanced and applied to create a reference implementation of the LSO architecture.

 

It all started last November, when Cisco DevNet helped MEF take a bold step into uncharted territory, holding its first ever hackathon. The primary goal was to bring together the key subject matter experts defining LSO with the developers creating industry changing open source projects for the mutual benefit of both. The focus was the LSO Presto interface, a"north-south" interface for network resource provisioning. Among other things, teams worked to add support for this interface to OpenDaylight. A complete a summary of this industry changing event can be found here: LSO Hackathon debut at GEN15.

 

The impact of that first hackathon extended well beyond the code produced over the course of that week. Participation by open source experts from a mix of long time MEF member companies and non-member companies caused the MEF to make its work-in-progress specifications and corresponding APIs available to non member companies. It also prompted MEF to consider how it treats contributions in the form of code rather than written documents and specifications. More publicly, it inspired the creation of two new projects within MEF, OpenLSO and OpenCS, both aimed at the production of open source reference implementations aligned with MEF architectures and specifications.

 

open-initiatives.png

Last but certainly not least, it led to MEF working with Cisco DevNet to plan a second LSO hackathon, the Euro16 Hackathon, as part of the recent Q2 MEF meeting in Rome. The Euro16 hackathon raised the bar early in the planning stages, challenging teams to work not only adding support for LSO Presto as they did during previous hackathon, but also on LSO Sonata, dealing with ordering and serviceability across service providers.

 

As with the previous hackathon, registration was free and open to everyone. Registrants included individuals from 16 different companies. Most participants met together in Rome, while others engaged effectively from remote locations. To get things going, organizers provided some background on the LSO architecture. Next, each team gave a brief presentation of their goals and objectives, including the projects and products they intended to use and how their proposed work fit into the LSO architecture. Party lines blurred almost immediately as participants identified and jumped at the chance to work across multiple teams with new colleagues and technologies. This excitement and energy continued for the next two and half days, as participants worked feverishly to make the most of the opportunity at hand. The results were astounding, exceeding all expectations of the event organizers and the participants themselves.

euro16-room.jpg

Screen Shot 2016-05-05 at 4.20.12 PM.pngOne team, with members from Cisco, HPE, Amartus, Microsemi, and Ericsson, worked on adding support for the Presto interface to OpenDaylight. This work was done within the context of the UniMgr project and running MEF's Network Resource Provisioning (NRP) UML model through the xmi2yang tools being defined by the ONF Eagle project to produce a YANG model that is then used to generate code for the Presto interface within OpenDaylight. The team also started work on Cisco IOS-XR, Microsemi, and Tail-f NETCONF interface activation drivers to enable OpenDaylight to configure the underlying network. Their work uncovered issues with the NRP model, the ONF Core Model core model on which it is based, and the xmi2yang tool coming out of the ONF Eagle project. It highlighted that code generation from the resulting YANG models is not straightforward, partly because ONF Core models and derived MEF YANG models are information models and code generation requires data models. Here we see a very important outcome of the hackathon, providing a reality check to potential approaches and shining a spotlight on important details that might otherwise get glossed over.

euro16-participants.jpg

Working closely with this team were folks from Gigaspaces. They used the northbound interface of the Cloudify open source orchestrator as a sample LSO Legato interface implementation, and implemented the Presto forwarding constructs to communicate with the OpenDaylight UniMgr implementation under development by the previous team. In doing so, they identified gaps in the Legato inputs for ordering. They also pointed out that support at the Presto interface today is layer 2 only and that MEF needs to add support for layer 3 to its forwarding constructs.

 

Another team, compromised primarily of participants from long time MEF member companies (e.g. AT&T, Ciena, CableLabs, Ericsson), broke new ground for the hackathon, tackling ordering and serviceability between service providers as defined by the Sonata interface. This team used AT&T’s internal API to simulate taking an order from a customer, then used an experimental version of the Sonata API to communicate the order details between service providers. In the process they discovered some redundancy/duplicate fields in the ordering API, (e.g. customer address fields repeated in multiple places). The receiving SP process the order and configured the underlying network accordingly using BluePlanet with the ONOS controllers and EdgeCore switches. Here we see the hackathon identifying gaps and issues in the interface specs at the time these specs are being produced.

 

Yet another team worked with Enterprise CORD (Central Office Re-architected as a DataCenter), or E-CORD. E-CORD makes heavy use of open source, most notably, XOS and ONOS. Through close interaction with other participants during the event, the E-CORD team arrived at a redesigned architecture that is more appropriate for LSO. The new architecture will replace what they brought to the hackathon and be used for future work and hackathons. This demonstrates the tremendous value of the hackathon to help identify and address issues early. They also started down the path of implementing the Presto interface via the evolving NRP API.

 

Overall, the hackathon was viewed by all involved as a huge success. Of course there were things that could have been done better, but the participants agreed that the time spent preparing for and participating in the hackathon were extremely valuable and in productive. Stay tuned for announcements and news regarding the next in the LSO hackathon series, most likely as part of MEF16 in early November in Baltimore-Washington.

Screen Shot 2016-05-05 at 4.26.36 PM.png

Thanks to David Ball and Donald Hunter for providing content used in this post.

Screen Shot 2016-04-26 at 2.31.56 AM.png

 

The IETF 95 Hackathon in Buenos Aires kicked off what was both the first and an extremely rewarding trip by the IETF community to South America. Roughy 100 participants, a record 10% of the total IETF meeting attendees, arrived early in Buenos Aires to put their talents to use tackling a diverse set of projects aimed at improving the internet we rely on every day.

 

The list of projects and teams included many familiar faces as well as a refreshing set of new participants and challenges. This was the first hackathon for about of the third or the participants, with over a dozen attending their first IETF meeting ever. Many first timers were from the host country, including from Buenos Aires and Mendoza, but there were two from Africa and others some Europe and the U.S. as well. Check out this story shared by one IETF and IETF hackathon first timer (https://communities.cisco.com/community/developer/opensource/blog/2016/04/25/first-timer-at-ietf-and-ietf-hackathon-shares-his-story).

 

Screen Shot 2016-04-26 at 2.21.44 AM.pngOther notable firsts for this hackathon were:

Charles Eckel, from Cisco DevNet, continues to run the hackathon in his role as hackathon chair and welcomes Barry Leiba, from Huawei as a appreciated and valued hackathon co-chair.

 

As with previous hackathons, participants worked cooperatively and tirelessly, producing fantastic results. Each team summarized their achievements in a brief presentation to judges and their peers. Tops honors and prizes were awarded for especially brilliant accomplishments, includes those of the FD.io/VPP team, the TLS 1.3 team (see story at https://www.ietf.org/blog/2016/04/ietf-hackathon-getting-tls-1-3-working-in-the-browser/), and the network-based network analytics team. Some teams demoed their work at Bits-n-Bites, including the NETCONF/YANG, I2RS, OpenDaylight teams, DNS/DNSSEC/DANE/DNS-over-(D)TLS teams, and the IBNEMO team. All the presentations and results are available via the proceedings page (https://www.ietf.org/proceedings/95/hackathon.html).

Screen Shot 2016-04-26 at 2.22.27 AM.png

 

Following the success in Buenos Aires, the IETF 96 Hackathon this summer in Berlin, July 16-17, is sure to be the biggest IETF hackathon ever.

http://www.ietf.org/hackathon/96-hackathon.html

 

Mark your calendars now and subscribe to the hackathon list (https://www.ietf.org/mailman/listinfo/hackathon) to remain abreast of the latest information, including announcements of new projects and the ability to reserve your place in this history making event.

IETF 95 Hackathon

Authored by: Agustín Formoso

TL;DR

Great f2f meeting, worth attending. Get to know new people coding similar stuff that you might be coding. Get to feel the IETF spirit.

Still, I think it needs some intermediate level between high-barrier-and-focused, and low-barrier-but-unfocused groups.

First impressions

The basics

Essential things for the hackathon to feel comfortable were there: the physical space for all the participants, food and drinks (actually there were some pretty good meals and snacks), and enough power outlets to charge all of our nerdy devices.

One thing that could had been of use are additional elements for sprint planning such as post-its, big papers to set up sprint backlogs, and some paper and pens to sketch and communicate with other strange-language-speaking group mate.

The groups

At the kickoff, the group champions explained what each group is about and what the main objective is. As a first timer, looking for a suitable group to work with during 2 days was a critical point. My previous experience with the hackathon was literally none, as I had no relation with any work in progress so far. I had to find a group which topic was of interest to me and which I had at least some vague concept about the technologies involved. Fortunately, I ended up in a group which required no previous experience with, no specific tools to do what was planned, just my laptop and my will to solve a problem. The problem was to find any metrics that helped discover anomalies or patterns in a dataset of traceroutes, it was a cool project and I enjoyed being the two days coding stuff for it. Besides, you get to feel the nice IETF spirit of building things for a better Internet.

The ending

The group deliverables

Probably as the group I ended up in was very generic and the entry barrier was pretty low, setting specific deliverables for the 2 day sprint was difficult. Other groups had more specific tasks to accomplish, such as building features for a YANG modelling application or implementing TLS 1.3 in a Firefox browser. I guess that by following some of the groups closer and collaborating remotely prior to the hackathon might end up in getting the most out of the hackathon, as in that case the hackathon would just be a team f2f meeting, without the hassles of setting up development environments, getting to learn new concepts, or new technologies entirely (nor was my case, but I easily see that situation as a very common scenario as IETF hackathons get more popular).

I still think that the hackathon should consider having low, intermediate, and high entry barrier groups. There's room to set an intermediate level in each hackathon where the group would require some things such as tools (virtual machines, IDEs) and some follow up (probably in the order of weeks time). In that case I think a better and more focused deliverable might be reached. In this consideration, the low entry barrier groups should approach newcomers with no experience or contact with the IETF hackathon, and the high entry barrier group should approach the usual hackathon participants.

Further work

The IETF hasn't finished yet and I think is a very good instance to get to know new people and establish links to motivate future work. The coding done in the group I was part of is of special interest to me and hope that some months from now we have a nice tool to analyze network graphs which benefits our champion (Pål) and the rest of us.

[Editors Note: For more information on the IETF hackathon series, see IETF Hackathon]

eckelcu

Euro16 LSO Hackathon in Rome

Posted by eckelcu Mar 21, 2016

Screen Shot 2016-03-21 at 11.33.27 AM.pngMEF Forum is holding the Euro16 LSO Hackathon in Rome, April 27-29. The hackathon is colocated with MEF’s Quarterly Member’s Meeting. The goal of this hackathon, and with the MEF’s LSO Hackathon series, is to be a catalyst for the creation of one or more reference implementations of the Lifecycle Services Orchestration (LSO) architecture. This not only validates the architecture in parallel with standardizing the APIs it defines, but also ensures these APIs are compatible with and supported by open source projects, such as OpenDaylight, OpenStack, and OPNFV, that play a role in the architecture. As such, a primary objective is pulling together active contributors of relevant standards organizations and open source communities to improve communication and collaboration.

 

You do not need to be a member of MEF to participate in the hackathon, and while attending the quarterly meeting is encouraged, it is not required. Participation in the Euro 16 LSO Hackathon is free of charge.

 

Cisco DevNet is a working closely with MEF and others to make this event a success.

cisco-devnet-logo.pngTo participate in the Euro16 LSO Hackathon as a networking expert, an operations expert or as a software developer, please register here (separate registration from the Quarterly Meeting) and we will get back to you with more information.

 

This is an excellent opportunity to access expertise to complement your own in the rapidly evolving areas of software defined networking, cloud computing, and the core work of the MEF in the LSO Reference Architecture.

Frequently asked questions and additional information can be found here.

You can catch a recap of what happened at the previous LSO hackathon, at GEN15 in Dallas, here.

Hope to see you in Rome!

hack-room.jpg

The Internet Engineering Task Force (IETF) is the home for the Internet. Over the years, the IETF has developed and refined and the core technologies required to run the Internet on which most of us rely for much of what we do every day. Today, the IETF works to make the Internet work better and more securely. Such work is useful for the Internet only if the IETF can “… produce high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet …” [RFC3935]. A resulting requirement of this is that the IETF be responsive in the face of changes in technology shifts and trends to corresponding user community. This need to explored in detail in a recently published paper titled IETF Trends and Observations, draft-arkko-ietf-trends-and-observations.

 

One particular trend noted in this paper is the importance of open source software. There is a growing recognition in the IETF of the value and need for active collaboration with open source communities, combining the respective strengths of open source and open standards in ways that creates value for the entire network engineering community.

 

One way the IETF is addressing this need is with IETF Hackathons. The first IETF Hackathon, proposed, sponsored and run by Cisco DevNet, cisco-devnet-logo.pngwas held as part of IETF 92 in Dallas in March 2015. Since then, each IETF meeting has included a hackathon. Next up is the IETF 95 Hackathon in Buenos Aires, April 2-3, 2016.

 

The IETF hackathon encourages developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards. Efforts are not limited to existing standards; in fact, work with emerging and evolving proposals are welcomed and encouraged. One goal is increased emphasis on running code in parallel with developer new standards, such that what is learned through early implementation efforts can be fed back into the standards development process. Another goal is providing a cultural experience in which contributors to open source and open standards come together, meet each other, and gain insights on each other’s work.

 

This hackathon, as with all previous ones, is organized by Cisco DevNet, with funding graciously provided by Huawei.

The current set of technologies and projects include:

 

  • DNS, DNSSEC, DANE, DTLS-ver-(D)TLS
  • Interactive Connectivity Establishment (ICE)
  • Network Based Metrics Analytics
  • NETCONF, YANG, I2RS, OpenDaylight
  • NETVC
  • Vector Packet Processing (VPP/FD.io)
  • TLS 1.3
  • SCTP

 

Additional technologies and projects are still being added and new proposals are welcome. See the participant wiki for all the latest updates. You can also check out who has signed up and for what.

Over 75 participants are already registered. The final number is expected to be close to 100.

Registration is required, but it is also free. Participants are welcomed and encouraged to register for the IETF 95 meeting that follows, but doing so is completely optional.

Feel free to comment here or contact me directly (Charles Eckel, eckelcu@cisco.com) with any questions. I hope to see you in Buenos Aires!

 

SAVE THE DATE: If you missed the hackathon in Buenos Aires, the next IETF Hackathon will be at IETF 96 in Berlin, July 16-17.

fosdem-banner.png

FOSDEM 2016, Jan 30-31, Brussels, Belgium

 

I experienced FOSDEM for the first time, and what an experience it was. I invite you to relive it with me.

 

Its 8:37am Saturday morning, light rain, walking from hotel to a bunch of bus stops in front of Brussels Central Station. Which one goes to the university hosting the conference? Probably the one with the guy wearing the Mozilla jacket and another with a LinuxWorld cap. Assumption confirmed as I approach to see a demo of Firefox OS running on another guys mobile. Bus arrives jam packed, we all cram in too, off we go. No commemorative photo, can’t reach phone in pocket. Bus stops km short of destination, roadwork prevents bus from going further, everyone piles off, raining harder now, follow crowd in general direction of university, I hope. Arrive at university, no registration area, no map, mobile app with map and list of sessions I plan to attend has crashed, raining harder, what have I gotten myself into -  a great weekend dedicated to open source software.

 

What is FOSDEM? It’s widely considered the premier open source conference in all of Europe. Its held every year at Université libre de Bruxelles in Belgium. FOSDEM is a free, non-commercial event, organized by the open source community for the open source community. The goal is to provide open source software developers and communities a place to meet to:

  • get in touch with other open source developers and projects
  • attend presentations on various topics by project leaders and committers
  • promote development and benefits of open source solutions

 

Developer rooms (devrooms)

 

Core to the FOSDEM experience is the concept of devrooms. Devrooms are a place for teams to discuss, hack and publicly present the latest directions, lightning talks, news and discussions. Devrooms often exist for open source projects, but they can also be created for specific topics or areas of interest. For example, this year witnessed the first ever SDN and NFV devroom (more on this later).

 

bar.png

The Bar

 

Equally central to the FOSDEM experience is the bar. This is a place where much of the real team building and direction setting happens.

How many times have you attended a talk with presenter and/or multiple members of the audience talking past each other in violent agreement?

The solution - take it to the bar.

How many times have you raced to a session only to find the room full and the door closed for capacity reasons?

The solution, take it to the bar.

How often have you been in Belgium for a conference and found you have precious little time for a representative sample of some of the worlds finest beer?

The solution, take it to the bar.

 

 

Because the conference is held at a university rather than a proper conference center, the venue is quite spread out. Its daunting for a first time attendee to find the building for a given session, not to mention navigating the maze of passageways once inside. Because the conference is free and community funded, there is no coffee in the morning, no food at lunch or breaks, and no sponsored social events. This combination makes the bar even more essential to conference attendees. The extensive selection and reasonable prices appeal to ever taste and budget.

 

stalman.pngPassion for Open Source

 

The love of open source was apparent everywhere you turned. This is what holds the conference together and helps it overcome all challenges. No where was this demonstrated better than in the “A discussion with Richard Stallman” session. It was standing room only. No punches were held as topics such as open source vs. free software, government and corporate use/misuse of open source, and can you really trust anyone or any foundation were debated. Yet when it came time for an auction to raise money for the Free Software Foundation, the bidding for a stuffed GNU fetched 342 Euro.

 

gnu.pngwww.gnu.org

 

Enormous Breadth and Depth of Content

 

FOSDEM welcomes everything open source. 5000+ developers, 600+ presentations, ten “main” tracks, and dozens of devrooms. There is something for everyone, and almost always too much too choose from. Like a kid in a candy store, I naively started out running from room to room trying to attend talks of particular interest,  only to be frustrated by getting lost, arriving late, and/or having the doors closed due to the session reaching max capacity. A strategy that worked much better for me and that I recommend to first time attendees is to pick one or two devrooms and focus on those, Stay in the same room, or at least the same general area, for an extended period of time. Not only will you have a better chance of catching the entire session, you will also build some continuity with the community and grasp the prevailing themes of those devrooms. For me, the most rewarding time spend was in the SDN and NFV devroom.

 

SDN and NFV Devroom

 

This was the first FOSDEM featuring an devroom dedicated to open source networking.  The SDN and NFV DevRoom covered two related fields:

  • Software Defined Networking (SDN), including virtual switching, dataplane performance, open source SDN controllers, and virtual routing
  • Network Functions Virtualization (NFV), covering open source NFV platforms, network functions and applications, and other related topics

Sessions ran all day Sunday and featured presentations on Data Plane Development Kit (DPDK), OpenVSwitch (OVS), OpenSwitch, distributed SDN, OpenDaylight (ODL), Service Function Chaining (SFC), container networking, and open source packet generators, IMS cores, and network management solutions.  A huge thanks to Dave Neary, Open Source Community Manager, RedHat, who spearheaded the creation and organization of the devroom. This devroom was the highlight of my FOSDEM experience, and several others I met in the devroom felt much the same way.

 

ODL SFC conclusions.png

One of the most valuable takeaways was the mutual expansion of our human networks as a direct result of meeting new colleagues within corporate, university, and open source communities. It was great to hear about the foothold open source had established for network functions and services such as SIP VoIP servers and IMS deployments. The session titled Experiences with OpenDaylight and Service Function Chaining (SFC) shared valuable insights gained as a result of deploying OpenDaylight with SFC (see "Conclusions" slide).

 

So yes, despite my initial challenges as a first time FOSDEM attendee, this was indeed a great weekend dedicated to open source software. I have marked my calendar for next year – not just to include myself within the community, but also to contribute to the valuable content and insightful presentations in the SDN and NFV devroom in 2017.

brussels-night.png

imtc-connect.pngHappy New Year everyone! I wish you all the best in 2016.

We closed out 2015 on a high note with a successful IMTC Connect, Dec 16-17. The agenda was packed with great sessions, there were many accomplished speakers, and the content and corresponding discussions throughout the event were insightful and thought provoking.

 

The organizers will make all the presentations and recordings available soon. In the meantime, you can access my presentations here:

 

 

The SIP session featured the announcement of the new name, and more importantly, the new charter for what we have all come to know and love as the SIP Parity Activity Group. Going forward, the group is known as the SIP Interconnect Activity Group.

 

Charter

 

The IMTC SIP Interconnect Activity Group provides a forum for IMTC member companies to cooperate and pool resources on issues and extensions to SIP based enterprise communication applications. With its best practices documents providing a shared foundation, the group identifies and tackles challenges and opportunities with interoperability, operation, and integration of SIP based applications with emerging communication and networking technologies.

 

What We Do

 

The main activities of the group are to:

  1. Organize interoperability test efforts (both virtual and face-to-face). These are done in cooperation and coordination with the WebRTC, MANE, SSV, and UC SDN activity groups and with SIP Forum/SIPit
  2. Provide a forum for members to agree on an overall SIP profile for communication applications, particularly where it involves interconnecting with other application and network technologies (e.g. WebRTC, SDN, IPv6)
  3. Educate members on recent developments in SIP standards and market evolution

 

You can find additional info, including how to join the group and subscribe to our email list, at at SIP Interconnect AG. We welcome your expertise and input as we update and publish our best practice documents and make our plans for SuperOp! 2016.

 

Cheers,

Charles Eckel, IMTC SIP Interconnect Activity Group Chair

You’ve seen previous posts here about open source and open standards. Now its time to add open APIs to the mix. More specifically, openVuln, an API for immediate and programmatic access to critical security vulnerability information in a number of standard formats.

 

Screen Shot 2015-12-17 at 4.47.46 PM.png

 

The Cisco Product Security Incident Response Team (PSIRT) recently released the openVuln API, a RESTful API that supports industry wide security standards such as the Common Vulnerability Reporting Framework (CVRF), Open Vulnerability and Assessment Language (OVAL), Common Vulnerability and Exposure (CVE) identifiers, and the Common Vulnerability Scoring System (CVSS). The openVuln API make it possible to build automated tools to deal with security vulnerability more quickly and effectively.

 

Automation is a hot topic in general these days, and security is no exception. Most organizations have many systems to patch and configure securely, with numerous versions of software and features enabled. Security administrators are seeking ways to leverage standards and available tools to reduce the complexity and time necessary to respond to security advisories, assess their devices, and ensure compliance so they can allocate resources to focus on other areas of their network and security infrastructure. The openVuln API addresses these needs. It allows Cisco customers and partners to leverage OVAL definitions and CVRF data to set up rules for the automated assessment of their own networks. It further simplifies the evaluation process and reduces the time between when a vulnerability is announced and the fix is actually implemented. That means less risk for them and their own customers tied to open vulnerabilities.

 

The openVuln API can be accessed via Cisco’s API Console. The console provides a simplified, guided experience through which partners and customers can obtain oAuth2 credentials and register a client application that accesses the Cisco PSIRT openVuln API. You can also access it using curl.

 

You can find technical details and information about the openVuln API at the new Cisco PSIRT DevNet site. We also encourage you to collaborate with others through the corresponding DevNet developer community, where users can get additional technical content, collaborate with peers, exchange sample code, and ask questions.

eckelcu

LSO Hackathon debut at GEN15

Posted by eckelcu Dec 1, 2015

sign.jpgThe first ever LSO hackathon was held November 17-19 in conjunction with the GEN15 conference, hosted by the Metro Ethernet Forum (MEF), in Dallas, TX. GEN15 is the MEF’s marquis event for the year, drawing networking professions together to enable the future of agile and orchestrated carrier grade services powered by LSO (Lifecycle Service Orchestration), SDN, and NFV.  With the support of Cisco DevNet, the MEF added a critical element this year, a hackathon aimed at accelerating the development of LSO architecture, its corresponding APIs, and adding support for those APIs into key open source projects that provide the foundation of the architecture.

 

The hackathon drew a diverse group of developers and subject matter experts from various open source communities and SDOs. Over 50 participants from more than 20 different companies gathered to collaborate on the combination of open source and open standards. Participating companies included AT&T, Amartus, Cable Television Labs, CenturyLink, Ciena Corporation, Cisco Systems, Comcast, ECI Telecom, Ericsson AB, Fujitsu Network Communications, Iometrix, Level 3 Communications, MEF, Microsemi, Oracle, PLDT Corp. Business Solutions, TM Forum, Tech 2000, Telecom Italia S.p.a.,, Time Warner Cable, and Verizon Business. In addition to many long time MEF contributors, we had active contributors from OpenDaylight, OPNFV, OpenStack, and IETF.

 

room.jpg

 

The event started with a workshop Monday afternoon to introduce participants to the LSO architecture and the aspects of it that served as the focus of the hackathon. That was followed by a series of brief technical presentations by experts of on each of the proposed projects. Participants were also introduced to the LSO hackathon network, consisting of a set of VMs to host applications and connected to CE 2.0 network gear to facilitate running real traffic through the setup.

 

diagram.png

 

Now sufficiently acquainted with the technologies and proposed projects, participants broke up in the teams that best matched their skillset and interests. The room was a bit crammed but this had its benefits as participants quickly found homes in one or more projects. Most teams included people from multiple companies and a combination of open source developers and authors of related standards and APIs. To capitalize on the networking and relationship building opportunity, all hackathon participants were then invited and encouraged to step away from the laptops, servers, and routers and join the rest of the GEN 15 conference attendees in the Networking Hall for the Welcome Reception.

 

The hackathon officially restarted at 9am the next morning. Many eager hackers were there well before that to dive into their new endeavors with their new friends. By design, the atmosphere was more collaborative and cooperative than competitive. Teamwork and the opportunity to move the industry forward were motivation enough, not to mention a constant flow of great food and caffeine in all the favorite forms.

 

redbull.png

 

Cisco DevNet addressed clothing needs with commemorative t-shirts. Equally critical were developer VMs on USB drives that enabled participants to quickly instantiate a development environment tailored to their project quickly on their own laptop.

 

tshirts.JPG

usb.png

 

Teams worked well into the evening. Around 7pm, many accepted to the call of a cocktail reception, proceeding to hash out the more delicate debates within their teams over a beer or two. Some preferred to code away until the doors officially closed around 9pm.

We started bright and early again on Wednesday. The previously agreed upon and ever looming deadline of 3:30pm inspired many to the hackathon room before even the coffee had arrived. Distracted only briefly by another decadent lunch buffet, teams worked efficiently, demonstrating time management skills second only to their coding abilities. The justification for the 3:30pm deadline was to ensure teams took adequate time to prepare a brief summary presentation of what they had achieved of the course of the past 2 days. These presentations were given to the hackathon participants and an ad-hoc group of onlookers who were curious to see firsthand why there was so much talk and excitement in the GEN 15 meeting about this first even hackathon. A brief summary of the projects is a follows:

 

  • UNI Manager OpenDaylight Plugin
  • LSO for NRP API implementation
  • End user GUI for NRP API implementation
  • GUI, orchestrator and NRP API implementation using Node.js & Spring Boot microservices
  • NRP API implementation using OpenDaylight
  • CE 2.0 Testing for LSO implementations
    • Note, NRP API was previously known as SCA API

 

In addition to the obvious learning through sharing, the presentations guaranteed that the great work everyone did and the lessons learned along the way benefit the larger community and extend well beyond the limited timeframe of the hackathon itself. Additional information on the hackathon and projects is available now through the hackathon wiki. A more permanent more is being created, and some of the code is already being prepared as upstream contributions into OpenDaylight and OPNFV, both as bug fixes and as contributions to the OpenDaylight UNI Manager project and the  OPNFV Connectivity Services LSO (LSOAPI) project.

 

Rome was not built in a day, nor was the entire LSO architecture implemented at the hackathon. It did jumpstart this endeavor. Not only that, it was instantly viewed as successful enough to warrant a complete series of LSO hackathons, the next one being held in conjunction with the MEF Q2 2016 meeting April 25-28 in – you guessed it, none other than Rome, Italy.rome.png


You can be sure myself and Cisco DevNet are already on board. Mark your calendars – we look forward to seeing you there!

If hackathons to advance the pace and relevance of open standards through open source is up your alley, check out this post about IETF hackathons.

yokohama.pngScreen Shot 2015-10-30 at 11.52.33 AM.png

 

Yokohama, Japan was the host city for IETF 94. The IETF hackathon, sponsored by Cisco DevNet, got things started the weekend before, October 31 – November 1. The hackathon was the 3rd in a continuing series to advance the pace and relevance of IETF standards activities by bringing the speed and collaborative spirit of open source software into the IETF.

young.png

More than 70 developers came together to test experimental protocols, produce reference implementations, create useful utilities, etc.  Many participants were long time IETF contributors, but there were several first time attendees and young developers with new ideas, including our youngest coder who was 16 years old.

 

More than 70 participants formed into roughly a dozen teams working across a wide range of technologies. These included many IETF working groups (e.g. dane, dhc, dnsop, dprive, homenet, i2rs, iptube, netconf, netvc, sfc) and corresponding open source projects (e.g. Dalla, getdns, Kea, OpenDaylight, OPNFV, RIOT, Thor). Each team produced significant results, including the DNS privacy and security team, which extended and demonstrated use of getdns APIs to eliminate metadata leakage, and the Homenet team, which prototyped and demonstrated provider aware selection of IPv6 prefixes from home routers, PCs, and mobile devices.

dns.pnghomenet-ipv6.png

 

How does an IETF Hackathon work?

The hackathon started Saturday at 09:00. Technology “champions” introduced each technology and proposed projects. Next, champions and participants formed teams and started hacking. Several teams included members from more than one IETF working group and/or open source community. The ensuing collaboration, mixing of cultures and ideas, and new friendships all point to the long term benefits that extends beyond the hackathon itself.

gitbub-bridge-gaps.png lunch.png

 

plugs.pngteamwork2.png


Motivated, caffeinated, and energized, participants worked tirelessly, advancing the standards that provide the internet’s foundation and creating open source implementations that validate these standards and makes them easier for others to consume. Not everything worked according to design and there were frustrating moments, but course correction and eventual success ruled the day.

 

bottles.png

not-working-yet.png

pleasant-surprise.png

huy-smile.png

 

 

 

 

 


















Sunday afternoon, each team shared accomplishments and lessons learned with peers and a panel of esteemed judges - Jari Arkko (IETF Chair), Ray Pelletier (IETF Administrative Director), and Adam Roach (NETVC chair). The judges recognized teams based on various criteria established for the hackathon:

 

criteria.png

In case you are tired of squinting, the slide reads:

  • Advance pace and relevance of IETF standards
    • Bring speed and collaborative spirit of open source software into the IETF
    • Flush out ideas, feed into WG session
    • Produce sample code/reference implementations
    • Create useful utilities
  • Attract developers, young people to IETF
    • There’s cool sh*t at IETF

 

There were techie prizes compliments of Cisco DevNet and tickets to the IETF social event donated by WIDE, but the real winners were the IETF community. The efforts of the hackers where shared in corresponding working group meetings the following week, and a number of teams demonstrated their work and fielded Q&A at Bits ’N Bites Thursday night.

 

bits-n-bites.png

 

The complete set of technologies and projects are available via the event Wiki. From the main hackathon page, its easy to navigate to this Wiki and those from previous hackathons as well. The IETF and open source communities are encouraged to bookmark and reference these sites to help with their ongoing work.

 


What comes next?

For the first time ever, the IETF goes to South America. IETF 95 is in Buenos Aires, with the Hackathon kicking things off the weekend before, April 2-3. So mark your calendar, plan to arrive early, and join us as we accelerate the pace and relevance of the IETF’s tireless work extending and improving the internet we all know, love, and use ever day.

 

buenos aires.png

 

Stay informed

The keep up to date with all things related to past and future hackathons, subscribe to hackathon@ietf.org.

OpenDaylight is getting the ability to subscribe to changes within switches and routers.   We need this because continuous, periodic polling of data is not adequate for applications requiring frequent/prompt updates of remote object state.  Having such a capability will address problems including:

  • unnecessary processing load on networks, controllers, routers, and applications, and 
  • overly high propagation latency where controllers cannot see key network changes quickly enough. 


The YANG PUBSUB project in OpenDaylight Beryllium addresses these problems by allowing applications to setup customized subscriptions on specific subtrees of YANG datastores in the network. With change-triggered subscriptions, any changes in interesting YANG objects will be pushed to OpenDaylight without any need to explicitly poll the data. Effectively, we are enabling a telemetry solution with customized YANG object delivery by subscriber.


More on the capability can be understood from the IETF NETCONF technology specification draft-ietf-netconf-yang-push, or the I2RS requirements draft-ietf-i2rs-pub-sub-requirements.

sub.jpg

hackathon

The Internet Engineering Task Force (IETF) is holding Hackathon to encourage developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards.

Sponsored by:
Cisco DevNet

When: Saturday October 31 and Sunday November 1 
Where: Pacifico Yokohama, Room TBD                                                          
Signup for the Hackathon here: https://www.ietf.org/registration/ietf94/hackathonregistration.py
View the list of Hackathon Attendees: Here

Keep up to date by subscribing to https://www.ietf.org/mailman/listinfo/hackathon

The Hackathon is free to attend.

 

The lineup of technologies and projects includes ICE, NETCONF/YANG, IR2S, OpenDaylight, NETVC, IBNEMO, Homenet, and RIOT. See the current list with additional details on the wiki.

 

There is still time to register, and additional champions and project proposals are welcome as well. But time is running out. So register now and plan on joining us for a weekend of open source and open standards in Yokohama.

eckelcu

OpenDaylight Summit Recap

Posted by eckelcu Aug 10, 2015

The OpenDaylight Summit 2015, Santa Clara, July 27-31, was my first OpenDaylight summit. It was a great experience. I was particularly impressed with the cooperation and collaboration among the various stakeholders and vendors at the event. Rather than marketing their own solutions, presenters focused on technical content and how they are partnering with other companies and communities to deliver new functionality on top of OpenDaylight or add a new component to OpenDaylight. Here are some  sessions I attended that had particularly good content for developers:

 


Giles and I received positive feedback on the talks we provided as well (see previous blogpost).

You can find additional presentations here:

Slides | OpenDaylight Summit 2015 | Linux Conferences and Linux Events | The Linux Foundation


Please share/comment regarding your overall impression of the conference and any sessions you found particularly good.

Filter Blog

By date:
By tag: