1 / 12

WEBI Working Group

The WEBI Working Group, co-chaired by Mark Nottingham and Ian Cooper, recently convened during IETF 50 in Minneapolis. The agenda included a recap of WEBI's status, discussions on requirements categories (MUSTs, SHOULDs, MAYs), and an exploration of use cases concerning RUP and IDD mechanisms. Key topics covered the boundaries of CDI/OPES, invalidation vs. update strategies, and practical do's and don'ts shared by Dan Li from Cisco Systems. The group aims to align efforts around these requirements for improved intermediary-enabling protocols and services in the internet ecosystem.

lada
Télécharger la présentation

WEBI Working Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WEBI Working Group IETF 50, Minneapolis Co-Chairs: Mark Nottingham Ian Cooper mnot@akamai.com icooper@equinix.com

  2. Agenda • Agenda bashing [5 min or more] • WEBI Group Status • Recap of other groups (what WEBI is not) [10 min] • WCIP; “do’s and don’ts”, Dan Li [20 min] • RUP requirements (MUSTs, SHOULDs, MAYs) [30 min] • Use cases • Scope (invalidation vs. update) • Initial protocol support? • IDD requirements (MUSTs, SHOULDs, MAYs) [20 min] • Use cases • Scoping and issues (CDI/OPES boundaries) • Wrap-up [10 min]

  3. Agenda Bashing • Any Other Business?

  4. WEBI Status • San Diego – got consensus, discussed areas of interest • Requirements Drafts – rough requirements, gathering use cases • Minneapolis – evaluate efforts based on requirements and use cases, determine support, next steps.

  5. Recap of Web-Related Groups • OPES: introduce a processing model into intermediaries • CDI: inter-CDN communication model • WEBI: general intermediary-enabling mechanisms. Provides services for other groups as well.

  6. WCIP: Do’s and Don’ts Dan Li, Cisco Systems

  7. RUP Requirements: Use Cases • Internet Proxy • Internet Surrogate (CDN) • Intra-CDN • Inter-CDN • Origin  CDN • CDN  Proxy • Intranet Proxy / Surrogate • Non-intermediary uses

  8. RUP Requirements: Use Cases (payloads) • Invalidations • Updates / Deltas / “hints” • Configuration / resource handling (metadata)

  9. RUP Requirements: Discussion • Open Discussion of the Draft • Next Steps?

  10. IDD Requirements: Use Cases • User-Agent configuration • Mesh-building • Surrogate shortcut

  11. IDD Requirements: Discussion • Open Discussion of the Draft • IDD Models • IDD Implementers

  12. Wrap-Up • RUP • IDD

More Related