1 / 11

OPES Tracing and Bypass Functionality

This document outlines the requirements for providing tracing and bypass functionality in an OPES (Open Pluggable Edge Services) system, including what can be bypassed and how tracing is implemented.

bradfordk
Download Presentation

OPES Tracing and Bypass Functionality

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OPES processor and end points communicationsdraft-ietf-opes-end-comm-05 Abbie Barbir abbieb@nortelnetworks.com

  2. Summary Tracing Bypass Progress from last meeting Some considerations Q&A Outline

  3. Specify requirements for providing Tracing functionality in OPES Bypass Functionality What is Traceable/Bypass-able in an OPES Flow? Requirements for OPES System , Entities, Processors and Callout Servers OPES processor and end points communicationsSummary

  4. OPES Tracing • OPES tracing • The inclusion of necessary information within a message in an OPES Flow that identify the collection of transformations or adaptations that have been performed on it before its delivery to an end point • Two use cases for a trace • Enables an end point to detect OPES processors • System administrator interprets OPES trace • Relayed to it by an end point as opaque data

  5. OPES Bypass • OPES Bypass • The act of avoiding the invocation of a service that is identified by a URI within a message in an OPES Flow before its delivery to an end point • What can be bypassed in an OPES Flow? • OPES services • Some or all services • Bypass entities that perform the service • Need access to non-OPES content • What is non-OPES content • We do not define it • OPES System Dependent

  6. Added new section on Bypass (Non-blocking) Fixed Must/Should/May Refined definitions Editorial fixes Issued WGLC Progress since last meeting

  7. Some Considerations • At what requirement level should OPES System be traced? • At what requirement level should OPES processor be traced? • Do we trace the order of service invocations or service completions or something else? • Does bypass semantics mean "give OPES version if non-OPES is not available" or "give an error if non-OPES is not available“ • Affects bypass design/rules

  8. Some Considerations • What can be bypassed? • What does it mean to bypass X? • Can processors be bypassed at all? • Do we allow trace manipulations? • Should we use a single HTTP header for all trace entries to preserve order? If yes, • how to distinguish one OPES system entries from another?

  9. Q&A

  10. Backup

  11. OPES Tracing Modified Message A + Trace Message A Recipient Sender OPES Notification • Basic Point • Done on per message Basis • In Band

More Related