datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Mobility Services Transport: Problem Statement
RFC 5164

Document type: RFC - Informational (March 2008)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 5164 (Informational)
Responsible AD: Jari Arkko
Send notices to: mipshop-chairs@tools.ietf.org, draft-ietf-mipshop-mis-ps@tools.ietf.org

Network Working Group                                      T. Melia, Ed.
Request for Comments: 5164                                 Cisco Systems
Category: Informational                                       March 2008

             Mobility Services Transport: Problem Statement

Status of This Memo

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

Abstract

   There are ongoing activities in the networking community to develop
   solutions that aid in IP handover mechanisms between heterogeneous
   wired and wireless access systems including, but not limited to, IEEE
   802.21.  Intelligent access selection, taking into account link-layer
   attributes, requires the delivery of a variety of different
   information types to the terminal from different sources within the
   network and vice-versa.  The protocol requirements for this
   signalling have both transport and security issues that must be
   considered.  The signalling must not be constrained to specific link
   types, so there is at least a common component to the signalling
   problem, which is within the scope of the IETF.  This document
   presents a problem statement for this core problem.

Melia, et al.                Informational                      [Page 1]
RFC 5164              Mobility Services Transport             March 2008

Table of Contents

   1. Introduction ....................................................2
   2. Terminology .....................................................3
      2.1. Requirements Language ......................................3
   3. Definition of Mobility Services .................................4
   4. Deployment Scenarios for MoS ....................................4
      4.1. End-to-End Signalling and Transport over IP ................5
      4.2. End-to-End Signalling and Partial Transport over IP ........5
      4.3. End-to-End Network-to-Network Signalling ...................6
   5. MoS Transport Protocol Splitting ................................7
      5.1. Payload Formats and Extensibility Considerations ...........8
      5.2. Requirements on the Mobility Service Transport Layer .......8
   6. Security Considerations ........................................11
   7. Conclusions ....................................................12
   8. Acknowledgements ...............................................13
   9. References .....................................................13
      9.1. Normative References ......................................13
      9.2. Informative References ....................................13
   Contributors ......................................................14

1.  Introduction

   This document provides a problem statement for the exchange of
   information to support handover in heterogeneous link environments
   [1].  This mobility support service allows more sophisticated
   handover operations by making available information about network
   characteristics, neighboring networks and associated characteristics,
   indications that a handover should take place, and suggestions for
   suitable target networks to which to handover.  The mobility support
   services are complementary to IP mobility mechanisms [4], [5], [6],
   [7], [8], [9] to enhance the overall performance and usability
   perception.

   There are two key attributes to the handover support service problem
   for inter-technology handovers:

   1. The Information: the information elements being exchanged.  The
       messages could be of a different nature, such as information,
       commands to perform an action, or events informing of a change,
       potentially being defined following a common structure.

Melia, et al.                Informational                      [Page 2]
RFC 5164              Mobility Services Transport             March 2008

   2. The Underlying Transport: the transport mechanism to support
       exchange of the information elements mentioned above.  This
       transport mechanism includes information transport, discovery of
       peers, and the securing of this information over the network.

   The initial requirement for this protocol comes from the need to
   provide a transport for the Media Independent Handover (MIH) protocol
   being defined by IEEE 802.21 [1], which is not bound to any specific
   link layer and can operate over more that one network-layer hop.  The
   solution should be flexible to accommodate evolution in the MIH
   standard, and should also be applicable for other new mobility
   signalling protocols that have similar message patterns and discovery
   and transport requirements.

   The structure of this document is as follows.  Section 3 defines

[include full document text]