RFC 5533: Shim6: Level 3 Multihoming Shim Protocol for IPv6
In plain English — editorial summary, not part of the RFC
This document defines the Shim6 protocol, a layer 3 shim for providing locator agility below the transport protocols, so that multihoming can be provided for IPv6 with failover and load-sharing properties, without assuming that a multihomed site will have a provider-independent IPv6 address prefix announced in the global IPv6 routing table. The hosts in a site that has multiple provider- allocated IPv6 address prefixes will use the Shim6 protocol specified in this document to set up state with peer hosts so that the state can later be used to failover to a different locator pair, should the original one stop working. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5533
- Published
- June 2009
- Authors
- E. Nordmark; M. Bagnulo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 124
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5534Failure Detection and Locator Pair Exploration Protocol for IPv6 MultihomingCurrent
June 2009
- RFC 5535Hash-Based Addresses (HBA)Current
June 2009
- RFC 5543BGP Traffic Engineering AttributeUpdated
May 2009
- RFC 5522Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile NetworksCurrent
October 2009
- RFC 5519Multicast Group Membership Discovery MIBCurrent
April 2009
- RFC 5549Advertising IPv4 Network Layer Reachability Information with an IPv6 Next HopObsoleted
May 2009
- RFC 5512The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation AttributeObsoleted
April 2009
- RFC 5555Mobile IPv6 Support for Dual Stack Hosts and RoutersUpdated
June 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?