RFC 5304: IS-IS Cryptographic Authentication
In plain English — editorial summary, not part of the RFC
This document describes the authentication of Intermediate System to Intermediate System (IS-IS) Protocol Data Units (PDUs) using the Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5) algorithm as found in RFC 2104. IS-IS is specified in International Standards Organization (ISO) 10589, with extensions to support Internet Protocol version 4 (IPv4) described in RFC 1195. The base specification includes an authentication mechanism that allows for multiple authentication algorithms. The base specification only specifies the algorithm for cleartext passwords. This document replaces RFC 3567. This document proposes an extension to that specification that allows the use of the HMAC-MD5 authentication algorithm to be used in conjunction with the existing authentication mechanisms. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5304
- Published
- October 2008
- Authors
- T. Li; R. Atkinson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5306Restart Signaling for IS-ISObsoleted
October 2008
- RFC 6622Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Obsoleted
May 2012
- RFC 7128Resource Public Key Infrastructure (RPKI) Router Implementation ReportCurrent
February 2014
- RFC 7182Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Current
April 2014
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 2754RPS IANA IssuesObsoleted
January 2000
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?