RFC 5206 on End-Host Mobility and Multihoming with the Host Identity Protocol

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

        RFC 5206

        Title:      End-Host Mobility and Multihoming with 
                    the Host Identity Protocol 
        Author:     P. Nikander, T. Henderson,
                    Ed., C. Vogt, J. Arkko
        Status:     Experimental
        Date:       April 2008
        Mailbox:    pekka.nikander@nomadiclab.com, 
                    thomas.r.henderson@boeing.com, 
                    christian.vogt@ericsson.com,
                    jari.arkko@ericsson.com
        Pages:      40
        Characters: 99430
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hip-mm-05.txt

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

This document defines mobility and multihoming extensions to the Host
Identity Protocol (HIP).  Specifically, this document defines a
general "LOCATOR" parameter for HIP messages that allows for a HIP
host to notify peers about alternate addresses at which it may be
reached.  This document also defines elements of procedure for
mobility of a HIP host -- the process by which a host dynamically
changes the primary locator that it uses to receive packets.  While
the same LOCATOR parameter can also be used to support end-host
multihoming, detailed procedures are left for further study.  This memo defines an Experimental Protocol for the Internet community.

This document is a product of the Host Identity Protocol Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

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

The RFC Editor Team
USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce