RFC 7690: Close Encounters of the ICMP Type 2 Kind (Near Misses with ICMPv6 Packet Too Big (PTB))
In plain English — editorial summary, not part of the RFC
This document calls attention to the problem of delivering ICMPv6 type 2 "Packet Too Big" (PTB) messages to the intended destination (typically the server) in ECMP load-balanced or anycast network architectures. It discusses operational mitigations that can be employed to address this class of failures.
Document record
- Document ID
- RFC7690
- Published
- January 2016
- Authors
- M. Byerly; M. Hite; J. Jaeggli
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 8161Benchmarking the Neighbor Discovery ProtocolCurrent
May 2017
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 8475Using Conditional Router Advertisements for Enterprise MultihomingCurrent
October 2018
- RFC 8501Reverse DNS in IPv6 for Internet Service ProvidersCurrent
November 2018
- RFC 8683Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise NetworksCurrent
November 2019
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 9096Improving the Reaction of Customer Edge Routers to IPv6 Renumbering EventsCurrent
August 2021
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?