ENUM Working Group Yongtae Shin Internet-Draft Soomin Park Expires: May 10, 2006 Sangchul Son ICN LAB of Soongsil Univ YoungWan Ju National Internet Development Agency of Korea October 2005 Extension MIB for ENUM management draft-shin-enum-emib-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on may 10, 2006. Copyright Notice Copyright (C) The Internet Society (2005). All Rights Reserved. Abstract It is service that ENUM replaces existent IP by telephone number and a user does various kinds devices so that is available by one peculiar number. As this ENUM's DNS becomes bulky, we need monitoring for ENUM. There is MIB to monitoring method that is used present. We propose standard for efficient ENUM DNS administration applying extension MIB that is this MIB's extension to ENUM. Shin, et al. Expires May 10, 2006 [Page 1] Internet-Draft Extension MIB for ENUM October 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Requirment. . . . . . . . . . . . . . . . . . . . . . . . . . 2 3.1 MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4. Protocol Details . . . . . . . . . . . . . . . . . . . . . . 3 4.1 Extended MIB design method for monitor application of ENUM . 3 4.2 MIB application way of ENUM . . . . . . . . . . . . . . . . . 4 4.3 Extended MIB ENUM model . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction Enum uses one number as telephone numbering mapping's acronym, it is doing service so that can interlock to device to user. ENUM uses to store and manage, for ENUM number using ENUM DNS. ENUM DNS does function such as existent DNS. Therefore, this ENUM DNS as existent DNS MIB's uses require. MIB is monitoring service that manage DNS's structure or computers basically. MIB comes out MIBv1 to visual point at present MIBv2, and extension MIB. MIB creates, manages and uses each object using SNMP protocol. So, this document uses extension MIB that is used present, ENUM DNS monitoring do if use this way by method to understand ENUM DNS's administration and uses many helps. 2. Terminology ASN: Abstract Syntax Notation DNS: Domain Name Server ENUM: ENUM is standard that is selected by IETF. It is used being mapped in telephone number that turn DNS to web address or URL. MIB: Management Information Base NMS: Network Management System. Software that system administrator is used controlling network SNMP: Simple Network Management Protocol. Protocol that watch and control network supervision and action of network device 3. Requirements 3.1 MIB MIB is Network administration's primary that exchange specific information between Manager and Agent. Specific information and resource that should be managed are known as object. Set that assemble these objects is MIB. Network management means that receive specific value among MIB that device offer and then grasp state of the equipment or change the value receiving specification value among MIB that devices offer. Network management means that receive specific value among MIB that devices -host such as workstation, printer/file server of course and communications equipment such as hub, router, Shin, et al. Expires May 10, 2006 [Page 2] Internet-Draft Extension MIB for ENUM October 2005 switch- offer and then grasp state of the equipment or change the value. Alteration of value can alter relevant MIB's String or value as well as state of devices through alteration and can instruct and run regular function in the device. That is, it can keep away transmission to specification port of hub as well as forbid communication of relevant device by correcting Interface's management value. Also it can reset HUB through altering specific MIB. SMI that is Framework that define and construct MIB defined the following item in RFC1155. 1.Each objects of MIB are defined using ASN.1 that is standardized and developed language by ISO(ISO 8824) and ITU-T(X.208) 2. All objects must have name, syntax, and encoding name - Object identification data that identify object Syntax - Data type of object (e.g. INTEGER, OCTET STRING etc) Encoding - What BIT pattern is object data transmitted? 3. MIB is defined usable thing and allowed structure in SNMP of data class is defined in ASN.1. MIB structure is forming stratified Tree structure. Specific object is identified by object identification(OID). Actually, OID is not character that we use usually but serial integer. MIB Tree is decided OID by way to sort objects belonging to equal category in the root and SNMP can read and write Leaf that is end node. For example, information in system location is not sysLocation of OID and is "1.3.6.1.2.1.1.6". And this object can read and write but system ("1.3.6.1.2.1.1") that is parents object can't read or write. If want to read all "sysDescr, sysObjectID, ... ,sysServices" that is low level object that follow hereupon, must ask to Agent specifying "1 ~ 7" OID. Most NMS receive value by Designating system group. In actuality operate with upside and get. SNMP SMI specifies "internet(1)" by "ISO(1) org(3) dod(6)" Sub-Tree, and define enterprises by "internet(1)" Sub-Tree and directory(1) , mgmt(2) , experimental(3), private(4) and private(4) Sub-Tree. MIB that only own company which is not defined by SNMP MIB standard offers can define to private(4) enterprises(1). But, MIB must have OID that distinguish all companies. It is managing in IANA (Internet Assigned Number Authority). Therefore, MIB should be given OID to IANA for implementation of private Enterprises MIB If is like this, uniqueness of the low rank MIB's object is guaranteed. Therefore, It is possible that MIB distinguishes with other company's private MIB 4. Protocol Details 4.1 Extended MIB design method for monitor application of ENUM (1) MIB is largely distinguished by standard MIB and non-standard MIB. Standard MIB is MIB that is established by standard like MIB-1 and MIB-2, non-standard MIB can use extending existent MIB. Therefore, We will use the non-standard MIB. Shin, et al. Expires May 10, 2006 [Page 3] Internet-Draft Extension MIB for ENUM October 2005 (2) Design of MIB firstly define administration object via specific of target design and make table according to value specific (3) Individual MIB allocates new object identification data under all enterprises or selects one among object identification data that is not registered or individual MIB makes it. (4) After creating OID by necessity, MIB makes MIB tree structure under enterprises Allocating identification data of objects (5) Access competence, explanation, object identification and type of administration object defines MIB according to SMI(Structure of Management Information) using ASN.1 (Abstract Syntax notation.1) 4.2 MIB application way of ENUM MIB is largely distinguished by MIB for hardware administration and MIB for software administration. Therefore, to think appliable MIB in ENUM, We can see hardware MIB system that can be monitoring traffic amount of ENUM devices and software MIB system that can be monitoring traffic amount of packet in ENUM DNS. However, that normalize hardware MIB is expected to be difficult because Standard enactment among devices. Therefore, way for standardization propulsion may have better establish software MIB. 4.3 Extended MIB ENUM model * Internet (1 3 6 1) | | * Private (4) | | * Enterprise (1) | | *------------+-------* enmapping (1) Enobject (99) | +-------* ensearch (2) | +-------* eninsert (3) | +-------* enmodify (4) | +-------* endelete (5) | +-------* enchange (6) | +-------* enex (7)
MIB tree structure that implements software MIB adaptively in ENUM environment. Shin, et al. Expires May 10, 2006 [Page 4] Internet-Draft Extension MIB for ENUM October 2005
is MIB tree structure that implements software MIB adaptively in ENUM environment. To explain above shown picture, Internet (1 3 6 1) is basic object that use in MIB and the side number means ID. Extended MIB defines in enterprise (1) in basis MIB's private (4) object inside of Internet (1 3 6 1) object. Enobject (99) means object to use in ENUM and ID 99 is the number that decide carelessly enmapping OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Object to sense mapping traffic with ENUM number and existing IP inside ENUM DNS." ::= { dnsServCounterEntry 5 } ensearch OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Object that using when existing IP searches ENUM number entering." ::= { dnsServCounterEntry 5 } eninsert OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-write STATUS current DESCRIPTION "Object that using when administrator registers ENUM number." ::= { dnsServCounterEntry 5 } enmodify( OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-write STATUS current DESCRIPTION "Object that using when administrator corrects existent ENUM number." ::= { dnsServCounterEntry 5 } endelete OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-write STATUS current DESCRIPTION "Object that using when administrator erases existent ENUM number." ::= { dnsServCounterEntry 5 } Shin, et al. Expires May 10, 2006 [Page 5] Internet-Draft Extension MIB for ENUM October 2005 enchange OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-write STATUS current DESCRIPTION "Object that using when change user's competence." ::= { dnsServCounterEntry 5 } enex OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-write STATUS current DESCRIPTION "Composure object for extension." ::= { dnsServCounterEntry 5 } Administrator can make easily solvable environment When course traffic with ENUM DNS's monitor ring happens by such MIB 5. Security Considerations More improvement way that is proposed in after through performance estimation, and security part that is limitation of mobile environment and DRM part that can protect intellectual property of multimedia contents research about works that need. 6. References [1] S. Kille, N. Freed, "Mail Monitoring MIB", RFC1566, 1994.1. [2] P. Faltstrom, "E.164 number and DNS", RFC2916, 2000. 9. [3] O. Levin, "Telephone Number Mapping (ENUM) Service Registration for H.323", RFC3762, "2004. 4. [4] J. Peterson, "Telephone Number Mapping (ENUM) Service Registration for Presence Services, RFC3935, "2005. 1. [5] S. Hollenbeck, "E.164 Number Mapping for the Extensible Provisioning Protocol (EPP), RFC 4114, 2005. 6. [6] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol (SNMP)", RFC 1098, University of Tennessee at Knoxville, NYSERNet, Inc., Rensselaer Polytechnic Institute, MIT Laboratory for Computer Science, April 1989. [7] Satz, G., "Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base", RFC 1162, cisco Systems, Inc., June 1990. [8] R. Austein, J. Saperia, "DNS Server MIB Extensions", RFC 1611, 1994. 5. [9] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, 1991. 3. [10] "Information processing systems - Open Systems Interconnection- Specification of Abstract Syntax Notation One (ASN.1)", International Organization for Standardization, International Standard 8824, 1987. 12. Shin, et al. Expires May 10, 2006 [Page 6] Internet-Draft Extension MIB for ENUM October 2005 [11] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, 1990. 5. [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1442, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, 1993. 4. [13] Kille, S., WG Chair, and N. Freed, Editor, "The Network Services Monitoring MIB", RFC 1565, ISODE Consortium, Innosoft, 1994. 1. Authors' Information Yongtae Shin Room 422 Information Science B/D, Soongsil University Sangdo5-dong Dongjak-gu Seoul, 156-743, South Korea Email: shin@cherry.ssu.ac.kr Soomin Park Room 402 Information Science B/D, Soongsil University Sangdo5-dong Dongjak-gu Seoul, 156-743, South Korea Email: smpark@cherry.ssu.ac.kr Sangchul Son Room 410A Information Science B/D, Sookmyung University Hyochangwon St.52 Yongsan-gu Seoul, 140-742, South Korea Email: yelhorse@cherry.ssu.ac.kr YoungWan Ju National Internet Development Agency of Korea 1321-11, Seocho2-dong, Seocho-gu, Seoul South Korea Email: ywju@nida.or.kr Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Shin, et al. Expires May 10, 2006 [Page 7] Internet-Draft Extension MIB for ENUM October 2005 Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Shin, et al. Expires May 10, 2006 [Page 8]