RFC 6273: The Secure Neighbor Discovery (SEND) Hash Threat Analysis
In plain English — editorial summary, not part of the RFC
This document analyzes the use of hashes in Secure Neighbor Discovery (SEND), the possible threats to these hashes and the impact of recent attacks on hash functions used by SEND. The SEND specification currently uses the SHA-1 hash algorithm and PKIX certificates and does not provide support for hash algorithm agility. This document provides an analysis of possible threats to the hash algorithms used in SEND. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6273
- Published
- June 2011
- Authors
- A. Kukec; S. Krishnan; S. Jiang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6276DHCPv6 Prefix Delegation for Network Mobility (NEMO)Current
July 2011
- RFC 6269Issues with IP Address SharingCurrent
June 2011
- RFC 6279Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem StatementCurrent
June 2011
- RFC 6282Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based NetworksUpdated
September 2011
- RFC 6261Encrypted Signaling Transport Modes for the Host Identity ProtocolCurrent
May 2011
- RFC 6253Host Identity Protocol CertificatesObsoleted
May 2011
- RFC 6245Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4Current
May 2011
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?