[rfc-dist] RFC 3963 on Network Mobility (NEMO) Basic Support Protocol

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Jan 24 15:55:46 PST 2005

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

        RFC 3963

        Title:      Network Mobility (NEMO) Basic Support Protocol
        Author(s):  V. Devarapalli, R. Wakikawa, A. Petrescu,
                    P. Thubert
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    vijay.devarapalli at nokia.com, ryuji at sfc.wide.ad.jp,
                    Alexandru.Petrescu at motorola.com,
                    pthubert at cisco.com
        Pages:      33
        Characters: 75955
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-nemo-basic-support-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3963.txt

This document describes the Network Mobility (NEMO) Basic Support
protocol that enables Mobile Networks to attach to different points
in the Internet.  The protocol is an extension of Mobile IPv6 and
allows session continuity for every node in the Mobile Network as
the network moves.  It also allows every node in the Mobile Network
to be reachable while moving around.  The Mobile Router, which
connects the network to the Internet, runs the NEMO Basic Support
protocol with its Home Agent.  The protocol is designed so
that network mobility is transparent to the nodes inside the Mobile

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

This is now a Proposed Standard Protocol.

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.

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

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.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list