RFC 8653: On-Demand Mobility Management
In plain English — editorial summary, not part of the RFC
Applications differ with respect to whether they need session continuity and/or IP address reachability. The network providing the same type of service to any mobile host and any application running on the host yields inefficiencies, as described in RFC 7333. This document defines a new concept of enabling applications to influence the network's mobility services (session continuity and/or IP address reachability) on a per-socket basis, and suggests extensions to the networking stack's API to accommodate this concept.
Document record
- Document ID
- RFC8653
- Published
- October 2019
- Authors
- A. Yegin; D. Moses; S. Jeon
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8658RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)Current
November 2019
- RFC 8638IPv4 Multicast over an IPv6 Multicast in Softwire Mesh NetworksCurrent
September 2019
- RFC 8633Network Time Protocol Best Current PracticesCurrent
July 2019
- RFC 8675A YANG Data Model for Tunnel Interface TypesCurrent
November 2019
- RFC 8676YANG Modules for IPv4-in-IPv6 Address plus Port (A+P) SoftwiresCurrent
November 2019
- RFC 8691Basic Support for IPv6 Networks Operating Outside the Context of a Basic Service Set over IEEE Std 802.11Current
December 2019
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 8575YANG Data Model for the Precision Time Protocol (PTP)Current
May 2019
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?