RFC 5535: Hash-Based Addresses (HBA)
In plain English — editorial summary, not part of the RFC
This memo describes a mechanism to provide a secure binding between the multiple addresses with different prefixes available to a host within a multihomed site. This mechanism employs either Cryptographically Generated Addresses (CGAs) or a new variant of the same theme that uses the same format in the addresses. The main idea in the new variant is that information about the multiple prefixes is included within the addresses themselves. This is achieved by generating the interface identifiers of the addresses of a host as hashes of the available prefixes and a random number. Then, the multiple addresses are generated by prepending the different prefixes to the generated interface identifiers. The result is a set of addresses, called Hash-Based Addresses (HBAs), that are inherently bound to each other. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5535
- Published
- June 2009
- Authors
- M. Bagnulo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 25
- 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 6316Sockets Application Program Interface (API) for Multihoming ShimCurrent
July 2011
- RFC 6317Basic Socket Interface Extensions for the Host Identity Protocol (HIP)Current
July 2011
- RFC 6418Multiple Interfaces and Provisioning Domains Problem StatementCurrent
November 2011
- RFC 6419Current Practices for Multiple-Interface HostsCurrent
November 2011
- RFC 5533Shim6: Level 3 Multihoming Shim Protocol for IPv6Current
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
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?