Exploring Transition-Based Services at the 49th IETF BOF in San Diego
The 49th IETF BOF, chaired by Michael Condry and Hilarie Orman, convened to discuss advancements in web caching and the introduction of transit-based services for intermediaries. Key discussions included application-specific services and the evolution of the client/server model. The workshop, held on September 13, 2000, aimed to establish a charter, understand draft relationships, and solicit design team members. The agenda featured presentations on use cases, ICAP progress, and document roadmaps, culminating in a collaborative effort to shape the future of proxy services.
Exploring Transition-Based Services at the 49th IETF BOF in San Diego
E N D
Presentation Transcript
Open Extensible Proxy Services BOF Session 49th IETF, San Diego Chairs: Michael Condry, Hilarie Orman
What’s This About? • On beyond web caching • Transit-based services for intemediaries • Application-specific services • Expansion of client/server model • draft-tomlinson-epsfw-00.txt, July 2000 • Workshop held September 13, 2000 • Website www.extproxy.org • Mailing list ietf-openproxy@vpnc.org
Goals of this BOF Meeting • Rough consensus on the charter • Understand relationship to CDNP, WREC/WEBI, C15N • Ignore relationship to RSPOOL, etc. • Explain current directions of drafts • Solicit design team members • Seek consensus on moving to WG status
Agenda • Introduction: Hilarie Orman 5 min • Charter Bashing: Michael Condry and Hilarie Orman 10 min • Use Cases: Marcus Hofmann 10 min • Rule Systems: Marcus Hofmann 5 mins • ICAP Progress: Don Gillies and Mark Nottingham 10 min • Relationship to CDN Peering: Mark Day 5 min • Workshop Summary: Michael Condry 5 min • Document Roadmap: Hilarie Orman 7 min • If time allows: • Discussion of other documents • Assignments and Administrivia
Charter • Standards for services at authorized intermediaries “in the network” • Protocols and API’s that facilitate efficiency delivery of complex content to users based on publisher/distributor instructions • Liason points: cache directives w/WREC, routing to surrogages w/CDNP, object name resolution w/C15N, policy rules w/PG
Document RoadmapRFCs • Requirements • Architecture. Editor: Condry • Security Policy • Configuration • Policy/filter rule language, API • Proxy RPC (ICAP) • Dynamic service instantiation language
DocumentsInformational? • Language specific service definition API • Java, Perl, XML • Service context API’s • Authentication services, paid content insertion, streaming media … • Protocol specific proxy API’s • RTP, secure MCAST • Application-specific name resolution