A new Request for Comments is now available in online RFC libraries.


        RFC 2103:

        Title:      Mobility Support for Nimrod :  Challenges and
                    Solution Approaches
        Author:     R. Ramanathan
        Date:       February 1997
        Mailbox:    ramanath@bbn.com
        Pages:      17
        Characters: 41352
        Updates/Obsoletes: None

        URL:        ftp://ds.internic.net/rfc/rfc2103.txt


This document discusses the issue of mobility in Nimrod.  While a
mobility solution is not part of the Nimrod architecture, Nimrod does
require that the solution have certain characteristics.  This document
identifies the requirements that Nimrod has of any solution for
mobility support.  It also classifies and compares existing approaches
for supporting mobility within an internetwork and discuss their
advantages and disadvantages.  Finally, as an example, it outlines the
mechanisms to support mobility in Nimrod using the scheme currently
being developed within the IETF - namely, the Mobile-IP protocol. This
document is the product of the New Internet Routing and Addressing
Architecture Working Group of the IETF.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute