RFC 5679: Locating IEEE 802.21 Mobility Services Using DNS
In plain English — editorial summary, not part of the RFC
This document defines application service tags that allow service location without relying on rigid domain naming conventions, and DNS procedures for discovering servers that provide IEEE 802.21-defined Mobility Services. Such Mobility Services are used to assist a Mobile Node (MN) supporting IEEE 802.21, in handover preparation (network discovery) and handover decision (network selection). The services addressed by this document are the Media Independent Handover Services defined in IEEE 802.21. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5679
- Published
- December 2009
- Authors
- G. Bajko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
- Updated by:
- RFC 8553
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
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 4339IPv6 Host Configuration of DNS Server Information ApproachesCurrent
February 2006
- RFC 5677IEEE 802.21 Mobility Services Framework Design (MSFD)Current
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
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?