SOP Message Flows
draft-dalela-sop-flows-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ashish Dalela , Mike Hammer | ||
| Last updated | 2012-07-06 (Latest revision 2012-01-03) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes the Service Orchestration Protocol (SOP) message flows for some important service orchestration scenarios. The flows contain complete packet information including both SOP and Service Description Framework (SDF) payloads. The message flows in this document are by no means exhaustive, but they carry sufficient information using which other flows can be easily constructed. The deployment scenarios for services are varied, and it is not possible to cover every possible scenario. Nevertheless, those flows will follow closely the information given in this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)