RFC 5677: IEEE 802.21 Mobility Services Framework Design (MSFD)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC5677
- Published
- December 2009
- Authors
- T. Melia; G. Bajko; S. Das; N. Golmie; JC. Zuniga
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5678Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) DiscoveryCurrent
December 2009
- RFC 5679Locating IEEE 802.21 Mobility Services Using DNSUpdated
December 2009
- RFC 5692Transmission of IP over Ethernet over IEEE 802.16 NetworksCurrent
October 2009
- RFC 5702Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSECUpdated
October 2009
- RFC 5648Multiple Care-of Addresses RegistrationUpdated
October 2009
- RFC 5713Security Threats and Security Requirements for the Access Node Control Protocol (ANCP)Current
January 2010
- RFC 5640Load-Balancing for Mesh SoftwiresUpdated
August 2009
- RFC 5637Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6Current
September 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?