Mobile IP Vendor/Organization-Specific Extensions
RFC 3025

Document Type RFC - Proposed Standard (February 2001; No errata)
Obsoleted by RFC 3115
Authors Gopal Dommety  , Kent Leung 
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3025 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         G. Dommety
Request for Comments: 3025                                      K. Leung
Category: Standards Track                                  cisco Systems
                                                           February 2001

           Mobile IP Vendor/Organization-Specific Extensions

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2001).  All Rights Reserved.


   This document defines two new extensions to Mobile IP.  These
   extensions will facilitate equipment vendors and organizations to
   make specific use of these extensions as they see fit for research or
   deployment purposes.

1. Introduction

   Current specification of Mobile IP [1] does not allow for
   organizations and vendors to include organization/vendor-specific
   information in the Mobile IP messages.  With the imminent wide scale
   deployment of Mobile IP it is useful to have vendor or organization-
   Specific Extensions to support this capability.  This document
   defines two extensions that can be used for making organization
   specific extensions by vendors/organizations for their own specific

1.1. Specification Language

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in RFC 2119 [3].

   In addition, the following words are used to signify the requirements
   of the specification.

Dommety & Leung             Standards Track                     [Page 1]
RFC 3025          Mobile IP Vendor Specific Extensions     February 2001

   silently discard
            The implementation discards the datagram without further
            processing, and without indicating an error to the sender.
            The implementation SHOULD provide the capability of logging
            the error, including the contents of the discarded datagram,
            and SHOULD record the event in a statistics counter.

2. Vendor/Organization Specific Extensions

   Two Vendor/Organization Specific Extensions are described, Critical
   (CVSE) and Normal (NVSE) Vendor/Organization Specific Extensions.
   The basic differences between the Critical and Normal Extensions are
   that when the Critical extension is encountered but not recognized,
   the message containing the extension MUST be silently discarded,
   whereas when a Normal Vendor/Organization Specific Extension is
   encountered but not recognized, the extension SHOULD be ignored, but
   the rest of the Extensions and message data MUST still be processed.
   Another difference between the two is that Critical
   Vendor/Organization Extension has a length field of two octets and
   the NVSE has a length field of only one octet.

2.1. Critical Vendor/Organization Specific Extension (CVSE)

   The format of this extension is as shown below.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   |     Type      |   Reserved    |            Length             |
   |                        Vendor/Org-ID                          |
   |          Vendor-CVSE-Type     |    Vendor-CVSE-Value ...

         Figure 1: Critical Vendor/Organization Specific Extension

   Type       CVSE-TYPE-NUMBER 37

   Reserved   Reserved for future use.  MUST be set to 0 on sending,
              MUST be ignored on reception.

   Length     Length in bytes of this extension, not including the Type
              and Length bytes.

Dommety & Leung             Standards Track                     [Page 2]
RFC 3025          Mobile IP Vendor Specific Extensions     February 2001

              The high-order octet is 0 and the low-order 3 octets are
              the SMI Network Management Private Enterprise Code of the
              Vendor in network byte order, as defined in the Assigned
              Numbers RFC [2].

              Indicates the particular type of Vendor-CVSE-Extension.
              The administration of the Vendor-CVSE-Types is done by the

              Vendor/organization specific data of this Vendor-CVSE-
              Extension.  These data fields may be published in future
Show full document text