Difference between revisions of "OPES/ONES"
From IUWG
| Line 1: | Line 1: | ||
| − | * RFC 3238 | + | == RFCs == |
| − | + | ||
| + | * RFC 3238 - IAB Architectural and Policy Considerations for Open Pluggable Edge Services | ||
* RFC 3705 | * RFC 3705 | ||
| − | * RFC 3835 | + | * RFC 3752 - Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios |
| − | * RFC 3914 | + | * RFC 3835 - An Architecture for Open Pluggable Edge Services (OPES) |
| − | * RFC 4037 | + | * 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) | ||
| + | * [http://tools.ietf.org/html/draft-ietf-opes-rules-p-02 draft-ietf-opes-rules-p-02] P: Message Processing Language | ||
| + | |||
| + | == Links and Documents == | ||
* [http://www.planethofmann.com/markus/publications/papers/ieee-internet-computing.pdf Open Pluggable Edge Services - An Architecture for Networked Content Services]] Markus Hofmann (Bell Labs/Alcatel-Lucent) Leland R. Beaumont (Simply Quality) | * [http://www.planethofmann.com/markus/publications/papers/ieee-internet-computing.pdf Open Pluggable Edge Services - An Architecture for Networked Content Services]] Markus Hofmann (Bell Labs/Alcatel-Lucent) Leland R. Beaumont (Simply Quality) | ||
| Line 12: | Line 22: | ||
* (fr) [http://fr.wikipedia.org/wiki/Internet_Content_Adaptation_Protocol ICAP Protocol] | * (fr) [http://fr.wikipedia.org/wiki/Internet_Content_Adaptation_Protocol ICAP Protocol] | ||
* (en) [http://en.wikipedia.org/wiki/Internet_Content_Adaptation_Protocol ICAP Protocol] | * (en) [http://en.wikipedia.org/wiki/Internet_Content_Adaptation_Protocol ICAP Protocol] | ||
| + | |||
| + | == IUDOCs == | ||
Revision as of 23:59, 13 April 2015
RFCs
- 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
Links and Documents
- Open Pluggable Edge Services - An Architecture for Networked Content Services] Markus Hofmann (Bell Labs/Alcatel-Lucent) Leland R. Beaumont (Simply Quality)
- OPES: ISOC Briefing
- (fr) ICAP Protocol
- (en) ICAP Protocol
