Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Open Pluggable Edge Services (OPES) Entities and End Points Communication (RFC3897)

IP.com Disclosure Number: IPCOM000031385D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2004-Sep-23
Document File: 15 page(s) / 34K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Barbir: AUTHOR

Abstract

This memo documents tracing and non-blocking (bypass) requirements for Open Pluggable Edge Services (OPES).

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: 3897                               Nortel Networks

Category: Informational                                   September 2004

             Open Pluggable Edge Services (OPES) Entities

                      and End Points Communication

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

   This memo documents tracing and non-blocking (bypass) requirements

   for Open Pluggable Edge Services (OPES).

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2

       1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . .  2

   2.  OPES System  . . . . . . . . . . . . . . . . . . . . . . . . .  2

   3.  Tracing Requirements . . . . . . . . . . . . . . . . . . . . .  3

       3.1.  Traceable entities . . . . . . . . . . . . . . . . . . .  3

       3.2.  System requirements  . . . . . . . . . . . . . . . . . .  5

       3.3.  Processor requirements . . . . . . . . . . . . . . . . .  5

       3.4.  Callout server requirements  . . . . . . . . . . . . . .  5

   4.  Bypass (Non-blocking feature) Requirements . . . . . . . . . .  6

       4.1.  Bypassable entities  . . . . . . . . . . . . . . . . . .  7

       4.2.  System requirements  . . . . . . . . . . . . . . . . . .  8

       4.3.  Processor requirements . . . . . . . . . . . . . . . . .  8

       4.4.  Callout server requirements  . . . . . . . . . . . . . .  9

   5.  Protocol Binding . . . . . . . . . . . . . . . . . . . . . . .  9

   6.  Compliance Considerations  . . . . . . . . . . . . . . . . . .  9

   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9

   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10

       8.1.  Tracing security considerations  . . . . . . . . . . . . 10

       8.2.  Bypass security considerations . . . . . . . . . . . . . 11

   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12

       9.1.  Normative References . . . . . . . . . . . . . . . . . . 12

       9.2.  Informative References . . . . . . . . . . . . . . . . . 13

   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13

Barbir                       Informational                      [Page 1]

RFC 3897        OPES Entities & End Points Communication  September 2004

   11. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 13

   12. Full Copyright Statem...