M3UA Deployment Considerations
draft-asveren-sigtran-m3uacons-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tolga Asveren | ||
| Last updated | 2005-11-28 | ||
| 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 provides some considerations regarding the deployment of M3UA protocol, which were originally brought up at the SIGTRAN mailing list. Certain parts of the discussions in this document are applicable to other SIGTRAN protocols as well.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)