RFC 4449: Securing Mobile IPv6 Route Optimization Using a Static Shared Key
In plain English — editorial summary, not part of the RFC
A mobile node and a correspondent node may preconfigure data useful for precomputing a Binding Management Key that can subsequently be used for authorizing Binding Updates. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4449
- Published
- June 2006
- Authors
- C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4285Authentication Protocol for Mobile IPv6Current
January 2006
- RFC 4280Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control ServersCurrent
December 2005
- RFC 4640Problem Statement for bootstrapping Mobile IPv6 (MIPv6)Current
September 2006
- RFC 4068Fast Handovers for Mobile IPv6Obsoleted
July 2005
- RFC 4067Context Transfer Protocol (CXTP)Current
July 2005
- RFC 4066Candidate Access Router Discovery (CARD)Current
July 2005
- RFC 4443Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationUpdated
March 2006
- RFC 4436Detecting Network Attachment in IPv4 (DNAv4)Current
March 2006
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?