The requirement of extending RFC4666 for the M3UA deployment
draft-zhang-sigtran-m3ua-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Zhao Yuyi | ||
| Last updated | 2008-02-18 | ||
| 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. M3UA is designed for SEP-(TDM)-SG-(IP)-IPSEP and IPSEP-(IP)-IPSEP applications, so the network level management function isn't required. SSNM(SS7 Signalling Network Management) messages defined in M3UA are only used for interworking with SS7. RFC 4666 doesn't define IPSEP- IPSTP-IPSEP application of M3UA. The signalling network management function for this application needs to be extended. Some parts of the specification are unclear,which may lead to misinterpretations and may weaken interoperability. This document provides extensions and clarifications to RFC 4666.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)