RFC 9511: Attribution of Internet Probes
In plain English — editorial summary, not part of the RFC
Active measurements over the public Internet can target either collaborating parties or non-collaborating ones. Sometimes these measurements, also called "probes", are viewed as unwelcome or aggressive. This document suggests some simple techniques for a source to identify its probes. This allows any party or organization to understand what an unsolicited probe packet is, what its purpose is, and, most importantly, who to contact. The technique relies on offline analysis of the probe; therefore, it does not require any change in the data or control plane. It has been designed mainly for layer 3 measurements.
Document record
- Document ID
- RFC9511
- Published
- November 2023
- Authors
- É. Vyncke; B. Donnet; J. Iurman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9515Revision to Registration Procedures for Multiple BMP RegistriesCurrent
December 2023
- RFC 9506Explicit Host-to-Network Flow Measurements TechniquesCurrent
October 2023
- RFC 9503Simple Two-Way Active Measurement Protocol (STAMP) Extensions for Segment Routing NetworksCurrent
October 2023
- RFC 9520Negative Caching of DNS Resolution FailuresCurrent
December 2023
- RFC 9499DNS TerminologyCurrent
March 2024
- RFC 9533One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation GroupCurrent
January 2024
- RFC 9534Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation GroupCurrent
January 2024
- RFC 9487Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)Current
November 2023
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?