The proposal of extenting RFC4666 for the M3UA deployment
draft-chen-sigtran-m3ua-ext-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Xu Chen | ||
| Last updated | 2007-11-16 | ||
| 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
RFC 4666 defines a protocol for supporting the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services of the Stream Control Transmission Protocol. Some parts of the specification are unclear that may lead to misinterpretations that may impair interoperability between different implementations. RFC 4666 doesn't define the application of IPSTP-IPSEP interface. For the signalling network management function, messages and procedures, it needs more contributes. This document provides clarifications and amendments to RFC 4666.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)