Difference between revisions of "OPES/ONES"

Revision as of 15:38, 14 April 2015

Nos politiques ne savent pas de ce quoi ils parlent. Voici les "boites noires" de la malloi.

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)
RFC 4902 - Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP
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)

@@ Line 15: / Line 15: @@
 * RFC 4037 - Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
 * RFC 4236 - HTTP Adaptation with Open Pluggable Edge Services (OPES)
+* RFC 4902 - Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP
 * [http://tools.ietf.org/html/draft-ietf-opes-rules-p-02 draft-ietf-opes-rules-p-02] P: Message Processing Language