[rfc-dist] RFC 4886 on Network Mobility Support Goals and Requirements

[rfc-editor at rfc-editor.org ([e-mail])]

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

        
        RFC 4886

        Title:      Network Mobility Support Goals and 
                    Requirements 
        Author:     T. Ernst
        Status:     Informational
        Date:       July 2007
        Mailbox:    thierry.ernst at inria.fr
        Pages:      13
        Characters: 29083
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nemo-requirements-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4886.txt

Network mobility arises when a router connecting a network to the
Internet dynamically changes its point of attachment to the Internet
thereby causing the reachability of the said network to be changed in
relation to the fixed Internet topology.  Such a type of network is
referred to as a mobile network.  With appropriate mechanisms,
sessions established between nodes in the mobile network and the
global Internet can be maintained after the mobile router changes its
point of attachment.  This document outlines the goals expected from
network mobility support and defines the requirements that must be
met by the NEMO Basic Support solution.  This memo provides information 
for the Internet community.

This document is a product of the Network Mobility
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...