RFC 4065: Instructions for Seamoby and Experimental Mobility Protocol IANA Allocations
In plain English — editorial summary, not part of the RFC
The Seamoby Candidate Access Router Discovery (CARD) protocol and the Context Transfer Protocol (CXTP) are experimental protocols designed to accelerate IP handover between wireless access routers. These protocols require IANA allocations for ICMP type and options, Stream Control Transmission Protocol (SCTP) Payload Protocol Identifiers, port numbers, and registries for certain formatted message options. This document contains instructions to IANA about which allocations are required for the Seamoby protocols. The ICMP subtype extension format for Seamoby has been additionally designed so that it can be utilized by other experimental mobility protocols, and the SCTP port number is also available for other experimental mobility protocols. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4065
- Published
- July 2005
- Authors
- J. Kempf
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5461TCP's Reaction to Soft ErrorsCurrent
February 2009
- RFC 2426vCard MIME Directory ProfileObsoleted
September 1998
- RFC 1256ICMP Router Discovery MessagesCurrent
September 1991
- RFC 7279An Acceptable Use Policy for New ICMP Types and CodesCurrent
May 2014
- RFC 8335PROBE: A Utility for Probing InterfacesCurrent
February 2018
- RFC 4066Candidate Access Router Discovery (CARD)Current
July 2005
- RFC 4067Context Transfer Protocol (CXTP)Current
July 2005
- RFC 4077A Negative Acknowledgement Mechanism for Signaling CompressionCurrent
May 2005
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?