Midcom Agents and Topology
draft-brim-midcom-inandout-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2001-09-10 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-brim-midcom-inandout-00.txt
Abstract
A midcom agent does not know whether to ask for a ruleset to be installed in a middlebox or not. Even when it does ask, in some situations the middlebox does not know how to apply the ruleset. This document tries to solve these problems without adding an overwhelming amount of complexity to every agent and middlebox.
Authors
Scott Brim
(sbrim@cisco.com)
Adina Simu
(asimu@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)