Browse Prior Art Database

Open Pluggable Edge Services (OPES) Treatment of IAB Considerations (RFC3914)

IP.com Disclosure Number: IPCOM000031689D
Original Publication Date: 2004-Oct-01
Included in the Prior Art Database: 2004-Oct-05
Document File: 17 page(s) / 37K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Barbir: AUTHOR [+2]

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

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' ...