Use SCTP as MEGACO Transport
draft-xie-sctp4megaco-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Roger Stewart , Ian Rytina | ||
| Last updated | 2000-03-09 | ||
| 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 discusses the use of the Simple Control Transmission Protocol (SCTP) [1], for carrying MEGACO [2] messages between an MGC and an MG. SCTP is currently being developed by IETF SIGTRAN Working Group. The framework architecture defined in RFC 2719 [3] can be used as a guideline for transporting MEGACO messages using SCTP. MEGACO implementations targeting for high capacity and high availability deployment can especially benefit from the stream capability, redundant network support, congestion avoidance, and strong security features provided by SCTP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)