Open Pluggable Edge Services (OPES) Treatment of IAB Considerations
RFC 3914
Document | Type |
RFC - Informational
(October 2004; No errata)
Was draft-ietf-opes-iab (opes WG)
|
|
---|---|---|---|
Authors | Alex Rousskov , Abbie Barbir | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3914 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ted Hardie | ||
Send notices to | (None) |
Network Working Group A. Barbir Request for Comments: 3914 Nortel Networks Category: Informational A. Rousskov The Measurement Factory October 2004 Open Pluggable Edge Services (OPES) Treatment of IAB Considerations Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2004). Abstract IETF Internet Architecture Board (IAB) expressed nine architecture- level considerations for the Open Pluggable Edge Services (OPES) framework. This document describes how OPES addresses those considerations. Babir & Rousskov Informational [Page 1] RFC 3914 OPES Treatment of IAB Considerations October 2004 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Consideration (2.1) 'One-party consent' . . . . . . . . . . . 3 4. Consideration (2.2) 'IP-layer communications' . . . . . . . . 4 5. Notification Considerations . . . . . . . . . . . . . . . . . 5 5.1. Notification versus trace. . . . . . . . . . . . . . . . 6 5.2. An example of an OPES trace for HTTP . . . . . . . . . . 8 5.3. Consideration (3.1) 'Notification' . . . . . . . . . . . 9 5.4. Consideration (3.2) 'Notification' . . . . . . . . . . . 10 6. Consideration (3.3) 'Non-blocking' . . . . . . . . . . . . . . 10 7. Consideration (4.1) 'URI resolution' . . . . . . . . . . . . . 11 8. Consideration (4.2) 'Reference validity' . . . . . . . . . . . 11 9. Consideration (4.3) 'Addressing extensions' . . . . . . . . . 12 10. Consideration (5.1) 'Privacy' . . . . . . . . . . . . . . . . 12 11. Consideration 'Encryption' . . . . . . . . . . . . . . . . . . 12 12. Security Considerations . . . . . . . . . . . . . . . . . . . 13 13. Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 14.1. Normative References . . . . . . . . . . . . . . . . . . 14 14.2. Informative References . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 16 1. Introduction The Open Pluggable Edge Services (OPES) architecture [RFC3835], enables cooperative application services (OPES services) between a data provider, a data consumer, and zero or more OPES processors. The application services under consideration analyze and possibly transform application-level messages exchanged between the data provider and the data consumer. In the process of chartering OPES, the IAB made recommendations on issues that OPES solutions should be required to address. These recommendations were formulated in the form of a specific IAB considerations document [RFC3238]. In that document, IAB emphasized that its considerations did not recommend specific solutions and did not mandate specific functional requirements. Addressing an IAB consideration may involve showing appropriate protocol mechanisms or demonstrating that the issue does not apply. Addressing a consideration does not necessarily mean supporting technology implied by the consideration wording. Babir & Rousskov Informational [Page 2] RFC 3914 OPES Treatment of IAB Considerations October 2004 The primary goal of this document is to show that all formal IAB recommendations are addressed by OPES, to the extent that those considerations can be addressed by an IETF working group. The limitations of OPES working group to address certain aspects of IAB considerations are also explicitly documented. IAB considerations document [RFC3238] contains many informal recommendations. For example, while the IAB informally requires OPES architecture to "protect end-to-end data integrity by supporting end-host detection and response to inappropriate behavior by OPES intermediaries", the IAB has chosen to formalize these requirements via a set of more specific recommendations, such as Notification considerations addressed in Section 5.3 and Section 5.4 below. OPES framework addresses informal IAB recommendations by addressing corresponding formal considerations. There are nine formal IAB considerations [RFC3238] that OPES has to address. In the core of this document are the corresponding nineShow full document text