draft-ietf-sigtran-m3ua-mib-06.txt   draft-ietf-sigtran-m3ua-mib-07.txt 
Network Working Group Antonio Roque Network Working Group Javier Pastor-Balbas (ed.)
INTERNET-DRAFT Antonio Canete INTERNET-DRAFT Antonio Canete
Javier Pastor-Balbas Antonio Roque
Ericsson Ericsson
Expires in six months October, 2003 Expires in six months August, 2004
SS7 MTP3-User Adaptation Layer (M3UA) SS7 MTP3-User Adaptation Layer (M3UA)
Management Information Base using SMIv2 Management Information Base using SMIv2
<draft-ietf-sigtran-m3ua-mib-06.txt> <draft-ietf-sigtran-m3ua-mib-07.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with all By submitting this Internet-Draft, I certify that any applicable patent
provisions of Section 10 of RFC 2026. Internet-Drafts are working or other IPR claims of which I am aware have been disclosed, and any of
documents of the Internet Engineering Task Force (IETF), its areas, and which I become aware will be disclosed, in accordance with RFC 3668.
its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and Internet-Drafts are draft documents valid for a maximum of six months and
may be updated, replaced, or obsoleted by other documents at any time. It may be updated, replaced, or obsoleted by other documents at any time. It
is inappropriate to use Internet-Drafts as reference material or cite is inappropriate to use Internet-Drafts as reference material or to cite
them other than as "work in progress". them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/lid-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This document is an individual submission to the IETF. Comments should be This document is a product of the Signaling Transport Working Group of
directed to the authors. the Internet Engineering Task Force (IETF). Comments are welcome should
be submitted to the mailing list sigtran@ietf.org.
Abstract Abstract
The MTP3-User Adaptation Layer is a protocol for the transport of any SS7 The MTP3-User Adaptation Layer is a protocol for the transport of any SS7
MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the
services of the Stream Control Transmission Protocol. Also, provision is services of the Stream Control Transmission Protocol. Also, provision is
made for protocol elements that enable a seamless operation of the MTP3- made for protocol elements that enable a seamless operation of the MTP3-
User peers in the SS7 and IP domains. This protocol would be used between User peers in the SS7 and IP domains. This protocol would be used between
a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP- a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP-
resident Database. It is assumed that the SG receives SS7 signaling over resident Database. It is assumed that the SG receives SS7 signaling over
skipping to change at page 2, line 15 skipping to change at page 2, line 15
This memo defines the Management Information Base (MIB) module, which This memo defines the Management Information Base (MIB) module, which
describes the minimum amount of objects needed to manage the describes the minimum amount of objects needed to manage the
implementation of the M3UA. implementation of the M3UA.
Open Issues Open Issues
- Remove this section. - Remove this section.
- Remove Revision History - Remove Revision History
- Decide under which object identifier branch of the SNMP tree, M3UA will - IANA -> Decide under which object identifier branch of the SNMP tree,
be placed (value obtained when submitted to the IETF editor). M3UA will be placed (value obtained when submitted to the IETF editor).
- Update references to drafts. - Update references to drafts.
- Check Security Considerations section - Check Security Considerations section
Table of Contents Table of Contents
1. Introduction...........................................4 1. Introduction...........................................4
1.1 Abbreviations.........................................4 1.1 Abbreviations.........................................4
2. The Internet-Standard Management Framework..............4 2. The Internet-Standard Management Framework..............4
3. Structure of the MIB...................................5 3. Structure of the MIB...................................5
3.1 Management............................................6 3.1 Management............................................6
3.1.1 Attributes..........................................6 3.1.1 Attributes..........................................6
3.1.2 ASP Tables..........................................7 3.1.2 ASP Tables..........................................7
3.1.3 SGP/IPSP Tables....................................11 3.1.3 SGP/IPSP Tables....................................11
3.1.4 Generic Tables.....................................16 3.1.4 Generic Tables.....................................16
3.1.4.1 Network Appearance Table..........................16
3.1.4.2 Generic Statistics Table..........................17
3.2 Conformance..........................................18 3.2 Conformance..........................................18
3.2.1 Groups..............................................18 3.2.1 Groups..............................................18
3.2.2 Compliance..........................................18 3.2.2 Compliance..........................................18
4. Definitions...........................................18 4. Definitions...........................................18
5. References.............................................57
5.1 Normative References..................................57 5.1 Normative References..................................57
5.2 Informative References................................58 5.2 Informative References................................58
6. Security Considerations................................59 6. Security Considerations................................59
7. Acknowledgements.......................................60 7. Acknowledgements.......................................60
8. Authors' Addresses.....................................60 8. Authors' Addresses.....................................60
9. Revision History.......................................60 9. Revision History.......................................60
9.1 Changes from draft rev 05 to draft rev 06:............60 9.1 Changes from draft rev 06 to draft rev 07:............60
9.2 Changes from draft rev 04 to draft rev 05:............61 9.2 Changes from draft rev 05 to draft rev 06:............60
9.3 Changes from draft rev 03 to draft rev 04:............61 9.3 Changes from draft rev 04 to draft rev 05:............60
9.4 Changes from draft rev 02 to draft rev 03:............61 9.4 Changes from draft rev 03 to draft rev 04:............61
9.5 Changes from draft rev 01 to draft rev 02:............62 9.5 Changes from draft rev 02 to draft rev 03:............61
9.6 Changes due to the alignment with the RFC2851 update..63 9.6 Changes from draft rev 01 to draft rev 02:............62
9.7 Changes due to the alignment with the RFC2851 update..63
1. Introduction 1. Introduction
This memo defines the Management Information Base (MIB) module which This memo defines the Management Information Base (MIB) module which
describes managed objects for implementations of the M3UA. describes managed objects for implementations of the M3UA.
The document starts with a brief description of the SNMP framework and The document starts with a brief description of the SNMP framework and
continues with the MIB explanation and security consideration among continues with the MIB explanation and security consideration among
others. others.
Terms related to the SCTP architecture are explained in [1]. Other Terms related to the SCTP architecture are explained in [1]. Other
skipping to change at page 58, line 32 skipping to change at page 58, line 32
Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V.
Paxson, "Stream Control Transmission Protocol", October 2000. Paxson, "Stream Control Transmission Protocol", October 2000.
[RFC3291] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder, [RFC3291] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder,
"Textual Conventions for Internet Network Addresses", May 2002. "Textual Conventions for Internet Network Addresses", May 2002.
[RFC3332] G. Sidebottom, K.Morneault, J. Pastor-Balbas, "SS7 MTP3-User [RFC3332] G. Sidebottom, K.Morneault, J. Pastor-Balbas, "SS7 MTP3-User
Adaptation Layer (M3UA)", March 2002. Adaptation Layer (M3UA)", March 2002.
[M3UAIG] J. Pastor-Balbas, K.Morneault, "M3UA Implementor's Guide", [M3UAIG] J. Pastor-Balbas, K.Morneault, "M3UA Implementor's Guide",
draft-ietf-sigtran-m3ua-implementors-guide-06.txt, October 2003. draft-ietf-sigtran-m3ua-implementors-guide-07.txt, February
2004.
5.2 Informative References 5.2 Informative References
[RFC1213] Rose, M. and K. McCloghrie, "Management Information Base for [RFC1213] Rose, M. and K. McCloghrie, "Management Information Base for
Network Management of TCP/IP-based internets", RFC 1213,March Network Management of TCP/IP-based internets", RFC 1213,March
1991. 1991.
[RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the
Transmission Control Protocol using SMIv2", RFC 2012, November Transmission Control Protocol using SMIv2", RFC 2012, November
1996. 1996.
skipping to change at page 59, line 13 skipping to change at page 59, line 13
March 1997 March 1997
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-Standard "Introduction and Applicability Statements for Internet-Standard
Management Framework", RFC 3410, December 2002. Management Framework", RFC 3410, December 2002.
[VANJ] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1988, [VANJ] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1988,
Stanford, California. Stanford, California.
[IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, [IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe,
A. and B. Zill, "IPv6 Scoped Address Architecture", draft-ietf- A. and B. Zill, "IPv6 Scoped Address Architecture", draft-ietf-
ipv6-scoping-arch-00.txt, June 2003. Work in progress. ipv6-scoping-arch-01.txt, February 2004. Work in progress.
[TCPMIB] Bill Fenner, Keith McCloghrie, Rajiv Raghunarayan, Juergen [TCPMIB] Bill Fenner, Keith McCloghrie, Rajiv Raghunarayan, Juergen
Schoenwalder, "Management Information Base for the Transmission Schoenwalder, "Management Information Base for the Transmission
Control Protocol (TCP) ", draft-ietf-ipv6-rfc2012-update-04.txt Control Protocol (TCP) ", draft-ietf-ipv6-rfc2012-update-06.txt
, September 2003. Work in progress. , February 2003. Work in progress.
[UDPMIB] Bill Fenner, "Management Information Base for User Datagram [UDPMIB] Bill Fenner, "Management Information Base for User Datagram
Protocol (UDP), draft-ietf-ipv6-rfc2013-update-01.txt, Protocol (UDP), draft-ietf-ipv6-rfc2013-update-03.txt,
October 2003. Work in progress. April 2004. Work in progress.
[MIBGUIDE] Heard, "Guidelines for MIB Authors and Reviewers", draft- [MIBGUIDE] Heard, "Guidelines for MIB Authors and Reviewers", draft-
ietf-ops-mib-review-guidelines-02.txt, August 2003. Work in ietf-ops-mib-review-guidelines-03.txt, June 2004. Work in
progress progress
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB that have
a MAX-ACCESS clause of read-write and/or read-create. Such objects
may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these objects when sending them
over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if security SNMPv1 by itself is not a secure environment. Even if security
measures are taken (e.g., using IPSEC), there is no per-user control measures are taken (e.g., using IPSEC), there is no per-user control
as to who (once an IPSEC association is established between hosts) is as to who (once an IPSEC association is established between hosts) is
allowed to GET or SET the objects in this MIB allowed to GET or SET the objects in this MIB
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the as provided by the SNMPv3 framework. Specifically, the use of the
User-based Security Model RFC 2574 [RFC2574] and the View-based Access User-based Security Model RFC 2574 [RFC2574] and the View-based Access
Control Model RFC 2575 [RFC2575] is recommended. Control Model RFC 2575 [RFC2575] is recommended.
skipping to change at page 60, line 22 skipping to change at page 60, line 14
7. Acknowledgements 7. Acknowledgements
The authors wish to thank Shyamal Prasad, Kurt Kite, Jennifer Jones, The authors wish to thank Shyamal Prasad, Kurt Kite, Jennifer Jones,
Srivats P., Ken Morneault, Tolga Asveren, Samuel Dur D. Jeyaseelan, Srivats P., Ken Morneault, Tolga Asveren, Samuel Dur D. Jeyaseelan,
Anjali Gurmukhani, Kamesh Kaul, Brian Bidulock for their comments and Anjali Gurmukhani, Kamesh Kaul, Brian Bidulock for their comments and
suggestions. suggestions.
8. Authors' Addresses 8. Authors' Addresses
Antonio Roque Tel: +34-91-339-3523 Jose-Javier Pastor-Balbas Tel: +34-91-339-1397
Ericsson Espana S.A. EMail: Antonio.Roque@ericsson.com Ericsson Espana S.A. EMail: J.Javier.Pastor@ericsson.com
Via de los Poblados 13, 4th floor Via de los Poblados 13
Madrid, 28033 Madrid, 28033
Spain Spain
Antonio Canete Tel: +34-91-339-2460 Antonio Canete Tel: +34-91-339-2460
Ericsson Espana S.A. EMail: Antonio.Canete@ericsson.com Ericsson Espana S.A. EMail: Antonio.Canete@ericsson.com
Via de los Poblados 13, 4th floor Via de los Poblados 13
Madrid, 28033 Madrid, 28033
Spain Spain
Jose-Javier Pastor-Balbas Tel: +34-91-339-1397 Antonio Roque Tel: +34-91-339-3523
Ericsson Espana S.A. EMail: J.Javier.Pastor@ericsson.com Ericsson Espana S.A. EMail: Antonio.Roque@ericsson.com
Via de los Poblados 13, 4th floor Via de los Poblados 13
Madrid, 28033 Madrid, 28033
Spain Spain
9. Revision History 9. Revision History
9.1 Changes from draft rev 05 to draft rev 06: 9.1 Changes from draft rev 06 to draft rev 07:
o References updated.
9.2 Changes from draft rev 05 to draft rev 06:
o Load-sharing objects (m3uaSpLshMethod, m3uaStreamLshMethod) are o Load-sharing objects (m3uaSpLshMethod, m3uaStreamLshMethod) are
removed since nothing is standardized about how to perform load- removed since nothing is standardized about how to perform load-
sharing. sharing.
o Typos. o Typos.
9.2 Changes from draft rev 04 to draft rev 05: 9.3 Changes from draft rev 04 to draft rev 05:
o Changed objects from having writing permission to read-only o Changed objects from having writing permission to read-only
o General MIBs boiler plate updated. o General MIBs boiler plate updated.
o Tables divided per node type: ASPs, SGP/IPSP and General Tables o Tables divided per node type: ASPs, SGP/IPSP and General Tables
(with general values and statistic, valid per every node type). (with general values and statistic, valid per every node type).
o Updated contact information. o Updated contact information.
o Removed CIC and SSN from the RK. o Removed CIC and SSN from the RK.
o Security Considerations updated. o Security Considerations updated.
o Copyright Statement included. o Copyright Statement included.
9.3 Changes from draft rev 03 to draft rev 04: 9.4 Changes from draft rev 03 to draft rev 04:
o Integer32 is imported but not used. Removed. o Integer32 is imported but not used. Removed.
o TEXTUAL-CONVENTION is imported but not used. Removed. o TEXTUAL-CONVENTION is imported but not used. Removed.
o mib-2 suggested as branch for mib. o mib-2 suggested as branch for mib.
o m3uaAppSpEpState consistently defined as INTEGER. o m3uaAppSpEpState consistently defined as INTEGER.
o m3uaPeerAppTrafficMode consistently defined as INTEGER. o m3uaPeerAppTrafficMode consistently defined as INTEGER.
o Fixed error in m3uaSpEpEntry object description text. o Fixed error in m3uaSpEpEntry object description text.
o Rework in m3uaAppType object description text. o Rework in m3uaAppType object description text.
9.4 Changes from draft rev 02 to draft rev 03: 9.5 Changes from draft rev 02 to draft rev 03:
o Value range of m3uaAppTrafficMode object is modified. o Value range of m3uaAppTrafficMode object is modified.
o Object m3uaLocalPort is changed to "read-write". A comment o Object m3uaLocalPort is changed to "read-write". A comment
is added with the recommended IANA port number. is added with the recommended IANA port number.
o Object m3uaFailOverBuffering is deleted. A comment in object o Object m3uaFailOverBuffering is deleted. A comment in object
m3uaTrValue is added: If Tr is 0 then FailOver Buffering is Off. m3uaTrValue is added: If Tr is 0 then FailOver Buffering is Off.
Thus, there is no further need for this element. Thus, there is no further need for this element.
skipping to change at page 62, line 42 skipping to change at page 62, line 36
o Added new Lookup Reverse Tables for: o Added new Lookup Reverse Tables for:
- Get EndPoint Id from Association Id. - Get EndPoint Id from Association Id.
- Get Routing Key Id from Application Id. - Get Routing Key Id from Application Id.
- Get Routing Key Id from DPC and NA. - Get Routing Key Id from DPC and NA.
- Get Endpoints serving an Application. - Get Endpoints serving an Application.
o Routing Table has been reestructured to deal with multiplicity o Routing Table has been reestructured to deal with multiplicity
of SIs, OPCs and CIC Ranges per Routing Key. of SIs, OPCs and CIC Ranges per Routing Key.
Three new subtables are used. Three new subtables are used.
9.5 Changes from draft rev 01 to draft rev 02: 9.6 Changes from draft rev 01 to draft rev 02:
o Section 3.1.2.3 Signaling Process Table - Chapter re-phrased. o Section 3.1.2.3 Signaling Process Table - Chapter re-phrased.
o Section 3.1.2.4 Signaling Process Endpoint Table - Last paragraph o Section 3.1.2.4 Signaling Process Endpoint Table - Last paragraph
removed. removed.
o Section 3.1.2.5 Signaling Process Endpoint Statistics Table o Section 3.1.2.5 Signaling Process Endpoint Statistics Table
m3uaAppId and m3uaSpEpId added to the table figure m3uaAppId and m3uaSpEpId added to the table figure
Corresponding changes in Definitions chapter applied. Corresponding changes in Definitions chapter applied.
skipping to change at page 63, line 18 skipping to change at page 63, line 13
Corresponding changes in Definitions chapter applied. Corresponding changes in Definitions chapter applied.
o Object definition of m3uaMaxStreamInbound is removed. o Object definition of m3uaMaxStreamInbound is removed.
o Object Definition of m3uaSpEpEntry o Object Definition of m3uaSpEpEntry
Index "m3uaAppId" is replaced by m3uaSpEpAssocId. Index "m3uaAppId" is replaced by m3uaSpEpAssocId.
o Object Definition of m3uaSpEpStatRowStatus o Object Definition of m3uaSpEpStatRowStatus
Definition is deleted. Definition is deleted.
9.6 Changes due to the alignment with the RFC2851 update. 9.7 Changes due to the alignment with the RFC2851 update.
o Include clarification text of the IP address types supported in the o Include clarification text of the IP address types supported in the
M3UA MIB. Chapter 3.1.2.7.2 (Local and Remote IP address table) M3UA MIB. Chapter 3.1.2.7.2 (Local and Remote IP address table)
o Remote Primary IP address: Addition of the ipv4z an ipv6z types for o Remote Primary IP address: Addition of the ipv4z an ipv6z types for
non-globally IP addresses in which a scope identifier is needed. non-globally IP addresses in which a scope identifier is needed.
Addition of the scope of ipv6 type. All of them according to the Addition of the scope of ipv6 type. All of them according to the
RFC2851update-v04 RFC2851update-v04
o InetAddressType for local and remote IP addresses: o InetAddressType for local and remote IP addresses:
skipping to change at page 63, line 51 skipping to change at page 64, line 4
Description: Specify that the M3UA MIB only need to support IPv4/IPv6 Description: Specify that the M3UA MIB only need to support IPv4/IPv6
addresses without a zone index, unknown type and DNS names. Support addresses without a zone index, unknown type and DNS names. Support
for for
IPv4/IPv6 addresses without zone indices is not required. IPv4/IPv6 addresses without zone indices is not required.
InetAddressType of local and remote IP address: Clarify the InetAddressType of local and remote IP address: Clarify the
implementation is only required to support IPv4 and IPv6 address types implementation is only required to support IPv4 and IPv6 address types
without zone indices. Clarify also that UNKONWN type is only used in without zone indices. Clarify also that UNKONWN type is only used in
case of local and remote addresses when invalid/unknown IP address case of local and remote addresses when invalid/unknown IP address
format. format.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/