Mobile IP Working Group D. Cong & M. Hamlen, editor INTERNET DRAFT Motorola expires in six months C. Perkins, editor IBM December 1995 The Definitions of Managed Objects for the Home Agent function of IP Mobililty Support draft-ietf-mobileip-mib-ha-00.txt Status of this Memo This document is a submission by the Mobile-IP Working Group of the Internet Engineering Task Force (IETF). Comments should be submitted to the mobile-ip@smallworks.com mailing list. Distribution of this memo is unlimited. This document is an Internet-Draft. 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.'' To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Home Agent function definied in the Mobile IP Protocol. Cong, Hamlen & Perkins expires in six months [Page 1] Internet Draft Mobile IP MIB Definition December 18, 1995 Table of Contents 1. The Network Management Framework ...................... 2 2. Objects ............................................... 2 2.1 Format of Definitions ................................ 2 3. Overview .............................................. 3 3.1 Object Selection Criteria ............................ 3 3.2 Structure of the Mobile IP ........................... 3 3.3 MIB Groups ........................................... 4 4. Definitions ........................................... 4 5. Acknowledgements ...................................... 16 6. Security Considerations ............................... 16 7. References ............................................ 17 8. Chair's Address ....................................... 18 9. Editor's Address ...................................... 18 1. The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: STD 16/RFC 1155 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. STD 16/RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. STD 17/RFC 1213 which defines MIB-II, the core set of managed objects for the Internet suite of protocols. STD 15/RFC 1157 which defines the SNMP, the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 2. Objects Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [3] defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. 2.1. Format of Definitions Cong, Hamlen & Perkins expires in six months [Page 2] Internet Draft Mobile IP MIB Definition December 18, 1995 Section 4 contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SMI, as amended by the extensions specified in [5,6]. 3. Overview 3.1. Object Selection Criteria To be consistent with IAB directives and good engineering practice, the authors have applied some criteria to select managed objects for the Mobile IP Protocol. (1) Partition management functionality among the Mobile Node, Home Agent, and Foreign Agent according to the partitioning seen in the Mobile IP Protocol. For example, the editors minimize the management requirements in the Mobile Node. (2) Require that objects be essential for either fault or configuration management. (3) Limit the total number of objects. (4) Exclude objects which are simply derivable from others in this or other MIBs. 3.2. Structure of the Mobile IP This section describes the basic model of Mobile IP used in developing the Mobile IP MIB. This information should be useful to the implementor in understanding some of the basic design decisions of the MIB. The Mobile IP Protocol introduces these new funtional entities: Mobile Node A host or router that changes its point of attachment from one network or subnetwork to another. A mobile node may change its location without losing connectivity and without changing its IP address. Home Agent A router on a mobile node's home network which tunnels packets for delivery to the mobile node when it is away from home, and maintains current location information for the mobile node. Foreign Agent Cong, Hamlen & Perkins expires in six months [Page 3] Internet Draft Mobile IP MIB Definition December 18, 1995 A router on a mobile node's visited network which provides routing services to the mobile node when it registers. The foreign agent detunnels and delivers packets to the mobile node that were tunneled by the mobile node's home agent. In the reverse direction, the foreign agent may serve as a default router for registered mobile node. This document specifies the objects used in managing one of these entities; namely, the Mobile node. 3.3. MIB Groups The definitions of managed objects for Mobile IP have been organized into several MIB groups: (1) The Mobile Node Group (2) The Foreign Agent Group (3) The Home Agent Group (4) The Security Group (Optional) The first three groups are related to the three entities defined in the Mobile IP Protocol specification. The Security Group is an optional group for all three entities, because it includes security configurations for each Mobile IP entity. If an agent seeking to implement the Mobile IP MIB does not support SNMPv2 with privacy, it is strongly advised that the Security Group not be implemented. This document specifies the Home Agent Group. 4. Definitions MIP-HA-MIB DEFINITIONS ::= BEGIN IMPORTS Counter, IpAddress, TimeTicks FROM RFC1155-SMI mib-2, DisplayString, PhysAddress FROM RFC1213-MIB mip, Boolean FROM MIP-MN-MIB OBJECT-TYPE FROM RFC-1212; -- Extend the MIB definitions ha OBJECT IDENTIFIER ::= { mip 3 } -- Home Agent Group Cong, Hamlen & Perkins expires in six months [Page 4] Internet Draft Mobile IP MIB Definition December 18, 1995 haSystem OBJECT IDENTIFIER ::= { ha 1 } haAdvertisement OBJECT IDENTIFIER ::= { ha 2 } haRegistration OBJECT IDENTIFIER ::= { ha 3 } -- Home Agent System Group haMobileIPEnable OBJECT-TYPE SYNTAX Boolean ACCESS read-write STATUS mandatory DESCRIPTION "Enables the home agent function as defined in IP Mobility Support. If it is true, it is enabled, otherwise it is disabled." ::= { haSystem 1 } haEncapsulationSupported OBJECT-TYPE SYNTAX INTEGER(0..256) ACCESS read-only STATUS mandatory DESCRIPTION "Encapsulation methods supported by the home agent. A home agent MAY support multiple encapsulation methods. The values can be distinguished by applying the appropriate testing bits. ipinip 0x01 IP Encapsulation within IP gre 0x02 Generic Routing Encapsulation, RFC1701 minenc 0x04 Minimal Encapsulation within IP." ::= { haSystem 2 } -- HA Advertisement Group -- Home agent advertisement configuration table haAdvConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF HaAdvConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table containing configurable advertisement parameters for all advertisement interfaces in home agent." ::= { haAdvertisement 1 } haAdvConfigEntry OBJECT-TYPE Cong, Hamlen & Perkins expires in six months [Page 5] Internet Draft Mobile IP MIB Definition December 18, 1995 SYNTAX HaAdvConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Advertisement parameters for one advertisement interface." INDEX { haInterfaceAddress } ::= { haAdvConfigTable 1 } HaAdvConfigEntry ::= SEQUENCE { haInterfaceAddress IpAddress, haAdvRegLifetime INTEGER, haAdvPrefixLengthInclusion Boolean, haAdvAddress IpAddress, haAdvMaxInterval INTEGER, haAdvMinInterval INTEGER, haAdvPeriod INTEGER } haInterfaceAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-write STATUS mandatory DESCRIPTION "IP address for advertisement interface." ::= { haAdvConfigEntry 1 } haAdvRegLifetime OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The longest lifetime in seconds that home agent is willing to accept in any registration request." ::= { haAdvConfigEntry 2 } haAdvPrefixLengthInclusion OBJECT-TYPE SYNTAX Boolean ACCESS read-write STATUS mandatory DESCRIPTION "Whether the advertisement should include the Prefix- Lengths Extension. If it is true, all advertisements sent over this interface should include the Prefix-Lengths Extension." ::= { haAdvConfigEntry 3 } haAdvAddress OBJECT-TYPE Cong, Hamlen & Perkins expires in six months [Page 6] Internet Draft Mobile IP MIB Definition December 18, 1995 SYNTAX IpAddress ACCESS read-write STATUS mandatory DESCRIPTION "The IP destination address to be used for advertisement sent from the interface. The only permissible values are the all-systems multicast address (224.0.0.1) or the limited-broadcast address (255.255.255.255)." ::= { haAdvConfigEntry 4 } haAdvMaxInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The maximum time in seconds between successive transmissions of Agent Advertisements from this interface." ::= { haAdvConfigEntry 5 } haAdvMinInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The minimum time in seconds between successive transmissions of Agent Advertisements from this interface." ::= { haAdvConfigEntry 6 } haAdvPeriod OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The time (in seconds) to be placed in the Lifetime field of the RFC 1256-portion of the Agent Advertisements sent over this interface." ::= { haAdvConfigEntry 7 } -- HA Advertisement Group Counters haAdvertisementsSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of advertisements sent by home agent." Cong, Hamlen & Perkins expires in six months [Page 7] Internet Draft Mobile IP MIB Definition December 18, 1995 ::= { haAdvertisement 2 } haAdvsSentForSolicitation OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of advertisements sent by home agent in response to mobile node solicitations." ::= { haAdvertisement 3 } haSolicitationsReceived OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of solicitations received by the home agent." ::= { haAdvertisement 4 } -- Home Agent Registration Group -- Home agent mobility binding list haMobilityBindingTable OBJECT-TYPE SYNTAX SEQUENCE OF HaMobilityBindingEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table containing the home agent's mobility binding list. The home agent updates this table in response to registration events from mobile nodes." ::= { haRegistration 1 } haMobilityBindingEntry OBJECT-TYPE SYNTAX HaMobilityBindingEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry on the mobility binding list." INDEX { haMobilityBindingMN, haMobilityBindingCOA } ::= { haMobilityBindingTable 1 } HaMobilityBindingEntry ::= SEQUENCE { haMobilityBindingMN IpAddress, haMobilityBindingCOA IpAddress, haMobilityBindingSourceAddress IpAddress, Cong, Hamlen & Perkins expires in six months [Page 8] Internet Draft Mobile IP MIB Definition December 18, 1995 haMobilityBindingRegFlags INTEGER, haMobilityBindingRegID1 INTEGER, haMobilityBindingRegID2 INTEGER, haMobilityBindingTimeGranted INTEGER, haMobilityBindingTimeRemaining INTEGER } haMobilityBindingMN OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Mobile node's home (IP) address." ::= { haMobilityBindingEntry 1 } haMobilityBindingCOA OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Mobile node's care-of-address. One mobile node can have multiple bindings with different care-of-addresses." ::= { haMobilityBindingEntry 2 } haMobilityBindingSourceAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "IP source address of the registration request as received by the home agent. Will be either a mobile node's COA or an address of the foreign agent." ::= { haMobilityBindingEntry 3 } haMobilityBindingRegFlags OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Registration flags sent by mobile node. Flags can be distinguished by applying the appropriate testing bit. Flag Bitmask Indication S 0x80 Request to retain prior binding B 0x40 Request to recieve broadcasts D 0x20 COA is local to mobile node M 0x10 Request to use minimal enc. G 0x8 Request to use GRE." ::= { haMobilityBindingEntry 4 } Cong, Hamlen & Perkins expires in six months [Page 9] Internet Draft Mobile IP MIB Definition December 18, 1995 haMobilityBindingRegID1 OBJECT-TYPE SYNTAX INTEGER (SIZE(0..32)) ACCESS read-only STATUS mandatory DESCRIPTION "Low 32 bits of identification used in that binding by the mobile node." ::= { haMobilityBindingEntry 5 } haMobilityBindingRegID2 OBJECT-TYPE SYNTAX INTEGER (SIZE(0..32)) ACCESS read-only STATUS mandatory DESCRIPTION "High 32 bits of identification of used in that binding by the mobile node." ::= { haMobilityBindingEntry 6 } haMobilityBindingTimeGranted OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The lifetime in seconds granted to the mobile node for this registration." ::= { haMobilityBindingEntry 7 } haMobilityBindingTimeRemaining OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of seconds remaining until the registration is expired. It has the same initial value as haMobilityBindingTimeGranted, and is counted down by the home agent." ::= { haMobilityBindingEntry 8 } -- Home Agent Registration Group Counters -- Home agent registration counters per node haCounterTable OBJECT-TYPE SYNTAX SEQUENCE OF HaCounterEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table containing registration statistics for all Cong, Hamlen & Perkins expires in six months [Page 10] Internet Draft Mobile IP MIB Definition December 18, 1995 mobile nodes authorized to use this home agent." ::= { haRegistration 2 } haCounterEntry OBJECT-TYPE SYNTAX HaCounterEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Registration statistics for one mobile node." INDEX { haMNHomeAddress } ::= { haCounterTable 1 } HaCounterEntry ::= SEQUENCE { haMNHomeAddress IpAddress, haServiceRequestsAccepted Counter, haServiceRequestsDenied Counter, haOverallServiceTime INTEGER, haRecentServiceAcceptedTime TimeTicks, haRecentServiceDeniedTime TimeTicks, haRecentServiceDeniedCode INTEGER } haMNHomeAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Mobile node's home IP address." ::= { haCounterEntry 1 } haServiceRequestsAccepted OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of service requests for the mobile node accepted by the home agent (Code 0 + Code 1)." ::= { haCounterEntry 2 } haServiceRequestsDenied OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of service requests for the mobile node denied by the home agent (sum of all registrations denied with Code 128 through Code 136)." ::= { haCounterEntry 3 } Cong, Hamlen & Perkins expires in six months [Page 11] Internet Draft Mobile IP MIB Definition December 18, 1995 haOverallServiceTime OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Overall service time (in seconds) that has accumulated for the mobile node since the home agent last rebooted." ::= { haCounterEntry 4 } haRecentServiceAcceptedTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The time at which the most recent registration request was accepted by the home agent for this mobile node." ::= { haCounterEntry 5 } haRecentServiceDeniedTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The time at which the most recent registration request was denied by the home agent for this mobile node." ::= { haCounterEntry 6 } haRecentServiceDeniedCode OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Code indicating the reason why the most recent registration request for this mobile node was rejected by the home agent." ::= { haCounterEntry 7 } -- Home agent registration counters for all nodes. haRegistrationAccepted OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests accepted by home agent (Code 0)." ::= { haRegistration 3 } Cong, Hamlen & Perkins expires in six months [Page 12] Internet Draft Mobile IP MIB Definition December 18, 1995 haMultiBindingUnsupported OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests accepted by home agent -- simultaneous mobility bindings unsupported (Code 1)." ::= { haRegistration 4 } haReasonUnspecified OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- reason unspecified (Code 128)." ::= { haRegistration 5 } haAdmProhibited OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- administratively prohibited (Code 129)." ::= { haRegistration 6 } haInsufficientResource OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- insufficient resources (Code 130)." ::= { haRegistration 7 } haMNAuthenticationFailure OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- mobile node failed authentication (Code 131)." ::= { haRegistration 8 } haFAAuthenticationFailure OBJECT-TYPE SYNTAX Counter Cong, Hamlen & Perkins expires in six months [Page 13] Internet Draft Mobile IP MIB Definition December 18, 1995 ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- foreign agent failed authentication (Code 132)." ::= { haRegistration 9 } haIDMismatch OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- identification mismatch (Code 133)." ::= { haRegistration 10 } haPoorlyFormedRequest OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- poorly formed request (Code 134)." ::= { haRegistration 11 } haTooManyBindings OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- too many simultaneous mobility bindings (Code 135)." ::= { haRegistration 12 } haUnknownHA OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests denied by home agent -- unknown home agent address (Code 136)." ::= { haRegistration 13 } haGratuitiousARPsSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory Cong, Hamlen & Perkins expires in six months [Page 14] Internet Draft Mobile IP MIB Definition December 18, 1995 DESCRIPTION "Total number of gratuition ARPs sent by the home agent on behalf of mobile nodes." ::= { haRegistration 14 } haProxyARPsSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of proxy ARPs sent by the home agent on behalf of mobile nodes." ::= { haRegistration 15 } haRegRequestsReceived OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests received by home agent." ::= { haRegistration 16 } haDeRegRequestsReceived OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration requests received by the home agent with a Lifetime of zero (requests to deregister)." ::= { haRegistration 17 } haRegRepliesSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration replies sent by the home agent." ::= { haRegistration 18 } haDeRegRepliesSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of registration replies sent by the home Cong, Hamlen & Perkins expires in six months [Page 15] Internet Draft Mobile IP MIB Definition December 18, 1995 agent in response to reguests to deregister." ::= { haRegistration 19 } END 5. Acknowledgments This document was produced by the Mobile IP working group. The editors wish to thank Jim Solomon, for his encouragement, patience, and help. Thanks to Fredrick Tarberg and Fredrik Broman (KTH) for their initial efforts on MIB definitions. Thanks to Frank Kastenholz(FTP), for his comments on the initial MIB from KTH. 6. Security Considerations The Mobile IP MIB affords the network operator the ability to configure and control the Mobile IP links of a particular system, including the Mobile IP authentication protocols, and shared secret key. This represents a security risk. These risks are addressed in the following manners: (1) All variables which represent a significant security risk are placed in separate, optional, MIB Groups. As the MIB Group is the quantum of implementation within a MIB, the implementor of the MIB may elect not to implement these groups. (2) The implementor may choose to implement the variables which present a security risk so that they may not be written, i.e., the variables are READ-ONLY. This method still presents a security risk, and is not recommended, in that the variables, specifically the Mobile IP Security Association variables, may be easily read. (3) Using SNMPv2, the operator can place the variables into MIB views which are protected in that the parties which have access to those MIB views use authentication and privacy protocols, or the operator may elect to make these views not accessible to any party. In order to facilitate this placement, all security-related variables are placed in separate MIB Tables. This eases the identification of the necessary MIB View Subtree. (4) The Mobile IP Security MIB contains several objects which are very sensitive from a security point of view. Cong, Hamlen & Perkins expires in six months [Page 16] Internet Draft Mobile IP MIB Definition December 18, 1995 Thus, in order to preserve the integrity, security and privacy of the Mobile IP security features, an implementation will allow access to this MIB only via SNMPv2 and then only for parties which are privacy enhanced. Other access modes, e.g., SNMPv1 or SNMPv2 without privacy-enhancement, are very dangerous and the security of the IP Mobility Support may be compromised. The other way to access this information is by use of SNMPv1 in concert with the IP security protocols (AH and ESP). This can also be done in a secure fashion. 7.0 References [1] Rose M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", STD 16, RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990. [2] McCloghrie K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets", STD 17, RFC 1213, Performance Systems International, March 1991. [3] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987. [4] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987. [5] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", STD 16, RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. [6] Rose, M., Editor, "A Convention for Defining Traps for use with the SNMP", RFC 1215, Performance Systems International, March 1991. [7] McCloghrie, K., "Extensions to the Generic-Interface MIB", RFC 1229, Hughes LAN Systems, Inc., May 1991. [8] Solomon J., "Mobile IP Protocol Applicability Statement", Internet Draft -- work in progress, December, 1995. [9] Perkins C., "IP Mobility Support", Internet Draft -- work in progress, December, 1995. Cong, Hamlen & Perkins expires in six months [Page 17] Internet Draft Mobile IP MIB Definition December 18, 1995 [10] Perkins C., "IP Encapsulation within IP". Internet Draft -- work in progress, October 1995. [11] Perkins C., "Minimal Encapsulation within IP". Internet Draft -- work in progress, July 1995. [12] Hanks S. et. al., "Generic Routing Encapsulation (GRE)", RFC 1701, October 1994. [13] Deering, S., "ICMP Router Discovery Messages", RFC 1256, September 1991. 8. Chair's Addresses The working group can be contacted via the current chairs: Jim Solomon Tony Li Motorola, Inc. cisco systems 1301 E. Algonquin Rd. 170 W. Tasman Dr. Schaumburg, IL 60196 San Jose, CA 95134 Work: +1-708-576-2753 Work: +1-408-526-8186 E-mail: solomon@comm.mot.com E-mail: tli@cisco.com 9. Editor's Address Questions about this memo can also be directed to: David Cong Room 3149 Motorola 1301 East Algonquin Rd. Schaumburg, IL 60196 Work: +1-708-576-1357 Fax: +1-708-538-3472 E-mail: cong@comm.mot.com Mark Hamlen Room 4413 Motorola 1301 East Algonquin Rd. Schaumburg, IL 60196 Work: +1-708-576-0346 Fax: +1-708-538-6150 Cong, Hamlen & Perkins expires in six months [Page 18] Internet Draft Mobile IP MIB Definition December 18, 1995 E-mail: hamlen@comm.mot.com Charles Perkins Room J1-A25 T. J. Watson Research Center IBM Corporation 30 Saw Mill River Rd. Hawthorne, NY 10532 Work: +1-914-784-7350 Fax: +1-914-784-7007 E-mail: perk@watson.ibm.com Cong, Hamlen & Perkins expires in six months [Page 19]