NETEXT Working Group Glenn Mansfield Keeni INTERNET-DRAFT Cyber Solutions Inc. Intended Status: Proposed Standard S. Gundavelli Expires: February 20, 2012 Cisco September 21, 2011 Textual Conventions for Proxy Mobile IPv6 Management Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and 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 document is a product of the NETEXT Working Group. Comments should be addressed to the authors or the mailing list at netext@ietf.org This Internet-Draft will expire on February 20, 2012. Glenn M. Keeni. Expires: February 20, 2012 [Page 1] Internet Draft pmipv6MIB-TC September 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Abstract This memo defines a Management Information Base (MIB) module which contains Textual Conventions to represent commonly used Proxy Mobile-IPv6 (PMIPv6) management information. The intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and used in PMIPv6 related MIB modules that would otherwise define their own representation(s). Table of Contents 1. Introduction .................................. 3 2. Terminology ................................... 3 3. The Internet-Standard Management Framework .... 3 4. The Proxy Mobile IPv6 Textual Conventions MIB . 4 5. Security Considerations ....................... 9 6. IANA Considerations ........................... 9 7. References .................................... 10 8 Acknowledgments ............................... 11 9. Authors' Addresses ............................ 11 Appendix ...................................... 12 Glenn M. Keeni. Expires: February 20, 2012 [Page 2] Internet Draft pmipv6MIB-TC September 2011 1. Introduction This memo defines a Management Information Base (MIB) module which contains Textual Conventions to represent commonly used Proxy Mobile-IPv6 (PMIPv6) management information. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 3. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. Glenn M. Keeni. Expires: February 20, 2012 [Page 3] Internet Draft pmipv6MIB-TC September 2011 4. The Proxy Mobile IPv6 Textual Conventions MIB PMIPv6-TC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2, Unsigned32 FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579] pmip6TCMIB MODULE-IDENTITY LAST-UPDATED "201106250000Z" -- 25th June, 2011 ORGANIZATION "IETF NETLMM Working Group" CONTACT-INFO " Glenn Mansfield Keeni Postal: Cyber Solutions Inc. 6-6-3, Minami Yoshinari Aoba-ku, Sendai, Japan 989-3204. Tel: +81-22-303-4012 Fax: +81-22-303-4015 E-mail: glenn@cysols.com Sri Gundavelli Postal: Cisco Systems 170 W.Tasman Drive, San Jose, CA 95134 USA Tel: +1-408-527-6109 E-mail: sgundave@cisco.com Support Group E-mail: netext@ietf.org " DESCRIPTION "This MIB module provides textual conventions for Proxy Mobile IPv6 Management information. Copyright (C) The IETF Trust (2011). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices. " -- RFC Ed.: replace XXXX with the actual RFC number & remove this Glenn M. Keeni. Expires: February 20, 2012 [Page 4] Internet Draft pmipv6MIB-TC September 2011 -- note REVISION "201106250000Z" -- 25th June, 2011 DESCRIPTION "The initial version, published as RFC XXXX." -- RFC Ed.: replace XXXX with the actual RFC number & remove this -- note ::= { mib-2 YYYY } -- Will be assigned by IANA -- IANA Reg.: Please assign a value for "YYYY" under the -- 'mib-2' subtree and record the assignment in the SMI -- Numbers registry. -- RFC Ed.: When the above assignment has been made, please -- remove the above note -- replace "YYYY" here with the assigned value and -- remove this note. -- ------------------------------------------------------------- -- Textual Conventions -- ------------------------------------------------------------- Pmip6TimeStamp64 ::= TEXTUAL-CONVENTION DISPLAY-HINT "6d:2d" STATUS current DESCRIPTION "A 64-bit unsigned integer field containing a timestamp. The value indicates the elapsed time since January 1, 1970, 00:00 UTC, by using a fixed point format. In this format, the integer number of seconds is contained in the first 48 bits of the field, and the remaining 16 bits indicate the number of 1/65536 fractions of a second. " REFERENCE "RFC 5213: Section 8.8" SYNTAX OCTET STRING (SIZE (8)) Glenn M. Keeni. Expires: February 20, 2012 [Page 5] Internet Draft pmipv6MIB-TC September 2011 Pmip6MnIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "The identity of a mobile node in the Proxy Mobile IPv6 domain. This is the stable identifier of a mobile node that the mobility entities in a Proxy Mobile IPv6 domain can always acquire and use for predictably identifying a mobile node. Various forms of identifiers can be used to identify a mobile node (MN). Two examples are a Network Access Identifier (NAI) [RFC4282] and an opaque identifier applicable to a particular application. " REFERENCE "RFC 4283: Section 3" SYNTAX OCTET STRING (SIZE (0..255)) Pmip6MnLLIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "An identifier that identifies the attached interface of a mobile node. For those interfaces that have a link-layer identifier, this identifier can be based on that. The link-layer identifier, in some cases, is generated by the mobile node and conveyed to the mobile access gateway. This identifier of the attached interface must be stable as seen by any of the mobile access gateways in a given Proxy Mobile IPv6 domain. In some other cases, there might not be any link-layer identifier associated with the mobile node's interface. An identifier value of all zeroes is not considered a valid identifier and cannot be used as an interface identifier. " REFERENCE "RFC 5213: Section 8.6" SYNTAX OCTET STRING (SIZE (0..255)) Glenn M. Keeni. Expires: February 20, 2012 [Page 6] Internet Draft pmipv6MIB-TC September 2011 Pmip6MnIndex ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "A unique integer value, greater than zero, assigned to each mobile node that is currently attached to the Proxy Mobile IPv6 domain by the management system. It is recommended that the values are assigned in a monotonically increasing order starting from 1. It may wrap after reaching its maximum value. The value for each mobile node must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. " SYNTAX Unsigned32 (1..4294967295) Pmip6MnLLIndex ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "A unique integer value, greater than zero, assigned to each interface of a mobile node that is currently attached to the Proxy Mobile IPv6 domain by the management system. It is recommended that the values are assigned in a monotonically increasing order starting from 1. It may wrap after reaching its maximum value. The value for each interface of a mobile node must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. " SYNTAX Unsigned32 (1..4294967295) Glenn M. Keeni. Expires: February 20, 2012 [Page 7] Internet Draft pmipv6MIB-TC September 2011 Pmip6MnInterfaceATT ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This specifies the access technology which connects the mobile node to the access link on the mobile access gateway. " REFERENCE "RFC 5213: Section 8.5, http://www.iana.org/assignments/mobility-parameters/ mobility-parameters.txt" SYNTAX INTEGER { reserved (0), logicalNetworkInterface(1), pointToPointInterface (2), ethernet (3), wirelessLan (4), wimax (5), threeGPPGERAN (6), threeGPPUTRAN (7), threeGPPETRAN (8), threeGPP2eHRPD (9), threeGPP2HRPD (10), threeGPP21xRTT (11), threeGPP2UMB (12) } END Glenn M. Keeni. Expires: February 20, 2012 [Page 8] Internet Draft pmipv6MIB-TC September 2011 5. Security Considerations This module does not define any management objects. Instead, it defines a set of textual conventions which may be used by other MIB modules to define management objects. Meaningful security considerations can only be written in the MIB modules that define management objects. This document has therefore no impact on the security of the Internet. 6. IANA Considerations The MIB modules in this document use the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER value ---------- ----------------------- pmip6TCMIB { mib-2 YYYY } IANA Reg.: Please assign a value under the 'mib-2' subtree for the 'pmip6TCMIB' MODULE-IDENTITY and record the assignment in the SMI Numbers registry. RFC Ed.: When the above assignments have been made, please - remove the above note - replace "YYYY" here with the assigned values and - remove this note. Glenn M. Keeni. Expires: February 20, 2012 [Page 9] Internet Draft pmipv6MIB-TC September 2011 7. References 7.1 Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and Patil, B., Proxy Mobile IPv6, RFC 5213, August 2008. 7.2 Informative References [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for the Internet-Standard Management Framework", RFC 3410, December 2002. [PMIP6MIB] Keeni, G., Koide, K., Gundavelli, S., and Wakikawa, R., "Proxy Mobile IPv6 Management Information Base", Work in Progress. Glenn M. Keeni. Expires: February 20, 2012 [Page 10] Internet Draft pmipv6MIB-TC September 2011 8. Acknowledgments The following groups and individuals have contributed to this draft with discussions and comments: WIDE Project netman-WG 9. Authors' Addresses Glenn Mansfield Keeni Cyber Solutions Inc. 6-6-3 Minami Yoshinari Aoba-ku, Sendai 989-3204 Japan Phone: +81-22-303-4012 E-mail: glenn@cysols.com Sri Gundavelli Cisco Systems 170 W.Tasman Drive, San Jose, CA 95134 USA Phone: +1-408-527-6109 E-mail: sgundave@cisco.com Glenn M. Keeni. Expires: February 20, 2012 [Page 11] Internet Draft pmipv6MIB-TC September 2011 APPENDIX This section documents the development of the draft. It will be deleted when the draft becomes an RFC. Revision History: Glenn M. Keeni. Expires: February 20, 2012 [Page 12]