RFC 3358: Optional Checksums in Intermediate System to Intermediate System (ISIS)
In plain English — editorial summary, not part of the RFC
This draft describes an optional extension to IS-IS protocol, used today by several ISPs for routing within their clouds. IS-IS is an interior gateway routing protocol developed originally by OSI and used with IP extensions as IGP. IS-IS originally does not provide CSNP and PSNP checksums, relying on the underlying layers to verify the integrity of information provided. Experience with the protocol shows that this precondition does not always hold and scenarios can be imagined that impact protocol functionality. This document introduces a new optional TLV providing checksums.
Document record
- Document ID
- RFC3358
- Published
- August 2002
- Authors
- T. Przygienda
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3359Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate SystemCurrent
August 2002
- RFC 2362Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol SpecificationObsoleted
June 1998
- RFC 4601Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)Obsoleted
August 2006
- RFC 3611RTP Control Protocol Extended Reports (RTCP XR)Current
November 2003
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- RFC 2375IPv6 Multicast Address AssignmentsCurrent
July 1998
- RFC 2049Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and ExamplesCurrent
November 1996
- RFC 2047MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII TextUpdated
November 1996
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?