Topology Considerations for IP Telephony MIDCOM Agents
draft-molitor-midbox-telephony-topology-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Molitor | ||
| Last updated | 2001-09-04 | ||
| 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 several operational scenarios for IP Telephony and some ways in which a suitable MIDCOM Agent might interwork with one or more middleboxes to facilitate those scenarios. From these scenarios, certain minimum requirements for Agent knowledge of network topology will be derived.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)