RFC 5677 on IEEE 802.21 Mobility Services Framework Design (MSFD)

rfc-editor@rfc-editor.org Sun, 06 December 2009 21:02 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 101563A67E2; Sun, 6 Dec 2009 13:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.276
X-Spam-Status: No, score=-17.276 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id KDhgYYPFGyBf; Sun, 6 Dec 2009 13:02:18 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 282EC3A67B0; Sun, 6 Dec 2009 13:02:18 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 7D7CD37F8E7; Sun, 6 Dec 2009 12:56:02 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5677 on IEEE 802.21 Mobility Services Framework Design (MSFD)
From: rfc-editor@rfc-editor.org
Message-Id: <20091206205602.7D7CD37F8E7@bosco.isi.edu>
Date: Sun, 06 Dec 2009 12:56:02 -0800
Cc: mipshop@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Dec 2009 21:02:19 -0000

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

        RFC 5677

        Title:      IEEE 802.21 Mobility Services Framework 
                    Design (MSFD) 
        Author:     T. Melia, Ed.,
                    G. Bajko, S. Das,
                    N. Golmie, JC. Zuniga
        Status:     Standards Track
        Date:       December 2009
        Mailbox:    telemaco.melia@alcatel-lucent.com, 
                    subir@research.telcordia.com, nada.golmie@nist.gov, 
        Pages:      25
        Characters: 57479
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mipshop-mstp-solution-12.txt

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

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.  [STANDARDS TRACK]

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute