RFC 6791: Stateless Source Address Mapping for ICMPv6 Packets
In plain English — editorial summary, not part of the RFC
A stateless IPv4/IPv6 translator may receive ICMPv6 packets containing non-IPv4-translatable addresses as the source. These packets should be passed across the translator as ICMP packets directed to the IPv4 destination. This document presents recommendations for source address translation in ICMPv6 headers to handle such cases. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6791
- Published
- November 2012
- Authors
- X. Li; C. Bao; D. Wing; R. Vaithianathan; G. Huston
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 6145
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
- RFC 4890Recommendations for Filtering ICMPv6 Messages in FirewallsCurrent
May 2007
- RFC 7279An Acceptable Use Policy for New ICMP Types and CodesCurrent
May 2014
- RFC 5508NAT Behavioral Requirements for ICMPUpdated
April 2009
- RFC 3609Tracing Requirements for Generic TunnelsCurrent
October 2003
- RFC 2463Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationObsoleted
December 1998
- RFC 1574Essential Tools for the OSI InternetCurrent
February 1994
- RFC 6782Wireline Incremental IPv6Current
November 2012
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?