Internet DRAFT - draft-bharatia-mobileip-gen-mipv4-ext

draft-bharatia-mobileip-gen-mipv4-ext



                                                                         
    
   Mobile IP Working Group                           Jayshree Bharatia 
   Internet Draft                                    Kuntal Chowdhury 
   Category: Standards Track                         Nortel Networks 
   Expires on December 2003                          Avi Lior 
   <draft-bharatia-mobileip-gen-mipv4-ext-02.txt>    Bridgewater 
                                                     Systems 
                                                     Lila Madour 
                                                     Ericsson 
                                                     June 2003 


         Mobile IPv4 Extension for Configuration Options Exchange  


   Status of this Memo 
                                                
   This document is an Internet-Draft and is in full conformance with 
   all provisions of Section 10 of RFC2026. 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 
    
   Abstract 
   IP Mobility support for IPv4 [RFC3344] defines a short and skippable 
   extension header format intended to extend the Mobile IP extension 
   address space. Based on the format presented in [RFC3344], this 
   draft defines a Mobile IP extension for configuration options, which 
   SHOULD be used by any Mobile IP entity to exchange information of 
   the network entities like DNS server address, previous Foreign Agent 
   (FA) address etc. 

1  Introduction 

   This draft uses short and skippable extension header format defined 
   by [RFC3344] and offers a generalized solution to exchange 
   information like address of DNS server, address of previous FA etc. 
    
1.1  Glossary of Terms 

   FA     Foreign Agent 

                       Expires December 2003                       1

                                   
   HA     Home Agent 
   MN     Mobile Node 
   DNS    Domain Name Server 
   DHCP   Dynamic Host Configuration Protocol 
   SIP    Session Initiation Protocol 

2  Conventions used in this document  

   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.  
    
3  Mobile IP Extension for Configuration Options Exchange 

   The Mobile IP extension SHALL have the format shown in this section 
   to carry information like IPv4 address. Note that this extension MAY 
   be included as a part of Mobile IP Registration Request. If this 
   extension is requested in the Registration Request, the network 
   entity (mentioned in the Entity-Type field) SHOULD provide requested 
   information in the Registration Reply. If multiple Sub-Types are 
   needed in the same message, the configuration options header SHOULD 
   be repeated for each Sub-Type. 
    
   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      |    Length     | Entity-Type   | Sub-Type      | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |   Data         
   +-+-+-+-+-+-... 

   Type 
       IPV4-CONF-OPTIONS-EXT-TYPE=TBD. This extension value will be 
       assigned by IANA from the numbering space defined in [RFC3344] 
       for skippable extensions.

   Length 
       Represents 8-bit unsigned integer (in octets). Length of the 
       extension includes the extension type and the extension Length 
       fields. This field MUST be set to 1 plus the total length of the 
       Data and Entity-Type fields. 
    
   Sub-Type 
       This field describes the type of entity, whose information is 
       requested from the network entities (mentioned in Entity-Type 
       field) when used in a configuration options extension for 
       Registration Request. But it describes the type of entity, whose 
       information is included in Data field when used in a 
       configuration options extension for Registration Reply. 
       Currently the following types are defined: 
       PRIMARY-DNS-SERVER = TBD 
       SECONDARY-DNS-SERVER = TBD 
       PREVIOUS-FOREIGN-AGENT = TBD 
       PRIMARY-SIP-SERVER = TBD 

                       Expires December 2003                       2

                                   
       SECONDARY-SIP-SERVER = TBD 
       DHCP-SERVER = TBD 
       MULTIMEDIA-MESSAGING-SERVER = TBD 
       BROADCAST-MULTICAST-CONTROL-SERVER = TBD 
    
   Entity-Type 
       This field in a configuration options extension for Registration 
       Request includes the type of the network entity from whom the 
       information is requested. When this field is included in the 
       configuration options extension for Registration Reply, it 
       refers to the network entity that inserts the Data field. 
       Currently the following types are defined: 
       HOME-AGENT = TBD 
       FOREIGN-AGENT = TBD 
    
   Data 
       This field is inserted in a Registration Reply by the network 
       entity mentioned in the Entity-Type of the Registration Request. 
       This field represents the data of the network entity mentioned 
       in the Sub-Type. 

4  Processing of Configuration Options Extension 

   When a network entity (mentioned in the extension format of the 
   Entity-Type) adds a configuration options extension to a 
   Registration Request or Registration Reply message, this extension 
   MUST appear prior to any authentication extensions added by that 
   entity. 

5  IANA Considerations 

   This draft defines new Mobile IPv4 extension of types IPV4-CONF-
   OPTIONS-EXT-TYPE as defined in section 3 of this document. This 
   value MUST be assigned by IANA from the Mobile IP numbering space 
   for skippable extensions. Additionally, unique values MUST be 
   assigned to each member of the Sub-Type and Entity-Type fields. 

6  Security Considerations 

   There are no additional security aspects imposed by this document in 
   addition to the one defined in [RFC3344]. 

7  References 

   [RFC3344]   "IP Mobility Support for IPv4", RFC3344 

8  Acknowledgments 

   Authors like to thank Curtis Provost and Tom Hiller for their 
   valuable input to this document.  

9  Author's Address 
    
   Jayshree Bharatia 
   Nortel Networks 
   2221, Lakeside Blvd,   

                       Expires December 2003                       3

                                   
   Richardson, TX-75082  
   Phone: +1 972-684-5767 
   jayshree@nortelnetworks.com 
    
   Kuntal Chowdhury 
   Nortel Networks 
   2221, Lakeside Blvd,   
   Richardson, TX-75082  
   Phone: +1 972-685-7788 
   chowdury@nortelnetworks.com 

   Avi Lior 
   Bridgewater Systems, 
   303 Terry Fox Drive, Suite 100 
   Ottawa, Ontario, Canada, K2K 3J1 
   Phone: +1 613-591-6655 
   avi@bridgewatersystems.com 
    
   Lila Madour 
   Ericsson Canada 
   8400 Decarie, TMR 
   Quebec, Canada 
   Phone: +1 514-345-7900 
   Lila.Madour@ericsson.ca 


                       Expires December 2003                       4