ONAP and the Internet Engineering Task Force Tony Hansen, AT&T ONAP Faace to Face December 11-12, 2017

What is the IETF? All about Open Internet Standards Open community TCP, IP, DNS, Email, HTTP, SIP, those kinds of protocols and APIs dealing with them YANG models Open community Anyone can participate No “membership” – if you are on the mailing list, you are a member Organized into ~100 Working Groups per topic Working groups are grouped into 7 Areas Applications and Real-Time, General, Internet, Operations and Management, Routing, Security, Transport Two governing boards: Internet Architecture Board Internet Engineering Steering Group

The IETF “Motto” Rough Consensus and running code

Interoperability between implementations through consensus vs SDO vs OSS tug of war Interoperability between implementations through consensus vs The code is the standard

We depend on many of the IETF protocols Bottom Line We depend on many of the IETF protocols

Working With the IETF ? The IETF is actively seeking opportunities to work with Open Source projects Hackathons at IETF meetings encourage fleshing out protocols and working through protocol kinks while getting IESG had been actively talking with Linux Foundation Talk at last IETF about Open Source and the IETF David Ward, Cisco Among many examples of OSS projects, repeatedly happens to highlight ONAP as an example of an Open Reference Platform

from 3 Years On: Open Standards, Open Source, Open Loop David Ward, Cisco

Questions Are there things that we’re creating that we should ask IETF to standardize to increase interoperability with other systems? Are there emerging protocols in the IETF that we need to be aware of, using and helping to standardize? ACME – automated certificate management (service available within K8S) IOAM – in-situ Operations, Administration, and Maintenance packets What could IETF use from ONAP to easily spin up something it is working on in one of its WGs? Make use of IETF Hackathon to push forward some IETF protocol on an ONAP framework?

Q&A Background Slides: Working Groups of Interest to ONAP

Working Groups of Interest to ONAP Applications & Real Time Protocols sipcore: Session Initiation Protocol Core stir: Secure Telephone Identity Revisited modern: Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers Internet Area Protocols sunset4: Sunsetting IPv4 tictoc: Timing over IP Connection and Transfer of Clock

Working Groups of Interest to ONAP Operations and Management netconf: network configuration netmod: network modeling v6ops: v6 operations Transport Protocols: ippm: IP Performance Measurement quic: QUIC: A UDP-Based Multiplexed and Secure Transport tcpinc: TCP Increase Security aqm: Active Queue Management and Packet Scheduling Routing PCE path computation element (functionality of SDN controller)

Working Groups of Interest to ONAP Security Protocols: ace: Authentication and Authorization for Constrained Environments acme: Automated Certificate Management Environment oauth: Web Authorization Protocol curdle: CURves, Deprecating and a Little more Encryption sacm: Security Automation and COntinuous Monitoring tls: Transport Layer Security

More Information Start at www.ietf.org Or beta.ietf.org (same information, designed more for those not in the IETF) Click on “WG Charters” If there is a working group you find interesting: Click on “Info for Newcomers” Join the mailing list for that working group Become active on the mailing list Three face-to-face week-long meetings per year, around the world