ATIS Open Web Alliance

1. ATIS Open Web Alliance • Jim McEachern • Senior Technology Consultant • ATIS • 10 July 2014

2. Agenda • Welcome & Call to Order • Introductions • Readout from Ad-Hoc F2F Meeting in Boston • Whitepaper • IETF update • Future meetings

3. ATIS Intellectual Property Rights (IPR) & Antitrust Policies ATIS Procedure Notice: ATIS Forum and Committee activities must adhere to the ATIS Operating Procedures (including basic principles such as fairness, due process, respect for minority opinions, and common sense). IPR Notice: In connection with the development of an American National Standard, or other deliverable that requires use of patented inventions, the use of patented inventions shall be governed by the ANSI Patent Policy as adopted by ATIS and as set forth in Section 10 of the "Operating Procedures for ATIS Forums and Committees." Under this policy: • Disclosure of relevant patented inventions at the earliest possible time in the development process is encouraged. An opportunity will be provided for the members to identify or disclose patents that any member believes may be essential for the use of a standard under development. • Neither the Committee, nor its leaders, can ensure the accuracy or completeness of any disclosure, investigate the validity or existence of a patent, or determine whether a patent is essential to the use of an ATIS deliverable. • ATIS prohibits any discussion of licensing terms in its Forums and Committees. Antitrust Risk Notice: The leaders further remind attendees that participation in industry fora involves the potential for antitrust concerns or risks. To avoid such concerns and risks, participants should carefully observe the "Operating Procedures for ATIS Forums and Committees". In addition, sensitive discussion topics such as price, territories, specific contractual terms, etc., should be avoided. Questions: Participants having questions, comments, or concerns regarding any of these topics should consult with their company's legal counsel, the Committee leadership, ATIS staff, or ATIS legal counsel.

4. Readout from Ad-Hoc F2F

5. High Level Workplan • Review proxy use cases (https://github.com/http2/http2-spec/wiki/Proxy-User-Stories) • Provide additional use cases if required • Analyze use cases • Assess common themes • Identify requirements • Proxy, server, and client • Review existing work • Trusted proxy • Publish requirements • IETF • Assess next steps

6. Use Case Analysis • All use cases are from: https://github.com/http2/http2-spec/wiki/Proxy-User-Stories • Use case analysis spreadsheet: https://docs.google.com/spreadsheets/d/1xlELKJO7b-C8Wl39l2KjyN7XVEqKKzY87bIQVV3zcHM/edit?pli=1#gid=0

7. Use Case Analysis • Problem statement: • End user needs • Admin needs • Device owner • Current solution for use case • Alternative approaches for use case • Does the location matter? • Capabilities required of a proxy based solution • Essence of use case => “Category” • Priority

8. Use Case “Categories” • Distill user stories down to a small number of use cases • Ensure it includes key points from input user stories • Focus on cases where trusted proxy adds value • Tentative use case categories: • Security • Information • Optimization • Compliance • Value added network services • Sponsored data

9. Network Functions • Many use cases depend on an understanding of network functions that are provided today. • Not generally understood by broader community • Proposal to write a white paper to address this. • Detailed discussion of network based services and network management functionality, in particular for mobile networks. The original OWA white paper highlighted some of the network functions that were impacted by SPDY and SPDY proxies, but it did not go into detail about these functions. This white paper will provide more detail about these network services and network management functions, and will also explain why many of them (especially network management and content optimization) can only be done effectively if they are located within the network, ideally near the access link.

10. Privacy • Several use cases identified a desire for the end user to be informed when data is accessed. • In reality today, in many cases, there is no disclosure of what is being done with data.

11. Browser Fragmentation? • Several use cases could be addressed by “special purpose browsers” to optimize performance. • Satellite • Mobile • Enterprise • Potential risk if requirements are not addressed.

12. IETF

13. HTTPbis Interim Meeting • Interim meeting June 5 • Focus on resolving open issues for HTTP/2 • Minutes are available at https://github.com/httpwg/wg-materials/blob/master/interim-14-06/minutes.md

14. IETF • IETF is meeting July 20 – 25 • Ad-hoc meetings for OWA participants. • Sunday evening • Debrief after HTTPbis sessions • Details tbd • Proposing to cancel OWA meeting currently scheduled for July 24th due to conflict with IETF.

15. Next Steps

16. Next steps • Confirm use case categories. • Comments on analysis welcome • Develop new (combined) use cases. • White paper outline. • Continue to socialize OWA objectives at IETF.

17. OWA Meeting Schedule • Proposed meeting schedule (through the summer): • Thursday July 24th, 11:00 – 1:00 EDT • Thursday Aug 7th, 11:00 – 1:00 EDT • Thursday Aug 21st, 11:00 – 1:00 EDT • Thursday Sept 4th, 11:00 – 1:00 EDT • Note: meeting invites are not automatically imported into your calendar.