datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

IEEE 802.21 Mobility Services Framework Design (MSFD)
RFC 5677

Network Working Group                                      T. Melia, Ed.
Request for Comments: 5677                                Alcatel-Lucent
Category: Standards Track                                       G. Bajko
                                                                   Nokia
                                                                  S. Das
                                             Telcordia Technologies Inc.
                                                               N. Golmie
                                                                    NIST
                                                              JC. Zuniga
                                        InterDigital Communications, LLC
                                                           December 2009

         IEEE 802.21 Mobility Services Framework Design (MSFD)

Abstract

   This document describes a mobility services framework design (MSFD)
   for the IEEE 802.21 Media Independent Handover (MIH) protocol that
   addresses identified issues associated with the transport of MIH
   messages.  The document also describes mechanisms for Mobility
   Services (MoS) discovery and transport-layer mechanisms for the
   reliable delivery of MIH messages.  This document does not provide
   mechanisms for securing the communication between a mobile node (MN)
   and the Mobility Server.  Instead, it is assumed that either lower-
   layer (e.g., link-layer) security mechanisms or overall system-
   specific proprietary security solutions are used.

Status of This Memo

   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.

IESG Note

   As described later in this specification, this protocol does not
   provide security mechanisms.  In some deployment situations lower-
   layer security services may be sufficient.  Other situations require
   proprietary mechanisms or as yet incomplete standard mechanisms, such
   as the ones currently considered by IEEE.  For these reasons, the
   specification recommends careful analysis before considering any
   deployment.

Melia, et al.               Standards Track                     [Page 1]
RFC 5677                          MSFD                     December 2009

   The IESG emphasizes the importance of these recommendations.  The
   IESG also notes that this specification deviates from the traditional
   IETF requirement that support for security in the open Internet
   environment is a mandatory part of any Standards Track protocol
   specification.  An exception has been made for this specification,
   but this should not be taken to mean that other future specifications
   are free from this requirement.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the BSD License.

Melia, et al.               Standards Track                     [Page 2]
RFC 5677                          MSFD                     December 2009

Table of Contents

   1. Introduction ....................................................4
   2. Terminology .....................................................4
      2.1. Requirements Language ......................................7
   3. Deployment Scenarios ............................................7
      3.1. Scenario S1: Home Network MoS ..............................8
      3.2. Scenario S2: Visited Network MoS ...........................8
      3.3. Scenario S3: Third-Party MoS ...............................9
      3.4. Scenario S4: Roaming MoS ...................................9
   4. Solution Overview ..............................................10
      4.1. Architecture ..............................................11
      4.2. MIHF Identifiers (FQDN, NAI) ..............................12
   5. MoS Discovery ..................................................12
      5.1. MoS Discovery When MN and MoSh Are in the Home
           Network (Scenario S1) .....................................13

[include full document text]