Difference between revisions of "OPES/ONES"

Revision as of 23:59, 13 April 2015

RFC 3238 - IAB Architectural and Policy Considerations for Open Pluggable Edge Services
RFC 3705
RFC 3752 - Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios
RFC 3835 - An Architecture for Open Pluggable Edge Services (OPES)
RFC 3836 - Requirements for Open Pluggable Edge Services (OPES) Callout Protocols
RFC 3837 - Security Threats and Risks for Open Pluggable Edge Services (OPES)
RFC 3838 - Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)
RFC 3897 - Open Pluggable Edge Services (OPES) Entities and End Points Communication
RFC 3914 - Open Pluggable Edge Services (OPES) Treatment of IAB Considerations
RFC 4037 - Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
RFC 4236 - HTTP Adaptation with Open Pluggable Edge Services (OPES)
draft-ietf-opes-rules-p-02 P: Message Processing Language

Open Pluggable Edge Services - An Architecture for Networked Content Services] Markus Hofmann (Bell Labs/Alcatel-Lucent) Leland R. Beaumont (Simply Quality)

Revision as of 23:59, 13 April 2015 (view source) Sysop (Talk \| contribs) ← Older edit		Revision as of 23:59, 13 April 2015 (view source) Sysop (Talk \| contribs) (→‎RFCs) Newer edit →
Line 1:		Line 1:

	== RFCs ==		== RFCs ==
		+

	* RFC 3238 - IAB Architectural and Policy Considerations for Open Pluggable Edge Services		* RFC 3238 - IAB Architectural and Policy Considerations for Open Pluggable Edge Services